Bug 447255
Summary: | gedit cannot save an edited file | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joachim Backes <joachim.backes> | ||||
Component: | gedit | Assignee: | Ray Strode [halfline] <rstrode> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 9 | CC: | balajig81, bugzilla, gsking1, mail, rpm | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-07-14 18:19:41 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Joachim Backes
2008-05-19 06:17:27 UTC
Created attachment 305904 [details]
strace of gedit
Changing Status to ASSIGNED Now using F10, and the problem still exists (gedit-2.24.2-1.fc10.i386). Weird: after copying the correspondent file to another one, I couldn't reproduce the described behaviour of gedit with the file copy. I can confirm the relationship between failure of Gedit to save backup copies on exit and the status of SELinux. Gedit Version: gedit-2.24.3-3.fc10 When SELinux is disabled, the problem occurs on all newly created and existing files opened for editing using Gedit, changed and then saved. When SELinux is enabled in "enforcing" mode the problem disappears. I think this may be a duplicate of bug #244605 - certainly, they sound very similar. That said, 244605 is CLOSED UPSTREAM but there doesn't seem to be much happening upstream to actually fix it. This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. On Fedora 12 I just encountered this. All it took me to trigger it was disabling SELinux and using gedit to edit text files. I have no such problem when SELinux is enabled. The message is this: "Could not create a temporary backup file while saving /home/gsking/Desktop/notes.txt" I am given the options of Save anyway or Don't save. Forgot to mention that I also had to reboot after making the SELinux changes. I think my problem has been solved thanks to this comment on an Ubuntu forum. https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/474579/comments/2 I would still consider this an open bug since this fix was not easily apparent. |