I confirm the same bug using Ubuntu 7.04 (32 bits) in a AMD64, with a Tungsten T5 connected via USB, and using /dev/pilot.
After sync finishes, and as soon as the Palm turns off, the gpilotd app begins to use CPU time at 90%, more or less. So, in System Monitor, I stop thist application, then kill it. So it turns again to 'Executable' status and CPU turns normal again. -- 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 Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
