kpilot crashes at sync

[Isaac Kriegman]

Binary package hint: kpilot

When trying to sync my treo 650, kpilot crashes.

It worked fine before I upgraded to dapper.

I tested it once on dapper and it seemed to work.

Next time I logged in it kpilotDaemon crashed at startup (before trying to sync or even connection my treo).

Everytime I started kpilot, kpilotDaemon would crash before doing anything.

I removed all the kpilot related configuration files from .kde/share/config and .kde/share/apps, and tried again.

However now it crashes when trying to detect my palm pilot. If I skip that step, it can successfully begin a sync, but crashes in the middle of it.

Overall a seemingly stable application has turned into a nightmare once I upgraded to dapper.

[Lynoure Braakman (lynoure)]

Actually crashes or stops responding? I'm asking because the latter also happens with me.

[Isaac Kriegman (kriegman)]

It actually crashes.

Lynoure Braakman wrote:
> Actually crashes or stops responding? I'm asking because the latter also
> happens with me.
>
>

[Elaine Normandy (elainen)]

Kpilot crashes for me too under dapper: worked fine under breezy. I use a T3.

[Elaine Normandy (elainen)]

more details:

1. will attempt to identify user and then crash after warm reboot

2. when attempting to start other than after a warm reboot, it just crashes.

[simonmarsden (simon-marsden)]

Same problems here. I can get it to sync sporadically after a reboot of the pc normally. I notice in /var/log/messages
usb 4-2: Handspring Visor / Palm OS converter now attached to ttyUSB0
usb 4-2: Handspring Visor / Palm OS converter now attached to ttyUSB1
then after trying to get it to work again
usb 4-2: Handspring Visor / Palm OS converter now attached to ttyUSB2
usb 4-2: Handspring Visor / Palm OS converter now attached to ttyUSB3

Obviously if device in kpilot is set to ttyUSB1 then it is going to get a bit confused here. Like previous posts I had this working in breezy with treo 650.

[ville palo (vi64pa)]

I think this can be confirmed because this seems to be reproducible on other systems too.

[Rich Johnson (nixternal)]

I cannot confirm this as I use KPilot on a daily basis. Is this still an issue with Edgy and/or Feisty up to date? Thanks!

[Edney Matias da Silva (edney)]

kpilotDaemon also crashes on edgy. I'm trying to sync a Palm Treo 650, but when kpilot try to write Date Book back to the Palm, the daemon crashes. I've tried to get some debug information with gdb, but i'm not that bug hunter, so i'm attaching the output i got. Any advice would be great, and i can attach anything else needed, just say what and how to get there!

Thank you!

[jerf (jerf-jerf)]

