GNOME Bugzilla – Bug 270431
gpilotd crashed while syncing calendar
Last modified: 2013-09-13 12:22:29 UTC
Distribution: SuSE Linux 9.2 (i586) Package: Evolution Priority: Normal Version: GNOME2.6. 2.0.12 Gnome-Distributor: SUSE Synopsis: gpilotd crashed while syncing calendar Bugzilla-Product: Evolution Bugzilla-Component: Gnome-pilot & pilot-link Bugzilla-Version: 2.0.12 BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: gpilotd crashed while syncing calendar Steps to reproduce the crash: 1. install evolution pilot conduits 2. sync with pilot 3. kaboom Expected Results: correct termination How often does this happen? first time I tried it Additional Information: Debugging Information: Backtrace was generated from '/usr/local:/opt/gnome:/usr/libexec/gpilotd' (no debugging symbols found)...Using host libthread_db library "/lib/tls/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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1089550336 (LWP 15027)] [New Thread 1112841136 (LWP 15273)] [Thread debugging using libthread_db enabled] [New Thread 1089550336 (LWP 15027)] [New Thread 1112841136 (LWP 15273)] [Thread debugging using libthread_db enabled] [New Thread 1089550336 (LWP 15027)] [New Thread 1112841136 (LWP 15273)] [New Thread 1110739888 (LWP 15272)] (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)...0xffffe410 in ?? ()
+ Trace 53380
Unknown version 2.0.12 in product Evolution. Setting version to the default, "unspecified". Unknown reporter: pgs@intellivid.com, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
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. (Looks somewhat similar to bug 166072, though)
since evolution 2.0.x is not maintained/patched anymore, moving all target milestones at least to 2.2.x. sorry for the noise. reassigning to vvaradhan.
no response, therefore closing as INCOMPLETE. please feel free to reopen when adding more comments; thanks for reporting anyway.
Sorry, I didn't see earlier questions about this. I don't have symbols in my build, but i can offer you something I hope will be better. I have a calendar.ics file that, when imported into an empty calendar in Evolution (versions that shipped with Suse 9.3), causes the gpilotd crash on the first sync afterwards. Note that after the first crash it doesn't crash again but exits silently without syncing calendars. I won't attach the calendar.ics file here, because it's my personal calendar and has 6 or 7 years' worth of personal info in it and I don't want it posted on the Web. However, if a developer wants to use the file for debugging without posting it on this Web site, I'd be happy to send it.
pgs: Thanks for the bug update. You could send it to vvaradhan@novell.com and I will make sure the privacy is secured. :)
pertty similar stacktrace to bug 274490 and 306694 which is a dup of bug 303702. *** This bug has been marked as a duplicate of 303702 ***