GNOME Bugzilla – Bug 66338
midnight crash [@ gdk_io_invoke]
Last modified: 2011-03-17 03:35:33 UTC
Package: gnome-pim Severity: normal Version: 1.2.0 Synopsis: gnomecal crashed overnight Bugzilla-Product: gnome-pim Bugzilla-Component: gnomecal Description: gnomecal had crashed overnight: I wasn't using it, so have no way to reproduce the problem. Debugging Information: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40583669 in __wait4 () from /lib/i686/libc.so.6
+ Trace 14677
------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-12-06 04:21 ------- Unknown version 1.2.x in product gnome-pim. Setting version to the default, "unspecified". The original reporter (david.osborne@nottingham.ac.uk) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-pim-maint@bugzilla.gnome.org.
*** Bug 70727 has been marked as a duplicate of this bug. ***
*** Bug 64492 has been marked as a duplicate of this bug. ***
*** Bug 64099 has been marked as a duplicate of this bug. ***
*** Bug 63766 has been marked as a duplicate of this bug. ***
*** Bug 62692 has been marked as a duplicate of this bug. ***
*** Bug 62677 has been marked as a duplicate of this bug. ***
*** Bug 61279 has been marked as a duplicate of this bug. ***
*** Bug 54613 has been marked as a duplicate of this bug. ***
*** Bug 71921 has been marked as a duplicate of this bug. ***
*** Bug 55055 has been marked as a duplicate of this bug. ***
*** Bug 56299 has been marked as a duplicate of this bug. ***
*** Bug 56649 has been marked as a duplicate of this bug. ***
*** Bug 59778 has been marked as a duplicate of this bug. ***
*** Bug 63066 has been marked as a duplicate of this bug. ***
*** Bug 63599 has been marked as a duplicate of this bug. ***
*** Bug 69272 has been marked as a duplicate of this bug. ***
*** Bug 70812 has been marked as a duplicate of this bug. ***
*** Bug 54443 has been marked as a duplicate of this bug. ***
*** Bug 54696 has been marked as a duplicate of this bug. ***
*** Bug 72937 has been marked as a duplicate of this bug. ***
*** Bug 62791 has been marked as a duplicate of this bug. ***
*** Bug 53894 has been marked as a duplicate of this bug. ***
*** Bug 56470 has been marked as a duplicate of this bug. ***
*** Bug 64517 has been marked as a duplicate of this bug. ***
*** Bug 38815 has been marked as a duplicate of this bug. ***
*** Bug 67279 has been marked as a duplicate of this bug. ***
*** Bug 50474 has been marked as a duplicate of this bug. ***
*** Bug 54745 has been marked as a duplicate of this bug. ***
Can't reproduce this (Linux, running recent CVS version). While testing another patch I had often set my clock shortly before midnight, run gnomecal and waited for shortly after midnight. Not one crash. Sebastian, can you reproduce? If not, I suppose this has been fixed in the meantime.
*** Bug 57392 has been marked as a duplicate of this bug. ***
Note that according to bug 67279 this does not only happen if a screensaver is running/the screen is locked.
I'm not so sure, since this crash seems to be quite unpredictable. I'm not even sure that this is caused by gnomecal and not some other component. I would like to let it open a little longer.
*** Bug 58927 has been marked as a duplicate of this bug. ***
*** Bug 74529 has been marked as a duplicate of this bug. ***
*** Bug 70363 has been marked as a duplicate of this bug. ***
*** Bug 79682 has been marked as a duplicate of this bug. ***
*** Bug 798408230 has been marked as a duplicate of this bug. ***
*** Bug 79840 has been marked as a duplicate of this bug. ***
*** Bug 57382 has been marked as a duplicate of this bug. ***
*** Bug 80767 has been marked as a duplicate of this bug. ***
*** Bug 81520 has been marked as a duplicate of this bug. ***
*** Bug 84870 has been marked as a duplicate of this bug. ***
According to bug 84870 this bug is still present in GNOME-PIM 1.4.6.
*** Bug 87974 has been marked as a duplicate of this bug. ***
There is a report in a private e-mail that an upgrade to GNOME-PIM 1.4.7 fixed this problem, but I'm still suspicious.
*** Bug 88303 has been marked as a duplicate of this bug. ***
*** Bug 89531 has been marked as a duplicate of this bug. ***
I have noticed that it doesn't crash when window is maximized, only when iconified.
François: Which version of GNOME-PIM are you using?
See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107058&repeatmerged=yes
*** Bug 95297 has been marked as a duplicate of this bug. ***
*** Bug 96064 has been marked as a duplicate of this bug. ***
*** Bug 95411 has been marked as a duplicate of this bug. ***
*** Bug 101611 has been marked as a duplicate of this bug. ***
*** Bug 102765 has been marked as a duplicate of this bug. ***
*** Bug 104007 has been marked as a duplicate of this bug. ***
*** Bug 110359 has been marked as a duplicate of this bug. ***
According to Bug 110359 this might be related to the switch to daylight savings time.
*** Bug 110560 has been marked as a duplicate of this bug. ***
*** Bug 111677 has been marked as a duplicate of this bug. ***
*** Bug 112274 has been marked as a duplicate of this bug. ***
This is the same as Debian bug #107058 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107058).
*** Bug 113078 has been marked as a duplicate of this bug. ***
*** Bug 113586 has been marked as a duplicate of this bug. ***
Just a note on this long standing bug: I noticed that the crashes are not random for me. It will crash at midnight if I have the date highlighted. E.g., say today is Feb 11, and I have Feb 12 highlighted (selected?) on the calendar. Then it crashes at midnight as the clock goes into Feb 12. Otherwise it doesn't crash. I have Debian's package, gnome-pim 1.4.9. Cheers!
gnome-pim development has been stalled and it has been unmaintained for a few years now. Maintainers don't have future development plan so i am closing the bugs as WONTFIX. Please feel free to reopen the bugs in future if anyone takes the responsibility for active development.