GNOME Bugzilla – Bug 313111
Evolution crashes when calender tab selected after updating meeting timezone
Last modified: 2005-08-11 15:26:23 UTC
Steps to reproduce: 1. Set local timezone to GMT (Europe/Belfast). Accept 9:30am meeting request from outlook user from Mountain Time Zone (America/Denver). 2. Note meeting shows in calender at 9:30am, not 4:30pm. 3. Change meeting timezone to America/Denver. Meeting moves to 4:30pm. 4. Switch to mail tab. 5. Switch back to calender tab. Notice meeting has disappeared. 6. Switch back to mail tab, re-accept the meeting request. 7. Switch to calender tab, evolution crashes. 8. Re-run evolution. 9. Evolution crashes. Stack trace: Backtrace was generated from '/usr/bin/evolution-2.2' (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)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 11983)] [New Thread 32769 (LWP 11992)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 11983)] [New Thread 32769 (LWP 11992)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 11983)] [New Thread 32769 (LWP 11992)] [New Thread 16386 (LWP 11993)] [New Thread 32771 (LWP 11994)] [New Thread 49156 (LWP 11997)] [New Thread 65541 (LWP 12038)] 0x40b1c0cb in waitpid () from /lib/libpthread.so.0
+ Trace 62360
Thread 5 (Thread 49156 (LWP 11997))
Thread 4 (Thread 32771 (LWP 11994))
Thread 3 (Thread 16386 (LWP 11993))
Other information: Distribution: Gentoo Base System version 1.6.8 Package: Evolution Severity: major Version: GNOME2.8.3 2.2.x Gnome-Distributor: Gentoo Synopsis: Evolution crashes when calender tab selected after updating meeting timezone Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.2.x BugBuddy-GnomeVersion: 2.0 (2.8.1)
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
$ gdb evolution-2.2 GNU gdb 6.0 Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/evolution-2.2 [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 8879)] es menu class init adding hook target 'source' Detaching after fork from child process 8890. [New Thread 32769 (LWP 8891)] [New Thread 16386 (LWP 8892)] [New Thread 32771 (LWP 8896)] [New Thread 49156 (LWP 8897)] calendar-gui-Message: ********* the state in ok is 3 Program received signal SIGSEGV, Segmentation fault.
+ Trace 62377
Thread 16384 (LWP 8879)
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 261154 ***