GNOME Bugzilla – Bug 151998
Crash when using any panel functionality on second desktop
Last modified: 2009-08-15 18:40:50 UTC
Distribution: Debian 3.1 Package: gnome-panel Severity: critical Version: GNOME2.6.1 2.6.x Gnome-Distributor: Debian Synopsis: Crash when using any panel functionality on second desktop Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: I have a multiheaded X setup with two head. There are two desktops one running on each head. The X Server is not running xinerama. If I attempt to use any panel functionality on the second head gnome-panel immediately crashes. The following errors are reported in .xessions errors file at the same time. The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 6549 error_code 8 request_code 56 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 6633 error_code 8 request_code 56 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Steps to reproduce the crash: 1. Right click on panel and choose properties on any panel running on the a desktop which is not the primary desktop (ie the one that the gnome spash screen appears on). Using any option on the "Actions" menu also provokes it infact almost any interaction with the panel at all provokes it. Expected Results: The panel should not crash when used on the second desktop. How often does this happen? Everytime. Additional Information: none Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1087682656 (LWP 21015)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x4077840e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 49928
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-06 13:22 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was paulg@chiark.greenend.org.uk. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
The stack trace looks really similar to one of the stack traces in bug #146075... I suppose you can always reproduce the bug... Mark: I know you love all the multihead bugs :-) and the last function in the trace is ORBit_adaptor_setup, so it'd be great if you could give a look to this bug.
Paul: is it reproducable with 2.8.2? If so, could you get a stack trace with the --sync parameter: 'gnome-panel --sync'. Thanks
I can't reproduce it with 2.8.2 so looks like it's been fixed (I am the original reporter). However I am just about to ditch GNOME due to the dummbing down that has taken place over the last few releases which has resulted in a desktop environment which I can no longer configure to behave the way I want it to. Therefore I'm no longer in a position to comment. You may like to reflect that in a headlong race to compete with MS Windows you are losing users such as myself.
Thanks for the update Paul. I'm sorry to learn that you don't like the road GNOME is taking.