Bug 451447 - After first hotsync, gpilotd hangs (probably busy waiting)
After first hotsync, gpilotd hangs (probably busy waiting)
Product: Fedora
Classification: Fedora
Component: gnome-pilot (Show other bugs)
i386 Linux
low Severity low
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-06-14 12:51 EDT by Gérard Milmeister
Modified: 2018-04-11 13:56 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-07 15:40:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gérard Milmeister 2008-06-14 12:51:40 EDT
I can synchronize normally the first time with a Palm TX on the "usb:" device.
Then gpilotd takes full cpu, and a second hotsync is no longer possible, the
applet is also dead.I have to kill gpilotd, which is respawned, and
synchronizing works again for one time.
Comment 1 Andrea Dell'Amico 2008-11-27 11:03:28 EST
I'm seeing something similar: the first sync hangs frequently, especially if there are MMSs to backup. gpilotd dies, I kill the pilot applet, then all goes well and I can sync with success until a suspend/resume cycle.

After suspend/resume, the sync connection fails (port busy). I have to manually kill gpilotd and the pilot applet to be able to sync again.

I usually sync via bluetooth, but via USB the behaviur is the same.
Comment 2 Matthew Barnes 2008-11-29 11:32:19 EST
Is this issue still present on Fedora 10 or later?
Comment 3 Matěj Cepl 2009-01-27 20:57:45 EST
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Comment 4 Matěj Cepl 2009-03-07 15:40:11 EST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.


Note You need to log in before you can comment on or make changes to this bug.