After I applied 20070618 updates then I cannot start any gnome session for a non-root user. For root I am getting a desktop as usual. On any non-root account of my test box it starts, I am getting a blue backgroud and that is it. Nothing happens after few minutes wait. A quick look at processes does not reveal anything obvious although I could possibly missed something.
Am I the only one with this problem? Any ideas what may be falling apart. '.xsession-errors' files are filling up with warnings like that:
***MEMORY-WARNING***: gnome-session[3348]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...
***MEMORY-WARNING***: gconf-sanity-check-2[3424]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...
but this breakage is nothing new in the current rawhide.
Maybe the above is really the clue as there is nothing after that for non-root accounts. For root this is followed by
SESSION_MANAGER=local/dyna0.xxx.yyy:/tmp/.ICE-unix/3534
and a big pile of other "***MEMORY-WARNING***" messages.
Yes, I checked, permissions on /tmp, .ICE-unix and that socket are like they should be. Maybe this gconf-sanity-check-2 is really stuck. Only /usr/libexec/gconf-sanity-check-2 did not change recently.
Michal
On Mon, Jun 18, 2007 at 10:00:12PM -0600, Michal Jaegermann wrote:
After I applied 20070618 updates then I cannot start any gnome session for a non-root user.
After some experiments it turned out that something stopped accepting my existing ~/.gconf directories. Even after 'gconftool-2 --dump >saved; rm -rf ~/.gconf; gconftool-2 --load saved', which swelled a .gconf directory from 384K to 9.4M, that something still does not like results and hangs starting sesssion.
If I will just 'rm -rf ~/.gconf' but this, of course, is loosing all customizations. It is a lot of work to restore some sanity here and many of those keys are not even releated to a desktop.
Michal
On Tue, 2007-06-19 at 12:43 -0600, Michal Jaegermann wrote:
On Mon, Jun 18, 2007 at 10:00:12PM -0600, Michal Jaegermann wrote:
After I applied 20070618 updates then I cannot start any gnome session for a non-root user.
After some experiments it turned out that something stopped accepting my existing ~/.gconf directories. Even after 'gconftool-2 --dump >saved; rm -rf ~/.gconf; gconftool-2 --load saved', which swelled a .gconf directory from 384K to 9.4M, that something still does not like results and hangs starting sesssion.
If I will just 'rm -rf ~/.gconf' but this, of course, is loosing all customizations. It is a lot of work to restore some sanity here and many of those keys are not even releated to a desktop.
Fixed in 2.19.4-2.fc8, provided you are complaining about rawhide... you didn't tell
On Tue, Jun 19, 2007 at 02:39:44PM -0400, Matthias Clasen wrote:
On Tue, 2007-06-19 at 12:43 -0600, Michal Jaegermann wrote:
If I will just 'rm -rf ~/.gconf' but this, of course, is loosing all customizations. It is a lot of work to restore some sanity here and many of those keys are not even releated to a desktop.
Fixed in 2.19.4-2.fc8, provided you are complaining about rawhide... you didn't tell
Thanks. I will check that out. Of course I am talking about rawhide. What else could be "after 20070618 changes"? Besides AFAIK this list is about rawhide even if some other posts sneek from time to time.
Michal
On Tue, Jun 19, 2007 at 02:39:44PM -0400, Matthias Clasen wrote:
On Tue, 2007-06-19 at 12:43 -0600, Michal Jaegermann wrote:
On Mon, Jun 18, 2007 at 10:00:12PM -0600, Michal Jaegermann wrote:
After I applied 20070618 updates then I cannot start any gnome session for a non-root user.
After some experiments it turned out that something stopped accepting my existing ~/.gconf directories.
Fixed in 2.19.4-2.fc8, provided you are complaining about rawhide... you didn't tell
I am guessing that this mysterious "2.19.4-2.fc8" will really mean currently available gnome-session-2.19.4-2.fc8. With that my old ~/.gconf directories seems to be acceptable again. Thanks.
OTOH there is a new surprise. On every seesion an alert shows up 'Failure to execute child process "xscreensaver" (No such file or directory)'. A typo somewhere? /usr/bin/xscreensaver definitely does exist and it will even run when started from a terminal window or that configuration thingy in "Preferences". I cannot find anything more about this failure in any possible logs.
Michal
On 6/20/07, Michal Jaegermann michal@harddata.com wrote:
On Tue, Jun 19, 2007 at 02:39:44PM -0400, Matthias Clasen wrote:
On Tue, 2007-06-19 at 12:43 -0600, Michal Jaegermann wrote:
On Mon, Jun 18, 2007 at 10:00:12PM -0600, Michal Jaegermann wrote:
After I applied 20070618 updates then I cannot start any gnome session for a non-root user.
After some experiments it turned out that something stopped accepting my existing ~/.gconf directories.
Fixed in 2.19.4-2.fc8, provided you are complaining about rawhide... you didn't tell
I am guessing that this mysterious "2.19.4-2.fc8" will really mean currently available gnome-session-2.19.4-2.fc8. With that my old ~/.gconf directories seems to be acceptable again. Thanks.
OTOH there is a new surprise. On every seesion an alert shows up 'Failure to execute child process "xscreensaver" (No such file or directory)'. A typo somewhere? /usr/bin/xscreensaver definitely does exist and it will even run when started from a terminal window or that configuration thingy in "Preferences". I cannot find anything more about this failure in any possible logs.
Reverting control-center to control-center-2.19.4-1.fc8 seems to fix this (and a few other problems) for me.
tom
On Wed, Jun 20, 2007 at 06:09:43PM -0700, Tom London wrote:
On 6/20/07, Michal Jaegermann michal@harddata.com wrote:
OTOH there is a new surprise. On every seesion an alert shows up 'Failure to execute child process "xscreensaver" (No such file or directory)'.
Reverting control-center to control-center-2.19.4-1.fc8 seems to fix this (and a few other problems) for me.
OTOH going from control-center-2.19.4-1.fc8 to the current control-center-2.19.4-3.fc8 apparently fixed this bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244920 although I am not entirely sure where was really the trouble.
Michal
On Mon, Jun 18, 2007 at 10:00:12PM -0600, Michal Jaegermann wrote:
Am I the only one with this problem? Any ideas what may be falling apart. '.xsession-errors' files are filling up with warnings like that:
Me too. Things have been Kinda Br0ke for a couple of weeks, in fact.
***MEMORY-WARNING***: gnome-session[3348]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...
[...]
but this breakage is nothing new in the current rawhide.
The only mailing list reference I find is
http://www.redhat.com/archives/rhl-devel-list/2007-June/msg00489.html
but we're now at 2.11.4 and things seem worse rather than better.
Then, there's half-a-dozen bugs in bugzilla, the most generic of which appears to be: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241925.
Anyone know more of what's going on?
On Wed, 20 Jun 2007 22:20:27 -0400, Matthew Miller wrote:
On Mon, Jun 18, 2007 at 10:00:12PM -0600, Michal Jaegermann wrote:
Am I the only one with this problem? Any ideas what may be falling apart. '.xsession-errors' files are filling up with warnings like that:
Me too. Things have been Kinda Br0ke for a couple of weeks, in fact.
***MEMORY-WARNING***: gnome-session[3348]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...
[...]
but this breakage is nothing new in the current rawhide.
The only mailing list reference I find is
http://www.redhat.com/archives/rhl-devel-list/2007-June/msg00489.html
but we're now at 2.11.4 and things seem worse rather than better.
Then, there's half-a-dozen bugs in bugzilla, the most generic of which appears to be: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241925.
Anyone know more of what's going on?
Here's some background: http://mail.gnome.org/archives/gtk-devel-list/2007-January/msg00005.html
On Thu, Jun 21, 2007 at 09:07:12AM +0200, Michael Schwendt wrote:
Anyone know more of what's going on?
Here's some background: http://mail.gnome.org/archives/gtk-devel-list/2007-January/msg00005.html
Interesting. I noticed a huge increase in instability at about the same time I started getting the warnings, and assumed they were related.
On Thu, Jun 21, 2007 at 09:07:12AM +0200, Michael Schwendt wrote:
On Wed, 20 Jun 2007 22:20:27 -0400, Matthew Miller wrote:
Me too. Things have been Kinda Br0ke for a couple of weeks, in fact.
***MEMORY-WARNING***: gnome-session[3348]: GSlice: g_thread_init()
....
Here's some background: http://mail.gnome.org/archives/gtk-devel-list/2007-January/msg00005.html
They sound in this thread like that was some "minor improvement" and a development helper. To me it looks like that mostly anything you touch and which is using gtk will spill such scary messages. I thought that maybe some common library is doing something which it should not but apparently this may be more problematic.
Spamming ~/.xsession-errors is at least annoying. It is hard to know where the real problems are in all this noise.
Michal
-
Matthew Miller -
Matthias Clasen -
Michael Schwendt -
Michal Jaegermann -
Tom London