GNOME Bugzilla – Bug 320240
gpilotd crashes when Pilot connects to desktop
Last modified: 2005-11-20 16:45:49 UTC
Distribution: Fedora Core release 4 (Stentz) Package: gnome-pilot Severity: blocker Version: GNOME2.10.0 2.0.x Gnome-Distributor: Red Hat, Inc Synopsis: gpilotd crashes when Pilot connects to desktop Bugzilla-Product: gnome-pilot Bugzilla-Component: gpilotd Bugzilla-Version: 2.0.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: - gpilotd crashses with a dialogue box say that "gpilotd died unexpectedly", and offering to submit a bug report. Steps to reproduce the crash: 1. Start gnome-pilot using gpilotd-control-applet. gpilotd is now seen running. 2. Put pilot in the cradle, press the pilot HotSync button. 3. Get a dialogue saying that gpilotd has died unexpectedly. Expected Results: - A desktop synchronisation How often does this happen? - Every time. Additional Information: - Pilot a Tungsten T3. - It is connected to USB port. - Configured the thing to use /dev/ttyUSB1 at 115200. - The pilot syncs fine through pilot-xfer, and I regularly back it up. Debugging Information: Backtrace was generated from '/usr/libexec/gpilotd' (no debugging symbols found) Using host libthread_db library "/lib64/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 46912496436832 (LWP 6814)] (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) 0x0000003f8130bf45 in waitpid () from /lib64/libpthread.so.0
+ Trace 63797
Thread 1 (Thread 46912496436832 (LWP 6814))
------- Bug moved to this database by unknown@gnome.bugs 2005-10-30 14:56 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was sev@severedhead.net.
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 ***