I hope this will be helpful. Modifying the instructions as mentioned earlier
for the hard link, I did the following:
as root:
# mknod /dev/m500 c 188 1
# chmod 766 /dev/m500
I was then able to use hotsync easily, since /dev/pilot was otherwise
created and deleted over my hard link. The new link
Thanks for following up. If somebody can isolate the fix, we can push it
to dapper-updates - the complete changes in pilot-link, gnome-pilot etc
are too huge to just push to dapper.
Please open a Dapper task, once a isolated fix is available.
** Changed in: gnome-pilot (Ubuntu)
Importance:
Well, this bug does have for Dapper Drake in the title - how much more
Dapper-y can you get?
I don't know who the person responsible for this is (whether it's the
maintainer of the pilot packages or the kernel team), but saying Please
open a Dapper task, once a isolated fix is available is
This does now work in Edgy.
However, Dapper is supposed to be supported for five years. People who
want a stable Ubuntu also want to be able to sync their Treos. A fix for
this problem needs to be backported.
--
Pb syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574
--
A new version (2.0.14) was uploaded to Edgy. It'd be nice if you had a
chance to test this and report back, if the problem still persists.
** Changed in: gnome-pilot (Ubuntu)
Status: Confirmed = Needs Info
--
Pb syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574
--
gpilotd now does a full sync reliably. But only if
I start it by manually from the command line.
Same here. See https://launchpad.net/distros/ubuntu/+source/gnome-
pilot/+bug/38574/comments/30
--
Pb syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574
--
ubuntu-bugs mailing
Glad that the kernel update appears to solve this issue, and that
setting a non-zero timeout appears to solve the problem with the ttyUSB
devices hanging around after a sync completes. I'm pretty sure this
latter issue has been solved in gnome-pilot CVS, and the timeout=0 trick
is only required
After some more playing around, I discovered that the timeout value
of 0 in gpilotd-control-applet was causing gpilot to hang at the end
of the sync. I changed that timeout to 4 seconds and now gpilotd
can perform multiple syncs without having to be killed and restarted.
I had changed it to 0
Tonight I tested a full restore of my palm device. First I synced it with
gnome-pilot, which worked correctly from the GUI. Next I cleared
the memory on the device. The restore results
were disappointing. The restore began properly, then the progress
bars started flashing back and forth
Any progress on solving this bug?
--
Pb syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm having this problem too. I was previously running Debian unstable
with all the same hardware and syncing worked fine to my USB visor using
pilot-link. I reinstalled the laptop with dapper drake and I'm getting
the flakiness reported here: once in a blue moon it will work, 95% of
the time it
I am sorry you are still having problems, I compiled 2.6.17.1 and now
have 100% success.
Because dapper uses UDEV I plug my palm in, start jpilot, hit the sync
button on my palm then click the sync button on jpilot. I am no expert
but can you post your pilot-link output ?
Dave
--
Pb syncing
I spent about a week in total on this problem, You have upgraded the
kernel I assume with 'make oldconfig' after my 'make oldconfig' I had to
tweak mine, If you want I will email you my .config, let me know ...
Dave
--
Pb syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574
--
Robert,
There has always been a human-level timing
issue when using pilot-link with a USB device:
you need to press the button on the cradle
first, then start pilot-link before the USB device
disconnects.
Actually, gpilotd and gnome-pilotd did *not* have any human-level timing
issues in
Hi all,
Syncing problems 100% solved :) - Upgraded kernel to 2.6.17.1 and Palm
syncing now works perfectly. So it appears that the default kernel is a
bit flaky on the USB front
Dave
--
Pb syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574
--
ubuntu-bugs mailing list
The following work-around has solved the problem for me -- i.e. the Treo
syncs fine _every time_ when I do the following:
1. Open a terminal and kill the panel applet and the daemon:
$ killall gpilot-applet gpilotd
2. At the command line, type 'gpilotd', but do NOT press Enter
3. Connect the
Hi Gerv,
I have tried just about everything I can think of, I have upgraded my
kernel, compiled the latest version of pilot-link which uses direct
libusb support bypassing the visor module, apt-get install --reinstall
numerous packages (you never know) and I still only get 1 in 20ish
syncs.
I
Thanks for the info, I will go down the build own kernel route at the
weekend.
Cheers
Dave
--
Pb syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
There's not much more to say on this one... it seems very likely that
the problem is with the ubuntu 2.6.15 kernel package and has been fixed
in more recent revisions. I'd advise building your own kernel, or
raising a bug against the kernel package.
--
Pb syncing treo 650 on dapper drake
19 matches
Mail list logo
