GNOME Bugzilla – Bug 167478
Crashed during "Add to Panel"
Last modified: 2015-03-24 13:00:49 UTC
Distribution: Debian 3.1 Package: gnome-panel Severity: critical Version: GNOME2.9.91 2.9.x Gnome-Distributor: Ubuntu Synopsis: Crashed during "Add to Panel" Bugzilla-Product: gnome-panel Bugzilla-Component: clock applet Bugzilla-Version: 2.9.x BugBuddy-GnomeVersion: 2.0 (2.9.1) Description: Description of the crash: On ubuntu-hoary-devel, on the lower panel i click "Add to panel" and it crashed. Steps to reproduce the crash: 1. Right click on lower panel 2. Say "Add to panel" 3. BINGO! ;) Expected Results: Must'nt Crash How often does this happen? Always 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 -1222982624 (LWP 7226)] [New Thread -1225163856 (LWP 7241)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 55735
Thread 2 (Thread -1225163856 (LWP 7241))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-15 10:08 ------- 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 rohandhruva@gmail.com. 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.
Can you install the gnome-panel-dbg package and paste new debugging informations (the stack trace is the important part) here? Thanks,
Created attachment 37525 [details] Stack Trace Installed gnome-panel-dbg Saved the bug buddy report to a file. Please advixe me what to do next.
Thanks for the stack trace. I'll look at it as soon as possible. Pasting the trace here so we don't have to click:
+ Trace 55760
Got it. It's fixed in CVS. Thanks for your help.
Thanks. Does it mean that i helped GNOME team fix a bug? Probably even nasty bug that could bring th world down to its knees :) Sorry for my bad sense of humor. Jokes apart, what do i do to fix it ? Wait for ubuntu/debian to update it in their repos or upgrade from CVS ? Rohan
Rohan: the easiest way is to wait for new ubuntu packages. But you can try to build it from cvs.
*** Bug 167779 has been marked as a duplicate of this bug. ***