Distribution: Fedora Core release 2 (Tettnang)
Package: gnome-pilot
Severity: major
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: gpilotd crashes on second run
Bugzilla-Product: gnome-pilot
Bugzilla-Component: gpilotd
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:
This are more details on a bug previosly reported. Included now trace
with debug symbols.

Same as bug #147406 (http://bugzilla.gnome.org/show_bug.cgi?id=147406),
this time INCLUDING the backtrace.


Steps to reproduce the crash:
1. Plug in the pilot (mine, USB Tungstein E)
2. Do one hotsync, OK
3. Do another hotsync (for a dry run), gpilotd crashes.

Expected Results:
A dry run, without updates.


How often does this happen?
Every time.


Additional Information:
Fedora Core 2 with updates - except kernel, no reboot since install (31
days).
Duron 1.8XP, 512MB ram.

[sedrez@sedrez ~]$ rpm -qf /lib/tls/libthread_db.so.1
/lib/tls/libpthread.so.0 /usr/lib/libgnomeui-2.so.0 /lib/tls/libc.so.6
/usr/lib/libglib-2.0.so.0 /usr/lib/libgobject-2.0.so.0 
glibc-2.3.3-27
glibc-2.3.3-27
libgnomeui-2.6.0-3
glibc-2.3.3-27
glib2-2.4.0-1
glib2-2.4.0-1
[sedrez@sedrez ~]$ uname -a
Linux sedrez.ods.org 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686
athlon i386 GNU/Linux
[sedrez@sedrez ~]$ rpm -q kernel gnome-pilot
kernel-2.6.5-1.358
kernel-2.6.6-1.435.2.3
gnome-pilot-2.0.10-6.1

How to avoid the crash:
1- plug in the pilot
2- do a hotsync, OK
3- unplug the pilot and plug it again
4- do a hotsync (dry run), OK.




Debugging Information:

Backtrace was generated from '/usr/libexec/gpilotd'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -150973792 (LWP 19108)]
0x003b3402 in ?? ()

+ Trace 48512

------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-12 08:54 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-pilot".
   Setting to default milestone for this product, '---'
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.