GNOME Bugzilla – Bug 155654
Gpilotd crashes upon trying to sync jpeg-foto
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: gnome-pilot Severity: major Version: GNOME2.8.1 unspecified Gnome-Distributor: Ubuntu Synopsis: Gpilotd crashes upon trying to sync jpeg-foto Bugzilla-Product: gnome-pilot Bugzilla-Component: gpilotd Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Using tungsten-e Upon trying to sync jpeng-foto, gpilotd crashes. This is unrecoverable Steps to reproduce the crash: 1. Connect T-E 2. Press hotsync on T-E 3. Wait for jpeg-foto to come around and watch the daemon crash Expected Results: Should back up the entire contents of my palm to the folder How often does this happen? Every time I try and sync with this application installed on my T-E Additional Information: See additional bug regarding file-foto, same result 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)...(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 1088156800 (LWP 4501)] (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 51101
Thread 1 (Thread 1088156800 (LWP 4501))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-17 15:11 ------- 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 cpcburger@hotmail.com. 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.
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 146228 ***