2006-10-20 09:44:41 |
Daniel Holbach |
gnome-pilot: statusexplanation |
|
Thanks for the bug report. Can you try this:
1. Kill gpilotd (you may need to remove the pilot applet from the panel, and then do killall gpilotd from a terminal window).
2. Now try running pilot-xfer: pilot-xfer -p /dev/pilot -l (or '-p /dev/ttyUSB0', or '-p /dev/ttyUSB1', or '-p net:', etc)
3. If that doesn't work, then you have most likely got a problem with your kernel/udev/usb/cables, etc, not gnome-pilot.
It can also be useful to see the output from the gpilotd daemon. To do this:
1. Kill gpilotd (you may need to remove the pilot applet from the panel, and then do killall gpilotd from a terminal window).
2. Restart gpilotd. |
|
2007-04-16 15:25:28 |
Daniel Holbach |
gnome-pilot: statusexplanation |
Thanks for the bug report. Can you try this:
1. Kill gpilotd (you may need to remove the pilot applet from the panel, and then do killall gpilotd from a terminal window).
2. Now try running pilot-xfer: pilot-xfer -p /dev/pilot -l (or '-p /dev/ttyUSB0', or '-p /dev/ttyUSB1', or '-p net:', etc)
3. If that doesn't work, then you have most likely got a problem with your kernel/udev/usb/cables, etc, not gnome-pilot.
It can also be useful to see the output from the gpilotd daemon. To do this:
1. Kill gpilotd (you may need to remove the pilot applet from the panel, and then do killall gpilotd from a terminal window).
2. Restart gpilotd. |
Thanks for following up. Closing the bug. |
|