After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 607773 - cdrom drive access error using integrity check in brasero
cdrom drive access error using integrity check in brasero
Status: RESOLVED OBSOLETE
Product: brasero
Classification: Applications
Component: general
2.28.x
Other Linux
: Normal normal
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on: 627116
Blocks:
 
 
Reported: 2010-01-22 15:09 UTC by TK009
Modified: 2011-10-07 05:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description TK009 2010-01-22 15:09:06 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."

brasero-2.28.3-1.fc12.i686

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
Comment 1 Leslie Viljoen 2010-08-14 15:08:19 UTC 
A work-around is to unmount the drive. This can be done using "Disk Utility" (palimpsest) on Ubuntu. The error message is a bit misleading, perhaps an extra check could be added and a better message given if the disk is mounted. Otherwise, could Brasero ask permission to unmount from the user and then run umount itself?
Comment 2 Philippe Rouquier 2010-08-16 12:45:27 UTC 
This should be fixed in a further version of brasero provided my patches providing drive locking in glib and GVFS get accepted (it takes time).
Comment 3 André Klapper 2011-08-25 09:06:43 UTC 
(In reply to comment #2)
> This should be fixed in a further version of brasero provided my patches
> providing drive locking in glib and GVFS get accepted (it takes time).

TK009, is this still an issue in 3.0 or 2.32?
Comment 4 TK009 2011-08-26 14:03:48 UTC 
Sorry about the delayed response, for whatever reason this is the first email I've seen about this report.

The problem is corrected in 3.0, and now works as expected. I can't speak for 2.32 as I don't run it any more.

thank you for the fix.
Comment 5 Akhil Laddha 2011-10-07 05:45:03 UTC 
Closing the bug as per comment#4