Ubuntu
pilot-link package

pilot-xfer fails to sync if there is another usb serial device

Bug #138823 reported by Kenny Duffus
6
Affects Status Importance Assigned to Milestone
pilot-link (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

pilot-xfer fails to talk to the palm device (in my case a treo 600) if you have already another usb serial device (something that uses ttyUSB0) connected, i had a belkin usb ir device

the result of having another serial device already attached is that the palm is assigned ttyUSB1 and ttyUSB2 (assuming only one other device already connected, i'm wondering if there is something hardcoded to assume those ports. the comandline option of -p should let you specify for instance normally with nothing else plugged in i'd use -p /dev/ttyUSB1 but specifying ttyUSB2 nothing happens

Revision history for this message
Kenny Duffus (kduffus) wrote :

pilot-link 0.12.2-7ubuntu1 on feisty with 2.6.20-16-generic kernel

Revision history for this message
Felipe Figueiredo (philsf) wrote :

Try unloading the module 'visor' and using port 'usb:' in your sync application, whatever it is.

Revision history for this message
Graham Power (grahampower70-deactivatedaccount) wrote : Autoreply: [Bug 138823] Re: pilot-xfer fails to sync if there is another usb serial device

I am changing my e-mail address to <email address hidden> .All mail sent to <email address hidden> are been forward to the hotmail account until this one is close down
sorry for any inconvenience

Revision history for this message
Kenny Duffus (kduffus) wrote :

unloading visor would mean you couldn't talk to the device

the application as stated is pilot-xfer, hence why the bug is filed against pilot-link, and it does not use a syntax like usb:

Revision history for this message
Felipe Figueiredo (philsf) wrote :

It does not. You will 'talk to the device using another method' (libusb), hence the 'usb:' port. Try this

pilot-xfer -p usb: -l

after unloading the module visor. If it works, blacklist the module visor.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom reproducible in a daily-live (desktop) image of 8.10?

Changed in pilot-link:
status: New → Incomplete
Revision history for this message
Ludovic Rousseau (ludovic-rousseau-gmail) wrote :

Please include the complete copy of the commands you executes and the generated output.

And try to use (all on 1 line):
$ PILOT_DEBUG=DEV PILOT_DEBUG_LEVEL=DEBUG PILOT_LOG=1 PILOT_LOGFILE=/tmp/pilot_log_file pilot-xfer -p usb: -l

and attach the generated /tmp/pilot_log_file file to this bug report

Revision history for this message
Felipe Figueiredo (philsf) wrote :

I think this should be marked "notabug" or wontfix, since this only occurs when one uses the old method of the module visor, which is not supported since a very long time.

The module in question in fact comes blacklisted by default in Ubuntu, and the recommended way is to use libusb (by means of port "usb:", even if the reporter refuses to acknowledge this). Please let visor RIP.

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

closing as won't fix, as requested

Changed in pilot-link (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.