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 161798 - Pilot crashed
Pilot crashed
Status: RESOLVED FIXED
Product: gnome-pilot
Classification: Other
Component: applet
unspecified
Other Linux
: High critical
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-12-20 16:13 UTC by kern
Modified: 2006-08-08 18:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gdb output of gpilod after crash (14.76 KB, text/plain)
2004-12-21 15:43 UTC, kern
Details

Description kern 2004-12-20 16:13:53 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: gnome-pilot
Severity: major
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Pilot crashed
Bugzilla-Product: gnome-pilot
Bugzilla-Component: applet
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
Crashed while attempting a synchronization


Steps to reproduce the crash:
1. Press the pilot sync button, crash
2. 
3. 

Expected Results:
Update Evolution data to the Pilot


How often does this happen?
Just this once.


Additional Information:
This program is  frustrating because there is no way to get information
on why things are not working or the status of the serial port. A small
effort in providing debug feedback (if desired) would solve a lot of
problems.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-20 11:13 -------


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 Elijah Newren 2004-12-20 17:01:06 UTC
Thanks for the bug report. Without a stack trace from the crash it's very hard
to determine what caused the crash.  Could you provide one?  Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information about getting
a useful stack trace.
Comment 2 kern 2004-12-21 15:43:19 UTC
Created attachment 35086 [details]
gdb output of gpilod after crash

Pushed the sync button on my Palm. Pilot Synchronizing EAddress window starts.
gpilotd crashes, before answering, I fire up debugger and produce the following
output.  Always repeatable.
Comment 3 kern 2004-12-21 15:46:00 UTC
I'm running FC3 with released updates applied. No other important software.
Comment 4 kern 2004-12-29 10:45:54 UTC
I am using evolution-2.0.2-3 on Fedora FC3. It automatically upgraded my
Evolution 1.4 data, which synced fine with my Palm. Since the upgrade, I have
been unable to sync.

I am using gnome-pilot-2.0.12-4

I am willing and able to provide more detailed bugging info to get a solution to
this problem.
Comment 5 Subodh Soni 2005-06-28 10:31:22 UTC
Thanks for taking the time to report this bug. This bug report isn't very useful
because it doesn't describe the bug well. If you have time and can still
reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add
a more useful description to this bug.
Comment 6 kern 2005-06-28 11:51:50 UTC
Gee, it is now 6 months. At the time, I would have done anything to get the 
Palm sync to work, and as I noted, the program was very frustrating because it 
gave almost no feedback and didn't even report obvious problems like 
permissions errors -- it simply goes dead silently. 
 
Anyway, I gave up long ago, switched to kpilot, which works like a charm 
*every* single time, and gives plenty of feedback. 
 
From my stand point, you can close this bug.  Good luck. 
Comment 7 Elijah Newren 2005-07-01 03:33:02 UTC
Subodh: Um, that stock response really isn't applicable/useful here.  The
reporter  provided as much information as they were able and pointed out that
they were willing to get more if provided directions on how to get it--and even
expressed frustration at the lack of status/debugging information provided from
the program.  If extra information is needed, the bugsquad or maintainers should
point out what information is needed.
Comment 8 kern 2005-07-01 21:29:08 UTC
The comment #7 from Elijah Newren is one of the best analysis(es?) that I have 
read in a long time :-)   
 
Comment 9 Matt Davey 2006-08-08 18:28:56 UTC
Marking as fixed.  I believe this was an issue on the Evolution side, in which incomplete charset support could cause crashes when certain non-ascii chars were encountered.