After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 147406 - gpilotd crashes on second run
gpilotd crashes on second run
Status: RESOLVED DUPLICATE of bug 146595
Product: gnome-pilot
Classification: Other
Component: gpilotd
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-07-12 11:57 UTC by Paulo Sedrez
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Paulo Sedrez 2004-07-12 11:59:19 UTC
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.

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 download.

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.

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.




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


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.

Comment 1 Paulo Sedrez 2004-07-12 13:20:57 UTC
Sorry, forgot the backtrace. Will generate another.
Comment 2 Paulo Sedrez 2004-07-12 13:22:46 UTC
backtrace on bug report #147412
http://bugzilla.gnome.org/show_bug.cgi?id=147412
Comment 3 Paulo Sedrez 2004-07-12 13:25:50 UTC

*** This bug has been marked as a duplicate of 146595 ***