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 348021 - No error msg when overwritting a vcard on a file with no write access
No error msg when overwritting a vcard on a file with no write access
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Contacts
2.8.x
Other Linux
: Normal major
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-07-19 14:46 UTC by Sebastien Bacher
Modified: 2013-09-13 00:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Sebastien Bacher 2006-07-19 14:46:55 UTC 
That bug has been opened onhttps://launchpad.net/distros/ubuntu/+source/evolution/+bug/53425

"Hi,

When saving/overwrite a vcard, Evolution doesn't tell that me that I have no write access on the file and do as if it was OK...

Step to reproduce :

1. open evolution with address book mode
2. right clic on an card and choose "save as"
3. save it on the desktop for exemple
4. right clic -> properties on this file on the desktop
5. remove my write access
6. in evolution try to save another card over the already saved file
7. It seem to be OK, but look inside the file, the content is the first saved card...

Regards
Mathieu ALORENT"
Comment 1 André Klapper 2006-07-19 18:21:34 UTC 
evo 2.7.4cvs on a gnome2.12/suse10.1:
if i save the original vcard to the desktop, it gets 755 here, after that, i changed it to 555 and 440.
i get a warning message here (file exists - overwrite?). if i choose overwrite, i get an error that it cannot be overwritten.
Comment 2 ushveen kaur 2006-09-12 09:27:47 UTC 
I agree with andre's comment,i am not allowed to overwrite the file.
Comment 3 Sebastien Bacher 2006-09-13 09:35:18 UTC 
Works fine now, marking as fixed. Might have been a GTK or gnome-vfs issue which has been fixed since