[Bug 17774] gnome-pilot sync crashes evolution-data-server

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=17774
Ubuntu | evolution-data-server





------- Additional Comments From sphillips53 at gmail.com  2005-10-29 07:03 UTC -------
I had the same problem with evolution data server crashing when running
gnome-pilot. When I tried to reproduce it after I had done a system update early
on the morming of 10/29/05 the crash of th evolution data server did not occur.
I did not note which files were updated, but after the update gnome-pilot
synchronized with evolution without problem when just the conduits for EAddress,
ECalendar, and EToDo were enabled.  However when Backup was enabled gpilotd
itself crashed with the following backtrace:
Backtrace was generated from '/usr/bin/gpilotd'

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1224735040 (LWP 7003)]
[New Thread -1241957456 (LWP 7172)]
[New Thread -1233564752 (LWP 7165)]
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb736d4ab in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7ec0508 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#3  <signal handler called>
#4  0xfffa14e1 in ?? ()
#5  0xbff49368 in ?? ()
#6  0x00000026 in ?? ()
#7  0xbff4933c in ?? ()
#8  0xb72db270 in ?? () from /usr/lib/libpisock.so.8
#9  0x080eeeb8 in ?? ()
#10 0x00000026 in ?? ()
#11 0xbff49378 in ?? ()
#12 0xb72c5a82 in dlp_ReadResourceByIndex () from /usr/lib/libpisock.so.8


-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.