GNOME Bugzilla – Bug 89776
crash on startup
Last modified: 2009-07-14 04:08:23 UTC
Package: gnome-pim Severity: normal Version: 1.91.1 Synopsis: crash on startup Bugzilla-Product: gnome-pim Bugzilla-Component: gnomecal BugBuddy-GnomeVersion: 2.0 (2.0.1) Description: Description of Problem: when i lanch a gnomecal it crash. Steps to reproduce the problem: 1. run gnomecal 2. 3. Actual Results: crash Expected Results: work :) How often does this happen? Additional Information: my systeme is gnu/debian SID . Debugging Information: Backtrace was generated from '/home/gigi/garnome/bin/gnomecal' [New Thread 1024 (LWP 12096)] 0x40721899 in wait4 () from /lib/libc.so.6
+ Trace 25806
Thread 1 (Thread 1024 (LWP 12096))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-08-03 06:51 ------- The original reporter (calca80@libero.it) 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.
if you are really using version 1.91.1, you should really update to 1.4.7. even if not, you should update to that version anyway, because it fixes this crash-on-startup bug :) *** This bug has been marked as a duplicate of 83840 ***
biesi: This looks like a genuine 1.91.x back-trace: The file gnomecal-main.c in a give away, it didn't exist in 1.4.x. Reopening.
Apologies for the spam- I'm removing 'bugsquad' from some keywords via the web interface. This is a one-time only thing before I re-add bugsquad via the SQL interface, which will generate no mail. Apologies again.
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.