Palm Sync Crashes with calendar conduit in Evolution

Thanks for your bug report. Which version of Ubuntu do you use?

I use Edgy Eft

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash (having gnome-pilot-conduits-dbgsym, libgnome-pilot2-dbgsym, gnome-pilot-dbgsym, libgtk2.0-0-dbg installed) or get the crash report from /var/crash and attach the file to the bug report. This will greatly help us in tracking down your problem.

I'm experiencing a similar issue, only it doesn't actually crash. What happens is the palm will time out and throw a "connection failed" error, while the hotsync progress dialog on the computer continues indefinitely, stuck on synchronizing ECalendar. I have to do a "killall gpilotd gpilot-control-applet gpilot-applet" to restore hotsync functionality. As this is not an actual crash I don't think there's any debugging symbols, but this seems to be a related issue. I'm running Ubuntu Feisty Fawn and trying to synchronize a Handspring Visor Prism using the USB cradle. I've got the port set to usb:, but I've also tried running "modprobe visor" and setting it to ttyUSB0/1, with the same results.

Not sure if this is the same bug, but I am finding a similar issue with gpilotd on gutsy.

It's definitely an evolution calendar problem because if I switch that conduit off it syncs fine.

The error message I am getting at the end of the sync is as follows:-

gpilotd-Message: Synchronisation ended
DEV TX Inet Bytes: 37
NET TX sd=15 type=1 txid=0xd0 len=0x001f
  0000 2a 01 20 1b 53 79 6e 63 68 72 6f 6e 69 7a 61 74 *. .Synchronizat
  0010 69 6f 6e 20 63 6f 6d 70 6c 65 74 65 64 20 00 ion completed .
DEV RX Inet Bytes: 6
DEV RX Inet Bytes: 4
NET RX sd=15 type=1 txid=0xd0 len=0x0004
  0000 aa 00 00 00 ....
DEV TX Inet Bytes: 42
NET TX sd=15 type=1 txid=0xd1 len=0x0024
  0000 11 01 20 20 00 00 03 e8 00 00 00 00 b1 0f a6 01 .. ............
  0010 07 d7 08 1b 0d 1e 32 00 ff 0a 41 6c 61 6e 20 50 ......2...Alan P
  0020 6f 70 65 00 ope.
DEV RX Inet Bytes: 6
DEV RX Inet Bytes: 4
NET RX sd=15 type=1 txid=0xd1 len=0x0004
  0000 91 00 00 00 ....

(gpilotd:29225): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Segmentation fault (core dumped)

I have the same problem with the Gutsy beta (fully updated), a Treo 680 and gnome-pilot-conduits. Feisty sometimes synced alright (even though this was somehow buggy), but Gutsy does not do at all. Hangs when syncing calendar.

Provided that this bug does not have anything to do with an individual hardware error on my side: Maybe the Palm sync should not be a standard prog in Ubuntu until all issues are solved?

Anyone interested in answering to my proposal?

Any progress on this bug? I'm not sure if this is the same bug as I am seeing, but I believe I am seeing the same thing on Fedora 9. I am attaching the bug report which was automatically generated.

This happens any time there is an actual change in my Evolution address book which is being synced to the Tungsten E. It is 100% repeatable, and completely prevents any useful syncing with the Palm.

....
backupconduit-Message: Net Prefs not modified since last sync
backupconduit-Message: Security_scrt_panl_a68k not modified since last sync
backupconduit-Message: Setup_setp_appl_a68k not modified since last sync
backupconduit-Message: ShortCuts_shct_panl_a68k not modified since last sync
backupconduit-Message: System MIDI Sounds not modified since last sync
backupconduit-Message: Splash-splH_appl_a68k not modified since last sync
backupconduit-Message: Making backup of Saved Preferences
backupconduit-Message: Wrote 22 of 22 resources, which is good
backupconduit-Message: AddressStatesDB not modified since last sync
backupconduit-Message: AddressTitlesDB not modified since last sync
backupconduit-Message: To Do List_todo_appl_a68k not modified since last sync
backupconduit-Message: VendorsDB not modified since last sync
gpilotd-Message: Synchronization ended

(gpilotd:6426): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
1da8fa1c-99bb-64f4-42234f3c-2641a5c7 is dumped
Segmentation fault

Asking once again: Provided that this bug does not have anything to do with an individual hardware error on my side: Maybe the Palm sync should not be a standard prog in Ubuntu until all issues are solved?

I have also tried to sync my new Palm Centro and the palm crashes (resets) when the calendar (aka datebook) conduit runs. Any progress on this bug?

I just got a Palm Centro and am running Hardy Heron Netbook version. When I tried to sync it just froze on the datebook sync. I finally had to reboot my phone. I hope there is a fix for this soon.

I'm using Ubuntu 8.04 and had similar irritating problems synchronising my Palm Tungsten E2 to Evolution via the USB cable link. It kept on timing out because the calendar sync didn't complete properly. I have now found a work around that works every time:
-with the computer up and running, turn on the E2;
-connect the USB smart cable with the sync button;
-start the gnome-pilot PDA service; press the cable button.
It works every time, but curiously if you change the connection order round the calendar sync times out or sometimes completes at a second attempt.

Thank you for reporting this bug.

Does this issue exist in Lucid?

Unfortunately, I am unable to tell at the moment as I have switched from Gnome to KDE and am no longer using Evolution. If I get a chance I will load up a liveCD and test whether this bug is still present. I apologize for not being able to provide more information.

On Tuesday 14 September 2010 1:11:12 am you wrote:
> Thank you for reporting this bug.
>
> Does this issue exist in Lucid?
>
>

Sorry, don't know. Things got so bad with the Palm phone itself, I switched
carriers and got a Droid.

Best regards,

On Tue, Sep 14, 2010 at 4:11 AM, rusivi1 <email address hidden> wrote:

> Thank you for reporting this bug.
>
> Does this issue exist in Lucid?
>
> --
> Palm Sync Crashes with calendar conduit in Evolution
> https://bugs.launchpad.net/bugs/73733
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Dave Busse
<email address hidden>
http://www.dbusse.org

I gave up and now sync on my Macbook Pro.