Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
when I am recording gnome session and I move that file I get no error. Correct behavior is to lock file or error announced with recording stopped afterwards.
Version-Release number of selected component (if applicable):
gnome-shell-3.4.1-5
How reproducible:
100%
Steps to Reproduce:
1.start recording
2.remove file you are recording into
Actual results:
no error, recording silently continues
Expected results:
error or some file lock preventing file removal
Additional info:
Try this
1) in one terminal
ls -R / > /tmp/output
2) in a second terminal
rm /tmp/output
Note that the ls process is not interrupted, if you look at /proc/<pid>/fd, you'll see for the "file descriptor" writing to that file:
l-wx------. 1 otaylor otaylor 64 Jun 11 11:09 1 -> /tmp/output (deleted)
The expected UNIX behavior is:
file is moved (within the same partition) - recording continues to the new location
file is deleted - recording continues, file is actually deleted from disk after recording finishes
To do something differently would require GNOME Shell to check periodically to see if the output file name is still there in it's original location.