GNOME Bugzilla – Bug 317776
gnimecal crashes on startup
Last modified: 2008-03-01 12:18:54 UTC
Distribution: Ubuntu 5.10 (breezy) Package: gnome-pim Severity: Normal Version: GNOME2.12.0 unspecified Gnome-Distributor: Ubuntu Synopsis: gnimecal crashes on startup Bugzilla-Product: gnome-pim Bugzilla-Component: gnomecal Bugzilla-Version: unspecified Description: Description of the crash: gnome calendar crashes when started (from gnome menu). error message: "Application "gnomecal" (process 13372) has crashed due to a fatal error. (Segmentation fault)" Steps to reproduce the crash: 1. try to start it again - crashes again 2. 3. Expected Results: How often does this happen? whenever the app. is started Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnomecal' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912540779376 (LWP 13305)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00002aaaacd92ba4 in waitpid () from /lib/libc.so.6
+ Trace 63326
Thread 1 (Thread 46912540779376 (LWP 13305))
------- Bug moved to this database by unknown@gnome.bugs 2005-10-02 22:54 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was sethavi@hotmail.com.
We got the bug reported in our BTS as well: https://launchpad.net/distros/ubuntu/+sources/gnome-pim/+bug/2740 The corresponding backtrace: http://librarian.launchpad.net/579506/579539/gdboutput.txt This is, what I got: Starting program: /usr/bin/gnomecal Program received signal SIGSEGV, Segmentation fault. 0x0000000000438d24 in month_view_size_allocate (widget=0x6d63b0, allocation=0x7fffffc13f50) at month-view.c:594 594 y = font->ascent + font->descent + 2 * SPACING; (gdb) thread apply all bt full (gdb) bt
+ Trace 63476
gnomecal is separated from gnome-pim and moved to sourceforge as another project (gnotime - http://gttr.sourceforge.net) on around 2002. And needless to say, there will be no future release of gnome 1.4.x. So I guess this bug can be closed as OBSOLETE.
In case any one needs a fix, The problem occurs because of fonts properties. gnome-pim version: 1.4.9 Folder: gncal File: month-view.c Line Number: 594 Code: y = font->ascent + font->descent + 2 * SPACING; Fixed code: y = 2 * SPACING; //a better solution is to fix the font properties Reported the same at Ubuntu bug tracker: https://launchpad.net/distros/ubuntu/+source/gnome-pim/+bug/2740
Closing as obsolete. Even if there is a fix, it won't be committed into GNOME svn as the project is abandoned.