Good news: I was able to identify the root cause of, and therefore
solve, this problem.
As mentioned in an earlier post, we were having this problem with only
one of our PCs running 9.10, but not with the others. After a bit of
poking around, we noticed that the Internet connection on the PC havi
Sorry, here's the correct log (I'd manually changed the name and email
address and needed to correct a typo):
[SNIP]
(process:5274): libebookbackendgoogle-DEBUG:
e_book_backend_google_create_contact
(process:5274): libebookbackendgoogle-DEBUG: Creating: BEGIN:VCARD
VERSION:3.0
.EMAIL;TYPE=WORK;X
We're having the same problem with one of our PCs running 9.10, but not
on others. I shut down and restarted evolution-data-server with
GOOGLE_BACKEND_DEBUG=1 exported, and this showed up in the following
log:
[SNIP]
(process:5274): libebookbackendgoogle-DEBUG:
e_book_backend_google_create_cont
Same problem here with proprietary nvidia drivers and fully updated
8.04. Let me add that the 'blank screen' screensaver was working as it
should until very recently.
--
[hardy] screensaver fails to start and screen fails to completely black out
https://bugs.launchpad.net/bugs/229144
You receive
> 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
--
desktop-bugs mailin
Oops, I meant to write "gpilotd," not "gpilotd and gnome-pilotd" in my
last post -- sorry for the typo.
--
Pb syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
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
Any progress on solving this bug?
--
Pb syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
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
3. Connect the Treo to
Matt, thank you.
Unfortunately, downgrading my kernel is impractical at the moment, as I
need continuous access to a handful of kernel-specific compiled
applications in this particular PC. However, if I get a chance, I'll
look into doing it on another machine (no promises, though).
Franz
--
Pb
Matt,
I ran into the same problems as saniac when trying to run pilot-xfer.
In any case, here's the output from `strace pilot-xfer -p /dev/ttyUSB1
-l`:
*** BOF ***
execve("/usr/bin/pilot-xfer", ["pilot-xfer", "-p", "/dev/ttyUSB1", "-l"], [/*
28 vars */]) = 0
uname({sys="Linux", node="heinsen-di
Matt, I just saw your question (I assume it was addressed to me -- my name is
spelled with a "z", not "k").
As of right now, with the latest Dapper Beta packages, only the usual two
/dev/ttyUSB* are being created when I hit the sync button, and they disappear
normally afterwards. I don't kn
Just a bit of clarification on my last post: syncing with a Treo 650 in the
Dapper beta is working, just not reliably.
That is, sometimes syncing works flawlessly, sometimes it doesn't work at all
(i.e., nothing happens), and sometimes I get the "invalid pointer" error shown
in the log above.
Sync is no longer working reliably for me on Dapper. Here's the log:
*** gpilotd log ***
gpilotd-Message: gnome-pilot 2.0.13 starting...
gpilotd-Message: compiled for pilot-link version 0.11.8
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpi
Poppy, following this how-to solved the problem for me:
http://doc.gwos.org/index.php/Palm_sync_dapper
Note: changing the device port to "/dev/pilot" while keeping its type as "USB"
was key to getting sync to work. (The device port and type can be changed just
by clicking on the pilot panel app
Same problem with Dapper. (Works fine with Breezy.)
--
Pb syncing treo 650 on dapper drake
https://launchpad.net/bugs/38574
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
16 matches
Mail list logo
