Bug 160802 - KPilot crashing at "Autodetecting Your Handheld"
Summary: KPilot crashing at "Autodetecting Your Handheld"
Status: RESOLVED DUPLICATE of bug 152681
Alias: None
Product: kpilot
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: groot
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-13 21:43 UTC by Ingvar Fröroth
Modified: 2009-01-19 04:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ingvar Fröroth 2008-04-13 21:43:11 UTC
Version:           4.9.2-358 (moribund alleycat) (using 3.5.7 "release 72" , openSUSE 10.3)
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.22.5-31-default

With a fresh installation of OpenSuSe 10.3 on a new x86_64 PC, it does not seem possible to get KPilot to work with any of my three PDAs, namely:
 . Handspring Visor, PalmOS v 3.1H3
 . PalmPilot m515, PalmOS v 4.1
 . Palm Tungsten E, PalmOS v 5.2.1
All of these have USB connectivity for HotSync. For KPilot versions, see below.

When using the configuration wizard, and "Automatically Detect Handheld & User Name", pressing the HotSync button as required, KPilot crashes and exits after having reached some 30% on the status progress bar.

When to proceed trying without using the wizard, KPilot & the PDA never gets in touch: The HotSync log window gets filled up with the following --

<b>Version:</b> KPilot 4.9.2-358 (moribund alleycat)
<b>Version:</b> pilot-link 0.12.2
<b>Version:</b> KDE 3.5.7 "release 72" 
<b>Version:</b> Qt 3.3.8

<qt><b>HotSync Log</b></qt>

<b>20:41:54</b> Starting the KPilot daemon ...
<b>20:41:54</b> Daemon status is `not running'
<b>20:41:55</b> Trying to open device /dev/pilot...
<b>20:42:15</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:42:15</b> Could not open device: /dev/pilot (will retry)
<b>20:42:37</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:43:56</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:44:18</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:44:40</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:45:02</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:45:24</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:45:46</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:46:08</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:46:30</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:46:52</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:47:14</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:47:36</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:47:41</b> Changed username to `Bernhard'.
<b>20:48:00</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:48:00</b> Next HotSync will be: HotSync. Please press the HotSync button.
<b>20:48:00</b> Trying to open device /dev/pilot...
<b>20:48:21</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:48:21</b> Could not open device: /dev/pilot (will retry)
<b>20:48:43</b> <i>Cannot accept Pilot (No such device)</i>
<b>20:49:05</b> <i>Cannot accept Pilot (No such device)</i>

 -- and so it goes on & on.

Thanks  /Ingvar F
Comment 1 Jason 'vanRijn' Kasper 2009-01-19 04:16:01 UTC
Hi Ingvar. The auto-setup-connection-wizard-detection thing is broken and there's another bug for that. You'll need to manually enter your device, sorry.

*** This bug has been marked as a duplicate of bug 152681 ***