gtk+-2.8.14 version bump

[Jan Eidtmann]

Am Thursday, 9. March 2006 09:44 schrieb Stefan Wold:
> The thing is that the problem doesn't start occuring right away, so a
> quick start and stop of a program won't reveal the crashes. It seems you
> have to be running a few hours before the problem occur. After that the
> apps just refuse to start. At that point restarting the computer or
> downgrading glib and rebuilding pango seem to be the only solution. I'm
> not saying glib-2.10.x is the full cause of this, it could be glib-2.10.x
> in conjuction with gtk and pango.
>
> Downgrading glib did however solve my crashes immediately.

i solved it by just
export G_SLICE=always-malloc

no more crashes for me (and ive had apps crashing too after the glib update)

>
> On Thu, 9 Mar 2006, Terry Chan wrote:
> > And the reason I posted to lunar instead of lunar-dev is that I also
> > STRONGLY disagree with you that this is only a dev concern.
> >
> > glib-2.10.0 works for Florin, and glib-2.10.0 and glib-2.10.1 works for
> > me. I haven't seen ANY proof that glib-2.10.x breaks ANYTHING useful in
> > moonbase other than ONE module mentioned in #lunar and I don't even count
> > gcalculator as being important enough to hold back glib and now gtk+-2.
> >
> > Show me the proof that glib-2.10.x is breaking anything for anyone, other
> > than idle chatter in #lunar.
> >
> > Terry Chan
> > --------------------------------------------------------------
> >
> > On Thu, Mar 09, 2006 at 08:20:26AM +0100, Moritz Heiber wrote:
> >> I object to the glib-2 bump. Infact, I even veto it. It has been made
> >> clear that many users including Ratler and me were recieving a lot of
> >> unusual segfaults in all sorts of places due to the new glib-2 release.
> >>
> >> Thus I STRONGLY suggest you refrain from bumping glib-2 until we find
> >> somebody else willing to test the new release giving his green
> >> lights.
> >>
> >> Because, if something's working _for you_ doesn't mean that it is
> >> working for all of us. That is exactly what's been driving me mad about
> >> Jan throughout the past .. and I know you can do better.
> >>
> >> Regards,
> >>
> >> Moritz
> >>
> >> PS: This is a developer concern. I wouldn't want to involve the users in
> >> this.
> >>
> >> On Wed, 8 Mar 2006 22:46:11 -0600
> >>
> >> Terry Chan <tpchan at comcast.net> wrote:
> >>>> From the ChangeLog for gtk+-2.8.14:
> >>>
> >>> Wed Mar  8 14:22:59 2006  Tim Janik  <timj at imendio.com>
> >>>
> >>>         * NEWS: announce change and glib-2.10.1 requirement.
> >>>
> >>>         * gtk/gtkobject.c: fixed up messing with non-GtkObject
> >>> floating flags. this requires glib-2.10.1.
> >>>
> >>> I've bumped gtk+-2 on my lunar box and recompiled many gtk+-2 apps
> >>> with no problems.  I'm already at glib-2.10.1.
> >>>
> >>> glib-2.10.1 works just fine with all of xfce4-profile, including
> >>> xfce4-panel.
> >>>
> >>> Unless I hear otherwise I WILL be bumping gtk+-2 to 2.8.14 and at the
> >>> same time I'll also bump glib-2.10.1.
> >>>
> >>> I really don't care that galculator segfaults with the new glib-2.
> >>> That's a problem that the galculator devs MUST fix, not the lunar
> >>> devs.
> >>>
> >>> Terry Chan
> >
> > _______________________________________________
> > Lunar-dev mailing list
> > Lunar-dev at lunar-linux.org
> > http://foo-projects.org/mailman/listinfo/lunar-dev
>
> _______________________________________________
> Lunar-dev mailing list
> Lunar-dev at lunar-linux.org
> http://foo-projects.org/mailman/listinfo/lunar-dev