Evolution does not show ubuntuone contacts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution-couchdb (Ubuntu) |
Incomplete
|
Undecided
|
Joshua Hoover | ||
ubuntuone-client (Ubuntu) |
Invalid
|
Medium
|
Ubuntu One Foundations+ team |
Bug Description
Binary package hint: ubuntuone-client
Hi,
I have two computers setup with Lucid Lynx (upgraded from Karmic) to sync with UbuntuOne.
Unfortunately after I boot my Laptop, Evolution does not show any contacts in the UbunutOne address book.
Only after I started the UbuntuOne Settings Applet the contacts start to show up.
I also tried the following sequence of commands described in a similar but at least from the logs not duplicate bug, 580884:
> killall beam.smp ; killall beam ; evolution --force-shutdown
< beam: no process found
> rm ~/.config/
> dbus-send --session --dest=
< Error org.freedesktop
> /usr/lib/
< evolution-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
e-data-
in server_log_handler
evolution-
After starting evolution I got:
impl_GNOME_
+ couchdb://127.0.0.1
=> 0xf5a180
impl_GNOME_
Segmentation fault
> u1sdtool -s
< State: QUEUE_MANAGER
connection: With User With Network
description: processing queues
is_connected: True
is_error: False
is_online: True
queues: IDLE
Any ideas what would help? Or which other log files you would need for diagnosis?
Thanks a lot, Fabian
Changed in ubuntuone-client (Ubuntu): | |
assignee: | nobody → Ubuntu One Foundations+ team (ubuntuone-foundations+) |
tags: | added: foundations+ |
Changed in ubuntuone-client (Ubuntu): | |
importance: | Undecided → Medium |
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test a current, supported, Ubuntu version. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.