ok try this # Create the '/dev/pilot' device again (I know you have, do it again just for kicks): usb: ln -s /dev/usb/ttyUSB1 /dev/pilot # You can find your port by doing a HotSync and then checking 'dmesg' output. # As root, change the permissions on the device /dev/pilot links to: chown 'user' /dev/usb/ttyUSB1 chgrp 'group' /dev/usb/ttyUSB1 chmod ug+rw /dev/usb/ttyUSB1 Log out of gnome/kde/whatever, log back in. Launch Evolution again and hit hotsync again. Let me know if this doesn't work. Following these instructions (so far) I've had 100% success rate personally (I have a M505, M515, Handspring Deluxe and Handspring Pro) and when I try to help out other people. I hope it works for you. Shaun -----Original Message----- From: Brian K. Jones [mailto:jonesy@CS.Princeton.EDU] Sent: Thursday, November 21, 2002 4:30 PM To: psyche-list@redhat.com Subject: RE: jpilot works, gnome-pilot (hence evolution) doesn't Hi. When I hit the sync button while in evolution, nothing happens for about 5 seconds, and then I get a message on the screen of my handspring that says that the connection between my handheld and the desktop cannot be established. Running the command you supplied (thanks) resulted in gnome-pilot running the 'you're running this for the first time' wizard, which also fails with the same errors as above every time, so I never get passed the 'About to grab id info from the handheld' screen. BTW - this all still remains true even though I have upgraded to the rawhide packages as you mentioned as well. I also tried configuring things in gnome-pilot manually (device, conduits, etc), still to no avail. Baffled. On Thu, 2002-11-21 at 12:08, Carter, Shaun G wrote: > what happens when you hit sync while evolution is up. Does it time out or > say "cleaning up"? If it says "cleaning up", all you have to do is > configure your conduits (the menu entry redhat decided to leave out this > time around). You can either update your gpilotd to the new version in > rawhide or run > > gpilotd-control-applet --cap-id=1 > > set up your conduits and run the sync again. If it says time out, you seem > to have everything configured correctly since JPilot works normally, let met > know and we'll dig deeper. > > Shaun Carter > > -----Original Message----- > From: Brian K. Jones [mailto:jonesy@CS.Princeton.EDU] > Sent: Wednesday, November 20, 2002 9:21 AM > To: psyche-list@redhat.com > Subject: jpilot works, gnome-pilot (hence evolution) doesn't > -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
