gpilotd locks up my Palm Z22

[Fridtjof Busse]

Binary package hint: gnome-pilot

Whenever I try to sync my palm on edgy, it locks up hard and I have to reset it. Used to work just fine on dapper.
gpilotd outputs this (/dev/pilot is the correct link to ttyUSB1):

$ gpilotd
gpilotd-Message: gnome-pilot 2.0.14 starting...
gpilotd-Message: compiled for pilot-link version 0.12.1
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Cradle (/dev/pilot) wird betrachtet
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 115e, f100
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:5626): gpilotd-WARNING **: pi_accept_to returned -202: No such file or directory

(gnome-pilot:5626): gpilotd-WARNING **: pi_accept_to: timeout was 2 secs

If you need more information, please let me know, the Z22 looks up very reliable every single time.

[Daniel Holbach (dholbach)]

It can be useful to figure out if the problem is with gnome-pilot or the lower, pilot-link, layer. To isolate (assuming you have pilot-xfer installed) try the following:
   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 (/usr/bin/gpilotd).

[Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount)]

'pilot-xfer -p /dev/pilot -l' works and gives the normal output. So the connection works.
And I already posted the output of gpilotd, see my initial report.

[Daniel Holbach (dholbach)]

Somebody of the team should forward this upstream.

[Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount)]

Did anybody already forward this upstream?
For me, this is quite a grave bug and I'd like to get it fixed.

[jon latorre (moebius-etxea)]

Same problem here. With dapper it works great. pilot-xfer also works. But when I try to sync with gnome-pilot my z22 crashes han have to reset it.

Upstream says it maybe related to bug #62310 in launchpad. But I have udev 093-0ubuntu17 instaled.

[William Grant (wgrant)]

