*** Bug 108167 has been marked as a duplicate of this bug. ***

Hi there,

Can you please list what version of pilot-link you are using for this?  You mentioned FC4, and that particular distribution has caused tons of problems for palm pilot users because they used unstable code for the pilot libraries.

Also, some cleanup work has been done in this area lately, and I'd really appreciate your help in testing it to see if it fixes your problem.

If you could get the latest source from svn for kpilot and test it against this problem, we can see if we still have a problem.  You can get the directions for how to do this at http://www.slac.com/pilone/kpilot_home/download.php.

Please make sure you build with debugging turned on, as directed on that page.

Thanks for your help!!

*** This bug has been confirmed by popular vote. ***

Um.  I'm all for being confirmed by popular vote and all, but I still have nothing to look for on trying to solve this problem, and what would be most helpful and necessary is if my questions above could be answered.

Thanks!!  =:)

I used pilot-link 0.12-pre3.

All, if you are using pilot-link 0.12-anything, you are using non-production-quality and unreleased software.  It might work and it might not.  For certain, I'm not using it and don't have a way of debugging problems with it.  It is best for you to uninstall pilot-link-0.12 and install pilot-link-0.11.8 from FC3 until pilot-link-0.12 is actually released.

Also, the best way for us to help fix these problems is if you recompile kpilot with debugging turned on (see the kpilot download page for how to do this) so that we can get a proper stack trace when something does go wrong.

Can anyone confirm this bug with pilot-link-0.11.8?  If not, I'm going to close this bug.  I'll wait to hear back from you all.  =:)

Thanks!!

I just (forcibly) installed pilot-link-0.11.8-8 from FC3 on my FC4 distro, compiled the 4.5.3 tarball from the kpilot website, and it worked without crashing.

Then I reinstalled pilot-link-0.12.0-pre3 from FC4, and it indeed crashed again.  Here is the log:

Version: KPilot 4.5.3 (peuter)
Version: pilot-link 0.12.0-pre3
Version: KDE 3.4.2-0.fc4.1 Red Hat
Version: Qt 3.3.4

HotSync Log

10:00:21 Starting the KPilot daemon ...
10:00:22 Daemon status is `Waiting for sync'
10:00:22 Next HotSync will be: HotSync. Please press the HotSync button.
10:00:22 Pilot device /dev/pilot does not exist. Probably it is a USB device and will appear during a HotSync.
10:00:37 Device link ready.
10:00:41 Checking last PC...
10:00:41 KPilot 4.5.3 (peuter) HotSync starting...

10:00:41 Using encoding ISO 8859-1 on the handheld.
10:00:41 [Internal Editors]
10:00:41 Databases with changed records: 
10:00:41 Databases with changed flags: 
10:00:41 Databases with changed AppBlock: 
10:00:41 [Conduit time_conduit]
10:00:41 Setting the clock on the handheld
10:00:42 [Conduit vcal-conduit]
10:00:44 Syncing with standard calendar resource.
10:00:44 Using non-local time zone: America/Denver
10:00:44 Copying records to PC ...
10:00:44 Copying records to Pilot ...
10:00:44 [Conduit abbrowser_conduit]

and the backtrace (SEGV, signal 11):

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208711488 (LWP 14340)]
[KCrash handler]
#4  0x00fd2c97 in PilotAddress::pack_ (this=0x98c4908, buf=0x9653940, 
    len=0xbfe6ea30) at pilotAddress.cc:681
#5  0x00fc8d14 in PilotAppCategory::pack (this=0x98c4908)
    at pilotRecord.cc:220
#6  0x006a5033 in AbbrowserConduit::_savePalmAddr (this=0x8b9a908, 
    palmAddr=0x98c4908, pcAddr=@0xbfe6ed44) at abbrowser-conduit.cc:1408
#7  0x006a5c64 in AbbrowserConduit::_copyToHH (this=0x8b9a908, 
    pcAddr=@0xbfe6ed44, backupAddr=0x9a04980, palmAddr=0x98c4908)
    at abbrowser-conduit.cc:1300
#8  0x006aa64d in AbbrowserConduit::syncAddressee (this=0x8b9a908, 
    pcAddr=@0xbfe6ed44, backupAddr=0x9a04980, palmAddr=0x98c4908)
    at abbrowser-conduit.cc:1265
#9  0x006ab6bf in AbbrowserConduit::slotPCRecToPalm (this=0x8b9a908)
    at abbrowser-conduit.cc:943
#10 0x006ab92e in AbbrowserConduit::qt_invoke (this=0x8b9a908, _id=5, 
    _o=0xbfe6eeb4) at abbrowser-conduit.moc:93
#11 0x048e2e34 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#12 0x04c5b286 in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#13 0x04900613 in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#14 0x04908ef5 in QSingleShotTimer::event ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#15 0x0487e0dd in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x0487ea5c in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#17 0x0503d851 in KApplication::notify () from /usr/lib/libkdecore.so.4
#18 0x04872972 in QEventLoop::activateTimers ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x0482835a in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x048967ab in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x048966b6 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x0487daa9 in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x0805a704 in main (argc=1, argv=0xbfe6f624) at pilotDaemon.cc:1367

Let me know if there is anything else I can do to help debug.  Thanks!

Thanks Randall!  =:)

It looks like this is another case of "don't use 0.12-pre*".  

Closing this as INVALID, since kpilot is not supported with 0.12-pre* versions of pilot-link.

Thanks for the bug reports though!!  

That's fine to call it INVALID, but as a point of fact, a very large number of linux users use FC4, and so all of those people are now unable to use this very important program!  Also, presumably 0.12 represents the next version of pilot-link, so at some point you'll have to make the necessary changes for kpilot to support it, so one could argue that doing so sooner rather than later would benefit a lot of people.  Cheers!

On Tuesday 23 August 2005 06:31, Randall O'Reilly wrote:
> 06:31 ------- That's fine to call it INVALID, but as a point of fact, a
> very large number of linux users use FC4, and so all of those people are
> now unable to use this very important program!  Also, presumably 0.12


That's true. Except that the maintainers of pilot link have repeatedly stated: 
don't package 0.12-pre versions. Don't ship it. Source, binary, and 
aardvark-incompatible changes _will_ happen within the -pre series and it 
will break any and all applications that use pilot link. Don't ship it. 
Really, really, don't ship it.

> represents the next version of pilot-link, so at some point you'll have to
> make the necessary changes for kpilot to support it, so one could argue
> that doing so sooner rather than later would benefit a lot of people. 


Sure. pilot-link 0.12-pre5 seems to work, since that is the most recent 
version of pilot-link. But KPilot works with either: 0.11.8 _or_ pilot-link 
CVS HEAD. Not anything else, definitely not the -pre2, -pre3 and -pre4 that 
FC4 feels it has to ship and which have source, binary and 
aardvark-incompatible changes amongst themselves so that no application 
compiled for one of those particular versions can work with any of the 
others. And it is infeasible to make KPilot work with each of the 
incompatible -pre versions -- so that's why it works with CVS HEAD, or not at 
all.

CC-ing -pim-users because this comes up so often.