"You do not have the required permissions to use this drive."

[pveurs]

Binary package hint: brasero

Writing ISO images using Brasero 2.28.2 all fail. After it's done burning it does not automatically check integrity, and when one tries to do so manually the following error appears:

The file integrity check could not be performed.
You do not have the required permissions to use this drive.

It should allow me to do this, though.

ProblemType: Bug
Architecture: amd64
Date: Fri Jan 22 19:33:00 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: brasero 2.28.2-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: brasero
Uname: Linux 2.6.31-17-generic x86_64

[pveurs (pveurshout)]

There appears to be more to it than just Brasero. Shortly after ejecting the disk, the icon comes back and dmesg floods with the following message:

[12728.420820] VFS: busy inodes on changed media or resized disk sr0
[12728.424706] VFS: busy inodes on changed media or resized disk sr0
[12728.428619] VFS: busy inodes on changed media or resized disk sr0
[12730.417739] VFS: busy inodes on changed media or resized disk sr0
[12730.420310] VFS: busy inodes on changed media or resized disk sr0
[12730.423987] VFS: busy inodes on changed media or resized disk sr0
[12732.419591] VFS: busy inodes on changed media or resized disk sr0
[12732.422445] VFS: busy inodes on changed media or resized disk sr0
[12732.427825] VFS: busy inodes on changed media or resized disk sr0
[12734.420404] VFS: busy inodes on changed media or resized disk sr0
[12734.424422] VFS: busy inodes on changed media or resized disk sr0
[12734.431626] VFS: busy inodes on changed media or resized disk sr0
[12736.419552] VFS: busy inodes on changed media or resized disk sr0
[12736.422786] VFS: busy inodes on changed media or resized disk sr0
[12736.426553] VFS: busy inodes on changed media or resized disk sr0
[12738.420037] VFS: busy inodes on changed media or resized disk sr0
[12738.423484] VFS: busy inodes on changed media or resized disk sr0
[12738.427539] VFS: busy inodes on changed media or resized disk sr0
[12740.420095] VFS: busy inodes on changed media or resized disk sr0
[12740.423564] VFS: busy inodes on changed media or resized disk sr0
[12740.427443] VFS: busy inodes on changed media or resized disk sr0
[12742.420377] VFS: busy inodes on changed media or resized disk sr0
[12742.424672] VFS: busy inodes on changed media or resized disk sr0
[12742.428657] VFS: busy inodes on changed media or resized disk sr0
[12744.420661] VFS: busy inodes on changed media or resized disk sr0
[12744.424569] VFS: busy inodes on changed media or resized disk sr0
[12744.428670] VFS: busy inodes on changed media or resized disk sr0
[12746.419820] VFS: busy inodes on changed media or resized disk sr0
[12746.423080] VFS: busy inodes on changed media or resized disk sr0
[12746.428019] VFS: busy inodes on changed media or resized disk sr0
[12748.421445] VFS: busy inodes on changed media or resized disk sr0
[12748.425201] VFS: busy inodes on changed media or resized disk sr0
[12748.429217] VFS: busy inodes on changed media or resized disk sr0
[12750.420353] VFS: busy inodes on changed media or resized disk sr0
[12750.423884] VFS: busy inodes on changed media or resized disk sr0
[12750.427881] VFS: busy inodes on changed media or resized disk sr0
[12752.420099] VFS: busy inodes on changed media or resized disk sr0
[12752.423006] VFS: busy inodes on changed media or resized disk sr0
[12752.426960] VFS: busy inodes on changed media or resized disk sr0
[12754.420976] VFS: busy inodes on changed media or resized disk sr0
[12754.424656] VFS: busy inodes on changed media or resized disk sr0
[12754.428777] VFS: busy inodes on changed media or resized disk sr0
[12756.420004] VFS: busy inodes on changed media or resized disk sr0
[12756.423159] VFS: busy inodes on changed media or resized disk sr0
[12756.426979] ...

[Pedro Villavicencio (pedro)]

Thanks for your report, could you get a brasero log? please run brasero as: brasero --brasero-burn-debug --brasero-media-debug &> brasero-debug.txt ; perform the operation to reproduce the bug and attach that resulting log file to the report, thanks. btw that doesn't look like a brasero problem.

[mahjong (wiktor-idzikowski)]

Added attachment.
Bug is the same as first post.
Brasero 2.28.2, Ubuntu 9.10 64-bit

[Rūdolfs Mazurs (rudolfs-mazurs)]

At least for me, unmounting the drive helped.

[Sam_ (and-sam)]

Burned an image within Nautilus.
Then opened Brasero -> check disk integrity
Result: same "no permission" message (german)
Right click on the image properties -> permissions are all root.
/media/cdrom0 = 40555
$groups
user adm dialout cdrom plugdev lpadmin admin sambashare

Confirm unmounting helps.
#Was not needed in Hardy.

[Sam_ (and-sam)]

Update: Couldn't reproduce it, no "no permission" message anymore.

[Marty Vona (vona)]

Just updated to 10.04 and I can confirm this bug. And that unmounting the drive (which apparently is now only doable from command line) works around the problem.

[Leslie Viljoen (leslieviljoen)]

Same here, worked after I unmounted. Thanks guys! You can use "administration -> disk utility" (palimpsest) to unmount it but I can't remember if that's in the default install.

Anyway, it would be nice if Brasero were fixed to handle this more elegantly.

[Leslie Viljoen (leslieviljoen)]

Upstream bug report here: https://bugzilla.gnome.org/show_bug.cgi?id=607773

[Sam_ (and-sam)]

After over one year it's still unconfirmed in bugzilla? Still exists in an updated Maverick (Desktop support till 4-2012).

[Victor Zamanian (victorz)]

I'm getting this in Ubuntu 11.10 with a fully upgraded system. Unmounting the volume in the "Disk Utility" program seems to do some sort of trick.

[ndstate (ndstate)]

This is confirmed in 12.04. Unmouting via Disk Utility is a work around.

[LoWang (vitas-lowang)]

those workarounds are not necessary IMHO. The media seems to be written properly even if this stupid error occurs. There may be just a little trouble opening the drive.
This bug is still present even in Ubuntu 12.10. How can we call this system "Linux for human beings" if it behaves like this?...