Well, I figured out why no data was moving from Evolution to my PDA - I apparently needed the 'evolution-pilot' package. Unfortunately, now I'm back to nothing working again. I give up for now. It's taking too much of my time to figure out this stuff, and it's not mission critical, so I'll just use jpilot until the next version of Redhat comes out or something. This is truly an annoyance, though, I must say. Especially since Redhat has made this their default mail client in 8.0. You'd think they would've tested this - but I guess it *is* a '.0' release, so... On Thu, 2002-11-21 at 20:59, Carter, Shaun G wrote: > restarting gpilotd would have done the trick too, it's just easier to log > out/in. Glad it's workin for ya. > > Shaun > > -----Original Message----- > From: Brian K. Jones [mailto:jonesy@cs.princeton.edu] > Sent: Thursday, November 21, 2002 8:18 PM > To: psyche-list@redhat.com > Subject: Re: jpilot works, gnome-pilot (hence evolution) doesn't > > > Holy crap! > > Well, I have to admit I didn't do *everything* you said, because I had done > exactly what you mentioned before - but I *did* double check every file and > permission and stuff. The only thing I did was restart GNOME and it > freakin' > worked! ACK! What's up with that? > > Actually, I only quickly tested gnome-pilot - and on my home box too (still > RH > 8, but I didn't do the rawhide updates yet, and evo is still at 1.0.8, not > 1.2 like at work). I'll test evolution next, but no reason it shouldn't > work > if gnome-pilot is working. I'll return if I see issues moving forward. > > Thanks a million. I'd still like to know what the magic service was that > wasn't picking up a change somewhere or something. I thought gnome-pilot > was > just a front end to pilot-link tools, which, as aforementioned, were > working. > > I REFUSE to fall into that Windows-ish 'if all else fails, restart X or > reboot' mentality. I WILL keep up with all of these changes and understand > what's happening. > > Thanks again. > /brian > > > On Thursday 21 November 2002 5:50 pm, Carter, Shaun G wrote: > > 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 -- Brian K. Jones <jonesy@cs.princeton.edu> Princeton University, Dept. of Computer Science -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
