Public bug reported:
Using a Palm V in its cradle with a Serial-to-usb cable, I'm unable to
access the pam with gnome-pilot or pilot link. both kpilot and jpilot
CAN access the Palm V using /dev/ttyUSB0 (though kpilot erased my palm
when I first tried syncing win kontact), so I suppose the device is
being set up correctly.
/dev/ttyS0 doesn't work at all, as far as I can tell, and in fact
attempts to sync over this device sometimes break the working
/dev/ttyUSB0 connection on subsequent attempts.
Steps to reproduce:
-set gpilotd device to /dev/ttyUSB0
-attach usb-to-serial cable to palm serial out.
-attach cable to usb port
-execute:
$ gpilotd
-press hotsync button on palm cradle
-wait for gpilotd to crash.
Again, pilot-link seemsto be affected as well as gpilot -- it also
fails, while jpilot and kpilot both handle the situation without any
problems.
Here' is some typical output of gpilotd (somewhat long).
---------------------------------------
[EMAIL PROTECTED]:~$ gpilotd
gpilotd-Message: gnome-pilot 2.0.13 starting...
gpilotd-Message: compiled for pilot-link version 0.11.8
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Watching USB Cradle (/dev/ttyUSB0)
gpilotd-Message: Found 4766, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0502, 0736
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 091e, 0004
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0100
gpilotd-Message: Using net FALSE
gpilotd-Message: Found 082d, 0200
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0300
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0c88, 0021
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0002
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0003
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0020
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0031
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0040
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0050
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0060
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0061
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0070
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0080
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 8001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 6601
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0038
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0066
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0095
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 009a
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00c9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00da
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00e9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0144
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0169
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 12ef, 0100
gpilotd-Message: Using net TRUE
gpilotd-Message: setting PILOTRATE=57600
(gnome-pilot:17630): gpilotd-WARNING **: pi_accept_to: Connection timed
out
(gnome-pilot:17630): gpilotd-WARNING **: pi_accept_to: timeout was 2 secs
gpilotd-Message: setting PILOTRATE=57600
(gnome_segv2:17635): Gtk-WARNING **: cannot open display:
---------
thanks for your help,
matt
** Affects: gnome-pilot (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
--
gpilotd fails with "cannot open display"
https://launchpad.net/bugs/46436
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
