GNOME Bugzilla – Bug 340815
clock applet crashes when clicked
Last modified: 2006-07-10 14:52:48 UTC
X-Mailer: bug-buddy 2.14.0 Subject: Clock crashes after clicking it Distribution: Ubuntu 6.06 (dapper) Package: gnome-panel Severity: Normal Version: GNOME2.14.1 unspecified Gnome-Distributor: Ubuntu Synopsis: Clock crashes after clicking it Bugzilla-Product: gnome-panel Bugzilla-Component: clock Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: Clock crashes after clicking it Steps to reproduce the crash: 1. Click the clock 2. An empty white square becomes visible, click it 3. The clock application crashes and brings up this bug reporting window Expected Results: The square should show a calendar, shouldn't it? How often does this happen? Every time I click the clock. I have not restarted the computer yet, so that might help. Additional Information: I am not an experienced user; I might just be doing something stupid. Other programs open: Thunderbird, Firefox Stats: 1,4 Ghz Celeron M (laptop) 512 MB RAM Debugging Information: Backtrace was generated from '/usr/libexec/ClockApplet' (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 -1228080928 (LWP 8908)] [New Thread -1229808720 (LWP 9012)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 68055
Thread 1 (Thread -1228080928 (LWP 8908))
------- Bug created by bug-buddy at 2006-05-06 11:31 -------
I did not mean to create a bug title like that. Sorry. Also IMHO, this: Severity: critical should be changed into a lower rating. I might have misspecified the steps to reproduce the bug. Ways I've managed to crash the clock: A Click on the clock. - Crash. B Click on the clock. Double-click on the current date. - Crash. C Click on the clock. Double-click on the current date. CLick on the clock. - Crash. Another thing that might be important: I'm running Dapper Drake Beta.
Hello kristian, thanks for the bug report! Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
I installed these: "The lib packages often have a -dbg variant (ie: libglib2.0-0-dbg), you just need to install them as gdb/bug-buddy will automatically pick up the debugging information the next time it runs. You probably want to install libglib2.0-0-dbg, libgtk2.0-0-dbg, and libgnomevfs2-0-dbg" but not this one: "in addition to debug packages specific for the application or library that is crashing." as I don't know what it should be called. If the trace is still not usefull, please tell me which program-specific package I should download. Kristian From: Kristian Koerselman <kristian.koerselman@stormoog.com> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.14.0 Subject: ClockApplet crash Distribution: Ubuntu 6.06 (dapper) Package: gnome-panel Severity: Normal Version: GNOME2.14.1 unspecified Gnome-Distributor: Ubuntu Synopsis: ClockApplet crash Bugzilla-Product: gnome-panel Bugzilla-Component: clock Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: as before Debugging Information: Backtrace was generated from '/usr/libexec/ClockApplet' (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) [Thread debugging using libthread_db enabled] [New Thread -1228482336 (LWP 9050)] [New Thread -1230197840 (LWP 9400)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 68067
Thread 1 (Thread -1228482336 (LWP 9050))
Wow, thank you for your fast response. gnome-panel-dbg should do it.
Created attachment 64951 [details] trace
"Wow, thank you for your fast response." No problem. :) I've attached the new trace. Also: Most reliable reproduction: 1 Click the clock 2 Double-click any date 3 Click the clock (sometimes needed): 4 Click the clock again Please let me know if there is anything else you need to know. Kristian
Thank you! Let's wait for comments by the gnome-panel maintainers now. BTW, I can't reproduce this on my dapper, and I'm not sure why your binary is "/usr/libexec/ClockApplet" while here is "/usr/lib/gnome-panel/clock-applet".
I can only guess. Im running Ubuntu Dapper Drake Beta. Either the Beta or the Ubuntu may have something to do with it. Do you think I should have written to the Ubuntu forums instead?
I can reproduce this everytime when unpressing the clock applet, no matter what I did with the applet when it was pressed. Also running same Ubuntu version, but I first noticed this when I used to run Mandriva 2006.
*** Bug 346795 has been marked as a duplicate of this bug. ***
Matches the stack traces and description in bug 345609, which has a more complete stack trace inline and a patch and a pointer to another which may fix the problem. *** This bug has been marked as a duplicate of 345609 ***