Bug 103053 - gnome-pilot-0.11.8 not comunicates with USB Palm m130
Summary: gnome-pilot-0.11.8 not comunicates with USB Palm m130
Status: RESOLVED DUPLICATE of bug 165455
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Beta 1
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-09 15:03 UTC by Ladislav Michnovic
Modified: 2006-05-08 19:18 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ladislav Michnovic 2005-08-09 15:03:01 UTC 
Gnome-pilot seems to do nothing with Palm m130.
In Craddle setup I choose USB connection and port /dev/ttyUSB0 (which I know
from /var/log/messages when plugin the Palm. Pilot-xfer communicates with the
same Palm on port /dev/ttyUSB0 succesfully.) After that I choose: Yes, I have
already using sync. Then I'm requested to press the Hotsync button, but nothing
happend.

We are testing a new version of pilot-link-0.12-pre4, but the patched
gnome-pilot (with patch for new API of pilot-link
http://mail.gnome.org/archives/gnome-pilot-list/2005-March/msg00012.html )
crashes after every push of Hotsync button on a Palm at the point described above.
Comment 1 Richard Thornton 2005-11-23 16:53:34 UTC 
I am using a m125 with final release Suse 10, and find it works fine, but one has to let it find your configuration on the palm first, then when it is ready to hotsync, push the sync button;  There is a vbit of a timing issue and one needs to possibly try it more than once.
Comment 2 JP Rosevear 2006-05-08 16:57:29 UTC 
I think this is probably a duplicate.

*** This bug has been marked as a duplicate of 164455 ***
Comment 3 JP Rosevear 2006-05-08 19:18:20 UTC 
Marked duplicate of wrong bug.
Comment 4 JP Rosevear 2006-05-08 19:18:42 UTC 

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