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 625330 - Can't copy "note" field for contacts in Google in Evolution 2.30
Can't copy "note" field for contacts in Google in Evolution 2.30
Status: RESOLVED DUPLICATE of bug 602244
Product: evolution
Classification: Applications
Component: Contacts
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
evolution[google]
Depends on:
Blocks:
 
 
Reported: 2010-07-26 15:55 UTC by putin_ai
Modified: 2011-04-05 09:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description putin_ai 2010-07-26 15:55:09 UTC 
Hi!

I can't edit "Note" field for contacts in Google Address book;
When i creating local contacts and copying it in Google Address Book, the "notes" field are also doesn't copy.

I heard about this bug https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/489378 and thought it was fixed in v.2.30, but it didn't.


Any suggestions?
Comment 1 André Klapper 2010-07-27 11:10:51 UTC 
So which exact version of Evolution are you running and which distribution?
(Note: This is bug 602244.)
Comment 2 putin_ai 2010-07-27 12:34:41 UTC 
ubuntu 10.04 desktop edition. evolution 2.28 and evolution 2.30 affected.
Comment 3 Tobias Wolf 2010-11-24 22:33:32 UTC 
I’m not sure what is going on and precisely where to look, but this commit seems to tell me that libgdata has support for Notes and Birthdays:

http://git.gnome.org/browse/libgdata/commit/?id=aa23ec1cdcaaa5511a5ba713bebdbe0f101bf180

But in Evolution a lot of the fields that are described in that commit are grayed out in a contact’s sheet.

I’m mostly after birthdays because Gmail for some odd unconceivable reason doesn’t remind you of birthdays.

libgdata7 is 0.6.4-2

So do I suppose right that 0.6.4 came out shortly before this commit and 0.7 would fix this bug?
Comment 4 Milan Crha 2011-04-05 09:22:16 UTC 
Thanks for a bug report. This is bug #630358 and bug #602244. I'm marking this as a duplicate of the older.

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