Same happens with my Zire m150. Worked fine in Dapper and below. Displays a `Fatal Exception', and has to be reset.

[Matt Davey (mcdavey)]

It's somewhat unusual to see gnome-pilot failing when pilot-link is reliable (especially in this way, which seems to be in the initial handshake with the PDA).

Here are a few things to try:
1. Run pilot-xfer with a '-t 2' option. (This does the handshake in a way more
    like gnome-pilot).
2. Run gnome-pilot with a timeout setting of zero (edit the device using the
    control applet, under the 'Devices' tab). This does the handshake more
    like the way pilot-xfer does by default.

There's a slight chance that (1) will lock up your device and (2) will magically fix the problem, but I don't hold out great hope. Worth checking out, though.

If that doesn't fix things, next:
3. Run gpilotd from a terminal, and enable the following pilot-link
     environment variables to get extra debugging. Then send us
     the output:
        PILOT_DEBUG="DEV SLP CMP PADP NET SOCK"
        PILOT_DEBUG_LEVEL="DEBUG"

And finally a possible workaround to help you get syncing while we get to the bottom of this:
4. We can use pi-nredir to redirect the pda connection to the network,
     and configure a network sync in gnome-pilot. First configure
     your PDA. On my PalmOS5 device it goes like this:
   a. specify 'Local' hotsync.
   b. edit hotsync 'LANsync preferences' and specify 'LANSync' instead
        of 'Local HotSync'.
   c. edit 'Primary PC Setup' in hotsync preferences, and specify '!!' as
        the primary PC name, specify the IP address of the machine where
        you'll run gnome-pilot in the 'Primary PC Address' box -- 127.0.0.1
        would be fine if you're on the same machine as your usb cable.
   d. enter an appropriate subnet mask. 255.255.255.0 will probably do
        fine.
  Now, open the gnome-pilot configuration applet, and delete your USB
  device and create a 'Network' device.
  Finally, press hotsync on your PDA and quickly run pi-nredir from a
  terminal window:
    > pi-nredir -p /dev/pilot
    ---- or '-p /dev/ttyUSBx', whatever you use.
  If all goes well, pi-nredir should redirect the incoming USB connection
  to the network and gnome-pilot should connect.

[Matt Davey (mcdavey)]

[aside] not sure why launchpad is reporting upstream status as 'rejected'. It was accidentally marked 'invalid' by the upstream reporter, but I reopened it today.

[jon latorre (moebius-etxea)]

I have tryed 1. and pilot-xfer keeps working fine. I try to set the timeout to 0 in gnome-pilot and the Z22 doens't crash but doesn't sync either.

I have set the timeout bac to 2 seconds and launched gpilotd with the extra debugging variables. The output is attachet to this comment.

My Z22 doesn't have LANsync or i don't see it .

[Matt Davey (mcdavey)]

Jon,
your output suggests that you have '/dev/pilot' configured as your device name in gnome-pilot, but that that device does not exist during the sync attempt. Is this the device name you use with pilot-xfer? If not, configure gnome-pilot using the configuration applet, and set the device name to whatever you used with pilot-xfer.

[jon latorre (moebius-etxea)]

Yes, these lines are strange. But /dev/pilot exists (it's a link to /dev/ttyUSB1) and it's the device I used with pilot-xfer.

[Matt Davey (mcdavey)]

Okay, taking a closer look, those lines are just showing that there's a gap between the usb device being detected and the creation of the /dev/pilot symlink. At the end of the output we can see the 'poll', which means we've found /dev/pilot and are trying to talk.

We've made some progress. The PDA crash does seem to be caused by some internal pilot-link code that sends some unexpected data to the PDA. I'm not entirely clear of the history of this code, but it appears to be an attempt to workaround some problems with udev device creation on linux :(

We're getting down to a fairly low level here, but it might be useful to see:
1. the pilot-link debugging for the 'timeout=0' gnome-pilot case, and the normal pilot-xfer case.
2. the strace output you get from gpilotd on the timeout=2 case. Run 'strace gpilotd'. It'll
    produce a long output. What I want to see is whether the 'poll' actually returns a timeout,
    or some error.

As for workarounds, it might be worth seeing if you can set up a direct 'libusb' connection:
http://code.pilot-link.org/README.libusb
once you've got it working for pilot-xfer, you just set the usb device in gnome-pilot to 'usb:' and hey presto, you don't need the visor module anymore.

[Matt Davey (mcdavey)]

Strange stuff. Looks like a timing issue.
I'd strongly recommend seeing if you can get libusb syncing to work.

What happened when you set the timeout to zero in gnome-pilot? Does it just sit there forever trying to connect until you kill it? You didn't send output for the gpilotd+timeout=0 case above... (I know, I'm very demanding)

In the pilot-xfer+timeout=2 case, did you try starting pilot-xfer BEFORE starting the sync on the PDA? That is most like the way that gpilotd tries to connect: i.e. it'll try to connect the instant the pda is detected.

Another thing to do is to try disabling HAL and restarting gpilotd. (/etc/init.d/hald stop, or something like that). That should fall back to checking for new USB devices every 2 seconds, instead of getting HAL notifications. That will introduce a random element into the attempts by gpilotd to connect. You may find that gnome-pilot will connect sometimes, and fail at other times.

Thanks for all your debugging. It is very helpful.

[Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount)]

Just on a sidenote: I got gpilotd working on 6.10. I deleted my config and reentered everything. It worked for a few syncs, then started to kill my Z22 again or gpilot just hung itself up (had to kill it as it wouldn't react to anything at all).
So it seems to be possible to sync, but I have no idea what causes the change in behavior as I definitly didn't change anything in the config after syncing successfully.

[Matt Davey (mcdavey)]

It all sounds like a timing issue. There have been several reports of regressions with minor udev updates, etc. It would be interesting if someone was able to report back with their experience of disabling HAL (see comment dated "2006-10-19 13:52:30 UTC") and/or libusb syncing.

It should be possible to build in an appropriate pause between HAL notification and gpilotd attempting a sync, but we need to have more of an idea of where the timing problem lies first.

It would also be good (as per my previous comment) to see if the device lock-ups can be reproduced with 'pilot-xfer -t 2', by starting pilot-xfer first and then attempting a sync.

[jon latorre (moebius-etxea)]

Sorry for the late answer :( I haven't be abble to use libusb (relly dind't try too hard, no much free time ). But I have try some of you suggestions.

If I launc pilot-xfer before pressing sync in the PDA pilot-xfer fails, but the PDA doens't hang(log attached).

I would try later to kill hal and try gpilot and to attach the log.

[Olivier Guerrier (olivier+launchpad-net)]

Same problem with a Palm m505.
Complete log attached upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=362565#c4

I've setup gpilotd to use libusb, and it works now.

[KenSentMe (jeroen-vandenieuwenhof)]

I have the same problem here with my Palm Zire 21.

I didn't try the libusb solution yet.

It seems like i can do a sync once, and when i try it the second time my Palm hangs completely and waits for me to reset it.

[Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount)]

Yes, I noticed this as well. If I restart gpilot via the gpilot-applet, it quite often starts to work again. Deleting the config in the gnome-pilot settings and entering them again also sometimes help. Very weird (and annoying).

[Guillaume Tamboise (gtamboise)]

I had the same problem with my Sony Clie (PEG-S360). A soft reset was (fortunately) enough on the Clie, it would not make me lose any data.
Setting the timeout to 0 on gpilotd made my Clie synchronize again. It has worked fine so far.

[Matt Davey (mcdavey)]

There is more info attached to the upstream bug, but the summary so far is:

some palmos devices appear to have problems if a sync is attempted immediately after the device connects to the host computer. gnome-pilot 2.0.14 uses HAL to detect a palmos device, and so tends to attempt a connection considerably faster than in 2.0.13 and earlier.

It's not clear what is causing this problem, but it seems to be in the usbserial / visor module case, so configuring libusb is a good workaround. Disabling HAL before attempting a sync also appears to work.

A patch is being worked on, and a testable gnome-pilot tarball can be downloaded from the upstream bug.

[Paul Roberts (paul-roberts)]

Thanks for the information so far and to Matt and others for their attention. I upgraded to Edgy this morning and have the same problem: my Palm Zire freezes and needs resetting when attempting a sync. I'll follow this and the upstream bug with eager interest!

[Daniel Holbach (dholbach)]

If somebody is keen enough to try feisty, I uploaded a gnome-pilot package with the workaround.

[KenSentMe (jeroen-vandenieuwenhof)]

There is an upstream fix for this bugs. Will this fix be implemented for the Edgy package too? It seems like a critical bug for this package.

[Phil (philipp-fischer)]

Matt Davey wrote: "A patch is being worked on, and a testable gnome-pilot tarball can be downloaded from the upstream bug".
Can anybody tell me where I can get this patch".
I use a Sony-Clie and a fix for this bug is really critical for me.
Thanks

[Matt Davey (mcdavey)]

Phil,
As mentioned by Daniel Holbach (2006-11-16 above), there is a testable package uploaded to Feisty. That package will contain the patch. In addition there's a link to the upstream bug at the top of this ticket and, as I mentioned, that contains a link to a downloadable tarball.

The version I committed to gnome-pilot CVS is viewable here:
http://cvs.gnome.org/viewcvs/gnome-pilot/gpilotd/gpilotd.c?r1=1.160&r2=1.161

It's also worth mentioning that gnome-pilot 2.0.15 has just been released. It will obviously take a bit of time for this to show up in Ubuntu.

[Phil (philipp-fischer)]

Dear Matt,
thanks a lot for this help. Sorry also for possibly asking stupid things
but I am more or less new in the Linux Community and actually try too
become a little bit more used to the system.
Thanks a lot
Philipp

Matt Davey schrieb:
> Phil,
> As mentioned by Daniel Holbach (2006-11-16 above), there is a testable package uploaded to Feisty. That package will contain the patch. In addition there's a link to the upstream bug at the top of this ticket and, as I mentioned, that contains a link to a downloadable tarball.
>
> The version I committed to gnome-pilot CVS is viewable here:
> http://cvs.gnome.org/viewcvs/gnome-pilot/gpilotd/gpilotd.c?r1=1.160&r2=1.161
>
> It's also worth mentioning that gnome-pilot 2.0.15 has just been
> released. It will obviously take a bit of time for this to show up in
> Ubuntu.
>
>

--
************************************************************
PD Dr. Philipp Fischer
Limnological Institute
University of Konstanz
Universitaetsstr. 10
D-78457 Konstanz
Germany
Tel: ++49 7531 884536
Fax: ++49 7531 883533

http://www.uni-konstanz.de/fischer-group
http://www.forschungstauchen-deutschland.de

[Phil (philipp-fischer)]

I just successfully compiled and installed gnome-pilot revision 1.161 on Edgy respectively my system says that I did it successfully. However, now I cannot start the gpilotd-control-applet in the shell. When I try to start it, the following message comes?

pfischer@pfischer-laptop:/usr/local/bin$ gpilotd-control-applet
** Message: No pilot userid/username information located
** Message: Unable to load pilot id/username, assuming unset
** Message: Cradle Type -> USB
** Message: cradle device name -> Cradle
** Message: cradle device name -> /dev/pilot
** Message: Pilot Speed -> 57600
** Message: Timeout -> 0

Until here I understand that message because the system is not configured yet.

However, now it comes:
** ERROR **: Es kann keine Verbindung zum GnomePilot-Dämon hergestellt werden
aborting...

My Translation:

**ERROR**:No connection to the GnomePilot-Deamon. aboarting.

** (bug-buddy:7061): WARNING **: Symbol für Ordner öffnen konnte nicht geladen werden

My Translation:

*** (bug-buddy:7061): WARNING **: Symbol for folder could not be loaded

Cannot access memory at address 0x1b90
Cannot access memory at address 0x1b90
pfischer@pfischer-laptop:/usr/local/bin$
pfischer@pfischer-laptop:/usr/local/bin$

Is there any idea what is going wrong?
Many thanks for the help.
Attached is the file from Bug-Buddey

[Matt Davey (mcdavey)]

Hi Phil,
It looks as though gnome-pilot hasn't actually been built correctly. I don't know what steps you took (I didn't give detailed instructions, because usually people asking for patches and building packages are old hands at this stuff).

You say you built "gnome-pilot 1.161", but 1.161 refers to one single file from the gnome-pilot source tree. So I don't know whether you checked out the whole gnome-pilot source from CVS (I doubt it) or just dropped the updated gpilotd.c file into some other source distribution of gnome-pilot.

Anyway, here are some more detailed instructions that might help you along:
1. download gnome-pilot 2.0.15 from gnome.org:
   http://ftp.gnome.org/pub/GNOME/sources/gnome-pilot/2.0/gnome-pilot-2.0.15.tar.gz
2. unpack the file using 'tar xzf gnome-pilot-2.0.15.tar.gz'
3. change into the gnome-pilot-2.0.15 directory.
4. build it, configuring it to put the installation somewhere that won't conflict with your system installation (so that if an updated Edgy version is released you can easily upgrade). Here's how to build it:
4a. "./configure --prefix=/tmp/gp" <-- or use some other location instead of /tmp/gp
4b. "make && make install"
5. Now, start the background daemon: "killall gpilotd; /tmp/gp/libexec/gpilotd"
6. In another window, start the corresponding config applet:
    "/tmp/gp/bin/gpilotd-control-applet"

With any luck, you'll be in business, i.e. able to configure and enable the backup conduit. You won't have Evolution conduits at this stage. If you want those,
copy the ".conduit" files from your system installation (I'm not 100% where they go on Ubuntu, so do 'locate e-address | grep conduit') and put them into /tmp/gp/share/gnome-pilot/conduits/.

These instructions are off the top of my head, so apologies if I've made some mistakes.

[Phil (philipp-fischer)]

Dear Matt,
thanks a lot for your great help. I now did as you said and installed
the gnome-pilot in /temp/gp.

Unfortunately, I now have the problem that the daemon obviously cannot
be registered (see below). Sorry for bothering you again but I really
do not have any clue what happens.

Again, thanks a lot.
Philipp
I have attached the entire output of the compiling, make ans make
install process.

root@pfischer-laptop:/home/pfischer/Install_test/gnome-pilot-2.0.15#
/temp/gp/libexec/gpilotd
gpilotd-Message: gnome-pilot 2.0.15 starting...
gpilotd-Message: compiled for pilot-link version 0.12.1
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]

(gnome-pilot:22702): GnomeUI-WARNING **: While connecting to session
manager:
Authentication Rejected, reason : None of the authentication protocols
specified are supported and host-based authentication failed.

(gnome-pilot:22702): gpilotd-WARNING **: Es stehen keine Geräte zur
Verfügung. (There are no devices available)

(gnome-pilot:22702): gpilotd-WARNING **: Keine Geräte verfügbar (No
devices available)

(gnome-pilot:22702): gpilotd-WARNING **: Number of PDAs is configured to 0
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 1
gpilotd-Message: Cannot register gpilotd because not listed
root@pfischer-laptop:/home/pfischer/Install_test/gnome-pilot-2.0.15#

Matt Davey schrieb:
> Hi Phil,
> It looks as though gnome-pilot hasn't actually been built correctly. I don't know what steps you took (I didn't give detailed instructions, because usually people asking for patches and building packages are old hands at this stuff).
>
> You say you built "gnome-pilot 1.161", but 1.161 refers to one single
> file from the gnome-pilot source tree. So I don't know whether you
> checked out the whole gnome-pilot source from CVS (I doubt it) or just
> dropped the updated gpilotd.c file into some other source distribution
> of gnome-pilot.
>
> Anyway, here are some more detailed instructions that might help you along:
> 1. download gnome-pilot 2.0.15 from gnome.org:
> http://ftp.gnome.org/pub/GNOME/sources/gnome-pilot/2.0/gnome-pilot-2.0.15.tar.gz
> 2. unpack the file using 'tar xzf gnome-pilot-2.0.15.tar.gz'
> 3. change into the gnome-pilot-2.0.15 directory.
> 4. build it, configuring it to put the installation somewhere that won't conflict with your system installation (so that if an updated Edgy version is released you can easily upgrade). Here's how to build it:
> 4a. "./configure --prefix=/tmp/gp" <-- or use some other location instead of /tmp/gp
> 4b. "make && make install"
> 5. Now, start the background daemon: "killall gpilotd; /tmp/gp/libexec/gpilotd"
> 6. In another window, start the corresponding config applet:
> "/tmp/gp/bin/gpilotd-control-applet"
>
> With any luck, you'll be in business, i.e. able to configure and enable the backup conduit. You won't have Evolution conduits at this stage. If you want those,
> copy the ".conduit" files from your system installation (I'm not 100% where they go on Ubuntu, so do 'locate e-address | grep conduit') and put them into /tmp/gp/share/gnome-pilot/conduits/.
>
> These instru...

[Matt Davey (mcdavey)]

On Fri, 2006-11-24 at 15:54 +0000, Phil wrote:
> Dear Matt,
> thanks a lot for your great help. I now did as you said and installed
> the gnome-pilot in /temp/gp.
>
> Unfortunately, I now have the problem that the daemon obviously cannot
> be registered (see below). Sorry for bothering you again but I really
> do not have any clue what happens.

I'm not surprised...

You need to copy the file:
/tmp/gp/lib/bonobo/servers/GNOME_Pilot_Daemon.server
into the right location, which is probably
/usr/lib/bonobo/servers/
(hint: look for other .server files...)

If you want to use the applet, you'll need to copy the other .server
file from /tmp/gp/lib/bonobo/servers/

Note, by the way, that /tmp/gp might well get cleared out on a reboot,
so if you want to keep this configuration for any length of time you may
want to install somewhere else :)

Matt

Matt Davey Never forget what a man says to you when he is angry.
<email address hidden>

[kbg (kbg)]

Hi Phil,

if you are still having problems you should give libusb a try. This is quite easy to configure and solved the problem for my m505.

For Edgy you can perform the following steps:

1. Make sure libusb is installed (apt-get install libusb-0.1-4).

2. Change the device via gpilotd-control-applet from "/dev/pilot" to "usb:". Now remove the gpilot-applet from the panel and killall gpilotd.

3. Remove the visor kernel module (rmmod visor) and put it on the blacklist by creating the file /etc/modprobe.d/blacklist-palm containing "blacklist visor" (without quotation marks).

4. Finally you need to install the udev rule for libusb by
  ln -s /usr/share/pilot-link/udev/60-libpisock.rules /etc/udev/rules.d/

Now add gpilot-applet to the panel again and your Palm should synchronize without hanging.

[Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount)]

Thanks for the libusb-tip. Unfortunatly, it doesn't work for my Z22 (ID is in the udev-file), the pilot-applet hangs as soon as I connect the PDA.
Is there going to be a fix for edgy? I'm not willing to upgrade to feisty and dapper won't boot. As this bug affects quite some people, a fixed package would be a really good thing IMO.

[Phil (philipp-fischer)]

Dear Matt,
thanks a lot for the helpfull tips. My sony clie now works more or less
fine, does not freeze any more and is able to synchronize. The last
thing what I have not managed up to now is to convince the applet to use
the conduits from evolution, which basically is my final goal.

You wrote that I have to copy the conduit files to the share/conduits
folder. I did this but these e-conduits do not show up in the
configuration list of the applet. Is there probably another way to get
these conduits to work.

Thanks again for this really great help.
Phil

 Again thousand thanks for these hepfull tips

Matt Davey schrieb:
> On Fri, 2006-11-24 at 15:54 +0000, Phil wrote:
>
>> Dear Matt,
>> thanks a lot for your great help. I now did as you said and installed
>> the gnome-pilot in /temp/gp.
>>
>> Unfortunately, I now have the problem that the daemon obviously cannot
>> be registered (see below). Sorry for bothering you again but I really
>> do not have any clue what happens.
>>
>
> I'm not surprised...
>
> You need to copy the file:
> /tmp/gp/lib/bonobo/servers/GNOME_Pilot_Daemon.server
> into the right location, which is probably
> /usr/lib/bonobo/servers/
> (hint: look for other .server files...)
>
> If you want to use the applet, you'll need to copy the other .server
> file from /tmp/gp/lib/bonobo/servers/
>
> Note, by the way, that /tmp/gp might well get cleared out on a reboot,
> so if you want to keep this configuration for any length of time you may
> want to install somewhere else :)
>
> Matt
>
> Matt Davey Never forget what a man says to you when he is angry.
> <email address hidden>
>
>

--
************************************************************
PD Dr. Philipp Fischer
Limnological Institute
University of Konstanz
Universitaetsstr. 10
D-78457 Konstanz
Germany
Tel: ++49 7531 884536
Fax: ++49 7531 883533

http://www.uni-konstanz.de/fischer-group
http://www.forschungstauchen-deutschland.de

[Phil (philipp-fischer)]

Hi Matt,
in between it is all fine with your great help. My Sony Clie is properly
working together with gnome-pilot and all syncs are running smoothly.
The last problem I had to solve was that the calendar sync stopped
somewhen in between. I solved this problem by doing a data reduction on
my palm before and deleting the dates older than 6 month from now on my
palm. Now all works fine.
I really want to say thank you for this great help and I am now the more
convinced that my change from Windows to Ubuntu was the right desicion.
Thanks a lot
Phil

Am Donnerstag, den 23.11.2006, 22:45 +0000 schrieb Matt Davey:

> Hi Phil,
> It looks as though gnome-pilot hasn't actually been built correctly. I don't know what steps you took (I didn't give detailed instructions, because usually people asking for patches and building packages are old hands at this stuff).
>
> You say you built "gnome-pilot 1.161", but 1.161 refers to one single
> file from the gnome-pilot source tree. So I don't know whether you
> checked out the whole gnome-pilot source from CVS (I doubt it) or just
> dropped the updated gpilotd.c file into some other source distribution
> of gnome-pilot.
>
> Anyway, here are some more detailed instructions that might help you along:
> 1. download gnome-pilot 2.0.15 from gnome.org:
> http://ftp.gnome.org/pub/GNOME/sources/gnome-pilot/2.0/gnome-pilot-2.0.15.tar.gz
> 2. unpack the file using 'tar xzf gnome-pilot-2.0.15.tar.gz'
> 3. change into the gnome-pilot-2.0.15 directory.
> 4. build it, configuring it to put the installation somewhere that won't conflict with your system installation (so that if an updated Edgy version is released you can easily upgrade). Here's how to build it:
> 4a. "./configure --prefix=/tmp/gp" <-- or use some other location instead of /tmp/gp
> 4b. "make && make install"
> 5. Now, start the background daemon: "killall gpilotd; /tmp/gp/libexec/gpilotd"
> 6. In another window, start the corresponding config applet:
> "/tmp/gp/bin/gpilotd-control-applet"
>
> With any luck, you'll be in business, i.e. able to configure and enable the backup conduit. You won't have Evolution conduits at this stage. If you want those,
> copy the ".conduit" files from your system installation (I'm not 100% where they go on Ubuntu, so do 'locate e-address | grep conduit') and put them into /tmp/gp/share/gnome-pilot/conduits/.
>
> These instructions are off the top of my head, so apologies if I've made
> some mistakes.
>

--
***************************************
PD Dr. Philipp Fischer
Limnological Institute
University Konstanz
78457 Konstanz
phone: ++49 (0)7531 884536
fax: ++49 (0)7531883533
www.uni-konstanz.de/fischer-group

[Matt Davey (mcdavey)]

I have built an unofficial Ubuntu package based on the recent fixes, which should be suitable for Edgy. You can try them out from:
http://www.inference.phy.cam.ac.uk/mcdavey/downloads/

This build is not an official Ubuntu release. It is unsupported, but should fix two specific issues with the current Edgy packages:
1. problems with crashing the palmos device when attempting a sync.
2. problems crashing the gpilotd-control-applet when retrieving the username and deviceID in the 'add pda' step.

If you have problems with these packages, feel free to open a bug on bugzilla.gnome.org. Strictly speaking, you shouldn't send them to ubuntu, because they haven't built this updated package...

If you have success, feel free update this bug with any success stories.

[Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount)]

Finally! :) Your packages work, thank you very much!
The libusb-stuff didn't, but now I can sync my palm again without crashing it.

Works for me, if it works for others I hope to see an official update for gnome-pilot, as this might affect many others as well.

[KenSentMe (jeroen-vandenieuwenhof)]

Well it doesn't work here. On both my desktop pc as my laptop i get a bug buddy report when running the sync with Evolution. In the attached file are both logs. My Palm Zire 21 doesn't crash though, it just loses connection after a while.

[Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount)]

OK, I don't use Evolution, but I'll check later if I get this crash as well.

[KenSentMe (jeroen-vandenieuwenhof)]

What program do you use then?

[KenSentMe (jeroen-vandenieuwenhof)]

I found out the sync process only crashes when syncing the Evolution Calendar. The other coduits are synced properly.

[Fridtjof Busse (fbusse-deactivatedaccount-deactivatedaccount)]

I only backup my files (calendar, etc) with gnome-pilot and let Gnome display the appointments in the calendar. I don't use Evolution for anything at all (although I have to let it run ones to include the info in the gnome calendar).
That looks like the reason I don't see you crash.

[Matt Davey (mcdavey)]

I set my sync options to "copy from PDA", and got a crash while syncing the calendar conduit. I did not have trouble with a "copy from PDA" in the address or memo conduits.

I tried downgrading to the Edgy package and produced the same crashes. So it seems to be a bug in the evolution calendar backend, or conduit. I guess you'd better disable the calendar conduit for the moment. There have been reports elsewhere of the calendar conduit not working, so I suspect a general problem in that code.

I didn't get the same crash as KenSentMe, my crash occured on the evolution-data-server side (icalcomponent_as_ical_string)

Regards,

Matt
----------------------------------
(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb75626cb in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2 0xb750a281 in strtold_l () from /lib/tls/i686/cmov/libc.so.6
#3 0xb750a632 in system () from /lib/tls/i686/cmov/libc.so.6
#4 0x0804b2f9 in gnome_segv_handler (signo=11) at server.c:114
#5 <signal handler called>
#6 pvl_head (L=0x813b3e0) at pvl.c:541
#7 0xb7d08744 in icalcomponent_as_ical_string (impl=0x807ef48) at icalcomponent.c:334
#8 0xb7169f38 in save_file_when_idle (user_data=0x80716a0) at e-cal-backend-file.c:176
#9 0xb7679aa1 in g_source_is_destroyed () from /usr/lib/libglib-2.0.so.0
#10 0xb767b802 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#11 0xb767e7df in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#12 0xb767eb89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#13 0xb7b10a23 in bonobo_main () from /usr/lib/libbonobo-2.so.0
#14 0x0804ba24 in main (argc=134643760, argv=0xbfe281b4) at server.c:393
#15 0xb74e98cc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#16 0x0804a451 in _start ()

[KenSentMe (jeroen-vandenieuwenhof)]

Is there a bug filed already on this calendar conduit problem. If no,
where should i file it?

[Matt Davey (mcdavey)]

https://launchpad.net/distros/ubuntu/+source/gnome-pilot/+bug/19528

[Phil (philipp-fischer)]

Dear Matt,
thanks a lot for the package. It works abolutely fine with my clie. No
more problems.
Thanks again for your help
Phil

Am Dienstag, den 28.11.2006, 18:49 +0000 schrieb Matt Davey:

> I have built an unofficial Ubuntu package based on the recent fixes, which should be suitable for Edgy. You can try them out from:
> http://www.inference.phy.cam.ac.uk/mcdavey/downloads/
>
> This build is not an official Ubuntu release. It is unsupported, but should fix two specific issues with the current Edgy packages:
> 1. problems with crashing the palmos device when attempting a sync.
> 2. problems crashing the gpilotd-control-applet when retrieving the username and deviceID in the 'add pda' step.
>
> If you have problems with these packages, feel free to open a bug on
> bugzilla.gnome.org. Strictly speaking, you shouldn't send them to
> ubuntu, because they haven't built this updated package...
>
> If you have success, feel free update this bug with any success stories.
>

--
***************************************
PD Dr. Philipp Fischer
Limnological Institute
University Konstanz
78457 Konstanz
phone: ++49 (0)7531 884536
fax: ++49 (0)7531883533
www.uni-konstanz.de/fischer-group

[Borden Rhodes (dominussuus-deactivatedaccount)]

I would like to add that this bug has, on occasion, wiped the RAM on my Palm T|X when I tried to sync. I think this is a serious enough problem that it should be patched in Edgy.

[Daniel Holbach (dholbach)]

Matt Davey: is this what you intended for the fix?

[Matt Davey (mcdavey)]

Yes, looks right.

Oddly there's one stray diff block I don't recognise:
------------------
@@ -1256,6 +1266,7 @@
 gpcap_save_state (GnomePilotCapplet *gpcap)
 {
  GnomePilotCappletPrivate *priv;
+ GtkObjectClass *gppd_class;

  priv = gpcap->priv;
 -------------------

This wasn't in the 02_capplet_pdialog.diff file in my edgy package, so I don't know where it came from! It'll just cause an unused variable warning, so it's not worth removing unless you feel like it.

[Daniel Holbach (dholbach)]

Thanks a lot Matt.

[Daniel Holbach (dholbach)]

The proposed update to edgy-updates adresses two issues:

  * gpilotd/gpilotd.c:
    - add usleep() to wait for devices not being ready immediately.

  * capplet/gnome-pilot-capplet.c, capplet/gnome-pilot-pdialog.c,
   capplet/gnome-pilot-pdialog.h, capplet/util.c:
    - fixes gnome-pilot crashers
      http://bugzilla.gnome.org/show_bug.cgi?id=365181

[jon latorre (moebius-etxea)]

I have tested de patch in x86 an ppc and seems to work well. I haven't see the package in edgy-proposed and have to manual patch the source package.

[Martin Pitt (pitti)]

First, please fix this bug in Feisty first and get it tested. Also, what's the last hunk good for, that seems like an unnecessary no-op to me?

[Martin Pitt (pitti)]

Also, did that work in dapper, i. e. is that a dapper->edgy regression?

[Martin Pitt (pitti)]

Please ignore my last question, further up it said that it worked in dapper.

[Martin Pitt (pitti)]

Please subscribe ubuntu-sru again after fixing the bug in Edgy and filing a SRU request that complies to the policy. Thank you!

[Launchpad Janitor (janitor)]

[Expired for gnome-pilot (Ubuntu Edgy) because there has been no activity for 60 days.]

[Wouter Stomp (wouterstomp-deactivatedaccount)]

This was fixed in 2.0.15