Bug 353758 – Clock crashes after certain number of certain clicks

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 353758 - Clock crashes after certain number of certain clicks


Summary:	Clock crashes after certain number of certain clicks


Status:	RESOLVED DUPLICATE of bug 344058

Product:	gnome-panel
Classification:	Other
Component:	clock
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-31 22:58 UTC by noortje_blond
Modified:	2006-08-31 23:36 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description noortje_blond 2006-08-31 22:58:27 UTC

Distribution: Ubuntu 6.06 (dapper)
Package: gnome-panel
Severity: None
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Clock crashes after certain number of certain clicks
Bugzilla-Product: gnome-panel
Bugzilla-Component: clock
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
unexpected quit

Steps to reproduce the crash:
1. click clock -> a little 'pop-out miniwindow' with dates appears
2. double-click a date -> pop-out miniwindow becomes white
3. click clock again -> pop-out miniwindow disappears
4. click clock again -> crash

How often does this happen?
Only when you're really trying, or when you're just that lucky. Up to
now, once.

Additional Information:
It's not really a big problem, just thought you may want to see :)


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 -1228306208 (LWP 10935)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 71336

Thread 1 (Thread -1228306208 (LWP 10935))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gtk_calendar_set_display_options
from /usr/lib/libgtk-x11-2.0.so.0
#5 ??
#6 ??
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2006-08-31 22:58 -------

Comment 1 Karsten Bräckelmann 2006-08-31 23:31:47 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 344058 ***

Comment 2 Karsten Bräckelmann 2006-08-31 23:36:02 UTC

Also, the maintainers need more information (better stacktrace with debugging symbols) to fix the bug. Could you please answer the questions in the other report?