Ubuntu
gnome-pilot package

2.6.27-4-generic gpilotd-control-applet does not sync

Bug #274936 reported by Marcel on 2008-09-26

This bug report is a duplicate of: Bug #282491: [intrepid] impossible to sync palm pilot device. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	gnome-pilot (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

With 8.10 alpha6 nothing happens when I try to sync my Palm TX. Sending and receiving the PDA identification also does not respond to the sync command from the PDA

I used to sync my PDA on 8.04.1 without any problem.

gnome-pilot 2.0.15-2ubuntu3
gnome-pilot-conduits 2.0.15-1.2
pilot-link 0.12.3-4ubuntu2

Tags:

Revision history for this message

Brian Murray (brian-murray) wrote on 2008-09-30:

Thank you for taking the time to report this bug and helping to make Ubuntu better. It'd be helpful to know how your device is connected to the system and additionally, the output of 'dmesg' after attempting a sync might be informative. Thanks in advance.

Changed in gnome-pilot:
status:	New → Incomplete

Revision history for this message

Marcel (marcel-vd-berg) wrote on 2008-10-01:

dmesg Edit (3.1 KiB, text/plain)

Thank you for taking the time to review this report and helping to make
Ubuntu better.

Sorry, I forgot to tell, I used a USB cable.
The wireless option will only work after I once selected [network] which follows after the "Get identification from PDA".

Attached: dmesg

Revision history for this message

Ioan Rogers (ioanrogers) wrote on 2008-10-01:

Hi, I have the same problem with alpha6. I only just got this centro today, so I don't know if it ever worked with gnome-pilot. I'm also using usb cable.

'pilot-xfer --list -p usb:' works fine, and I've successfully sync'd the device with Evolution using multisync0.90.

gnome-pilot just sits there never seeing the device.

gnome-pilot settings are the same as I use for pilot-link:
** Message: Cradle Type -> USB
** Message: cradle device name -> Centro
** Message: cradle device name -> usb:
** Message: Pilot Speed -> 57600
** Message: Timeout -> 2

I also build the latest upstream stable release (2.0.16), but I get the same issue.

Thanks

Revision history for this message

Ioan Rogers (ioanrogers) wrote on 2008-10-01:

Oops, gpilotd went in /usr/libexec, not /usr/bin, so I think I may have still been running the old daemon.

So after killing all gpilot* processes, and purging the packages, I tried again. 2.0.16 works fine /only if/ compiled without HAL support. The gui becomes fairly unresponsive (excessive polling, maybe?) but it does sync.

I'll try rebuilding the intrepid packages without hal later to see if that helps.

Revision history for this message

SimonSoltek (ssoltek) wrote on 2008-10-20:

The same here with Tungsten E2

gpilotd from current intrepid simply hangs.

Revision history for this message

Ioan Rogers (ioanrogers) wrote on 2008-10-21:

I didn't get around to rebuilding the ubuntu sources yet, but upstream definitely works without hal, and fails with hal. Upstream does list hal support as experimental, so I guess they weren't lying!

Workarounds:
* rebuild from source without hal
* if you have bluetooth, you can do the hotsync over tcp over ppp over bluetooth, as documented on pilot-link.org, and tell gpilot to use "net:"

Revision history for this message

Brian Murray (brian-murray) wrote on 2008-11-17:

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, this bug is a duplicate of bug 282491, which is now fixed in Intrepid and Jaunty, and is being marked as such. Please feel free to submit any future bugs you may find.