[Bug 465015] Re: Evolution fails to add google contacts with message Error adding Contact other error
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 having this problem was using Comcast's DNS servers, whereas the others were using various other DNS servers. Not expecting much, we changed the DNS servers on that PC to Google's public DNS servers (http://code.google.com/speed/public-dns), and, voilà, problem solved. We can reproduce the problem by changing the DNS servers back to Comcast's, so there appears to be something wrong with Comcast's DNS servers. Specifically, it appears that some HTTP requests to google's service are not being correctly directed. Or perhaps it's something worse: it's entirely possible that Comcast's DNS servers may have been hijacked by a third party which is intercepting requests to google...? I don't know, but for safety's sake, we've decided to avoid Comcast's DNS servers here. If you are experiencing this problem, try changing your DNS servers. That solved the problem for us. -- Evolution fails to add google contacts with message Error adding Contact other error https://bugs.launchpad.net/bugs/465015 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 465015] Re: Evolution fails to add google contacts with message Error adding Contact other error
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_contact (process:5274): libebookbackendgoogle-DEBUG: Creating: BEGIN:VCARD VERSION:3.0 .EMAIL;TYPE=WORK;X-EVOLUTION-UI-SLOT=1:john...@somewhere.com X-MOZILLA-HTML:FALSE X-EVOLUTION-VIDEO-URL: FBURL: CALURI: X-EVOLUTION-BLOG-URL: X-EVOLUTION-FILE-AS:doe\, tom N:doe;john;;; FN:john doe NOTE: X-EVOLUTION-SPOUSE: NICKNAME: X-EVOLUTION-ASSISTANT: X-EVOLUTION-MANAGER: ROLE: TITLE: URL: END:VCARD (process:5274): libebookbackendgoogle-DEBUG: google_book_add_contact (process:5274): libebookbackendgoogle-DEBUG: unsupported vcard field: X-MOZILLA-HTML: FALSE (process:5274): libebookbackendgoogle-DEBUG: New primary email entry john...@somewhere.com (http://schemas.google.com/g/2005#work/(null)) (process:5274): libebookbackendgoogle-DEBUG: new entry with xml: ?xml version=1.0? entry xmlns:gd=http://schemas.google.com/g/2005; xmlns=http://www.w3.org/2005/Atom;category scheme=http://schemas.google.com/g/2005#kind; term=http://schemas.google.com/contact/2008#contact/title type=texttom doe/titlegd:email address=john...@somewhere.com rel=http://schemas.google.com/g/2005#work; primary=true//entry (process:5274): libebookbackendgoogle-DEBUG: Creating contact failed: Adding entry failed due to 'Bad Request' (HTTP code 400) [END SNIP] On other computers, which allow adding new contacts, evolution-data- server's log looks exactly the same except for that last line. I hope this helps solve the problem. -- Evolution fails to add google contacts with message Error adding Contact other error https://bugs.launchpad.net/bugs/465015 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 465015] Re: Evolution fails to add google contacts with message Error adding Contact other error
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-EVOLUTION-UI-SLOT=1:john...@somewhere.com X-MOZILLA-HTML:FALSE X-EVOLUTION-VIDEO-URL: FBURL: CALURI: X-EVOLUTION-BLOG-URL: X-EVOLUTION-FILE-AS:doe\, john N:doe;john;;; FN:john doe NOTE: X-EVOLUTION-SPOUSE: NICKNAME: X-EVOLUTION-ASSISTANT: X-EVOLUTION-MANAGER: ROLE: TITLE: URL: END:VCARD (process:5274): libebookbackendgoogle-DEBUG: google_book_add_contact (process:5274): libebookbackendgoogle-DEBUG: unsupported vcard field: X-MOZILLA-HTML: FALSE (process:5274): libebookbackendgoogle-DEBUG: New primary email entry john...@somewhere.com (http://schemas.google.com/g/2005#work/(null)) (process:5274): libebookbackendgoogle-DEBUG: new entry with xml: ?xml version=1.0? entry xmlns:gd=http://schemas.google.com/g/2005; xmlns=http://www.w3.org/2005/Atom;category scheme=http://schemas.google.com/g/2005#kind; term=http://schemas.google.com/contact/2008#contact/title type=textjohn doe/titlegd:email address=john...@somewhere.com rel=http://schemas.google.com/g/2005#work; primary=true//entry (process:5274): libebookbackendgoogle-DEBUG: Creating contact failed: Adding entry failed due to 'Bad Request' (HTTP code 400) [END SNIP] -- Evolution fails to add google contacts with message Error adding Contact other error https://bugs.launchpad.net/bugs/465015 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 229144] Re: [hardy] screensaver fails to start and screen fails to completely black out
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 received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
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 mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
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
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
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 5.10 -- they worked fine every single time. The issue of this bug report appears more like a hang that occurs after pilot-link or gnome-pilot establishes the connection with the device. If you look at the thread, this bug report covers both the occasional hang as well as more frequent time-outs. -- 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
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
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
[Bug 38574] Re: Pb syncing treo 650 on dapper drake - temporary solution
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 Treo to the PC, and click the Treo's sync button 4. When the Treo's screen displays the Connecting with the desktop... message, press enter at the command line to run gpilotd So far, it has worked every time I've tried. Hopefully this information will help solve the 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
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
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 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
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
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-dimension-3000, ...}) = 0
brk(0) = 0x804e000
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f75000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
old_mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f73000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=69132, ...}) = 0
old_mmap(NULL, 69132, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f62000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libpisock.so.8, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0J\0\000..., 512) =
512
fstat64(3, {st_mode=S_IFREG|0644, st_size=139648, ...}) = 0
old_mmap(NULL, 142712, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7f3f000
old_mmap(0xb7f5e000, 16384, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e000) = 0xb7f5e000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/libncurses.so.5, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 \343\0..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=262860, ...}) = 0
old_mmap(NULL, 264108, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7efe000
old_mmap(0xb7f36000, 32768, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x38000) = 0xb7f36000
old_mmap(0xb7f3e000, 1964, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f3e000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/libreadline.so.5, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220\272..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=466058, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7efd000
old_mmap(NULL, 187108, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7ecf000
old_mmap(0xb7ef8000, 16384, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x29000) = 0xb7ef8000
old_mmap(0xb7efc000, 2788, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7efc000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/tls/i686/cmov/libc.so.6, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220O\1..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1232784, ...}) = 0
old_mmap(NULL, 1238972, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7da
old_mmap(0xb7ec5000, 28672, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x125000) = 0xb7ec5000
old_mmap(0xb7ecc000, 10172, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7ecc000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/tls/i686/cmov/libdl.so.2, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\v\0..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=8204, ...}) = 0
old_mmap(NULL, 11016, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7d9d000
old_mmap(0xb7d9f000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1000) = 0xb7d9f000
close(3)= 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7d9c000
set_thread_area({entry_number:-1 - 6, base_addr:0xb7d9c6c0, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0,
useable:1}) = 0
munmap(0xb7f62000, 69132) = 0
time(NULL) = 1147975581
write(2, \n, 1
) = 1
brk(0) = 0x804e000
brk(0x806f000) = 0x806f000
open(/dev/null, O_RDWR) = 3
open(/dev/ttyUSB1, O_RDWR|O_NONBLOCK) = 4
ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS unfinished ...
+++ killed by SIGSEGV +++
*** EOF ***
And here's the output from `strace pilot-xfer -p /dev/pilot -l`:
*** BOF ***
execve(/usr/bin/pilot-xfer, [pilot-xfer, -p, /dev/pilot, -l], [/* 28
vars */]) = 0
uname({sys=Linux, node=heinsen-dimension-3000, ...}) = 0
brk(0) = 0x804e000
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7fd3000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
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 know if more than two ttyUSB* were being created prior to upgrading to the latest packages. In any case, syncing still takes a couple of tries, though I'm no longer getting the invalid pointer error when it doesn't work; instead, the daemon just keeps trying to communicate with the Treo. Here's a snip from the log: *** gpilotd log *** gpilotd-Message: setting PILOTRATE=115200 (gnome-pilot:17104): gpilotd-WARNING **: pi_accept_to: Connection timed out (gnome-pilot:17104): gpilotd-WARNING **: pi_accept_to: timeout was 3 secs gpilotd-Message: setting PILOTRATE=115200 (gnome-pilot:17104): gpilotd-WARNING **: pi_accept_to: Connection timed out (gnome-pilot:17104): gpilotd-WARNING **: pi_accept_to: timeout was 3 secs ... [these messages keep getting repeated until I interrupt the daemon.] *** At least now I'm been able to stop the daemon with a normal kill i.e. without having to send it a SIGKILL. As before, syncing suddenly works fine after a couple of tries. -- 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
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
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. I just keep killing -9 `pidof gpilotd` and re-running it, until eventually, syncing suddenly works again. Hope this is helpful. -- 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
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
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 gpilotd-Message: bonobo_activation_active_server_register = 0 gpilotd-Message: Watching Cradle (/dev/pilot) gpilotd-Message: Found 4766, 0001 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0502, 0736 gpilotd-Message: Using net TRUE gpilotd-Message: Found 091e, 0004 gpilotd-Message: Using net TRUE gpilotd-Message: Found 082d, 0100 gpilotd-Message: Using net FALSE gpilotd-Message: Found 082d, 0200 gpilotd-Message: Using net TRUE gpilotd-Message: Found 082d, 0300 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0c88, 0021 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0001 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0002 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0003 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0020 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0031 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0040 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0050 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0060 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0061 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0070 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0830, 0080 gpilotd-Message: Using net TRUE gpilotd-Message: Found 04e8, 8001 gpilotd-Message: Using net TRUE gpilotd-Message: Found 04e8, 6601 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0038 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0066 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0095 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 009a gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00c9 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00da gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00e9 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0144 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0169 gpilotd-Message: Using net TRUE gpilotd-Message: Found 12ef, 0100 gpilotd-Message: Using net TRUE gpilotd-Message: Client seems ok gpilotd-Message: setting PILOTRATE=115200 (gnome-pilot:13394): gpilotd-WARNING **: Unable to bind to pilot gpilotd-Message: setting PILOTRATE=115200 (gnome-pilot:13394): gpilotd-WARNING **: pi_accept_to: Input/output error (gnome-pilot:13394): gpilotd-WARNING **: pi_accept_to: timeout was 0 secs gpilotd-Message: setting PILOTRATE=115200 gpilotd-Message: Cradle Cradle has 0 events gpilotd-Message: corba: orbed_notify_user, notifications-connect.size = 1, id = Treo-650 gpilotd-Message: Client appears to be disconnected... (gnome-pilot:13394): gpilotd-WARNING **: orbit_daemon_glue.c:1494 Exception: IDL:omg.org/CORBA/COMM_FAILURE:1.0 gpilotd-Message: removing monitor on Treo-650 for IOR:01 *** glibc detected *** free(): invalid pointer: 0x080d7ea0 *** *** EOF *** -- 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
[Bug 38574] Re: Pb syncing treo 650 on dapper drake
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
