View previous topic :: View next topic |
Author |
Message |
stardotstar l33t
Joined: 10 Feb 2006 Posts: 887 Location: 2074/SYD/NSW/AU
|
Posted: Sat Aug 04, 2007 8:38 am Post subject: K3B was working; now cant get perms to write to device ... |
|
|
Having been using K3B for a while to do my MP3 discs I find suddenly (no doubt after some recent emergence) I cannot burn to my CD/DVD RW
It is reporting a permisisons thing that I don't seem to see solved elsewhere.
The debug info from K3B is straightforward:
Code: |
System
-----------------------
K3b Version: 1.0.3
KDE Version: 3.5.7
QT Version: 3.3.8
Kernel: 2.6.20-mactel
Devices
-----------------------
MATSHITA DVD-R UJ-846 FQ3T (/dev/hda, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R Sequential, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, Restricted Overwrite]
Used versions
-----------------------
cdrecord: 2.1.1a30
cdrecord
-----------------------
/usr/bin/cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits./usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns.
/usr/bin/cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
/usr/bin/cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
/usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/hda'
devname: '/dev/hda'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
SCSI buffer size: 64512
Cdrecord-ProDVD-ProBD-Clone 2.01.01a30 (i686-pc-linux-gnu) Copyright (C) 1995-2007 Jörg Schilling
TOC Type: 0 = CD-DA
Using libscg version 'schily-0.9'.
Driveropts: 'burnfree'
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 2
Capabilities :
Vendor_info : 'MATSHITA'
Identifikation : 'DVD-R UJ-846 '
Revision : 'FQ3T'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: CD-R
Profile: DVD+R/DL
Profile: DVD+R
Profile: DVD+RW
Profile: DVD-RW restricted overwrite
Profile: DVD-RW sequential recording
Profile: DVD-R sequential recording
Profile: DVD-ROM
Profile: CD-RW
Profile: CD-R (current)
Profile: CD-ROM
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO
Drive buf size : 1310720 = 1280 KB
FIFO size : 4194304 = 4096 KB
pregap1: -1
Track 01: audio 3 MB (00:22.57) no preemp swab copy
Track 02: audio 34 MB (03:22.22) no preemp swab copy
Track 03: audio 50 MB (04:59.60) no preemp swab copy
Track 04: audio 51 MB (05:04.64) no preemp swab copy
Track 05: audio 48 MB (04:45.49) no preemp swab copy
Track 06: audio 64 MB (06:22.72) no preemp swab copy
Track 07: audio 50 MB (04:57.25) no preemp swab copy
Track 08: audio 33 MB (03:18.90) no preemp swab copy
Track 09: audio 61 MB (06:04.96) no preemp swab copy
Track 10: audio 54 MB (05:21.70) no preemp swab copy
Track 11: audio 53 MB (05:15.30) no preemp swab copy
Track 12: audio 26 MB (02:36.81) no preemp swab copy
Track 13: audio 47 MB (04:42.21) no preemp swab copy
Track 14: audio 138 MB (13:42.13) no preemp swab copy
Total size: 716 MB (70:56.54) = 319241 sectors
Lout start: 716 MB (70:58/41) = 319241 sectors
/usr/bin/cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl.
/usr/bin/cdrecord: Operation not permitted. Cannot open or use SCSI driver.
/usr/bin/cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
/usr/bin/cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
cdrecord command:
-----------------------
/usr/bin/cdrecord -v gracetime=2 dev=/dev/hda speed=24 -dao driveropts=burnfree -eject -useinfo -audio /tmp/kde-stardotstar/k3b_audio_0_01.inf /tmp/kde-stardotstar/k3b_audio_0_02.inf /tmp/kde-stardotstar/k3b_audio_0_03.inf /tmp/kde-stardotstar/k3b_audio_0_04.inf /tmp/kde-stardotstar/k3b_audio_0_05.inf /tmp/kde-stardotstar/k3b_audio_0_06.inf /tmp/kde-stardotstar/k3b_audio_0_07.inf /tmp/kde-stardotstar/k3b_audio_0_08.inf /tmp/kde-stardotstar/k3b_audio_0_09.inf /tmp/kde-stardotstar/k3b_audio_0_10.inf /tmp/kde-stardotstar/k3b_audio_0_11.inf /tmp/kde-stardotstar/k3b_audio_0_12.inf /tmp/kde-stardotstar/k3b_audio_0_13.inf /tmp/kde-stardotstar/k3b_audio_0_14.inf
|
and I have tried several suggestions from other posts - chmod g+s /usr/bin/cdrecord; change group to cdrom for cdrecord, ensure that stardotstar is in group cdrom; tested that I can scanbus with root and stardotstar etc...
Not really sure why this kicked in. Can anyone see the issue - I am really not across all the ATAPI/SCSI emulation and fear and loathing etc of burning
Code: |
spitfire / # uname -a
Linux spitfire 2.6.20-mactel #11 SMP PREEMPT Wed Jul 25 12:10:15 EST 2007 i686 Genuine Intel(R) CPU T2600 @ 2.16GHz GenuineIntel GNU/Linux
spitfire / # cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 2.01.01a30 (i686-pc-linux-gnu) Copyright (C) 1995-2007 J��rg Schilling
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.9'.
scsibus1000:
1000,0,0 100000) 'MATSHITA' 'DVD-R UJ-846 ' 'FQ3T' Removable CD-ROM
1000,1,0 100001) *
1000,2,0 100002) *
1000,3,0 100003) *
1000,4,0 100004) *
1000,5,0 100005) *
1000,6,0 100006) *
1000,7,0 100007) *
spitfire / # ls -l /usr/bin/cdrecord
-rwxr-xr-x 1 root cdrom 376916 Jul 24 23:39 /usr/bin/cdrecord
spitfire / #
|
lots of this in dmesg:
Code: |
ATAPI device hda:
Error: Illegal request -- (Sense key=0x05)
Logical block address out of range -- (asc=0x21, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 "
end_request: I/O error, dev hda, sector 0
hda: command error: status=0x51 { DriveReady SeekComplete Error }
hda: command error: error=0x50 { LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hda:
Error: Illegal request -- (Sense key=0x05)
Logical block address out of range -- (asc=0x21, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 00 00 01 00 00 01 00 00 00 00 00 00 00 "
end_request: I/O error, dev hda, sector 4
hda: command error: status=0x51 { DriveReady SeekComplete Error }
hda: command error: error=0x50 { LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hda:
Error: Illegal request -- (Sense key=0x05)
Logical block address out of range -- (asc=0x21, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 "
end_request: I/O error, dev hda, sector 0
hda: command error: status=0x51 { DriveReady SeekComplete Error }
hda: command error: error=0x50 { LastFailedSense=0x05 }
ide: failed opcode was: unknown
ATAPI device hda:
Error: Illegal request -- (Sense key=0x05)
Logical block address out of range -- (asc=0x21, ascq=0x00)
The failed "Read 10" packet command was:
"28 00 00 00 00 01 00 00 01 00 00 00 00 00 00 00 "
end_request: I/O error, dev hda, sector 4
|
the drive opens fine for all normal read operations in gnome etal...
Just checked and Gnome cd burn in nautilus does not work either - much less specific with its error "an error occurred while writing"
Any help appreciated guys
Will _________________ ]8P |
|
Back to top |
|
|
gerard27 Advocate
Joined: 04 Jan 2004 Posts: 2377 Location: Netherlands
|
Posted: Sat Aug 04, 2007 9:06 am Post subject: |
|
|
Hi stardotstar,
Try going to k3b>tools>k3bsetup.
You'll have to supply root password.
Once set up you shouldn't have any problem.
Gerard. _________________ To install Gentoo I use sysrescuecd.Based on Gentoo,has firefox to browse Gentoo docs and mc to browse (and edit) files.
The same disk can be used for 32 and 64 bit installs.
You can follow the Handbook verbatim.
http://www.sysresccd.org/Download |
|
Back to top |
|
|
stardotstar l33t
Joined: 10 Feb 2006 Posts: 887 Location: 2074/SYD/NSW/AU
|
Posted: Mon Aug 06, 2007 9:55 am Post subject: |
|
|
It isn't so unfortunately;
I have no k3b setup in tools menu:
copy...
erase...
format...
rip various etc
and no setup in configure k3b either, no prompt for root password at any stage.
is this because I am running it on gnome?
thanks
will _________________ ]8P |
|
Back to top |
|
|
roderick l33t
Joined: 11 Jul 2005 Posts: 908 Location: St. John's, NL CANADA
|
Posted: Mon Aug 06, 2007 1:10 pm Post subject: |
|
|
Open a command prompt and run
It should prompt for the password (root password) and then provide you a setup to update permissions. _________________ If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/ |
|
Back to top |
|
|
darkphader Veteran
Joined: 09 May 2002 Posts: 1217 Location: Motown
|
Posted: Mon Aug 06, 2007 1:18 pm Post subject: |
|
|
The setup is in the the "Settings" menu:
- Settings > Setup System Permissions...
Chris _________________ WYSIWYG - What You See Is What You Grep |
|
Back to top |
|
|
gerard27 Advocate
Joined: 04 Jan 2004 Posts: 2377 Location: Netherlands
|
Posted: Mon Aug 06, 2007 1:54 pm Post subject: |
|
|
You are right chris.My mistake.
Gerard _________________ To install Gentoo I use sysrescuecd.Based on Gentoo,has firefox to browse Gentoo docs and mc to browse (and edit) files.
The same disk can be used for 32 and 64 bit installs.
You can follow the Handbook verbatim.
http://www.sysresccd.org/Download |
|
Back to top |
|
|
darkphader Veteran
Joined: 09 May 2002 Posts: 1217 Location: Motown
|
Posted: Mon Aug 06, 2007 2:03 pm Post subject: |
|
|
I think they moved it sometime back. So it's possible we're both right...it just depends on which version you have installed.
Chris _________________ WYSIWYG - What You See Is What You Grep |
|
Back to top |
|
|
stardotstar l33t
Joined: 10 Feb 2006 Posts: 887 Location: 2074/SYD/NSW/AU
|
Posted: Tue Aug 07, 2007 12:43 pm Post subject: |
|
|
hmmm, thanks for the replies guys but I am starting to feel rather more stupid than I normally do.
no k4bsetup in my bin paths,,, and (being a gnome user?_) I am not seeing the setup menus you speak of ...
Code: |
Password:
spitfire / # cd /usr/bin
spitfire bin # ls k3*
k3b
spitfire bin # whereis k3bsetup
k3bsetup:
spitfire bin #
|
thanks for the replies people
BTW it must be a simple permissions thing because I can burn from VMWARE using NERO! to think I had to resort to that _________________ ]8P |
|
Back to top |
|
|
roderick l33t
Joined: 11 Jul 2005 Posts: 908 Location: St. John's, NL CANADA
|
Posted: Tue Aug 07, 2007 1:56 pm Post subject: |
|
|
roderick wrote: | Open a command prompt and run
It should prompt for the password (root password) and then provide you a setup to update permissions. |
If whereis doesn't work, it may be the db isn't updated. You can also try locate and which to try and find it. You can also use the following to see what files are actually installed by k3b:
You should see k3bsetup somewhere in that output.
If it doesn't exist, then you have a busted install of k3b. Re-install it.
Verify you have the proper use flags for your setup before doing this. You may also want to run a revdep-rebuild an emerge -avuND world to ensure your system is completely sane.
Both equery and revdep-rebuild are part of the package gentoolkit. Install it if you do not have it. _________________ If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/ |
|
Back to top |
|
|
stardotstar l33t
Joined: 10 Feb 2006 Posts: 887 Location: 2074/SYD/NSW/AU
|
Posted: Tue Aug 07, 2007 10:51 pm Post subject: |
|
|
I regularly revdep-rebuild and deep update world. Unless the use flags have changed since I was last burning with k3b that should be fine...
I can't see the setup programme you refer to (as directed)
Code: |
spitfire / # equery files k3b | grep setup
spitfire / # equery files k3b | grep *setup*
spitfire / # equery files k3b | grep k3bsetup
spitfire / #
|
Code: |
spitfire / # equery which k3b
/usr/portage/app-cdr/k3b/k3b-1.0.3.ebuild
spitfire / #
|
perhaps I should remove and rebuild k3b
in the mean time I will set revdep-rebuild after a sync/emerge deep world and check again. _________________ ]8P |
|
Back to top |
|
|
b0b0 n00b
Joined: 18 Nov 2004 Posts: 43
|
Posted: Tue Aug 07, 2007 11:51 pm Post subject: |
|
|
You have to build k3b with the kde useflag in order to get k3bsetup. |
|
Back to top |
|
|
roderick l33t
Joined: 11 Jul 2005 Posts: 908 Location: St. John's, NL CANADA
|
Posted: Wed Aug 08, 2007 12:46 am Post subject: |
|
|
b0b0 found it... I bet if you look at your USE flags, you must have removed kde from /etc/make.conf or /etc/portage/package.use recently (OR at least sometime since needing k3bsetup).
So, rule of thumb... when in doubt, check the ebuild. There's actualy a elog warning that gets printed if you do not have the kde use flag enabled.
Code: |
>>> Emerging (1 of 1) app-cdr/k3b-1.0.3 to /
* k3b-1.0.3.tar.bz2 RMD160 ;-) ... [ ok ]
* k3b-1.0.3.tar.bz2 SHA1 ;-) ... [ ok ]
* k3b-1.0.3.tar.bz2 SHA256 ;-) ... [ ok ]
* k3b-1.0.3.tar.bz2 size ;-) ... [ ok ]
* checking ebuild checksums ;-) ... [ ok ]
* checking auxfile checksums ;-) ... [ ok ]
* checking miscfile checksums ;-) ... [ ok ]
* checking k3b-1.0.3.tar.bz2 ;-) ... [ ok ]
* You haven't set the kde use flag. k3bsetup won't be installed.
|
Granted... I think this warning should be a bit more visible and not so obscurely hidden. I never would have picked up on this as I always use KDE and have kde enabled in my /etc/make.conf.
So, thanks b0b0 _________________ If God were a pickle, I'd still say "no pickle on my burger".
http://roderick-greening.blogspot.com/ |
|
Back to top |
|
|
b0b0 n00b
Joined: 18 Nov 2004 Posts: 43
|
Posted: Wed Aug 08, 2007 2:02 am Post subject: |
|
|
You're welcome, but surely there is a better way to grant access to the cdrw device besides giving k3b root access? I would much rather give my user account specific permission (maybe through group permissions?) to the dvd-rw device rather than let k3b use root in order to cdrecord. What do you all think would be the safest way to do this?
Edit:
This is weird. I just added myself to the "cdrw" group, thinking this might fix the problem, but it has not. |
|
Back to top |
|
|
b0b0 n00b
Joined: 18 Nov 2004 Posts: 43
|
Posted: Thu Aug 09, 2007 1:05 am Post subject: |
|
|
Setting suid root for /usr/bin/cdrecord solves the problem, but surely there has to be a better way to do this. |
|
Back to top |
|
|
stardotstar l33t
Joined: 10 Feb 2006 Posts: 887 Location: 2074/SYD/NSW/AU
|
Posted: Thu Aug 09, 2007 2:51 am Post subject: |
|
|
I have set suid root for cdrecord at the moment and then look at the implications of changing my use flag for either the package or generally.
The issue being that it seems more to do with cdrecord because I found that Gnome CD Burner wouldn't work either but now it does.
strangely enough the VMWare guest can use nero. _________________ ]8P |
|
Back to top |
|
|
Tolstoi l33t
Joined: 20 May 2004 Posts: 678
|
Posted: Fri Aug 10, 2007 6:23 pm Post subject: |
|
|
As root I added
because that's the group k3b requests in its setup and the I added myself (user) to the burning group.
I had to restart because k3b suddenly didn't recognize the empty cdr in the drive and then the drive itself.
After that everything went fine.
I also had to reemerge k3b with the kde use flag as mentioned above to get that setup thing working. |
|
Back to top |
|
|
b0b0 n00b
Joined: 18 Nov 2004 Posts: 43
|
Posted: Sat Aug 11, 2007 3:12 am Post subject: |
|
|
But surely there has to be a better way than setting cdrecord to suid root. I am in the cdrom and cdrw groups; doesn't this give me permission to write CDs? |
|
Back to top |
|
|
Corona688 Veteran
Joined: 10 Jan 2004 Posts: 1204
|
Posted: Sat Aug 11, 2007 5:12 am Post subject: |
|
|
b0b0 wrote: | But surely there has to be a better way than setting cdrecord to suid root. I am in the cdrom and cdrw groups; doesn't this give me permission to write CDs? | Last I heard it required root permissions to burn CD's since the same general group of drive ioctl's used to burn CD's can also be used to update drive firmware; meaning, if someone wanted to be malicious, anyone with burning privileges could brick your drive. So they required root as a security measure. _________________ Petition for Better 64-bit ATI Drivers - Sign Here
http://www.petitiononline.com/atipet/petition.html |
|
Back to top |
|
|
airman Tux's lil' helper
Joined: 06 Aug 2004 Posts: 82 Location: Utah, USA
|
Posted: Mon Jan 21, 2008 11:27 pm Post subject: |
|
|
Thanks guys. This thread solved my problem with K3b not having the proper permissions to burn a CD. |
|
Back to top |
|
|
babudro n00b
Joined: 30 Sep 2005 Posts: 35 Location: Canada
|
Posted: Wed Jan 23, 2008 7:31 pm Post subject: Burning group |
|
|
The "burning" group did the trick for me. I didn't have to restart either, as Tolstoi did, just did "groupadd burning" then "usermod -a -G burning." It's such a relief to fix this problem that had me baffled. I tried all the usual things that people above recommended, but hadn't hit on this "burning" group idea until now. So thanks very much, Tolstoi! |
|
Back to top |
|
|
speeddemon Apprentice
Joined: 27 Sep 2003 Posts: 162
|
Posted: Sun Mar 16, 2008 9:16 pm Post subject: |
|
|
Ok, I have the same problem now, but there is now no kde use flag for k3b (doesn't matter whether I use it or not, it doesn't pop up in the list).
Code: | blueshee pparson # USE=kde emerge -va k3b
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] app-cdr/k3b-1.0.4 USE="alsa dvdr dvdread encode mp3 vorbis -arts -css -debug -emovix -ffmpeg -flac -hal -musepack -musicbrainz -sndfile -vcd -xinerama" LINGUAS="-af -ar -bg -br -bs -ca -cs -cy -da -de -el -en_GB -es -et -eu -fa -fi -fr -ga -gl -he -hi -hu -is -it -ja -ka -lt -mk -ms -nb -nds -nl -nn -pa -pl -pt -pt_BR -ru -rw -se -sk -sr -sr@Latn -sv -ta -tr -uk -uz -zh_CN -zh_TW" 0 kB |
And I have no k3bsetup.
WTF happened to K3b? |
|
Back to top |
|
|
nemesiss41 n00b
Joined: 24 Nov 2007 Posts: 10
|
Posted: Mon Mar 17, 2008 8:36 pm Post subject: |
|
|
Try adding yourself to the "burning" group.
Code: |
# groupadd burning
# usermod -a -G burning [your_user]
|
You have to log out and log in again after this for the group settings to take effect.
This solved it for me. |
|
Back to top |
|
|
speeddemon Apprentice
Joined: 27 Sep 2003 Posts: 162
|
Posted: Sun Apr 06, 2008 10:24 pm Post subject: |
|
|
nemesiss41 wrote: | Try adding yourself to the "burning" group.
Code: |
# groupadd burning
# usermod -a -G burning [your_user]
|
You have to log out and log in again after this for the group settings to take effect.
This solved it for me. |
Haven't gotten around to this till now, but I have no burning group on this PC, doesn't exist. Tried reinstalling K3b, tried reinstalling cdrtools. Still getting the cdrtools permission problem. I have no k3bsetup program, I have no permissions anything in any menu.
What the hell?
EDIT: apparently known problem with cdrtools, Code: | chmod u+s /usr/bin/cdrecord | fixed the problem. |
|
Back to top |
|
|
penetrode Apprentice
Joined: 29 Dec 2003 Posts: 285 Location: Calgary, Alberta
|
Posted: Thu Apr 17, 2008 3:55 am Post subject: Extremely bad idea |
|
|
Quote: | EDIT: apparently known problem with cdrtools,
Code: | chmod u+s /usr/bin/cdrecord |
fixed the problem. |
Uh, dude -- that is incredibly bad advice you're handing out there. Setting cdrecord setuid root is a workaround, not a solution.
If there's no burning group on your system, you're supposed to add it. |
|
Back to top |
|
|
mimosinnet l33t
Joined: 10 Aug 2006 Posts: 713 Location: Barcelona, Spain
|
Posted: Mon May 05, 2008 5:20 pm Post subject: |
|
|
Thanks very much! This thread has been very helpful.
There was a permissions issue and I have follow the different steps in this thread.
What I have not tried:
* Like stardotstar, I do not have k3bsetup but I have the kde flag set, so I was unable to run k3bsetup.
* Like penetrode, I do not think it is a good idea to set cdrecord setuid root.
What I did:
Add myself to the cdrom and cdrw. Create the burning group and add myself to that group. These are the groups to which my user (perru) belongs:
# cat /etc/group | grep perru
wheel::10:root,perru
audio::18:perru,pulse
cdrom::19:haldaemon,perru
video:!:27:root,perru
cdrw::80:haldaemon,perru
users::100:games,perru
perru:x:1000:
plugdev:!:1004:haldaemon,perru
burning:x:1012:perru
Finally, this did not work till I exit and enter back to kde
My question: How is that the group 'burning' is not created by default?
Thanks to all!!! |
|
Back to top |
|
|
|