gnome-panel crashes when clicking launcher on second screen

StacktraceTop:?? () from /usr/lib/libgdk-x11-2.0.so.0
_XError (dpy=0xa27410, rep=0x10cb160)
process_responses (dpy=0xa27410,
_XReply (dpy=0xa27410, rep=0x7fff8df1f090, extra=0,
XGetWindowProperty (dpy=0xa27410, w=14681313,

Thank you for taking the time to report this bug and helping to make Ubuntu better. I reported this issue upstream, you can track the status and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=551879

I am also having look-a-like problem not with the gnome-panel but with the Create Launcher window. I have submitted a question here with details: https://answers.launchpad.net/ubuntu/+question/52164

Take a look. It seems the behaviors are similar.

I am getting the same behaviour on both my laptops running dual X screens-
laptop 1:
Ubuntu 8.10/ Dell Vostro/ NVidia 8600GT
laptop 2:
Ubuntu 8.10/ Dell XPS/ NVidia 8700GT
launchers on the desktop work fine.

In addition sometimes when i launch an application on the second screen it shows on the first screen - am not usre if this is related.

I'd like to confirm this bug still exists on Jaunty at the time of writing.

I'm using a dual X setup with 2 screens. The second screen shows just like the primary screen, buttons and all are there. However, when clicking any of the launchers on top (firefox, evolution, help) the gnome-panel freezes. If i have a terminal open on either of the screens i can kill and restart gnome-panel (it auto restarts after killing).

Attempting to create a new launcher also results in a crash. Using the menu to start an application works as expected most of the time. Sometimes however it will start on the primary screen while using the menu on the secondary screen. Expected behaviour would be that the app would start on the secondary screen. Nautilus will always start on the primary screen, even when started from the secondary screen.

Please ask for any information you may need.

Regards, Serenity

I have the same bug on Ubuntu 9.04.
I use dual head with two nvidia cards.
The panel won't even start. It starts and crashes, then restarts and so on.
I have to kill it with pkill.
Is there a way to restrict the panel to one specific screen, hiding the other from it, as a workaround until a fix will be released? Then i could use fbpanel on the second head.

read(3, "\226\341\274\377\224\341\273\377\223\340\272\377\221\341\271\377\220\340\270\377\217\337\267\377\225\343\273\377\221\337\267\377\16"..., 12608) = 12608
read(3, 0xfa3444, 4096) = -1 EAGAIN (Resource temporarily unavailable)
*** glibc detected *** strace: malloc(): memory corruption (fast): 0x0000000000e52460 ***
======= Backtrace: =========
/lib/libc.so.6[0x7f57fbcebcb8]
/lib/libc.so.6[0x7f57fbcef351]
/lib/libc.so.6(__libc_malloc+select(Aborted

I'm currently building a version in my ppa with the patch from upstream's report attached. Could you test the package once it's built and confirm it fixes this issue? Thanks. PPA: https://edge.launchpad.net/~amoog/+archive/ppa/

Andreas Moog: Confirming that your PPA gnome-panel package works on Jaunty amd64.
I just had the same issue, downloaded your version and now clicking panel launchers on the second screen starts them instead of reloading the panel.
Thank you!

The fix for karmic is at lp:~amoog/gnome-panel/ubuntu

This bug was fixed in the package gnome-panel - 1:2.26.2-1ubuntu4

---------------
gnome-panel (1:2.26.2-1ubuntu4) karmic; urgency=low

  * debian/patches/31_fix_crash_second_screen.patch
    - Add patch by Gerd Kohlberger to fix a crash when clicking
      a launcher on a second screen. (LP: #256041)

 -- Andreas Moog <email address hidden> Fri, 03 Jul 2009 17:30:57 +0200