Bug 557501 - cdrom drive access error using integrity check in brasero
Summary: cdrom drive access error using integrity check in brasero
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: brasero
Version: 13
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-21 16:24 UTC by TK009
Modified: 2011-06-24 13:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-24 13:08:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 607773 0 None None None Never

Description TK009 2010-01-21 16:24:42 UTC
Description of problem: 
When running an integrity check on a disc in brasero get error message saying "You do not have permission to use this drive."


Version-Release number of selected component (if applicable):
polkit-0.95-0.git20090913.3.fc12.x86_64


How reproducible: 
100%


Steps to Reproduce:
1. start brasera, Tools>Integrity Check
2. select disk and file
3. start integrity check
  
Actual results:
Pop up window
The file integrity check could not be performed.
You do not have the required permissions to use this drive.


Expected results:
Complete integrity check

Additional info:

Comment 1 David Zeuthen 2010-01-21 17:50:38 UTC
Uhm, why do you think this is a polkit bug? Reassigning to brasero.

Comment 2 TK009 2010-01-21 18:41:57 UTC
The failure was mine for not adding additional information.

I "think" it "could be" a polkit bug because the problem seems to be with permissions. I am going on nothing else but that. I don't want to question just get to the bottom of this bug.

This bug may or may not help.
https://bugzilla.redhat.com/show_bug.cgi?id=505582

The problem in that report has been corrected and is fixed/closed upstream. I am not at all sure polkit is the problem, nor am I sure it is a brasero problem. The correction seems to have occurred from F11 to F12. What was 'fixed' and where is not at all clear.

I am sure about being willing to help troubleshoot and track down the cause of this bug.

What can I do to better track down the root problem?

 

TK009
---

Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 TK009 2010-01-22 15:11:40 UTC
Filed upstream

https://bugzilla.gnome.org/show_bug.cgi?id=607773


TK009
---

Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 TK009 2010-08-08 10:12:51 UTC
Changed version.

Comment 5 Bug Zapper 2011-06-02 16:47:37 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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

Comment 6 TK009 2011-06-24 13:08:55 UTC
The owner doesn't seem to care, and neither do I any longer.


Note You need to log in before you can comment on or make changes to this bug.