Version: kdepim-3.5.8 (using KDE 3.5.9) Installed from: Ubuntu Packages Compiler: gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) export DEB_BUILD_OPTIONS="debug nostrip noopt" OS: Linux I added this remote resource to korganizer: webcal://calagator.org/events.ics name: remote resource read-only automatic reload: never automatic save: never upload-to is blank I then do a hotsync with my Treo. kpilotDaemon crashes. If I uncheck the box next to "remote resource" sync occurs properly. I built kpilotDaemon with debugging symbols using this process: 501 sudo apt-get install devscripts fakeroot 502 dpkg --search kpilotDaemon 503 sudo apt-get install devscripts fakeroot 504 sudo apt-get build-dep kpilot 505 export DEB_BUILD_OPTIONS="debug nostrip noopt" 506 fakeroot apt-get source -b kpilot 509 cd kdepim-3.5.8/ 531 ./debian/tmp/usr/bin/kpilotDaemon --debug 1 --nofork >/tmp/kpilot.log 2>&1 532 ls /home/cdawson/.kde/share/apps/kcal/uidmaps/ 533 ls -la /home/cdawson/.kde/share/apps/kcal/uidmaps/ I then ran kpilotDaemon with this command: ./debian/tmp/usr/bin/kpilotDaemon --debug 1 --nofork >/tmp/kpilot.log 2>&1 cdawson@moema:~$ tail -f /tmp/kpilot.log setupWidget: Finished getting icons PilotDaemon: The daemon is ready with status PilotDaemon=Waiting for sync; Ne xtSync=HotSync (KPilotDeviceLink=DeviceOpen); (5) showTray: Tray icon displayed. startHotSync: Starting Sync with type HotSync startHotSync: Status is Waiting for sync isSyncPossible: Could not call KPilot for status. shouldBackup: Backup Frequency is: [0]. shouldBackup: Should do backup... exec: User name set to pc <Xhris Dawson> hh <Xhris Dawson> exec: Installing 0 files QThread object destroyed while thread is still running. ASSERT: "!name.isEmpty()" in /build/buildd/kdelibs-3.5.8/./kdecore/kinstance.cpp (76) libkcal: ERROR: Can't read uid map file '/home/cdawson/.kde/share/apps/kcal/uidmaps/remote_mO3tebyvE3' libkcal: ERROR: Can't read uid map file '/home/cdawson/.kde/share/apps/kcal/uidmaps/remote_mO3tebyvE3' KCrash: Application 'kpilotDaemon' crashing... There is no file named: /home/cdawson/.kde/share/apps/kcal/uidmaps/remote_mO3tebyvE3 Backtrace from non-debug build: (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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1235765568 (LWP 7819)] [New Thread -1237525616 (LWP 7820)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xb57b758c in PCToHHState::handleRecord () from /usr/lib/kde3/conduit_vcal.so #7 0xb57b43ee in VCalConduitBase::slotProcess () from /usr/lib/kde3/conduit_vcal.so #8 0xb57b4452 in VCalConduitBase::qt_invoke () from /usr/lib/kde3/conduit_vcal.so #9 0xb57aec0b in VCalConduit::qt_invoke () from /usr/lib/kde3/conduit_vcal.so #10 0xb6e27893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #11 0xb71b38ec in QSignal::signal () from /usr/lib/libqt-mt.so.3 #12 0xb6e47842 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #13 0xb6e4f258 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #14 0xb6dbeaf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #15 0xb6dc091f in QApplication::notify () from /usr/lib/libqt-mt.so.3 #16 0xb7584cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4 #17 0xb6d51209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #18 0xb6db153b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #19 0xb6d65d49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #20 0xb6dd91ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #21 0xb6dd8fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #22 0xb6dc0699 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #23 0x08058a24 in ?? () #24 0xbf842614 in ?? () #25 0x08072518 in ?? () #26 0x00000001 in ?? () #27 0x00000000 in ?? ()
Hi Chris, Yeah, this is the problem with the old KDE3 PIM asynchronous resources. For KDE 4.2, we should have this fixed by virtue of the fact that we're using Akonadi, which handles all that back-end nastiness for us. For KDE3, you can get around this by using the file resource in the conduit configuration settings instead of the "standard resource". Thank you for the bug report!! Also, I'd really appreciate your help in testing out KPilot from the really-soon-to-be-released KDE 4.2!!! =:)