GNOME Bugzilla – Bug 568390
crash in Window Selector: Dual head setup, gnome 2...
Last modified: 2009-01-20 07:57:44 UTC
Version: 2.24.3 What were you doing when the application crashed? Dual head setup, gnome 2.24.3. 4 panels, screen 1 top and bottom, screen 2 top and bottom. Added window list to both bottom panels, added workspace list to scree 1 bottom panel. When I add a workspace list to screen 2 bottom panel, the window lists crash. Distribution: Unknown Gnome Release: 2.24.3 2009-01-19 (GNOME.Org) BugBuddy Version: 2.24.2 System: Linux 2.6.27.10-2.1-64bit #1 SMP Mon Jan 12 09:29:15 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 33161216 vsize: 33161216 resident: 13754368 share: 10547200 rss: 13754368 rss_rlim: 18446744073709551615 CPU usage: start_time: 1232434080 rtime: 34 utime: 30 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xf690f700 (LWP 3335)] 0xf7f00425 in __kernel_vsyscall ()
+ Trace 211693
Thread 1 (Thread 0xf690f700 (LWP 3335))
----------- .xsession-errors (47 sec old) --------------------- ** (gnome-panel:2904): WARNING **: Exception from popup_menu 'IDL:omg.org/CORBA/COMM_FAILURE:1.0' ** (gnome-panel:2904): WARNING **: Exception from popup_menu 'IDL:omg.org/CORBA/COMM_FAILURE:1.0' ** (gnome-panel:2904): WARNING **: Exception from popup_menu 'IDL:omg.org/CORBA/COMM_FAILURE:1.0' ** (gnome-panel:2904): WARNING **: Exception from popup_menu 'IDL:omg.org/CORBA/COMM_FAILURE:1.0' ** (gnome-panel:2904): WARNING **: Exception from popup_menu 'IDL:omg.org/CORBA/COMM_FAILURE:1.0' --------------------------------------------------
100% reproduceable on my system. I'm running a 64-bit kernel, but my entire userspace is 32-bit, so ignore the 64bit in the uname :) All of gnome is built for sources, from the 2.24.3 paths. Problem was also in 2.24.2. It crept in somewhere between 2.18 and 2.24. Kind Regards Nigel
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 472773 ***