Bugzilla – Bug 144722
crash in Workspace Switcher applet at startup
Last modified: 2006-05-12 20:15:43 UTC
When ever I start GNOME on an older system (400MHz), GNOME session menager reports several crashed applications. When I select to retry starting these applications, everything seems to be fine. Therefore I suspect the bug is in session manager: When applications do not appear quickly enough, session manager reports a crashed application (when in fact it did not start yet). Maybe the problem is also that too many applications are started at the same time, some of those being "fat & slow" (liek acroread, gnome-terminal, evolution).
Can you attach .xsession-errors when the failures occur?
Created attachment 66494 [details] ~/.xsession-errors Here's the file you wanted. However I'm afraid it doesn't contain what you hoped to see.
Yah, not much there. We put out a libbonobo update in the last few days, could you download and install it?
I did install all the recent updates (libbonobo-2.10.1-3.2). However when rebooting this morning, the same effect appeared. It seems GNOME is logging those "application crashes" nowhere!
Which applications are failing?
The German titles are: "Desktop anzeigen" (display desktop) "Fensterliste" (window list) "Arbeitsflächenumschalter" (desktop switcher) Furthermore it seems the problem does not occur when logging out and back in (maybe the disk cache is fast enough then), but only after a reboot. It may be accidentially that, when it worked, the lower and upper panels were up already when the applets started, but the panels weren't when the warnings about crashed applets popped up.
ok, so this is the wnck bassed applets.
Do you run the workspace switcher applet? (The one that lets you switch between multiple desktops.) If you remove it from the panel, does the crash go away? If so, is there anything odd about (a) the settings you have in the Preferences of that applet, (b) your windowmanager preferences, (c) your monitor setup (multiple monitors, etc)? (This may be the same as bug 152735.)
Yes, I run the "workspace switcher applet" (isn't it default?). Before I remove it, I'll have to find out how to add it again (it's not in the applet menu). Despite of that, I still think this is a timing issue, because during start I see the harddisk LED being "always on", indicating a busy system. I only have one monitor. In which format you'd like to see my settings?
BTW: "You are not authorized to access bug #152735."
You ought to be able to re-add it by doing right click -> Add to Panel, and choosing the right applet. ("Arbeitsflächenumschalter" I guess.) Yes, I'm sure this is a timing issue/race condition of some sort, I'm just trying to narrow down *where* the timing issue is occurring. For the settings, I guess just do "gconftool-2 -R /apps/panel > /tmp/settings" and then attach that file. (This should show all of the panel settings, as well as what applets and launchers you have on your panel and what settings they have.)
Created attachment 71291 [details] Output of "gconftool-2 -R /apps/panel"
Actually, it seems that removing the "Arbeitsflächenumschalter" fixed the problems.
*** Bug 152735 has been marked as a duplicate of this bug. ***
What version of libwnck do you have? Have you installed updated packages from PLUS, and if so, did the bug only appear when you did that? (I think I've found the bug, in one of our fairly recent patches.)
Please try http://primates.ximian.com/~danw/libwnck-2.12.2-14.i586.rpm and let me know if that fixes the problem for you. (You ought to be able to add back the Workspace Switcher and not get a crash.)
(In reply to comment #15) > What version of libwnck do you have? Have you installed updated packages from > PLUS, and if so, did the bug only appear when you did that? libwnck-2.12.0-3 I don't know what "PLUS" is, but I did a YOU this week.
With the newer library startup went much smoother. However for statistical significance, I'd had to boot more than once to make sure ;-)
ok, i'll leave this NEEDINFO for a few days. let me know if the crash comes back.
On Friday I discovered an update for libnck that was flagges "optional" and not "recommened". Thus YOU did not install that automatically. I chose to install that (libwnck-2.12.0-3.2). That version does not fix the problem. So I guess the version from comment #16 is actually needed.
This is fixed in CODE10 already, and the reporter has a fixed package. I'm holding off actually getting it into 10.0 because I want to do it together with bug 78329, which is still NEEDINFO. So lowering the priority to get it off the CODE10 blocker list.
bug 78329 still hasn't gotten fixed and now SUSE 10.1 is out so there's not much point trying to get this into 10.0.