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 344058 - ClockApplet crash
ClockApplet crash
Status: RESOLVED DUPLICATE of bug 345609
Product: gnome-panel
Classification: Other
Component: clock
unspecified
Other other
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 344834 352522 353758 361920 362912 403133 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-06-06 19:50 UTC by francois.vaningelgom
Modified: 2007-05-16 23:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
debug information... (3.98 KB, text/plain)
2006-06-07 19:52 UTC, francois.vaningelgom
Details
stack crash dump (70.84 KB, text/plain)
2007-02-04 12:29 UTC, Mike Jonkmans
Details

Description francois.vaningelgom 2006-06-06 19:50:43 UTC
From: francois  <f.vaningelgom@hotmail.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:
Description of the crash:
?Calendar crash!

Steps to reproduce the crash:
1. click the date top right
2. double click on a day
3. crash

Expected Results:
don't know


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

Thread 1 (Thread -1229506336 (LWP 23843))

  • #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-06-06 19:50 -------

Comment 1 Elijah Newren 2006-06-06 20:25:59 UTC
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.
Comment 2 francois.vaningelgom 2006-06-07 19:52:27 UTC
Created attachment 66927 [details]
debug information...
Comment 3 francois.vaningelgom 2006-06-07 19:54:15 UTC
I didn't achieve finding something else than what i transmitted you first i found this but i think it i very similar... Instead of finding what you asked i'll try to be clearer in the how-to to reproduce the crash:

1. I click on the date + hour once to show the calendar
2. I doubble click on a date
3. Calendar is blancked like if it was loading..
4. After a long time i decide to re click on the date
5. He tells me ClockApplet crashed and purpose me to reload application.

Sorry but i can't be clearer...

If you need any information more, tell me.
Comment 4 Elijah Newren 2006-06-14 03:45:53 UTC
*** Bug 344834 has been marked as a duplicate of this bug. ***
Comment 5 Karsten Bräckelmann 2006-08-31 23:31:38 UTC
*** Bug 352522 has been marked as a duplicate of this bug. ***
Comment 6 Karsten Bräckelmann 2006-08-31 23:31:47 UTC
*** Bug 353758 has been marked as a duplicate of this bug. ***
Comment 7 Karsten Bräckelmann 2006-08-31 23:39:48 UTC
Fixed the MIME type of attachment 66927 [details]. Unfortunately, still no additional information in the stacktrace.

Please see comment 1. 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.
Comment 8 Elijah Newren 2006-10-13 14:08:50 UTC
*** Bug 361920 has been marked as a duplicate of this bug. ***
Comment 9 Elijah Newren 2006-10-17 17:30:47 UTC
*** Bug 362912 has been marked as a duplicate of this bug. ***
Comment 10 palfrey 2007-02-01 13:11:51 UTC
*** Bug 403133 has been marked as a duplicate of this bug. ***
Comment 11 Mike Jonkmans 2007-02-04 12:29:42 UTC
Created attachment 81860 [details]
stack crash dump

As i was so lazy as to file a duplicate bug - i felt compelled to create the requested stack trace. So here it is, i hope it helps.

A slightly more detailed sequence of events leading to the crash:
- click on clock/date in panel --> shows month overview
- double click on any of the days --> month overview goes blank (hangs)
- click again on the clock/date in the panel --> blank month oveview goes away
- click again --> crash

Regards,
    Mike Jonkmans
Comment 12 Vincent Untz 2007-05-13 00:25:27 UTC
Thanks!
Comment 13 Vincent Untz 2007-05-14 13:01:26 UTC
I can't reproduce the crash and I fail to see how we can pass NULL to gtk_calendar_set_display_options() since two lines before the call the same cd->calendar works in gtk_calendar_get_display_options(). It'd be great if someone who can reproduce the bug could play with it in gdb.

Interesting thing to note: all crashes are from GNOME 2.14/Ubuntu 6.06. This could indicate the bug has been fixed since then, or that it was because of an Ubuntu patch.

It's also interesting that the month overview goes blank. There's no reason for this to happen. Do you have evolution installed?
Comment 14 Vincent Untz 2007-05-16 23:18:00 UTC
Can you reply in bug 345609? Thanks.

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