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 736372 - Incorrect error reported: File not saved; Error setting security.selinux
Incorrect error reported: File not saved; Error setting security.selinux
Status: RESOLVED OBSOLETE
Product: evince
Classification: Core
Component: PDF
3.10.x
Other Linux
: Normal minor
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-09-10 02:42 UTC by The Nate
Modified: 2018-05-22 15:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description The Nate 2014-09-10 02:42:08 UTC 
Context: I was filling out some pretty bog standard PDF form for an application.*
System: KDE 4.13 running as WM. (It's simply that I prefer QT.)

Error: When saving the filled form, I got the following error: 

"The file could not be saved as <filename>.
Error setting extended attribute 'security.selinux': Operation not supported"

(*I don't know the legality of sending the application form to you, but this happened on every form they sent.)

The thing of it is, however, that the file saved properly. I have found no signs of error. 

I believe that there is probably a legitimate error going on, but the one listed is not it. This could be a duplicate of Bug 692552, but I'm not sure.

Anytime I've tried this, this happens, so I don't know what else is required to cause this.
Comment 1 Germán Poo-Caamaño 2017-10-02 14:49:05 UTC 
Can you still reproduce the issue?

Bug 692552 was fixed in 2016, so if it is the same bug, you should not see the behaviour reported anymore.
Comment 2 GNOME Infrastructure Team 2018-05-22 15:52:06 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/evince/issues/510.