GNOME Bugzilla – Bug 307857
fc4 hotsync immediately crashes gpilotd
Last modified: 2005-06-24 16:32:57 UTC
Distribution: Fedora Core release 4 (Stentz) Package: gnome-pilot Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: fc4 hotsync immediately crashes gpilotd Bugzilla-Product: gnome-pilot Bugzilla-Component: gpilotd Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: when i hit the hotsync button on my usb pilot crade, i get an error message that gpilotd has crashed Steps to reproduce the crash: 1. have palm cradle attached via usb in fc4 2. hit hotsync button Expected Results: palm will sync How often does this happen? every time Additional Information: Debugging Information: Backtrace was generated from '/usr/libexec/gpilotd' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208277312 (LWP 5390)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x005b3402 in ?? ()
+ Trace 61081
Thread 1 (Thread -1208277312 (LWP 5390))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-16 00:44 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was amessina@messinet.com.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 274032 ***