After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 356842 - gpilotd crashes while synchronizing Date Book
gpilotd crashes while synchronizing Date Book
Status: RESOLVED FIXED
Product: gnome-pilot
Classification: Other
Component: gpilotd
2.0.x
Other All
: Normal critical
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-20 05:19 UTC by Daniel Hackney
Modified: 2006-09-22 09:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Hackney 2006-09-20 05:19:26 UTC
Steps to reproduce:
1. Enable the calendar sync from gnome-pilot settings
2. Start gpilotd from the command line
3. Press HotSync on the palm


Stack trace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1225406800 (LWP 6331)]
0xb74d8cea in pi_buffer_clear () from /usr/lib/libpisock.so.9
(gdb) thread apply all bt

Thread 7 (Thread -1269195872 (LWP 6374))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_unlock_wake
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 _L_mutex_unlock_269
    from /lib/tls/i686/cmov/libpthread.so.0
  • #3 ??
    from /usr/lib/libecal-1.2.so.7
  • #4 g_thread_use_default_impl
    from /usr/lib/libglib-2.0.so.0
  • #5 ??
  • #6 ??
  • #7 e_cal_new_system_calendar
    from /usr/lib/libecal-1.2.so.7
  • #8 e_cal_new_system_calendar
    from /usr/lib/libecal-1.2.so.7
  • #9 e_cal_marshal_VOID__INT_POINTER
    from /usr/lib/libecal-1.2.so.7
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 e_cal_listener_new
    from /usr/lib/libecal-1.2.so.7
  • #15 _ORBIT_skel_small_GNOME_Evolution_Calendar_CalListener_notifyChanges
    from /usr/lib/libecal-1.2.so.7
  • #16 IOP_start_profiles
    from /usr/lib/libORBit-2.so.0
  • #17 ORBit_OAObject_invoke
    from /usr/lib/libORBit-2.so.0
  • #18 ORBit_small_invoke_adaptor
    from /usr/lib/libORBit-2.so.0
  • #19 ORBit_recv_buffer_return_sys_exception
    from /usr/lib/libORBit-2.so.0
  • #20 ORBit_recv_buffer_return_sys_exception
    from /usr/lib/libORBit-2.so.0
  • #21 giop_thread_queue_process
    from /usr/lib/libORBit-2.so.0
  • #22 giop_init
    from /usr/lib/libORBit-2.so.0
  • #23 g_thread_pool_push
    from /usr/lib/libglib-2.0.so.0
  • #24 g_thread_create_full
    from /usr/lib/libglib-2.0.so.0
  • #25 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #26 clone
    from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread -1225406800 (LWP 6331))

  • #0 pi_buffer_clear
    from /usr/lib/libpisock.so.9
  • #1 dlp_ReadAppBlock
    from /usr/lib/libpisock.so.9
  • #2 conduit_get_gpilot_conduit
    from /usr/lib/evolution/2.8/conduits/libecalendar_conduit.so
  • #3 gtk_marshal_INT__POINTER
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #7 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 gnome_pilot_conduit_sync_abs_new
    from /usr/lib/libgpilotdconduit.so.2
  • #9 sync_Synchronize
    from /usr/lib/libpisync.so.0
  • #10 gnome_pilot_conduit_sync_abs_new
    from /usr/lib/libgpilotdconduit.so.2
  • #11 gnome_pilot_conduit_standard_new
  • #12 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emitv
    from /usr/lib/libgobject-2.0.so.0
  • #16 gnome_pilot_conduit_standard_synchronize
    from /usr/lib/libgpilotdconduit.so.2
  • #17 gpilot_synchronize
  • #18 gpilot_unload_conduits
  • #19 gpilot_sync_default
  • #20 _start


Other information:
I am using a Palm z22 on Ubuntu Edgy i386 on an Athlon 64 X2 3800+.
Comment 1 Matt Davey 2006-09-20 07:45:51 UTC
Thanks for this bug report.

Please let us know the package versions for the following components:
gnome-pilot, pilot-link and evolution.

