GNOME Bugzilla – Bug 529037
crash in gnome_calendar_get_current_view_widget()
Last modified: 2009-02-25 11:45:57 UTC
What were you doing when the application crashed? Distribution: Solaris Express Community Edition snv_79 X86 Gnome Release: 2.20.1 2007-11-19 (Sun Microsystems, Inc.) BugBuddy Version: 2.20.1 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: nimbus Icon Theme: nimbus Memory status: size: 601632768 vsize: 601632768 resident: 426528768 share: 393216 rss: 426528768 rss_rlim: 0 CPU usage: start_time: 0 rtime: 135509 utime: 1270735247 stime: 84359202 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) sol-thread active. Retry #1: Retry #2: Retry #3: Retry #4: [New LWP 1 ] [New Thread 1 (LWP 1)]
+ Trace 195686
Thread 1 (LWP 1)
Thread 14 (Thread 25 (LWP 25)): #-1 0xfe242f07 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 13 (Thread 23 ): #-1 0xfe23f51b in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 12 (Thread 22 ): #-1 0xfe23f51b in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 11 (Thread 19 ): #-1 0xfe23f51b in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 10 (Thread 4 (LWP 4)): #-1 0xfe242f07 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 9 (Thread 2 ): #-1 0xfe23f51b in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 8 (LWP 2 ): #-1 0xfe23f51b in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 7 (LWP 4 ): #-1 0xfe242f07 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 6 (LWP 25 ): #-1 0xfe242f07 in __pollsys () from /usr/lib/libc.so.1 No symbol table info available. Thread 5 (LWP 23 ): #-1 0xfe23f51b in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 4 (LWP 22 ): #-1 0xfe23f51b in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 3 (LWP 19 ): #-1 0xfe23f51b in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 2 (Thread 1 (LWP 1)): #-1 0xfe2434b7 in _waitid () from /usr/lib/libc.so.1 No symbol table info available. Thread 1 (LWP 1 ): #-1 0xfe2434b7 in _waitid () from /usr/lib/libc.so.1 No symbol table info available. #-1 0xfe2434b7 in _waitid () from /usr/lib/libc.so.1
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml, gtk, glib, libsoup, gnome-vfs, libgnome, orbit2 and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.26.5-45.fc9.i686 #1 SMP Sat Sep 20 03:45:00 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10500000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 165281792 vsize: 165281792 resident: 84238336 share: 23035904 rss: 84238336 rss_rlim: 4294967295 CPU usage: start_time: 1223459467 rtime: 3896 utime: 3460 stime: 436 cutime:458 cstime: 30 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb8051980 (LWP 27537)] [New Thread 0xb59fcb90 (LWP 31734)] [New Thread 0xb6595b90 (LWP 31733)] 0x00110416 in __kernel_vsyscall ()
+ Trace 207908
Thread 1 (Thread 0xb8051980 (LWP 27537))
Just ran into this myself. Had the calendar/clock expanded in the gnome-panel and deleted a local calendar in evolution. evo crashed.
*** Bug 560307 has been marked as a duplicate of this bug. ***
*** Bug 482958 has been marked as a duplicate of this bug. ***
*** Bug 563973 has been marked as a duplicate of this bug. ***
*** Bug 564870 has been marked as a duplicate of this bug. ***
*** Bug 566877 has been marked as a duplicate of this bug. ***
*** Bug 568121 has been marked as a duplicate of this bug. ***
anybody working on this? From bug 568121:
+ Trace 211626
*** Bug 569692 has been marked as a duplicate of this bug. ***
*** Bug 570082 has been marked as a duplicate of this bug. ***
*** Bug 570605 has been marked as a duplicate of this bug. ***
see bug 570605 for latest traces (2.24.x) , he has mentioned steps to reproduce the bug
Hmm, I wonder if I can trick mcrha into providing a patch for 2.24.5/2.25.91 :-D
Looks like a signal isn't getting disconnect when a GnomeCalendar is finalized, so the signal callback fires on a dead object (priv=0x0 is the giveaway).
+ Trace 212299
Looks like this was introduced quite some time ago (bug #328484): http://svn.gnome.org/viewvc/evolution/trunk/calendar/gui/calendar-component.c?r1=33755&r2=33754&pathrev=33755 Odd that the bug only manifested a year later. Perhaps the "source-removed" signal stopped firing, or something is finalizing the calendar too early.
The calendar component window isn't disconnecting signals on sources in time of free properly, steps: a) Open Evolution in a calendar window b) File->New Window c) close that new window d) Preferences on any existing source, change name or anything, press OK it'll not be OK after d), there will be a bug-buddy shown.
Created attachment 128307 [details] [review] proposed evo patch for evolution; I believe it was there even a year ago, it only wasn't tested with such scenario.
Nice fix!! Please commit the patch to trunk and stable.
Committed to trunk. Committed revision 37335. Committed to gnome-2-24. Committed revision 37336.