'[kdepim-users] Kpilot suddenly won't even detect the palm pilot'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdepim-users
Subject:    [kdepim-users] Kpilot suddenly won't even detect the palm pilot
From:       Yatin Mirakhur <ymirakhur () gmail ! com>
Date:       2007-02-21 2:00:36
Message-ID: 200702202100.36788.ymirakhur () gmail ! com
[Download RAW message or body]

Hello Everyone,
I am running Kubuntu Edgy with KDE 3.5.6. I have  Palm Treo 600

This includes:

Version: KPilot 4.9.0 (deepsix)
Version: pilot-link 0.12.1
Version: KDE 3.5.6
Version: Qt 3.3.6

Since KDE 3.5.6 came out (with Kubuntu packages), I have been using this 
latest version of KPilot with absolutely no problems. I had a compiled 
version installed before that. I simply let Adept updater do its thing: it 
installed a new version of KDE, including the latest KPilot, and all was 
well. Upon this installation, I ran the KPilot configuration wizard, which 
detected my palm pilot and set the device as "/dev/ttyUSB1". I had previously 
left it at "/dev/pilot" but this change had no effect on my synching (it was 
working better than ever before, so I just let it be the way it was)

I synched my pilot last on Feb. 19, sometime in the morning. Next, I tried to 
synch it at around 6 pm on Feb. 20. However, when I pressed the HotSync 
button, absolutely nothing happens. The below is what I see in the KPilot log 
area:

HotSync Log

20:49:38 Starting the KPilot daemon ...
20:49:39 Daemon status is `not running'
20:49:39 Pilot device /dev/ttyUSB1 does not exist. Probably it is a USB device 
and will appear during a HotSync.

(normally after this, it would detect the pilot and then go on to synch. 
However, suddenly, it seems to have stopped detecting the pilot. I have no 
idea what could cause this. My only idea is this: Before the pilot stopped 
working, I was having a small problem with my printer driver, which led me to 
try to uninstall 2 .deb's which made up my printer driver, then install them 
again. I did this by using the command line: dpkg -i [etc]. I'm not sure 
really how this could have caused any problem, but I am sure that it is the 
only system change i made between the two synchs. Adept installed no updates 
or anything like that. Here is my dpkg log:

2007-02-19 18:21:37 status installed brhl2070nlpr 2.0.0-2
2007-02-19 18:21:53 remove brhl2070nlpr 2.0.0-2 2.0.0-2
2007-02-19 18:21:53 status half-configured brhl2070nlpr 2.0.0-2
2007-02-19 18:21:55 status half-installed brhl2070nlpr 2.0.0-2
2007-02-19 18:21:55 status config-files brhl2070nlpr 2.0.0-2
2007-02-19 18:21:55 purge brhl2070nlpr 2.0.0-2 2.0.0-2
2007-02-19 18:21:55 status config-files brhl2070nlpr 2.0.0-2
2007-02-19 18:21:55 status config-files brhl2070nlpr 2.0.0-2
2007-02-19 18:21:55 status config-files brhl2070nlpr 2.0.0-2
2007-02-19 18:21:55 status config-files brhl2070nlpr 2.0.0-2
2007-02-19 18:21:55 status config-files brhl2070nlpr 2.0.0-2
2007-02-19 18:21:55 status not-installed brhl2070nlpr <none>
2007-02-19 18:21:55 status installed cupswrapperhl2070n 2.0.0-2
2007-02-19 18:21:55 remove cupswrapperhl2070n 2.0.0-2 2.0.0-2
2007-02-19 18:21:55 status half-configured cupswrapperhl2070n 2.0.0-2
2007-02-19 18:21:57 status half-installed cupswrapperhl2070n 2.0.0-2
2007-02-19 18:21:57 status config-files cupswrapperhl2070n 2.0.0-2
2007-02-19 18:21:57 purge cupswrapperhl2070n 2.0.0-2 2.0.0-2
2007-02-19 18:21:57 status config-files cupswrapperhl2070n 2.0.0-2
2007-02-19 18:21:57 status config-files cupswrapperhl2070n 2.0.0-2
2007-02-19 18:21:57 status config-files cupswrapperhl2070n 2.0.0-2
2007-02-19 18:21:57 status config-files cupswrapperhl2070n 2.0.0-2
2007-02-19 18:21:57 status config-files cupswrapperhl2070n 2.0.0-2
2007-02-19 18:21:57 status not-installed cupswrapperhl2070n <none>
2007-02-19 18:23:59 install brhl2070nlpr <none> 2.0.0-2
2007-02-19 18:23:59 status half-installed brhl2070nlpr 2.0.0-2
2007-02-19 18:23:59 status unpacked brhl2070nlpr 2.0.0-2
2007-02-19 18:23:59 status unpacked brhl2070nlpr 2.0.0-2
2007-02-19 18:23:59 status unpacked brhl2070nlpr 2.0.0-2
2007-02-19 18:23:59 status half-configured brhl2070nlpr 2.0.0-2
2007-02-19 18:23:59 status installed brhl2070nlpr 2.0.0-2
2007-02-19 18:24:28 install cupswrapperhl2070n <none> 2.0.0-2
2007-02-19 18:24:28 status half-installed cupswrapperhl2070n 2.0.0-2
2007-02-19 18:24:28 status unpacked cupswrapperhl2070n 2.0.0-2
2007-02-19 18:24:28 status unpacked cupswrapperhl2070n 2.0.0-2
2007-02-19 18:24:28 status unpacked cupswrapperhl2070n 2.0.0-2
2007-02-19 18:24:28 status half-configured cupswrapperhl2070n 2.0.0-2
2007-02-19 18:24:30 status installed cupswrapperhl2070n 2.0.0-2

["cupswrapperhl2070n" and "brhl2070nlpr" were the packages for my printer 
driver.]

Presently, even when I try to run the config wizard, it detects nothing. I'm 
not sure how to go about testing whether this is a problem with the kernel 
itself reading the palm pilot as a usb device or if there is a problem with 
pilot-link or if kpilot itself has a problem, or if my palm-pilot itself has 
a problem.

Any help that you could give is greatly appreciated. Until now, KPilot in KDE 
3.5.6 has been working flawlessly out of the box.

Thanks.
_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users
[prev in list] [next in list] [prev in thread] [next in thread] 