kpilotDaemon crashing in gutsy and hardy

[Philip Tuckey]

Binary package hint: kdepim

I have just upgraded to the gutsy release candidate.

kpilotDaemon appears to block as soon as it is started, for example :
- the systray icon does not redraw itself
- if in kpilot I click on Settings -> Configure kpilot, then kpilot blocks (e.g. does not redraw itself), presumably waiting on kpilotDaemon

When a sync is started from the handheld, kpilot Daemon crashes. Standard error shows:

*** glibc detected *** kpilotDaemon: double free or corruption (out): 0x08110df0 ***

then backtrace.

In some circumstances I also see:

kpilot: symbol lookup error: /usr/lib/kde3/kcm_kpilot.so: undefined symbol: _ZN17ConduitConfigBase9aboutPageEP7QWidgetP10KAboutData

ProblemType: Bug
Architecture: i386
Date: Wed Oct 17 15:11:15 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/kpilotDaemon
NonfreeKernelModules: nvidia
Package: kpilot 4:3.5.7enterprise20070926-0ubuntu2
PackageArchitecture: i386
ProcCmdline: kpilotDaemon
ProcCwd: /home/pat
ProcEnviron:
 PATH=/home/pat/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: kdepim
Uname: Linux joey 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

[Philip Tuckey (philtuckey)]

I attach the traceback from the kpilotDaemon crash.

Sorry for the vague comment about the kpilot crash:
kpilot: symbol lookup error: /usr/lib/kde3/kcm_kpilot.so: undefined symbol: _ZN17ConduitConfigBase9aboutPageEP7QWidgetP10KAboutData
This happens when, after kpilotDaemon has crashed, I do
Settings -> Configure kpilot
in kpilot.

[Philip Tuckey (philtuckey)]

the gutsy version of kpilot displays this when it starts up:
Version: KPilot 4.9.2-358 (moribund alleycat)
Version: pilot-link 0.12.2
Version: KDE 3.5.7
Version: Qt 3.3.7
It has the problems described in the previous messages.

kpilot from the gutsy kdepim source package recompiled under gutsy says:
Version: KPilot 4.9.2-358 (moribund alleycat)
Version: pilot-link 0.12.2
Version: KDE 3.5.8
Version: Qt 3.3.7
Notice that it now says it was compiled under KDE 3.5.8. However it suffers from the same problems as the gutsy binary.

So then I recompiled the svn code (under gutsy):
svn co svn://anonsvn.kde.org/home/kde/branches/kdepim/enterprise/kdepim/kpilot
cd kpilot
./configure --prefix=/usr --enable-debug=yes
make -f Makefile.cmake
sudo make -f Makefile.cmake install

Now the kpilot window shows:
Version: KPilot 4.9.2-358 (moribund alleycat)
Version: pilot-link 0.12.2
Version: KDE 3.5.8
Version: Qt 3.3.7
and it and the kpilotDaemon work fine.

So is the gutsy kdepim source corrupted somehow?

[dukat (dukat)]

Having kpilot configured ti use device usb:, and settings "Copy handhelp->PC", I can start kpilotDeamon normally and it's responding. However, it always crashes after around 30 seconds.

[dukat (dukat)]

Updated to latest Hardy beta, and Kpilot crashes always with my Treo 680

As soon as the Treo is in the cradle and kpilot deamon starts polling, it crashes.

[dukat (dukat)]

The version in Hardy:

Version: KPilot 4.9.3-359 (palo alto)
Version: pilot-link 0.12.3
Version: KDE 3.5.9
Version: Qt 3.3.8b

[Jason 'vanRijn' Kasper (vr-movingparts)]

@dukat: You are describing a different problem. It's unrelated to this bug. This bug is about KPilot hanging, waiting for a device connection, and nothing being responsive.

@Philip: Hi there! =:) I believe that this bug was about using KPilot from < KDE 3.5.10 with "usb:" as the device string? Yeah, the problem was that libusb blocks when KPilot tries to connect to "usb:" and it doesn't timeout and it doesn't release. It looks to KPilot like there's a valid connection, so KPilot was blocking and waiting for the handshake to complete, which, obviously, it never did. I fixed this in KDE 3.5.10, iirc. One workaround would be to use the old /dev/ttyUSB1, or the other would be to upgrade to KDE 3.5.10.

Sorry for the bug!! =:(

[Jonathan Thomas (echidnaman)]

Fixed in KDE 3.5.10 -> closing as fixed released.
Thanks for the info!

[Felipe Figueiredo (philsf)]

Not fixed for me. I experience the bug daily. I'm not using usb: anymore, but net:, since I connect my Palm TX via Wifi.

I'm using version 4:3.5.10-0ubuntu1~hardy3, from hardy-updates.

This even keeps me from rebooting/shutting down the box, unless I kill kpilotDaemon first.