Re: gnome-pilot can't see my palm V (jpilot can)

["Matt Price" <moptop99 gmail com>]

On 5/25/06, Matt Davey <mcdavey mrao cam ac uk> wrote:
> > Hi,
> > I've been happily running gnome-pilot & evolution on debian sid for a
> > while, and my palm v has synced pretty well.  Unfortunately my
> > ocmputer died & I upgraded both hard and software, and I'm now running
> > Ubuntu dapper (gnome-pilot 2.0.13-0ubuntu16 is the package version).
> > My palm is an old Palm V which connects over USB using a Belkin
> > Serial-to-USB cable.
>
> First, a couple of quick questions as to your setup.  How do you
> configure your device in gnome-pilot?  I'm presuming that if you
> have a serial-to-usb cable you have to add a specific usb
> vendor/device id to gnome-pilot's devices.xml file that matches
> whatever the palmV appears as?

er, I was entirley ignormant of the devices.xml file, but now that
I've found it, it turns out that the vendor and ProdID of my cable are
already listed under Palm M100.  So I've simply changed those lines
to:

 <!-- Palm Serial Adaptor -->
 <device vendor_id="0830" product_id="0080" />

... which merely changes the comment value, I guess.


> There have been some changes to gp on Ubuntu dapper, because dapper
> has removed the usbfs filesystem at /proc/bus/usb, which gp
> relied on.  You may have a version that uses HAL callbacks to spot
> when hardware appears, in which case we should definitely try
> to debug it!

ok excellent, I'll do my best.
> > I'd really like to use gnome-pilot,
> > though, but unfortunately gpilotd dies when I press the hotsync
> > button with a gtk-warning "cannot open display".
>
> I'd love to know exactly where that crash happens.  Do you get a
> 'bug-buddy' dialog when it crashes?  If so, you should be able to
> get a stack trace.  Alternatively, try starting gpilotd with a
> debugger:
>         killall gpilotd
>         gdb /usr/libexec/gpilotd
>
> When it crashes, type 'bt' to get a 'backtrace'.
> If you can send the complete gpilotd output, from when it starts
> to the backtrace, that would be great.  This output will also
> confirm which version of pilot-link you're using.
>

ok, I've pasted that in to the bottom of this em.

> The other simple thing worth trying (with pilot-link 0.11.8) is
> increasing the 'timeout' value configured in gnome-pilot.  At the
> moment you have it at '2'; try increasing it to 100 (pilot-link
> 0.11.8 interprets the number as milliseconds, not seconds.  It'll
> be fixed in 0.12.0).

found that value after some searching in
~/.gnome2/gnome-pilot.d/gpilotd.  Changing it didn't seem to have much
effect.

> Would you be interesting in trying to compile from a tarball?
> If so, I can give you some pointers to the most recent gnome-pilot
> development source.

sure, I'd try that.  But I guess the better scenario would be to
figure out where Dapper's going wrong & fix THAT too, since there are
zillions of Ubuntu users out there...

> Hang in there, we'll get you going.
>
> Matt

thanks Matt!


OK, here is the gpilotd output followed by the stacktrace.  As you'll
see here, I fired up gpilotd-control-applet as well to generate the
crash (occurred on pushing hotsync button after choosing "Get ID from
Palm" in gpilotd-control-applet).

matt anarres-64:~$ gdb /usr/bin/gpilotd
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/gpilotd
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912587637712 (LWP 6560)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
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=9600

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: Connection timed out

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: timeout was 100 secs
gpilotd-Message: setting PILOTRATE=9600

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: Connection timed out

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: timeout was 100 secs
gpilotd-Message: setting PILOTRATE=9600

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: Connection timed out

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: timeout was 100 secs
gpilotd-Message: Client seems ok
gpilotd-Message: Client seems ok
gpilotd-Message: monitor_on(pilot_name="PalmVUSB",client_id =
IOR:010000001b000000...)
gpilotd-Message: corba:
notify_on(event_type=CONNECT,callback=IOR:010000001b000000...)
gpilotd-Message: corba:
notify_on(event_type=DISCONNECT,callback=IOR:010000001b000000...)
gpilotd-Message: setting PILOTRATE=9600

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: Connection timed out

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: timeout was 100 secs
gpilotd-Message: setting PILOTRATE=9600

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: Connection timed out

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: timeout was 100 secs
gpilotd-Message: corba: get_user_info(cradle=USB Cradle,survival=0,timeout=0)
gpilotd-Message: assigned handle num 9
gpilotd-Message: corba: get_system_info(cradle=USB Cradle,survival=0,timeout=0)
gpilotd-Message: assigned handle num 10
gpilotd-Message: setting PILOTRATE=9600

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: Connection timed out

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: timeout was 100 secs
gpilotd-Message: setting PILOTRATE=9600

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: Connection timed out

(gnome-pilot:6560): gpilotd-WARNING **: pi_accept_to: timeout was 100 secs
gpilotd-Message: setting PILOTRATE=9600

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912587637712 (LWP 6560)]
0x00002aaaac2d1af3 in memcpy () from /lib/libc.so.6
(gdb) bt
#0  0x00002aaaac2d1af3 in memcpy () from /lib/libc.so.6
#1  0x00002aaaac2d10dd in memmove () from /lib/libc.so.6
#2  0x00002aaaac017f29 in net_rx () from /usr/lib/libpisock.so.8
#3  0x00002aaaac018209 in net_rx_handshake () from /usr/lib/libpisock.so.8
#4  0x000d000000000000 in ?? ()
#5  0x2aaaac01f1250000 in ?? ()
#6  0x0000005fb9100000 in ?? ()
#7  0x2aaaabd62fd00000 in ?? ()
#8  0x2aaaabd62fd00000 in ?? ()
#9  0x7fffff9717300000 in ?? ()
#10 0x0000005714300000 in ?? ()
#11 0x0000004067450000 in ?? ()
#12 0x7fffff9716700000 in ?? ()
#13 0x0000000000010000 in ?? ()
#14 0x7fffff971a7c0000 in ?? ()
#15 0x0000005476f00000 in ?? ()
#16 0x7665642f00000000 in ?? ()
#17 0x304253557974742f in ?? ()
#18 0x0000000000040000 in ?? ()
#19 0x7fffff9718500000 in ?? ()
#20 0x0000000000000000 in ?? ()
(gdb)