The kernel recognizes the device, setting up ttyUSB[0..5], thus:
Jan  6 10:22:43 treehouse kernel: visor 1-3:1.0: device disconnected
Jan  6 10:23:01 treehouse kernel: usb 1-3: new full speed USB device using ohci_hcd and address 56
Jan  6 10:23:01 treehouse kernel: usb 1-3: Product: Palm Handheld
Jan  6 10:23:01 treehouse kernel: usb 1-3: Manufacturer: Palm, Inc.
Jan  6 10:23:01 treehouse kernel: usb 1-3: SerialNumber: PN70MC47V0KW
Jan  6 10:23:01 treehouse kernel: usb 1-3: configuration #1 chosen from 1 choice
Jan  6 10:23:01 treehouse kernel: visor 1-3:1.0: Handspring Visor / Palm OS converter detected
Jan  6 10:23:01 treehouse kernel: usb 1-3: Handspring Visor / Palm OS converter now attached to ttyUSB4
Jan  6 10:23:01 treehouse kernel: usb 1-3: Handspring Visor / Palm OS converter now attached to ttyUSB5
Jan  6 10:23:29 treehouse kernel: usb 1-3: USB disconnect, address 56
Jan  6 10:23:29 treehouse kernel: visor ttyUSB4: Handspring Visor / Palm OS converter now disconnected from ttyUSB4
Jan  6 10:23:29 treehouse kernel: visor ttyUSB5: Handspring Visor / Palm OS converter now disconnected from ttyUSB5
Jan  6 10:23:29 treehouse kernel: visor 1-3:1.0: device disconnected
Jan  6 10:23:30 treehouse kernel: usb 1-3: new full speed USB device using ohci_hcd and address 57
Jan  6 10:23:30 treehouse kernel: usb 1-3: Product: Palm Handheld
Jan  6 10:23:30 treehouse kernel: usb 1-3: Manufacturer: Palm, Inc.
Jan  6 10:23:30 treehouse kernel: usb 1-3: SerialNumber: PN70MC47V0KW
Jan  6 10:23:30 treehouse kernel: usb 1-3: configuration #1 chosen from 1 choice
Jan  6 10:23:30 treehouse kernel: visor 1-3:1.0: Handspring Visor / Palm OS converter detected
Jan  6 10:23:30 treehouse kernel: usb 1-3: Handspring Visor / Palm OS converter now attached to ttyUSB4
Jan  6 10:23:30 treehouse kernel: usb 1-3: Handspring Visor / Palm OS converter now attached to ttyUSB5
Jan  6 10:24:47 treehouse kernel: visor ttyUSB2: Handspring Visor / Palm OS converter now disconnected from ttyUSB2
Jan  6 10:24:47 treehouse kernel: visor ttyUSB3: Handspring Visor / Palm OS converter now disconnected from ttyUSB3
Jan  6 10:24:50 treehouse kernel: visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
Jan  6 10:24:50 treehouse kernel: visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
Jan  6 10:26:19 treehouse kernel: usb 1-3: USB disconnect, address 57
Jan  6 10:26:19 treehouse kernel: visor ttyUSB4: Handspring Visor / Palm OS converter now disconnected from ttyUSB4
Jan  6 10:26:19 treisor ttyUSB5: Handspring Visor / Palm OS converter now disconnected from ttyUSB5
Jan  6 10:26:19 treehouse kernel: visor 1-3:1.0: device disconnected
Jan  6 10:26:20 treehouse kernel: usb 1-3: new full speed USB device using ohci_hcd and address 58
Jan  6 10:26:20 treehouse kernel: usb 1-3: Product: Palm Handheld
Jan  6 10:26:20 treehouse kernel: usb 1-3: Manufacturer: Palm, Inc.
Jan  6 10:26:20 treehouse kernel: usb 1-3: SerialNumber: PN70MC47V0KW
Jan  6 10:26:20 treehouse kernel: usb 1-3: configuration #1 chosen from 1 choice
Jan  6 10:26:20 treehouse kernel: visor 1-3:1.0: Handspring Visor / Palm OS converter detected
Jan  6 10:26:20 treehouse kernel: usb 1-3: Handspring Visor / Palm OS converter now attached to ttyUSB0
Jan  6 10:26:20 treehouse kernel: usb 1-3: Handspring Visor / Palm OS converter now attached to ttyUSB1

