Hide Forgot
Description of problem: An install may include the nautilus package, providing the GNOME Files application. However, the default installation does not include the brasero-nautilus package necessary for burning CD's or DVD's from Files. In this state, the Files application will show blank CD/DVD devices and allow drag-and-drop of files into their directory. However, it will not burn the contents to the devices. It does provide an eject button but no indication that the burn did not occur. As a result, the default user experience may imply to users that they have burned content to a CD or DVD, when they have not. No errors or warnings are provided in this state. A user may lose data, thinking they have burned it to a CD or DVD when they have not. Ideally, the nautilus user interface should be modified to clarify that burning is not an option and prevent dragging and dropping of files into a blank CD or DVD directory when the necessary dependencies are missing. An appropriate bug could be reported upstream. A work-around would be to make the brasero-nautilus dependency (and its dependent packages) mandatory for the nautilus package. This will ensure the dependencies for burning are in place and prevent the misleading user experience. Version-Release number of selected component (if applicable): nautilus-3.22.3-5.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Setup an installation with nautilus-3.22.3-5.el7.x86_64 installed and brasero-nautilus not installed. 2. Connect a CD/DVD burner and load blank media. 3. Open Files and observe the new blank media directory is available. 4. Drag-and-drop content into the new directory in Files. 5. Eject the media from Files. 6. Re-insert the blank media. Note that the content is listed, incorrectly implying it exists on the media. 7. Insert the media into another system and observe that the content is not on the media. Additional info: Since a default installation exhibits a user experience that can lead to loss of user data, this issue should be given a high priority.
Making Breasero hard dependency sounds good for RHEL. Ideally Nautilus would check if that's available anyway, but since no other distro is shipping Brasero by default or expecting that to work I guess it's fine ignoring upstream on this one.
It may be useful to reference this bug report in the RPM packing notes when taking the dependency approach. Ensuring the dependent package is available should prevent the user experience that may lead to loss of user data with current versions of the up-stream code. However, a side-effect will be that users working on systems that do not have a CD/DVD drive could be confused by the need to install CD/DVD burning software. As nautilus is a more of a core GNOME component, they may see the extra dependency as inefficient.
Will be resolved in Bug 1628523 outside of nautilus it self, but not in 7.6. Sorry
Hi Carlos, could you please provide me with information about this known issue and fill it in the Doc Text field? If this bug does not have to be documented, please write it in a comment. If you need a reference for filling up the Doc Text field, use this: -- Cause What actions or circumstances cause the bug to present (if known). Note that if the cause is not known or is not fully diagnosed, current hypotheses or theories should be noted. Consequence What happens when the bug presents. Workaround What actions, if any, reduce the bug’s effects or prevent it from presenting entirely. Result If the bug’s effect is only reduced, what consequences still follow; if the bug is prevented, what restrictions does the workaround impose. -- If you have any other questions, please contact me. Thank you! Adam Kvítek
Hey Adam, Cause brasero-nautilus package missing in the installation Consequence Brasero integration in Nautilus doesn't work, i.e. when clicking "burn to disk" it will do nothing. Workaround Install brasero-nautilus Result The issue is fixed Hope this is clear enough, cheers
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2044