GNOME Bugzilla – Bug 72646
Panel Crashes when trying to remove
Last modified: 2015-03-24 13:00:31 UTC
Package: gnome-panel Severity: critical Version: 1.5.10 Synopsis: [Solaris] Crash when trying to remove panel Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (1.111.1) Description: The beta release of Gnome 2.0 components were built on 25th Feb 2002 in a Sun Sparc (SunBlade) machine, running Solaris 2.9 (32 bit). The components are being run from the CDE environment by setting up Library paths to the latest Gnome 2.0 components Description of Problem: When gnome-panel-2 is chosen to be removed using right-click, the panel crashes Steps to reproduce the problem: 1. Invoke a gnome panel, by typing 'gnome-panel-2' on the command prompt 2. Panel starts up successfully (Appears at the bottom, and the menu panel at the top) 3. Close the panel by right clicking (on the menu panel, at the top of the desktop) and choosing 'Remove from Panel' option 4. The menu panel closes and a crash occurs Actual Results: Crash occurs Expected Results: No Crash How often does this happen? Always Additional Information: Stack trace is attached Debugging Information: (no debugging symbols found)...Retry #1: Retry #2: Retry #3: Retry #4: [New LWP 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)... (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)...0xfdd9ced0 in _waitid () from /usr/lib/libc.so.1
+ Trace 18311
Thread 1 (LWP 1)
Anand: two things: 1) You guys should be building with symbols; not having symbols makes your stack traces much less useful. Please pass that on to whoever is doing build work for you. Thanks. 2) Was this when removing a panel? or when removing a pager? For me, it occurred when I was removing a pager, not the complete panel. George, Mark- don't know if that helps, but I hope so :) This is a better stack trace, from CVS on 2/28. --- [New Thread 1024 (LWP 17858)] 0x40934e29 in __wait4 () from /lib/libc.so.6
+ Trace 18533
Thread 1 (Thread 1024 (LWP 17858))
note that there are similar bugs: http://bugzilla.gnome.org/show_bug.cgi?id=72296 and http://bugzilla.gnome.org/show_bug.cgi?id=73019, with their duplicates and different backtraces. As I can see, it happens when removing a panel which has pager on it, or at least pager causes panel to crash.
It fails in a cast, so pager->pager does not exist or is corrupted. And what's up with internal_size = -512?
Gedeminas: yes, I've seen that there are a number of things with roughly similar cause, but they all seem to have slightly different traces. Do you think I should mark them all as duplicates anyway?
Matching trace, with symbols... --- [New Thread 1024 (LWP 29395)] 0x4094ce29 in __wait4 () from /lib/libc.so.6
+ Trace 18645
Thread 1 (Thread 1024 (LWP 29395))
Confirmed patch fixes this crash. *** This bug has been marked as a duplicate of 73224 ***
Fixed by bug 73224. Closing