GNOME Bugzilla – Bug 346523
Gnome-Panel crashes when selecting Always on Visible Workspace
Last modified: 2007-05-29 01:41:41 UTC
Distribution: Ubuntu 6.06 (dapper) Package: gnome-panel Severity: major Version: GNOME2.14.2 2.14.x Gnome-Distributor: Ubuntu Synopsis: Gnome-Panel crashes when selecting Always on Visible Workspace Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.14.x BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: If you select "Always on Visible Workspace" on an application in the task panel, gnome-panel will crash when you right click the button next time. This has been verified with both a terminal and Beep Media Player. I have also tried to reboot my computer and tested this with no other applications running than one terminal window. Steps to reproduce the crash: 1. Open any application (I tested with a Terminal window) 2. Right click the Terminal button in the Task Panel, and select "Always on Visible Workspace". 3. Right click the Terminal button again, and gnome-panel crashes. 3. Expected Results: The context meny should appear. How often does this happen? Every time I try Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224771904 (LWP 5025)] [New Thread -1239782480 (LWP 5028)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 69179
Thread 1 (Thread -1224771904 (LWP 5025))
------- Bug created by bug-buddy at 2006-07-04 08:34 -------
Just to say I have found exaclty the same problem with every application I've tried it with. Debugging information below. Distribution: Ubuntu 6.06 (dapper) Package: gnome-panel Severity: normal Version: GNOME2.14.2 2.14.x Gnome-Distributor: Ubuntu Synopsis: Multi-workspace application crashes gnome-panel Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.14.x BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/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) (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 -1224436032 (LWP 10426)] [New Thread -1245520976 (LWP 10435)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 69420
Thread 1 (Thread -1224436032 (LWP 10426))
Exactly the same problem here, however I use Ubuntu Edgy Eft (6.10), and thus Gnome 2.16 instead of 2.14. Below my debugging information. Memory status: size: 42074112 vsize: 0 resident: 42074112 share: 0 rss: 18317312 rss_rlim: 0 CPU usage: start_time: 1160419383 rtime: 0 utime: 268 stime: 0 cutime:238 cstime: 0 timeout: 30 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/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) (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 -1225681232 (LWP 14163)] (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) (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75480
Thread 1 (Thread -1225681232 (LWP 14163))
I'm seeing this on SLED as well, so it's not a complete Ubuntuism.
*** Bug 381567 has been marked as a duplicate of this bug. ***
I can't reproduce this with gnome-panel 2.14.3 on Debian. Does upgrading to at least 2.14.3 fix the problem?
Do people having that problem use a patched libwnck for compiz?
That's the case for me on SLED. Package changelog excerpt: * Tue May 30 2006 - danw@suse.de - Patch in a new method from libwnck HEAD to allow compiz to know when a window has a real name (as opposed to a fallback name like "untitled window"). I can look into reproducing on an unpatched libwnck, if that's the patch you're suspecting is the problem. We can also wait to hear whether Ubuntu users have a similar patch. Awaiting further feedback.
all the ubuntu bugs reported on launchpad with a similar backtrace are happening to people who installed a un-official package patched for compiz, trying without that patch would be nice
*** Bug 386937 has been marked as a duplicate of this bug. ***
I got the crash with 2.16.1-0ubuntu1.1 Did not explicitly previously select "always in front" or "always on visible workspace" For installing the -dbgsym debug package, I had to revert to 2.16.1-0ubuntu1 which does not exhibit the crash advancing to 2.16.1-0ubuntu1.1 again and i can trigger the crash seb128? no patched libwnck here for compiz, I believe
Christian, Ubuntu has no such libwnck version: 2.16.1-0ubuntu1.1, that's the version used by people who provide a deb patched for compiz though. Where did you get it? What is the current changelog entry from that package?
I recently installed a libwnck with an updated patch for compiz and am no longer able to reproduce the bug. I therefore feel quite confident in attributing my problems to the earlier patch for compiz.
marking the bug NOTGNOME, that's due to a libwnck patch
*** Bug 391929 has been marked as a duplicate of this bug. ***
*** Bug 416577 has been marked as a duplicate of this bug. ***
*** Bug 441895 has been marked as a duplicate of this bug. ***