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 352522 - the clock crash when i double-click on a date
the clock crash when i double-click on a date
Status: RESOLVED DUPLICATE of bug 344058
Product: gnome-panel
Classification: Other
Component: clock
unspecified
Other other
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-23 11:31 UTC by arnaud.charlier
Modified: 2006-08-31 23:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description arnaud.charlier 2006-08-23 11:31:25 UTC
Distribution: Ubuntu 6.06 (dapper)
Package: gnome-panel
Severity: major
Version: GNOME2.14.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: the clock crash when i double-click on a date
Bugzilla-Product: gnome-panel
Bugzilla-Component: clock
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1.
2.
3.

Expected Results:


How often does this happen?


Additional Information:



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

Thread 1 (Thread -1228478240 (LWP 6296))

  • #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



---------------------------------

Ce message et toutes les pieces jointes (ci-apres d\xE9nomm\xE9 le "message") sont etablis a l'attention exclusive de ses destinataires et sont donc confidentiels. Si toutefois vous recevez ce message par erreur, nous vous remercions de bien vouloir le detruire et d'en avertir immediatement l'expediteur au sein de l'Ecole Sup\xE9rieure d'Informatique de Paris (ci-apr\xE8s d\xE9nomm\xE9e "SUPINFO"). Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Internet ne permettant pas d'assurer l'integrite des messages e-mail en g\xE9n\xE9ral et donc de ce message en particulier, SUPINFO et ses filiales, sites r\xE9gionaux, laboratoires ou autres entit\xE9s attach\xE9es, declinent toute responsabilite au titre du pr\xE9sent message qui ne pourrait engager que son auteur et non SUPINFO et seulement dans l'hypothese ou le message n'aurait pas ete modifie par quelque moyen que ce soit.

---------------------------------

This message and any attachments (hereinafter referred to as the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender at Paris Academy of Computer Science (hereinafter referred to as "SUPINFO"). Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. Because the internet can not guarantee the integrity of this message, SUPINFO and its subsidiaries, laboratories and regional branches will not therefore be liable for the message that could only engage his author, not SUPINFO, and only if not modified.

---------------------------------




------- Bug created by bug-buddy at 2006-08-23 11:31 -------

Comment 1 Karsten Bräckelmann 2006-08-31 23:31:38 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?