GNOME Bugzilla – Bug 318576
gnome-cal crashes on start-up (segmentation fault)
Last modified: 2009-03-12 09:20:49 UTC
Steps to reproduce: 1. gnome-pim 1.4.9-2.2 installed into ubuntu with synaptic 2. start the menu Applications->Applications->Calendar. 3. Program displays an "Error" Window. Stack trace: Debugging Information: Backtrace was generated from '/usr/bin/gnomecal' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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 -1216710976 (LWP 9413)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 63483
Thread 1 (Thread -1216710976 (LWP 9413))
Other information: The package was reinstalled but the behavior stayed the same.
*** Bug 360281 has been marked as a duplicate of this bug. ***
No news for 2 years... Is this still an issue in a current version? If not, this should probably be closed as OBSOLETE.
Closing as per comment #2.