kpilot crashes on gutsy. I start it up for the first time and use the wizard, click "automatically detect handheld and user name", then hit the synchronize button. It seems to extract the user, then crashes with an error in the threading library. (There's no other useful information in the trace.)

[Sarah Kowalik (hobbsee-deactivatedaccount)]

Is this still an issue in gutsy? There's no backtrace, so...

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems. <http://wiki.ubuntu.com/DebuggingProcedures> Thanks!

[Launchpad Janitor (janitor)]

[Expired for kdepim (Ubuntu) because there has been no activity for 60 days.]

[dukat (dukat)]

The daemon crashed on gutsy always after about 30 seconds without doing anything. I've configured Kpilot to use device usb: and to to jhadhelp->pc copy. Sometime I get lucky and I can achieve this before the daemon crashes.

[Jonathan Anderson (jonathan-anderson)]

I also get Gutsy crashes (a LOT), and here's the backtrace.

[JohnL (jwillar)]

My situation seems to be relevant; this has been posted on the Ubuntu-KDE-PIM site as well.

Apparently this task is beyond my abilities and I need help. I recently purchased a new Palm TX and want to sync it with the KDE-PIM suite Kontact (calendar, contacts, notes, to-do, email). I am using KPilot (4.9.2-358 for KDE 3.5.8) on Kubuntu (7.10-Gutsy). Here are the results of my current configuration. I am willing to provide any additional information when requested.

> Palm cradle is connected directly by USB to my DELL Latitude D820 Laptop (not through a USB hub or docking station).
> Palm HotSync is configured to connect to the 'PC' via the 'Cradle/Cable' at a speed of '9,600 bps' while set to 'Automatic' Flow Control.
> KPilot 'Wizard' failed at 30% reporting KPilot crashed was caused by a signal 11 (already reported multiple time on Bug list w/o solution). Back to the Wizard configuration screen, I set my Use name to 'john' (as listed on the Palm HotSync screen) and set Device to '/dev/ttyUSB3'. I saved these setting by selecting 'Next' then 'Finish' (default set to 'KDE-PIM suite') in order to create '/dev/pilot'.
> The file '/dev/pilot' points to 'ttyUSB3'.
> The file '/dev/ttyUSB3' permissions are set to 'Can Read & Write' for 'Others'.
> Linked Palm device to the correct USB port using 'ln -s /dev/ttyUSB3 /dev/pilot'
> ensured permissions by 'chmod 666 /dev/ttyUSB3'
> Inserted the following line in '/etc/udev/rules.d/10-custom.rules'.
 BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB*", NAME{ignore_remove}="pilot", MODE="666"
> Inserted the word 'Visor' after the last line in '/etc/modules'.

After rebooting and the KPilot Daemon in my taskbar tray, I opened Konsole and entered 'tail -f /var/log/messages' to see how the above configuration worked while attempting to HotSync my Palm device; results follow:

> With the Palm resting in the cradle. The following lines list in the Konsole:
Nov 23 07:35:14 john-laptop kernel: [34783.644000] usb 4-1: Handspring Visor / Palm OS converter now attached to ttyUSB3
Nov 23 07:42:58 john-laptop kernel: [35247.460000] usb 4-1: USB disconnect, address 8
Nov 23 07:42:58 john-laptop kernel: [35247.460000] visor ttyUSB2: Handspring Visor / Palm OS converter now disconnected from ttyUSB2
Nov 23 07:42:58 john-laptop kernel: [35247.460000] visor ttyUSB3: Handspring Visor / Palm OS converter now disconnected from ttyUSB3
Nov 23 07:42:58 john-laptop kernel: [35247.460000] visor 4-1:1.0: device disconnected
Nov 23 07:44:27 john-laptop kernel: [35336.520000] usb 4-1: new full speed USB device using uhci_hcd and address 9
Nov 23 07:44:28 john-laptop kernel: [35336.692000] usb 4-1: configuration #1 chosen from 1 choice
Nov 23 07:44:28 john-laptop kernel: [35336.696000] visor 4-1:1.0: Handspring Visor / Palm OS converter detected
Nov 23 07:44:28 john-laptop kernel: [35336.696000] usb 4-1: Handspring Visor / Palm OS converter now attached to ttyUSB2
Nov 23 07:44:28 john-laptop kernel: [35336.696000] usb 4-1: Handspring Visor / Palm OS converter now attached to ttyUSB3

> Pressing the Palm HotSync button, Palm reports “Connecting with desktop using Cradle/Cable”. The following lines list in th...

[JohnL (jwillar)]

If I only tried a few minutes more. I got my Palm TX to sync with Kontacts vis KPilot.

From my Palm - HotSync screen I changed my settings from 'Local' and 'Cradle/Cable' to 'Local' and 'john-laptop' (my computer's name). To set this permanently on my Palm, I edited the Connection (John-Laptop) to connect to my 'PC' via “Cradle/Cable'. Selecting the details, I set the speed to '19200' with 'Automatic' flow control. Then in KPilot, I set the speed to match '19200'. The speed settings were match and set slower to enable a successful sync.

One more comment, make sure your Palm 'contacts' match those in 'Kontacts'. By default, Palm only had Friends/Business where I had many more in Kontact. After the sync was complete, most of my contacts on my Palm were “undefined”.

 I hope this prove useful to others, good luck.

JohnL

[[redacted] (frozenfire-deactivatedaccount)]

Mine crashes too:
nathan@lion:~$ kpilot
nathan@lion:~$ QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such signal KPilotDeviceLink::deviceReady(KPilotDeviceLink*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'unnamed')
QObject::conn...

[Jonathan Thomas (echidnaman)]

Hi,
We were wondering if this was still an issue in KDE 4.2 and/or Kubuntu 9.04.
Thanks in advance!

[Isaac Kriegman (zackriegman)]

I have no idea. Haven't used kpilot for years.

On Jun 20, 2009 6:05 PM, "Jonathan Thomas" <email address hidden> wrote:

Hi,
We were wondering if this was still an issue in KDE 4.2 and/or Kubuntu 9.04.
Thanks in advance!

** Changed in: kdepim (Ubuntu)
      Status: Confirmed => Incomplete

-- kpilot crashes at sync https://bugs.launchpad.net/bugs/48550 You received
this bug notification...

[Jonathan Thomas (echidnaman)]

Ok, thanks. We can always reopen this if the issue re-occurs.