GNOME Bugzilla – Bug 337454
Calendar crashed when modifying entry
Last modified: 2013-09-13 00:54:03 UTC
Distribution: Ubuntu 6.04 (dapper) Package: Evolution Priority: Normal Version: GNOME2.14.0 unspecified Gnome-Distributor: Ubuntu Synopsis: Calendar crashed when modifying entry Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.14.0) Description: Description of the crash: Logged into Exchange account, editing Web based calendar, and after modifying an entry and saving, Evolution crashes. When the application is restarted, it continues to crash. This could be related to a slow Internet connection. Is a greater tolerance for losing contact with the Exchange server possible? Steps to reproduce the crash: 1. Setup Exchange account 2. Create a calendar entry, then modify it 3. When you save the entry, it will possibly crash Expected Results: Entry was to be saved and changes applied successfully. How often does this happen? Intermittently. More frequent on a slower Internet connection, such as off the work network where the Exchange server is located. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231882016 (LWP 10890)] [New Thread -1300792400 (LWP 10964)] [New Thread -1266828368 (LWP 10958)] [New Thread -1284006992 (LWP 10957)] [New Thread -1266562128 (LWP 10938)] [New Thread -1249211472 (LWP 10927)] [New Thread -1239864400 (LWP 10926)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 67498
Thread 1 (Thread -1231882016 (LWP 10890))
-- Thanks, Ben Simpson csu16451@mail.claytonstate.net ------- Bug created by bug-buddy at 2006-04-06 03:49 -------
stacktrace is a bit similar to bug 325068
but crashes in some other frame. 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.
*** Bug 345290 has been marked as a duplicate of this bug. ***
Ubuntu bug with a similar backtrace: https://launchpad.net/distros/ubuntu/+source/evolution/+bug/50228 "After importing ics calendar, evolution crashes on startup It crashes at startup because it starts in calendar view, and this is what crashes. Clock-calendar applet chrashes also when trying to display calendar info. In Dapper final, clean install, fully updated. ¿Is there any way to delete calendar data so I can start evolution? http://librarian.launchpad.net/3085487/gdb-evolution.txt gdb Backtrace http://librarian.launchpad.net/3085492/ev Bug buddy http://librarian.launchpad.net/3085497/export.ics Imported calendar causing crash ... > Thanks for your bug. Importing that calendar works fine on edgy, could you get a backtrace with evolution-data-server-dbg and evolution-dbg installed? The backtrace looks like http://bugzilla.gnome.org/show_bug.cgi?id=337454 upstream ... http://librarian.launchpad.net/3670407/backtrace_bugbuddy_withdbg Backtrace was generated from '/usr/bin/evolution-2.6' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1231718176 (LWP 3831)] [New Thread -1261872208 (LWP 3833)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 69871
It does not crash at startup anymore, but then again when I reported the bug it was June, so june was displayed at startup... Calendar applet seems to be working ok now. It doesn't crash anymore with this calendar and the events are displayed correctly. I include the backtrace you asked for (I hope it is what you needed. If not, ask again) Thanks. ... http://librarian.launchpad.net/3707597/evolution-2.8-bugreport.txt another backtrace ..." It doesn't happen on my edgy i386 installation but does happen on dapper amd64, the issue seems to be architecture specific. Updating the settings since it happens on GNOME 2.15.90 on amd64 too
Set target milestone to 2.8
Created attachment 93029 [details] [review] proposed eds patch for evolution-data-server; Patch behaves regarding to this citation: ----- start of citation from chapter 4.6.1 of RFC 2445 ----- The "DTSTART" property for a "VEVENT" specifies the inclusive start of the event. For recurring events, it also specifies the very first instance in the recurrence set. The "DTEND" property for a "VEVENT" calendar component specifies the non-inclusive end of the event. For cases where a "VEVENT" calendar component specifies a "DTSTART" property with a DATE data type but no "DTEND" property, the events non-inclusive end is the end of the calendar date specified by the "DTSTART" property. For cases where a "VEVENT" calendar component specifies a "DTSTART" property with a DATE-TIME data type but no "DTEND" property, the event ends on the same calendar date and time of day specified by the "DTSTART" property. ----- end of citation from chapter 4.6.1 of RFC 2445 -----
Chen: Can you get this reviewed for the next dot release?
Looks good to commit.
Committed to trunk. Committed revision 7980.