Sadly I cannot give any hard facts. I bump my gnome today. Once I log in the gnome-panel segfaults. After unemerging the gnome-extra/quick-lounge-applet everything is fine again. What information would help?
Then try to get a proper backtrace: FEATURES="$FEATURES debug splitdebug" CFLAGS="-O2 -pipe -ggdb" CXXFLAGS="-O2 -pipe -ggdb" emerge -1 glib gtk+ gconf gnome-panel bug-buddy Then, logout and login and try to reproduce the crash, bug-buddy should then appear and guide you.
Also verify how does it work when gnome-panel is compiled with USE="bonobo"
(In reply to comment #1) > Then, logout and login and try to reproduce the crash, bug-buddy should then > appear and guide you. Never used bugbuddy.So I didn't know how to get bt from only the gnome-panel. Will test that.
(In reply to comment #2) > Also verify how does it work when gnome-panel is compiled with USE="bonobo" > It is already compiled with bonobo. Does it makes sense to remove it?
No, if I don't misremember that old applet wasn't ported yet
Created attachment 256686 [details] backtrace.log I am able to reproduce
But I will probably need more time to recompile more packages with debugging symbols (like glibc, bonobo stuff), and I won't have time for that for now :-/
Created attachment 256713 [details] Bug-buddy bt Done with a clean profile
(In reply to comment #8) > Created an attachment (id=256713) [details] > Bug-buddy bt > > Done with a clean profile > I think you should open an upstream bug report with it (bug-buddy should offer you to do it itself on the next crash), then, post the link here to let us track the problem. Thanks
gnome panel or quick-lounge-applet upstream? I don't like to crash everything again. :)
(In reply to comment #10) > gnome panel or quick-lounge-applet upstream? > > I don't like to crash everything again. :) > I would open it against gnome-panel, since looks like a bonobo related crash :-/ (also, bug-buddy will probably open the bug against gnome-panel automatically... and I am sure gnome-panel upstream is much more active than quick-lounge one)
*** Bug 348139 has been marked as a duplicate of this bug. ***
Maybe we should hardmask quick-lounge :-/
(In reply to comment #13) > Maybe we should hardmask quick-lounge :-/ > The upstream report says that it is a gnome-panel thing, or am I wrong?
(In reply to comment #14) > (In reply to comment #13) > > Maybe we should hardmask quick-lounge :-/ > > > > The upstream report says that it is a gnome-panel thing, or am I wrong? > It's not clear, for now looks like gnome-panel is crashing but it's not clear if it's due a bug in gnome-panel or this applet doing something "wrong". The problem is that quick-loungue applet looks to be unmaintained by upstream and I have been unable to find any fix for this in other distributions (also looks it has been already dropped on a lot of them).
What is the alternative to it?
(In reply to comment #16) > What is the alternative to it? > Looks like it has no alternative, but I failed to find any fix for this, upstream looks dead and major distributions have already dropped it :-|
# Pacho Ramos <pacho@gentoo.org> (26 Jan 2011) # It makes gnome-panel-2.32 to crash, since upstream looks dead # any help on fixing bug 348123 is highly appreciated. gnome-extra/quick-lounge-applet
Looks like quick-lounge-applet upstream is dead -> I vote for last ritting it
(In reply to comment #19) > Looks like quick-lounge-applet upstream is dead -> I vote for last ritting it > Sadly that seems to be true. Go ahead.
Was dropped