Bug 1276723

Summary: errors and lockups
Product: [Fedora] Fedora Reporter: Richard Jasmin <spike85051>
Component: xfburnAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: christoph.wickert, fkluknav, hhorak
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:22:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Richard Jasmin 2015-10-30 16:03:55 UTC 
Description of problem:
"Failed to unmount 'Blank BD-R Disc'. Drive cannot be used for burning."
Keeps popping up while burning a bdrom to near-capacity.

Also: getting weird lockups between burns, seemingly having to do with mounting of blank media.

Along with the: what to do with this? messages popping up en mass.

Dont know if an update broke this, but appears to be indicative of just that.

Version-Release number of selected component (if applicable):
22

How reproducible:
nearly always, didnt used to do this.

Steps to Reproduce:
1.xfburn something(burning backup set)


Actual results:
see above

Expected results:
this should not be
Comment 1 Fedora End Of Life 2016-07-19 18:22:39 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.