After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 604939 - Unable to use "Notes" field in Evolution with a Google address book
Unable to use "Notes" field in Evolution with a Google address book
Status: RESOLVED DUPLICATE of bug 602244
Product: evolution
Classification: Applications
Component: Contacts
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
evolution[google]
Depends on:
Blocks:
 
 
Reported: 2009-12-18 18:07 UTC by Pedro Villavicencio
Modified: 2009-12-21 04:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Pedro Villavicencio 2009-12-18 18:07:54 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/489378

"The "Notes" fields from Google address books are not synced with Evolution address books. All notes fields appear blank when synced to Evolution, and they are not editable in Evolution.

1) Create a gmail account.
2) Open gmail contacts.
3) Import or add some contacts, and fill in some text data to some "Notes" fields.
4) Open Evolution
5) Click "New" -> Address Book
6) Select Google for "Type"
7) Imput your gmail account username
8) When prompted, enter your password
9) Allow your contacts to sync
10) Click on "Contacts" in Evolution
11) Select the address book for your gmail account
12) Select a contact for which you added note data in Gmail
13) notice that you cannot view the note data
14) Select any contact
15) notice that you cannot type in the notes field of that contact in evolution."

Thanks,
Comment 1 Akhil Laddha 2009-12-21 04:53:04 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 602244 ***