GNOME Bugzilla – Bug 104007
gnomecal coredumps
Last modified: 2011-03-17 03:35:30 UTC
After running for many days gnomecal dies with Application "gnomecal" (process xxxx) has crashed due to a fatal error. (Segmentation fault) Running version 1.4.9 of gnome-pim
Please include a backtrace of the crash using bug-buddy or gdb. See http://bugzilla.gnome.org/getting-traces.cgi for more information. Thanks.
My report was misleading. No core file was produced even though my coredumpsize is set to unlimited. I am not sure what I can do to get the core file in order to generate the stack trace. Note that the program runs fine for 3-7 days before dying with the "segmentation fault" pop-up window.
Created attachment 14750 [details] Backtrace of gnomecal after a crash
Which version of glib and gtk+ are you using? Your backtrace suggest that it's crashing in one of them.
Regarding the versions of glib and gtk+: The glib version is 1.2.10, Release 8 The gtk+ version is 1.2.10, Release 22 Both are part of Redhat 8.0 and I believe that the machine is patched up-to-date with Redhat patches
I guess that this crash occured during the night? If so, this is most probably another occurence of the infamous midnight crash. (Sadly.) *** This bug has been marked as a duplicate of 66338 ***
Created attachment 15039 [details] [review] Backtrace of gnomecal after crash at 2pm (not midnight...)
It doesn't necessarily crash at "midnight". Today it crashed just as it was supposed to alert me to a meeting at 1:59pm. See the attached backtrace.
Created attachment 15076 [details] stdout+stderr from another gnomecal crash
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.