GNOME Bugzilla – Bug 300612
gpilotd crashes before hotsync finishes
Last modified: 2006-03-26 16:40:12 UTC
Distribution: Debian 3.1 Package: gnome-pilot Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Ubuntu Synopsis: gpilotd crashes before hotsync finishes Bugzilla-Product: gnome-pilot Bugzilla-Component: gpilotd Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: - gpilotd crashes in the midst of a hotsync with the Treo 650 Steps to reproduce the crash: 1. Connect Treo to USB port 2. Click hotsync button 3. Sync starts and then abruptly ends with message about gpilotd unexpectedly crashing Expected Results: - Hotsync should finish without crashing How often does this happen? - Intermittently Additional Information: - Previously, in order to get gnome-pilot working, I had to add the following entry for the Treo 650 to /usr/share/gnome-pilot/devices.xml: <!-- Treo 650 --> <device vendor_id="0830" product_id="0061" /> Debugging Information: Backtrace was generated from '/usr/bin/gpilotd' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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) [Thread debugging using libthread_db enabled] [New Thread -1222522208 (LWP 31653)] [New Thread -1240040528 (LWP 31901)] [New Thread -1231647824 (LWP 31900)] (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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 58169
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-14 10:01 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-pilot". Setting to default milestone for this product, '---' 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 fheinsen@earthlink.net. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Would appear to be a duplicate of the '> 64k segment' issue with pilot-link versions up to 0.11.*. A workaround is to list the culprit pdb/prc file in the list of files to exclude from backups. *** This bug has been marked as a duplicate of 136010 ***