From: Heiko Ossowski <mycket@freenet.de>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.4.2
Subject: gnome-pilot-deamon crashes with Sony clie PEG TJ-25/E1

Distribution: Debian testing/unstable
Package: gnome-pilot
Severity: normal
Version: GNOME2.4.1 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: gnome-pilot-deamon crashes with Sony clie PEG TJ-25/E1
Bugzilla-Product: gnome-pilot
Bugzilla-Component: gpilotd
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:

Deamon gave a message "not connected. restart deamon to reconnect"
I plugged my TJ-25 to /dev/USB0, pressed HOTSync and 
selected "restart" on the context-menu on the pilot-applet symbol
in the gnome-panel. Then I got the "crashed" error.

Gnome-Pilot does not find the PEG-TJ-25 (KPilot works fine, so
I think the Hardware is OK). When I restart the Deamon, it crashes :-(
This happened every time i tried to get my clie working with gnome.

I use Debian testing distribution...



Debugging Information:

Backtrace was generated from '/usr/bin/gpilot-applet'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/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)...[Thread debugging using
libthread_db enabled]
[New Thread 1088029248 (LWP 2343)]
(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)...0x4067e40e in __waitpid_nocancel () from
/lib/tls/libpthread.so.0

+ Trace 47584

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


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 mycket@freenet.de.
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.