When KPilot is started, with the T|X plugged in, it causes the T|X to reboot, and this is appears in the log:
10:11:52 Starting the KPilot daemon ...
10:11:52 Daemon status is `not running'
10:11:53 Trying to open device /dev/pilot...

There is a partial solution posted here: http://home.cfl.rr.com/genecash/palm_tx_sync/index.html

that uses a modified version of JPilot.  The author says this:
"These devices are retarded.

They immediately attach as a USB device, but of course you can't sync then. Then when you do hit the hotsync button, they disconnect, connect again, pause for a couple of seconds, then disconnect and reconnect AGAIN.

You can only sync with pilot-link during that short pause. If it's already disconnected and reconnected the second time, you're out of luck."

I have not been able to get his solution to work.  However, the syslog as shown above suggests that he's onto something here.

When KPilot crashes with SIGSEV (i.e. when the Configuration Wizard is run), the bug report says that it cannot generate a backtrace.

There seems to be a bunch of bugs referring to a crash when scanning for a Palm device.  I'm not sure which one to add my experience to.  

I have a Tungsten E and the Wizard crashes every time I try to find it.  It also seems to happen at about 30%.  I'm running Konqueror 3.5.8 on OpenSuSE 10.3   and KPilot 4.9.2-358

I believe that my experiences are related to your own, and I've posted the bug report here:  http://bugs.kde.org/show_bug.cgi?id=160888
 
I tried using the bug report to add mine as a comment to this, but in spite of my entering the bug number 152681, the site ignored my intent...ever the way of the computer.  :-)

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

I have te same problem with slackware 12.1 an palm centro 
sometimes sync good, other times crash after syncr or in means of one syncronizacion. Also open the program without palm plug in.

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

(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)
(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 0xb66356d0 (LWP 13957)]
[New Thread 0xb653db90 (LWP 13958)]
(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]
#5  0xb6ecf6e4 in QApplication::sendPostedEvents ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#6  0xb6ecf846 in QApplication::sendPostedEvents ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#7  0xb6e7f1dd in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#8  0xb6ee4720 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#9  0xb6ee45b6 in QEventLoop::exec ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#10 0xb6ecdbbf in QApplication::exec ()
   from /usr/lib/qt-3.3.8b/lib/libqt-mt.so.3
#11 0x08058253 in ?? ()
#12 0xbfb77ab0 in ?? ()
#13 0x08071178 in ?? ()
#14 0x00000001 in ?? ()
#15 0x00000000 in ?? ()

Same error sync with bluetooth!!!

(In reply to comment #6)
> Same error sync with bluetooth!!!
> 

I correct, only crash when try to change preference .
Sync by bluetooth work more slow but without crash...

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

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

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

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

Okay, so let's just clarify..... This bug started out and now stands for the failure of our auto-device-detection wizard. In KDE 3.5.x, this resulted in a crash. In KDE 4.2+, this button has been disabled. We would REALLY like to get this working again, but it is not going to happen unless someone steps up and helps get this working again. I'm going to change this to a wishlist item, since we've stopped it from being a crasher. Someone please help us get this working again?

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!!! =:) 

(In reply to comment #12)
> Okay, so let's just clarify..... This bug started out and now stands for the
> failure of our auto-device-detection wizard. In KDE 3.5.x, this resulted in a
> crash. In KDE 4.2+, this button has been disabled. We would REALLY like to get
> this working again, but it is not going to happen unless someone steps up and
> helps get this working again. I'm going to change this to a wishlist item,
> since we've stopped it from being a crasher. Someone please help us get this
> working again?
> 
> 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!!! =:) 
> 
ok, is posible to use kpilot in kde 4.2? compiling o existe package 

Hi Maximo,

Yes, KPilot is packaged and distributed with KDE 4.2. I've made a lot of bug fixes since the last rc1 release, though, so if you're testing, you'll want to install the latest KDE 4.2 RC1 packages and then compile KPilot from svn (see http://kpilot.org/develop.php for more info).

Thanks! =:)

I'm also using kPilot with the Handspring Visor.

Version: KPilot 4.9.4-3510 (elsewhere)
Version: pilot-link 0.12.3
Version: KDE 3.5.10
Version: Qt 3.3.8b

I had the same Problem using the 'Auto-Detection' mechanism. I found a tip (I guess at ubuntuusers.de?) that one should specify only the device 'usb:' without any Parameters: that worked fine 'til I hit the next Error, Syncing of KNotes...but it's another Bug(-Report).
 
But -as you see below- the PDA is only visible, when the 'Sync-Button' on the cradle is pressed.

Hope it helps..

mue.de

Attachment:
HotSync-Protokoll

18:25:27 Der Status des Dienstes ist "Waiting for sync"
18:25:27 Versuch das Gerät usb: zu öffnen ...
===>> Press the Sync-Button

18:36:38 Letzter PC wird überprüft ...
18:36:38 KPilot 4.9.4-3510 (elsewhere) Direktabgleich wird gestartet ...

18:36:38 Auf dem Pilot wird Zeichensatz ISO 8859-1 verwendet.


Result (extract from /tmp/kpilot-syslog.html):

Number of addresses, to-dos, events, and memos
Record type
# of recs
Addresses:  568 entries in Addressbook
  Events:  168 entries in Calendar
  To-dos:  461 entries in To-do list
  Memos:  474 memos
  Synchronization Information
Last sync attempt:  18.10.2009 21:00:42
  Last successful sync:  18.10.2009 21:00:42
  Last sync with PC (ID):  8323329
  Version Information (Desktop)
Application
Version
Operating System:  Linux 2.6.24-24-generic, i686
  Hostname:  muelux-LT6cA
  Qt Version:  3.3.8b
  KDE Libraries Version:  3.5.10
  KPilot Version:  4.9.4-3510 (elsewhere)
  Pilot-Link Version:  0.12.3
  Version Information (Handheld)
Application
Version
PalmOS:  PalmOS 1.2

Unfortunately, KPilot is unmaintained due to lack of manpower and will not be part of KDE SC 4.4.

This bug reports will now be closed.