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 146842 - crash on syncronizing with palm
crash on syncronizing with palm
Status: VERIFIED INCOMPLETE
Product: gnome-pilot
Classification: Other
Component: conduit system
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-24 05:17 UTC by aargon
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description aargon 2004-07-09 11:37:14 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: gnome-pilot
Severity: normal
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: crash on syncronizing with palm
Bugzilla-Product: gnome-pilot
Bugzilla-Component: conduit system
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:
when trying a hotsync the applet crashes after a few seconds
(synchronizing EAddress). 

Steps to reproduce the crash:
1. press hotsync button on palm m505 craddle (serial)
2. 
3. 

Expected Results:
hotsyncing

How often does this happen?
every time

Additional Information:




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


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 aargon@rat.at.
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 Elijah Newren 2004-07-09 19:55:37 UTC
Thanks for the bug report. Without a stack trace from the crash it's very hard
to determine what caused the crash.  Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information about getting
a useful stack trace.
Comment 2 Elijah Newren 2004-08-11 03:13:43 UTC
No response--closing.