GNOME Bugzilla – Bug 123157
hotsync crash
Last modified: 2006-03-13 22:50:50 UTC
Package: gnome-pilot Severity: normal Version: 0.1.71 Synopsis: hotsync crash Bugzilla-Product: gnome-pilot Bugzilla-Component: gpilotd Description: Description of Problem: gpilotd crash when i hotsync. It's always when the file "TnSilkChanger" have to be backup. Steps to reproduce the problem: 1. hotsync 2. 3. Actual Results: crash after this file and dosent continue Expected Results: How often does this happen? any time i hotsync Additional Information: i have a Sony clie PEG-NX80 Debugging Information: Backtrace was generated from '/usr/bin/gpilotd' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1082589216 (LWP 14108)] 0xffffe002 in ?? ()
+ Trace 40411
Thread 1 (Thread 1082589216 (LWP 14108))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-09-24 21:01 ------- The original reporter (darkice69@msn.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-pilot-maint@bugzilla.gnome.org.
According to the stack trace, this bug occurred in a Gnome 1.x application. Please upgrade to a newer and improved version of gnome, e.g. 2.8.
*** This bug has been marked as a duplicate of 136010 ***