Bug 432301

Summary: Can not mount CD created with CD/DVD Creator except as root.
Product: [Fedora] Fedora Reporter: Need Real Name <donpa>
Component: halAssignee: David Zeuthen <davidz>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 7CC: axel.thimm, mclasen, triage
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-17 03:01:10 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 Flags
Error message received when trying to read CD none

Description Need Real Name 2008-02-11 03:13:32 UTC
Description of problem:  Can not access a CD that has been created with CD/DVD
Creator if created when NOT in root. Must login as root to access CD.  Error
message when trying to load and read CD is, "Can Not Mount Volume." "Error
org.freedesktop.Hal.PermissionDenied. "  Details = "Permission Denied. Not in
Active Session"  (See attached .png)


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


How reproducible: Create CD with Creator when NOT logged in as root then try to
read it (when NOT root).  Login as root and try to read.


Steps to Reproduce:
1. Log in other than root.  Copy some directory to the CD/DVD Creator Folder. 
Create CD by clicking "Write to Disk". 
2.  After write finishes and ejects CD insert and wait for spin up.
3.  You should get same error.  You must then logout and log back in as root to
access the CD.
  
Actual results:  Get error message when trying to mount.  See attached screenshot.


Expected results:


Additional info:

Comment 1 Need Real Name 2008-02-11 03:13:32 UTC
Created attachment 294531 [details]
Error message received when trying to read CD

Comment 2 Bug Zapper 2008-05-14 15:19:10 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'.

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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2008-06-17 03:01:09 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 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.

Comment 4 Axel Thimm 2009-05-24 07:34:02 UTC

*** This bug has been marked as a duplicate of bug 160945 ***