Gnome pilot hangs with Evolution's couchdb address book
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gnome-Pilot |
New
|
Undecided
|
Unassigned | ||
evolution-couchdb |
Fix Released
|
Undecided
|
Ubuntu One Client Engineering team | ||
gnome-pilot-conduits |
New
|
Undecided
|
Unassigned | ||
evolution-couchdb (Ubuntu) |
Fix Released
|
Undecided
|
Ubuntu One Client Engineering team |
Bug Description
Binary package hint: evolution-couchdb
I recently got a Palm TX handheld which I want ubuntu and specifically evolution to sync with, unfortunately I was in trouble when Syncing as gnome-pilot would lose connection with the palm TX when syncing with the Eaddress component, not only that but it would also keep trying to sync indefinitely unless I explicitly killed gpilotd.
When I tried something else, well, I found that this behavior did not occur when I switched the couchdb address book with my personal address book, meaning that the responsible was evolution-couchdb.
I do not know how easy is this to fix, yet I think is important for this address book is the main one I use, because it is able to sync with ubuntu one.
I hope I made myself clear in the subject, thanks in advance
Changed in evolution-couchdb (Ubuntu): | |
assignee: | nobody → Ubuntu One Desktop+ team (ubuntuone-desktop+) |
status: | New → Confirmed |
Changed in evolution-couchdb: | |
status: | New → Confirmed |
assignee: | nobody → Ubuntu One Desktop+ team (ubuntuone-desktop+) |
tags: | added: desktop+ |
Thank you for taking the time to file this bug report. It does sound like it may be an issue related to the Ubuntu One address book based on the information you provided. I think it might be helpful if you can try the following:
1. Open Applications- >Accessories- >Terminal, and run: evolution/ evolution- data-server- 2.28 > ~/evolution_ debug.log
evolution --force-shutdown
/usr/lib/
2. Open Applications- >Internet- >Evolution Mail debug.log to a bug report
3. Try to reproduce bug and then attach ~/evolution_
This will provide us with a bit more of the specifics on what may be causing this problem.
Thank you,
Joshua