Red Hat Bugzilla – Bug 175383
[RHEL4] A specific v2.1 Vcard fails to import, entirely silently
Last modified: 2008-02-03 11:59:47 EST
Description of problem:
The attached v2.1 vcard fails to import, with no message telling you that it
didn't work. I suspect a format problem, as I was able to import other v2.1
vcards, but it really ought to _tell_ you that it didn't work (and possibly
why), rather than be quiet about it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open Evolution
2. File -> Import
3. Import the attached file
Error message explaining that it can't be imported (and why)
Created attachment 122084 [details]
v2.1 vcard which won't import into Evo contacts
Tested with rawhide and it worked:
Tried on a RHEL4 test box with
evolution-data-server-1.0.2-9.fix169497.1 (mostly the same as 1.0.2-9)
Worked first time (popped up a contact editor dialog, with a Cancel button but
an insensitive Ok button), having cancelled I'm seeing similar symptoms on
May well be affected by file type detection; did you select Automatic or VCard
in step 3?
I don't recall. I'd only have specfied which kind of file type if it couldn't
figure it out on my own, I think.
Evolution 2.0.2 is only being updated for security issues. Closing as WONTFIX.