Upon starting a gnome session, gnome-panel starts and crashes (and gets restarted again and again). Reproducible: Always Steps to Reproduce: 1. log into a gnome session 2. observe gnome-panel crashing Actual Results: gnome-panel won't work correctly Expected Results: gnome-panel should not crash rolling back to 2.30.2 fixed the problem
Created attachment 256729 [details] xsessions-errors
Please try to provide a backtrace of the problem [1] [1] http://www.gentoo.org/proj/en/qa/backtraces.xml
Also try on a new created user account
This problem is still present on 2.32.1. I noticed that no problem happens when I only use one screen ! but it happens every time when the second screen works
Creating a new user did not help : the problem is present on a just-created account.
Created attachment 259869 [details] gdb gnome-panel --sync I tried to run gnome-panel with gdb using --sync but it can't seem to find gdk_x_error. I'm willing to help further if you help me help you :)
Created attachment 259905 [details] crash callstack Recompiling x11-libs/gdk-pixbuf with debug flag gave me a callstack. I attached it here : callstack.txt
Added crash callstack
What is "gnome-panel-renamed"? I would also recompile x11-libs/libX11 with debugging symbols and follow Code Listing 1.4 from http://www.gentoo.org/proj/en/qa/backtraces.xml (I mean, "set logging file" stuff and attaching generated backtrace.log) Thanks
gnome-panel-renamed is just gnome-panel, I renamed it to prevent it from being launched on the beginning of the session. I'll try and provide more detailed log.
Created attachment 259921 [details] crash callstack with mode symbols Okay this is a richer call stack. Thanks for your advises :)
Looks something related with X :-/, but maybe you could get a richer backtrace installing bug-buddy and letting him catch the crash Also, maybe this is related (or a dupe) of bug 348240
same problem for me, gnome-panel crashes when session is launched on two separate X screens. seems like an upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=632369
Thanks for finding the links :-) https://bugzilla.gnome.org/show_bug.cgi?id=632369 https://bugzilla.redhat.com/show_bug.cgi?id=650638 Could reporter confirm it's the same issue? Are you using nvidia-drivers?
some problem for me and Im using nvidia-drivers and 2 screens
Upstream bug report talks about running two X instances, so I guess the problem is slightly different. Could you file a new bug report upstream with your backtrace and paste the URL here ?
Maybe affected people could try to install development versions that leaded to 2.32 releases: ftp://ftp.gnome.org/pub/gnome/sources/gnome-panel/2.31/ That way maybe we could try to locate when and where was the problem introduced since looks like 2.30 wasn't affected by this, no?
Other option you should probably try BEFORE trying with 2.31 releases: 1. Create a new user account. 2. Log in into it with only one screen to not hit the problem. 3. Remove ALL applets (remember notification area also) 4. Try to reproduce the problem.
Please try to bisect this to find commit causing the problems, for that, follow these instructions: ln -s /usr/include/dbus-1.0/dbus/ /usr/include/dbus # To prevent compilation problems with older gnome-panel versions. Drop the link when all ends. emerge -av1 gtk-doc gnome-doc-utils # needed for autogen.sh cd ~ git clone git://git.gnome.org/gnome-panel gnome-panel.git cd gnome-panel.git git bisect start git bisect good GNOME_PANEL_2_30_0 git bisect bad master cd m4/ wget ftp://ftp.free.fr/mirrors/ftp.gentoo.org/distfiles/introspection.m4.bz2 bunzip2 introspection.m4.bz2 cd .. ./autogen.sh --disable-introspection && make ./gnome-panel/gnome-panel --replace Now, if it crashes: git bisect bad Compile again and repeat *ALL* steps after ./autogen.sh... If it works fine: git bisect good Compile again and repeat *ALL* steps after ./autogen.sh... Stop following previous procedure when a message similar as follows is shown (this is only an example): e2e95ce27e565578c04686239752d7e2a0a0702b is the first bad commit commit e2e95ce27e565578c04686239752d7e2a0a0702b Author: Vincent Untz <vuntz@gnome.org> Date: Wed Aug 18 17:33:02 2010 +0200 [release] 2.31.90 :100644 100644 59fc3ff95d81ec17b727e287e523414b6ecb061f 61b02563a12cb4ddbd421e5cf677fffc4aa7569a M NEWS :100644 100644 f6b785625faa4afc8fe49ec50edf444e271bc3bf 9859a4260bd847cc3e19f7b78508725c32421f9c M README :100644 100644 38b2db2ef866545bec39f56b4e72526a83d3fb40 550c1ac0b867196f2df92c8a4e47993d69f635d1 M configure.in Thanks
Please also take a look to the following patches that could solve this issue: https://bugzilla.gnome.org/show_bug.cgi?id=632369#c12 https://bugzilla.gnome.org/show_bug.cgi?id=632369#c15
(In reply to comment #20) > Please also take a look to the following patches that could solve this issue: > https://bugzilla.gnome.org/show_bug.cgi?id=632369#c12 > https://bugzilla.gnome.org/show_bug.cgi?id=632369#c15 Dear users, please give feedback on this issue, so we can resolve loads of other problems, including security issues.
> Dear users, please give feedback on this issue, so we can resolve loads of > other problems, including security issues. > these patches prevent gnome-panel from crashing, though there is another problem context menu of applets on second X screen appears on the first screen. (such behavior described also by several users at https://bugzilla.gnome.org/show_bug.cgi?id=632369)
Yesterday (or day before yesterday) I unmask gnome-panel and some related packages And after upgrade problem not appear anymore
I think that it's because latest revision includes Vuntz patches to improve the situation
Anyone still having problems with gnome-panel ?
We are already applying upstream patches for improving the situation, if better patches appear in upstream report in the future, we will consider their inclusion
*** Bug 359845 has been marked as a duplicate of this bug. ***