Bug 87839 - Evolution and gpilot computer lock up
Summary: Evolution and gpilot computer lock up
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 9
Hardware: athlon
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-03 00:06 UTC by Clayton Rogers
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-30 15:40:44 UTC

Attachments (Terms of Use)

Description Clayton Rogers 2003-04-03 00:06:38 UTC
Description of problem:
When synching evolution and my palm using the gpilot connector I get an entire
system lock up.  

Version-Release number of selected component (if applicable):
rpm -qa | grep -i pilot && rpm -q evolution

How reproducible:
It will synch the first time.  I see that the gpilotd process is running and
evolution is running.  As soon as I press the hotsync button, lock up.

Steps to Reproduce:
1.  Open evolution and mount palm in cradle.
2.  Go to Tools -> Pilot Settings to get the gpilotd process started.
3.  Press hot sync button then wait.
4.  Hot sync works and then I press it again, complete lock up. ("un-ping-able")
Actual results:

Lock up.

Expected results:

To hot sync properly.

Additional info:

Comment 1 Jeremy Katz 2003-04-03 00:10:28 UTC
What type of pilot?  When it locks up, do the keyboard LEDs blink?

Comment 2 Clayton Rogers 2003-04-03 00:16:39 UTC
It is a Palm m130.

No computer activity at all.  No lights on keyboard.

Comment 3 Tom Wood 2003-06-20 23:36:01 UTC
Same issue with a Handspring Visor Pro, except that, since the very first
syncing ever, the lockup occurs every time now.  Hard lock as well, no keyboard
light toggling, unpingable.

I also have jpilot-0.99.2-11 installed, if it matters.  Otherwise, list is same
as Clayton's.

Comment 4 Tom Wood 2003-06-20 23:38:10 UTC
Running gpilotd manually works for me.

Comment 5 Bugzilla owner 2004-09-30 15:40:44 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

Note You need to log in before you can comment on or make changes to this bug.