I think this bug needs to be reviewed. I can confirm the same problem as
the original reporter: gpilotd consuming 100% CPU after a successful
sync. Actually, there are two outcomes after a sync: either gpilotd
starts eating up the CPU, or the "Pilot applet" stops responding to
requests (gnome-pilot settings dialog are not displayed). In both
situations the solutions is to run 'killall gpilotd'. In the latter
case, this follows by several gnome-pilot settings windows being opened.
All this is happening on Feisty with Palm TX connected via USB. I'm
using 'usb:' as the palm device, not /dev/pilot.
** Changed in: gnome-pilot (Ubuntu)
Status: Fix Released => Confirmed
--
gpilotd runs away with CPU after completing hotsync
https://bugs.launchpad.net/bugs/29043
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