From your back trace, it appears that you are using pilot-link 0.12.x, which is pretty new.  There isn't an official release of evolution that supports pl 0.12.0, so there may be some glitches with the (presumably) patched version you have installed.
Comment 2 Carlos Castillo 2006-09-20 11:28:36 UTC
Same here. This used to work fine, but it started to crash after the last upgrade. I moved from Ubuntu Dapper to Edgy and it worked fine, then recently it seems that the last upgrade of evolution broke this.

All the other conduits work fine, except for EAddress, ECalendar and EToDo. Tried with setting them to 'Copy to PDA' but gpilotd still crashes.

Versions:

- Evolution package: 2.8.0-0ubuntu2
- Gnome-pilot package: 2.0.14-0ubuntu1

Here is the stack trace from gpilotd when it crashes while trying to use the ECalendar conduit:

=============================================================

Memory status: size: 66498560 vsize: 0 resident: 66498560 share: 0 rss: 32497664 rss_rlim: 0
CPU usage: start_time: 1158751328 rtime: 0 utime: 72 stime: 0 cutime:67 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/gnome-pilot'

(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 -1225009488 (LWP 15253)]
[New Thread -1234269280 (LWP 15286)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225009488 (LWP 15253))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 pi_buffer_clear
    from /usr/lib/libpisock.so.9
  • #5 dlp_ReadAppBlock
    from /usr/lib/libpisock.so.9
  • #6 conduit_get_gpilot_conduit
    from /usr/lib/evolution/2.8/conduits/libecalendar_conduit.so
  • #7 gtk_marshal_INT__POINTER
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gnome_pilot_conduit_sync_abs_new
    from /usr/lib/libgpilotdconduit.so.2
  • #13 sync_Synchronize
    from /usr/lib/libpisync.so.0
  • #14 gnome_pilot_conduit_sync_abs_new
    from /usr/lib/libgpilotdconduit.so.2
  • #15 gnome_pilot_conduit_standard_new
    from /usr/lib/libgpilotdconduit.so.2
  • #16 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emitv
    from /usr/lib/libgobject-2.0.so.0
  • #20 gnome_pilot_conduit_standard_synchronize
    from /usr/lib/libgpilotdconduit.so.2
  • #21 gpilot_synchronize
  • #22 gpilot_unload_conduits
  • #23 gpilot_sync_default
  • #24 _start
  • #0 __kernel_vsyscall

=========================================================

Thank you for your time.
Comment 3 Daniel Hackney 2006-09-20 12:23:36 UTC
Oh, sorry about not including app version info. I'm kind of new at bugzilla bla bla.

gnome-pilot 2.0.13-0ubuntu16
pilot-link 0.12.1-3
evolution 2.8.0-0ubuntu1

So yeah, I am definitely using pilot-link 0.12.1 which I saw was the first release in about 3 years, so I can understand some changes and bugs with that. Let me know if there is anything else I can do to help, since I really would like this to work.
Comment 4 Daniel Holbach 2006-09-20 13:40:51 UTC
Can you try to upgrade to gnome-pilot 2.0.14 and try again? According to https://launchpad.net/distros/ubuntu/+source/gnome-pilot/2.0.14-0ubuntu1 and https://launchpad.net/distros/ubuntu/+source/gnome-pilot-conduits/2.0.14-0ubuntu1 they built correctly for all arches.
Comment 5 Daniel Hackney 2006-09-20 15:05:17 UTC
Okay, I tried that, and now I have gnome-pilot 2.0.14 up and running. The same problem still occurs though. I did notice that when it crashes, the last line complains about not being able to find "/usr/libexec/gnome-pilot" which does not exist. Here is a full output from the command line:

$ gpilotd
gpilotd-Message: gnome-pilot 2.0.14 starting...
gpilotd-Message: compiled for pilot-link version 0.12.1
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network] 
GTK Accessibility Module initialized
Bonobo accessibility support initialized
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Watching Cradle (/dev/ttyUSB1)
gpilotd-Message: Found 4766, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0502, 0736
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 091e, 0004
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 115e, f100
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0100
gpilotd-Message: Using net FALSE
gpilotd-Message: Found 082d, 0200
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0300
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0c88, 0021
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0002
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0003
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0020
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0031
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0040
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0050
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0060
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0061
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0070
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0080
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 8001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 6601
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0038
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0066
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0095
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 009a
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00c9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00da
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00e9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0144
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0169
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 12ef, 0100
gpilotd-Message: Using net TRUE
gpilotd-Message: setting PILOTRATE=57600
gpilotd-Message: Device Cradle has 0 events
gpilotd-Message: Instantiating 3 conduits...
ecalconduit-Message: in calendar's conduit_get_gpilot_conduit

