GNOME Bugzilla – Bug 309098
gpilotd crashes at time of pressing sync button on pilot
Last modified: 2005-08-03 19:39:07 UTC
Steps to reproduce: 1. Start gpilotd-control-applet 2. Connect USB port with palm 3. Press sync buttin Stack trace: AFTER MESSAGE LOG AND program output YOU WILL FIND THE TRACE... Result from message log: Jun 26 21:21:18 viclap kernel: usb 1-1.3: new full speed USB device using uhci_hcd and address 6 Jun 26 21:21:18 viclap kernel: visor 1-1.3:1.0: Sony Clie 5.0 converter detected Jun 26 21:21:18 viclap kernel: usb 1-1.3: Sony Clie 5.0 converter now attached to ttyUSB0 Jun 26 21:21:18 viclap kernel: usb 1-1.3: Sony Clie 5.0 converter now attached to ttyUSB1 Jun 26 21:22:09 viclap kernel: usb 1-1.3: USB disconnect, address 6 Jun 26 21:22:09 viclap kernel: clie_5 ttyUSB0: Sony Clie 5.0 converter now disconnected from ttyUSB0 Jun 26 21:22:09 viclap kernel: clie_5 ttyUSB1: Sony Clie 5.0 converter now disconnected from ttyUSB1 Jun 26 21:22:09 viclap kernel: visor 1-1.3:1.0: device disconnected Output from gpilotd-control-applet: ** Message: Pilot name -> MyPilot ** Message: Pilot id -> 17492 ** Message: Pilot username -> Victor Tapia ** Message: Pilot creation/rom = 0/0 ** Message: Cradle Type -> USB ** Message: cradle device name -> Cradle ** Message: cradle device name -> /dev/pilot ** Message: Pilot Speed -> 115200 ** Message: Timeout -> 2 gpilotd-Message: Activating object OAFIID:GNOME_Pilot_Daemon ** Message: pilot = MyPilot ** Message: Pilot name -> MyPilot ** Message: Pilot id -> 17492 ** Message: Pilot username -> Victor Tapia ** Message: Pilot creation/rom = 0/0 ** Message: Cradle Type -> USB ** Message: cradle device name -> Cradle ** Message: cradle device name -> /dev/pilot ** Message: Pilot Speed -> 115200 ** Message: Timeout -> 2 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 -1208322368 (LWP 20530)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x00e96402 in ?? ()
+ Trace 61549
Thread 1 (Thread -1208322368 (LWP 20530))
Other information: I had Fedora Core 3 with no problem (once in a while I had to execute procedure twice), I just upgraded to fedora Core 4 and the crash always happens.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
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 ***