GNOME Bugzilla – Bug 70812
gnomecal crash
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-pim Severity: normal Version: 1.2.0 Synopsis: gnomecal crash Class: sw-bug Distribution: Red Hat Linux release 7.1 (Seawolf) System: Linux 2.4.2-2 i686 unknown C library: glibc-2.2.2-10 C compiler: 2.96 glib: 1.2.9 GTK+: 1.2.9 ORBit: ORBit 0.5.7 gnome-libs: gnome-libs 1.2.8 libxml: 1.8.10 gnome-print: gnome-print-0.25-9 gnome-core: gnome-core 1.2.4 Description: it crashed while I was gone, I hope bug-buddy will generate a core file and attach it. Debugging information: using standard .gdbinit file!!!! ~/.gdbinit (defined by cloutier) end of standard .gdbinit (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x40585519 in __wait4 () from /lib/i686/libc.so.6
+ Trace 17436
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-02-07 08:45 ------- Unknown version 1.2.x in product gnome-pim. Setting version to the default, "unspecified". The original reporter (cloutier@avanticorp.com) 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.
I assume, gnomecal crashed during the night?
Yes it crashed overnight so that on Feb 7 I came in and it had crashed. I suspect that on the 6th I had changed an appointment so that it now had the following text (before my change it was a single line): ---- Subject: Lunch Reminder @12:00 Chelmsford Papa Ginos The x-synergy lunch has appeared on my event horizon, see you at papa ginos at 12:00 rich ---- before and after my change to the text of the appointment, the notification of this appointment had the mailto selected so that it would send me a message. I might have changed the time for mailto from 1 day to 48 hours (I don't recall when I made that change)
This is the famous "midnight crash". I'm merging this bug report with the others. Thanks for your reply! *** This bug has been marked as a duplicate of 66338 ***