GNOME Bugzilla – Bug 413973
syncing gnome-pilot crashes evolution data server
Last modified: 2013-09-13 12:24:53 UTC
Distribution: Debian 4.0 Package: Evolution Severity: major Version: GNOME2.14.3 2.6.x Gnome-Distributor: Debian Synopsis: syncing gnome-pilot crashes evolution data server Bugzilla-Product: Evolution Bugzilla-Component: Gnome-pilot & pilot-link Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: Crash on syncing calendars. This may be involved in the specific calendar setup I have here - on Exchange, there is the personal calendar as well as a group calendar. I'd expect it to sync the former, but skip the latter. If it does that, then there's something specific in my appts. Which is kinda funny, since I created them by syncing in from the palm pilot in the first place. Steps to reproduce the crash: 1. open evolution, wait for filtering to complete 2. hit sync on palm cradle 3. wait. Expected Results: Well, it'd be nice if it actually synced properly. :-) How often does this happen? 100% of the time. It used to happen sometimes, and I could get past it if I restarted evolution entirely (--force-shutdown, then start it up again) but for the last 6 months or so, it's been every time. Debugging Information: Backtrace was generated from '/usr/libexec/evolution-exchange' (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 -1233770816 (LWP 31945)] [New Thread -1274025040 (LWP 32746)] [New Thread -1234396240 (LWP 31946)] (no debugging symbols found) 0xb7f49410 in ?? ()
+ Trace 115278
------- Bug created by bug-buddy at 2007-03-02 19:49 -------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Being on debian/testing (mostly), I followed instructions, and added: evolution-data-server-dbg, evolution-dbg, libglib1.2-dbg, libgnomeui-0-dbg, libgnomevfs2-0-dbg, libgtk2.0-0-dbg, libgtkhtml3.8-dbg However, this didn't change the critical segment of the backtrace - ie, the start of it. LD_LIBRARY_PATH=/usr/lib/debug evolution .. and it locked up. Running gpilotd in the same manner, with evolution running normally, caused evolution-data-server to die, immediately following gpilotd returning: ----- ecalconduit-Message: --------------------------------------------------------- ecalconduit-Message: pre_sync: Calendar Conduit v.0.1.6 ecalconduit-Message: Using timezone: /softwarestudio.org/Olson_20011030_5/Europe/London ecalconduit-Message: Authenticating calendar ----- Running both in debug gave me: ----- Backtrace was generated from '/usr/libexec/evolution-exchange' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233910080 (LWP 27834)] [New Thread -1276118096 (LWP 16783)] [New Thread -1234535504 (LWP 27836)] 0xb7f27410 in ?? ()
+ Trace 116156
Which says to me there's still something missing. So... compiling evolution-exchange as per http://wiki.debian.org/HowToGetABacktrace gave me a deb to install. With that, and both evolution and gpilotd started in debug mode gave me much the same, with gnome-pilotd rather than exchange-storage as the culprit. At this point, having spent two and ahalf hours on this, I've given up for the night. Any suggestions for next moves would be gratefully accepted. I think my next step will be a debug build of gnome-pilotd. More details tomorrow night.
This bug is currently fixed in SVN trunk. Is it possible to try with current SVN trunk? or if you can apply the patch attached to bug#393029 to your version and try, that would let us close this bug. TIA.
That fixed it. Patching evolution-exchange-2.6.3.dfsg-1 worked just fine. Close away :) I'll pass this across to the debian maintainer, along with my compliments. :)
Closing as fixed then.