Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Jan 2009 21:56:04 +0100
From:      "Michal Varga" <varga.michal@gmail.com>
To:        "Doug Barton" <dougb@freebsd.org>
Cc:        ports@freebsd.org
Subject:   Re: gnome-session 2.24 (upstream) mess
Message-ID:  <3f1fd1ea0901101256y126c7c69rea04e3222ffa8363@mail.gmail.com>
In-Reply-To: <4968FE90.6040807@FreeBSD.org>
References:  <3f1fd1ea0901101039j69b09b18s44650cbe3bbca45b@mail.gmail.com> <4968FE90.6040807@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 10, 2009 at 9:01 PM, Doug Barton <dougb@freebsd.org> wrote:
> Michal Varga wrote:
>> Hello guys,
>> I noticed that Gnome 2.24 was commited today along with gnome-session
>> 2.24, so I need to ask - how did FreeBSD Gnome team decide to deal
>> with the recent session management ...
>
> FYI we don't use that kind of language on our lists.
>
> In any case it seems something like this should be in the pkg-message
> so that users are aware.
>
> Doug
>
You're right, I apologize for the somewhat improper language, It's
been just stuck in my head since I've been debugging this behaviour
for a friend and came across the whole issue, then immediately started
tearing my hair out (obviously, I'm a heavy session user too).

The whole situation made quite a number of people angry, and not just
because of missing "my windows won't pop back when i relog". With
this, uhm, politely said, regression (at least on Ubuntu where I've
been pointed to to check it), fully gnome-aware applications now
simply crash when you log out of Gnome (take with a grain of salt - I
didn't check if they are actually sig-terminated, or if they shut
themselves semi-correctly when X server terminates, or anything
deeper). But the outcome is that the next time you log back and
restart your applications manually, you get a nice show of "It seems
that Galeon crashed last time, It seems that Evolution crashed last
time, poink, poink, poink..". Or if you have an application with
unsaved changes or crunching some data, it is not able to prevent
logout and it's closed (with a hammer) too. The whole situation makes
one want to cry, some online discussions about it are a pretty nice
evidence of that. Still you are right, I'll watch my language next
time and prevent any similar slips.

(And, Jeremy - I'm sorry I didn't take part in testing this particular
release from MarcusCom, I've been doing it for years and somewhat grew
too lazy over time.. At least you can be sure you will definitely have
one tester back for 2.26 :)

m.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3f1fd1ea0901101256y126c7c69rea04e3222ffa8363>