etodoconduit-Message: in todo's conduit_get_gpilot_conduit

gpilotd-Message: Instantiated 1 backup conduits, 0 file conduits, 2 other conduits
gpilotd-Message: HotSync button pressed, synchronizing PDA
gpilotd-Message: PDA ID is 1000, name is mobile-hax, owner is Daniel Hackney
gpilotd-Message: Pilot has 0 entries in restore queue
gpilotd-Message: Pilot has 0 entries in conduit queue
backupconduit-Message: CarrierProfiles2 not modified since last sync
backupconduit-Message: Making backup of ContactsDB-PAdd
backupconduit-Message: Wrote 208 of 208 records, which is good
backupconduit-Message: CalendarDB-PDat not modified since last sync
backupconduit-Message: MemosDB-PMem not modified since last sync
backupconduit-Message: TasksDB-PTod not modified since last sync
backupconduit-Message: Queries not modified since last sync
backupconduit-Message: Making backup of AddressDB
backupconduit-Message: Wrote 208 of 208 records, which is good
ecalconduit-Message: ---------------------------------------------------------

ecalconduit-Message: pre_sync: Calendar Conduit v.0.1.6
ecalconduit-Message:   Using timezone: /softwarestudio.org/Olson_20011030_5/America/New_York
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized

** (bug-buddy:8044): WARNING **: Couldn't load icon for Decrypt File

** (bug-buddy:8044): WARNING **: Couldn't load icon for Import Key

** (bug-buddy:8044): WARNING **: Couldn't load icon for Open Folder

** (bug-buddy:8044): WARNING **: Couldn't load icon for Verify Signature
/usr/libexec/gnome-pilot: No such file or directory.
application finalize called
Comment 6 Carlos Castillo 2006-09-20 15:16:34 UTC
I also use gnome-pilot 2.0.14 and got the same messages in the output of gpilotd.

@Daniel: messages after 'GTK Accessibility Module initialized' including the one about /usr/libexec/gnome-pilot are generated by bug-buddy, not by gpilotd.

Here is my output from gpilotd:

===============================================================================

ecalconduit-Message: ---------------------------------------------------------

ecalconduit-Message: pre_sync: Calendar Conduit v.0.1.6
ecalconduit-Message:   Using timezone: /softwarestudio.org/Olson_20011030_5/Europe/Madrid

** (bug-buddy:27770): WARNING **: Couldn't load icon for Decrypt File

** (bug-buddy:27770): WARNING **: Couldn't load icon for Import Key

** (bug-buddy:27770): WARNING **: Couldn't load icon for Open Folder

** (bug-buddy:27770): WARNING **: Couldn't load icon for Verify Signature
Comment 7 Daniel Holbach 2006-09-20 21:42:31 UTC
I uploaded 2.8.0-0ubuntu3 with a patch that Matt pointed me to - it has not built this minute, but should be in the archive later, please test with that patch (https://launchpad.net/distros/ubuntu/+source/evolution/2.8.0-0ubuntu3)
Comment 8 Daniel Holbach 2006-09-21 15:44:37 UTC
Re: gpilotd crashes when syncing adresses/calendar/todo from Martin Albisetti at 2006-09-21 17:30:45 CEST

I can confirm the latest update to evolution fixes this problem.
Thank you very much ;D
Comment 9 Matt Davey 2006-09-21 16:02:43 UTC
Congratulations!

You now have the first official working release of gnome-pilot 2.0.14, pilot-link 0.12.x and evolution conduits.  A first for Ubuntu...
Comment 10 Daniel Holbach 2006-09-21 16:14:06 UTC
Thanks for all your work.
Comment 11 Daniel Hackney 2006-09-21 19:53:32 UTC
Works wonderfully, thanks!
Comment 12 Carlos Castillo 2006-09-22 09:11:18 UTC
evolution/2.8.0-0ubuntu3 fixed this problem for me also. Thank you very much.