Hi - I can't burn CD's in k3b as a user. I can burn successfully as root. It's obviously a permissions problem but I can't see where. If I look at k3b's error log it seems to be complaining about not having permissions for /dev/pg1 but I've set every permission possible on this device file but still I get the same error. Here's some details k3b gives the device as Samsung cd-r/rw sw-216b /dev/sr0 (0,1,0) interface generic scsi write modes sao, tao, raw raw/r96r permissions set are lrwxrwxrwx 1 root root 3 2003-10-29 22:28 /dev/cdrecorder -> sr0 brw-rw-rw- 1 root disk 11, 0 2003-09-23 18:59 /dev/sr0 crw-rw-rw- 1 root disk 21, 0 2003-09-23 18:59 /dev/sg0 crwxrwxrwx 1 root disk 97, 1 2003-09-23 19:01 /dev/pg1 Can anyone tell me what else I have to set? Best wishes - Ken
In a previous message, Kenneth Payne <kmp@atrium.fsnet.co.uk> wrote:
I can't burn CD's in k3b as a user. [snip] Can anyone tell me what else I have to set?
Run k3bsetup - that should set everything correctly. John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Knossos: escape the ever-changing labyrinth before the Minotaur catches you!
John - Hi, thanks for your help. I remember k3bsetup on SuSE 8.1 but there's no such program in SuSE 9.0 as far as I can tell. It doesn't exist in /opt/kde3/bin nor can Yast2 find it in a package search. Strangely, there *are* png graphics for it in /opt/kde3/ share/apps/pics Am I looking in the wrong place? Best wishes - Ken On Thursday 20 November 2003 3:44 pm, John Pettigrew wrote:
In a previous message, Kenneth Payne <kmp@atrium.fsnet.co.uk> wrote:
I can't burn CD's in k3b as a user.
[snip]
Can anyone tell me what else I have to set?
Run k3bsetup - that should set everything correctly.
John
-----Original Message----- From: Kenneth Payne [mailto:kmp@atrium.fsnet.co.uk] Sent: 20 November 2003 16:36 To: suse-linux-e@suse.com Subject: Re: [SLE] Re: Permissions and K3b John - Hi, thanks for your help. I remember k3bsetup on SuSE 8.1 but there's no such program in SuSE 9.0 as far as I can tell. It doesn't exist in /opt/kde3/bin nor can Yast2 find it in a package search. Strangely, there *are* png graphics for it in /opt/kde3/ share/apps/pics Am I looking in the wrong place? Best wishes - Ken On Thursday 20 November 2003 3:44 pm, John Pettigrew wrote:
In a previous message, Kenneth Payne <kmp@atrium.fsnet.co.uk> wrote:
I can't burn CD's in k3b as a user.
[snip]
Can anyone tell me what else I have to set?
Run k3bsetup - that should set everything correctly.
John
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com Hi, Not sure if this helps but I am running Slackware 9.1, and there is a K3b setup entry ,in KDE's control panle-> System Administration->k3bsetup. I had similar problems with Slackware, and I was able to sort it from there. Richard G.
Hi Jason - Been there. Done that. No module for k3bsetup. Best wishes - Ken On Thursday 20 November 2003 4:56 pm, Jason wrote:
On Thursday 20 November 2003 16:34, Richard Gelling wrote:
Am I looking in the wrong place?
Have a look in the KDE control centre in the System Administration section.
I got caught by this one when I compiled K3b from CVS...
Jason
On Thursday 20 November 2003 18:38, Kenneth Payne wrote:
Been there. Done that. No module for k3bsetup.
Maybe SuSE's control centre customisation has got in the way... Try typing 'kcmshell k3bsetup2' in a root terminal shell. Works here, anyway. Regards, Jason
Jason - How do you know these things? I never seem to know any tricks like that. Unfortunately, no luck. kmp@ravenclaw:~> kcmshell k3bsetup2 kcontrol: ERROR: Module k3bsetup2 not found! QMutex::unlock: unlock from different thread than locker was locked by 0, unlock attempt from 16384 kmp@ravenclaw:~> Best wishes - Ken On Thursday 20 November 2003 6:47 pm, Jason wrote:
On Thursday 20 November 2003 18:38, Kenneth Payne wrote:
Been there. Done that. No module for k3bsetup.
Maybe SuSE's control centre customisation has got in the way...
Try typing 'kcmshell k3bsetup2' in a root terminal shell. Works here, anyway.
Regards,
Jason
On Thursday 20 November 2003 19:12, Kenneth Payne wrote:
How do you know these things? I never seem to know any tricks like that.
I'm just a bit sad, that's all... :-) Sorry you're having troubles... I discovered this because I'm now running the latest KDE from CVS -- what will be 3.2... which I update every week or two, including K3b from the kde-extragear module. A few weeks ago I was trying to get K3b working and wondered where the setup program had disappeared to. I discovered where it was after reading the k3b web pages at k3b.sourceforge.net There's a mailing list archive at: http://sourceforge.net/mailarchive/forum.php?forum=k3b-user I'm wondering if SuSE's build of K3b doesn't include k3bsetup2 for some reason... I think the separate setup program was dropped in K3b 0.10 in favour of the control centre module. You could try the RPMs of the latest (0.10.2) version at the Packman site: http://packman.links2linux.de/?action=219 Hope this helps, Jason
Jason wrote:
I'm wondering if SuSE's build of K3b doesn't include k3bsetup2 for some reason... I think the separate setup program was dropped in K3b 0.10 in favour of the control centre module.
I have been following your discussion with interest, having recently moved from 8.2 to 9, and from a perfectly functioning K3b setup to what 9 proposes, and was nor very functional for me. Namely, CDrecorder as /dev/sr0 (scsi emulation) and my dvd reader as /dev/hdd. Just when I thought a SuSE version had come alond that did not require fiddling with grub parameters, I realized that starting k3b produced an error message saying that CDRDAO could not be used with an atapi drive, and so taht setting scsi-emulation for both drives was far better (this is the officioal error message from the k3b development team!). Now I've been with SuSE since 5.3, and CD burning has always been a problem. If scsi emulation simplifies everybody's life, including k3b developers, why isn't this the default? Then, to come back to the discussion at hand, I also looked for that handy configuartion program, k3b-setup when I got 9, but could not find it anymore. Mind you, after enabling scsi-emulation on both drives and changing permissions on /dev/sr0-1, everything was fine. So I tried kcmshell k3bsetup2, which produced no result then /opt/kde/bin/kcmshell k3bsetup2 , which produced the setup programme I was looking for. (By the way, I run k3b-0.10.1, from packman through apt, and have upgraded kde 3.1.4 too. ). Then checking the kde control centre, I found k3bsetup2 under System administration, while the CDbakeoven options can be changed in the main tree, just after Appearance and Themes (not too obvious, one would say). Conclusion: unnecessarily complicated! A new user who is not particularly computer literate would have no chance to get it to work. FX -- ______________________ Courtesy of SuSE Linux http://www.nibz.org
FX - I read your message with interest. I've now installed the latest version of k3b. (10.2cvs) I run it and it gives me the following errors cdrdao does not run with root privileges readcd does not run with root privileges no support for ATAPI with cdrdao and tells me I should use k3bsetup to sort it out. Hurrah, I now find I have a k3bsetup in the KDE control centre. I go into administrator mode. The k3bsetup module is anything but intuitive, but I click on the "defaults" button and click "apply". K3bsetup tells me permissions have successfully been set. I relaunch k3b. Only the message about ATAPI is still present. So I assume that this refers either to my DVD drive or to my Seagate tape drive and will not be a problem. I try burning a CD and *still* I get the error. Once again the message seems to say I have no permissions for /dev/pg1. You've used k3bsetup successfully. What did you do? I notice that on the CD-RW drive the permissions are given as 666 root.disk whereas on my dvd drive they are given as 666 kmp.disk. Is this right? I can't see how you change them in k3bsetup. I thought then that perhaps kmp needed to be in group disk. I added disk to my groups using YAST but it made no difference to k3b. I must say that when I first posted my problem on this list I thought I'd get a reply which simply said - "chmod a+w /dev/???????? and that will fix it." I can't believe I'm still struggling with this despite the best endeavours of all the kind and helpful people on this list. Best wishes - Ken On Friday 21 November 2003 8:32 am, FX Fraipont wrote:
I have been following your discussion with interest, having recently moved from 8.2 to 9, and from a perfectly functioning K3b setup to what 9 proposes, and was nor very functional for me. Namely, CDrecorder as /dev/sr0 (scsi emulation) and my dvd reader as /dev/hdd.
Kenneth Payne wrote:
I relaunch k3b. Only the message about ATAPI is still present. So I assume that this refers either to my DVD drive or to my Seagate tape drive and will not be a problem.
It will. Use hdc=ide-scsi hdd=ide-scsi in /boot/grub/menu.lst, it will save a lot of trouble.
I try burning a CD and *still* I get the error. Once again the message seems to say I have no permissions for /dev/pg1.
You've used k3bsetup successfully. What did you do? I notice that on the CD-RW drive the permissions are given as 666 root.disk whereas on my dvd drive they are given as 666 kmp.disk. Is this right? I can't see how you change them in k3bsetup. I thought then that perhaps kmp needed to be in group disk. I added disk to my groups using YAST but it made no difference to k3b.
My permissions are set like this: brw-rw-rw- 1 root disk 11, 0 2003-09-23 19:59 /dev/sr0 brw-rw-rw- 1 root disk 11, 1 2003-09-23 19:59 /dev/sr1 Have you checked that you as a user were a member of the disk group? What is the result of cdrecord -scanbus run as normal user? These are my permissions for cdrecord: -r-sr-xr-x 1 root root 389463 2003-09-23 19:38 /usr/bin/cdrecord FX -- ______________________ Courtesy of SuSE Linux http://www.nibz.org
FX - Thanks for your help.
Use hdc=ide-scsi hdd=ide-scsi in /boot/grub/menu.lst, it will save a lot of trouble.
A question first : is this likely to break anything? For example, will I still be able to play dvd movies from /dev/hdd? Will it make them jerky because hdparm will be ignored? And if root can burn cds on the current setup, why can't kmp?
Have you checked that you as a user were a member of the disk group?
According to Yast I was. But I'll try again just to be sure. My permissions are set like this : brw-rw-rw- 1 root disk 11, 0 2003-09-23 18:59 /dev/sr0 brw-r----- 1 root disk 11, 1 2003-09-23 18:59 /dev/sr1 Not much difference from yours.
What is the result of cdrecord -scanbus run as normal user?
This is interesting. What do you make of this - cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Run as root, cdrecord -scanbus gives : Linux sg driver version: 3.1.25 Using libscg version 'schily-0.7' cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.75-resmgr-patch '@(#)scsi-linux-sg.c 1.75 02/10/21 Copyright 1997 J. Schilling'). scsibus0: 0,0,0 0) 'Seagate ' 'STT8000A ' '5.44' Removable Tape 0,1,0 1) 'SAMSUNG ' 'CD-R/RW SW-216B ' 'Q001' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * The permissions on cdrecord are : -rws--x--x 1 root root 389463 2003-09-23 18:38 /usr/bin/cdrecord Does this give you any clues? Best wishes and thanks again for your help. - Ken
Kenneth Payne wrote:
FX -
Thanks for your help.
Use hdc=ide-scsi hdd=ide-scsi in /boot/grub/menu.lst, it will save a lot of trouble.
A question first : is this likely to break anything? For example, will I still be able to play dvd movies from /dev/hdd? Will it make them jerky because hdparm will be ignored? And if root can burn cds on the current setup, why can't kmp?
You will have to change the symlinks /dev/dvd and /dev/cdrom and have them point to /dev/sr1.
What is the result of cdrecord -scanbus run as normal user?
This is interesting. What do you make of this -
cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
- Ken
from man cdrecord: (but substitute "disk" for "cdburners") If you don't want to allow users to become root on your system, cdrecord may safely be installed suid root. This allows all users or a group of users with no root privi? leges to use cdrecord. Cdrecord in this case checks, if the real user would have been able to read the specified files. To give all user access to use cdrecord, enter: chown root /usr/local/bin/cdrecord chmod 4711 /usr/local/bin/cdrecord To give a restricted group of users access to cdrecord enter: chown root /usr/local/bin/cdrecord chgrp cdburners /usr/local/bin/cdrecord chmod 4710 /usr/local/bin/cdrecord and add a group cdburners on your system. Hope this helps FX -- ______________________ Courtesy of SuSE Linux http://www.nibz.org
On Friday 21 November 2003 12:45, FX Fraipont wrote:
It will. Use hdc=ide-scsi hdd=ide-scsi in /boot/grub/menu.lst, it will save a lot of trouble.
I agree - Crdao can't copy from ATAPI cdrom/dvd drives -- which is why K3b complains about a drive not using SCSI emulation. I have a DVD on /dev/hdc and CDRW on /dev/hdd -- using ide-scsi emulation these are turned into /dev/sr0 and /dev/sr1. K3bsetup has given these ownership and permissions as below: brw-rw---- 1 root cdrecord 11, 0 2003-03-14 13:07 /dev/sr0 brw-rw---- 1 root cdrecord 11, 1 2003-04-20 18:40 /dev/sr1 To make k3bsetup2 work I found I had to make a change to one of the options, then click on the 'apply' button. This is in administrator mode. K3bsetup also changes the permissions of cdrdao, cdrecord and readcd to 4710, ownership is root.cdrecord -- which allows users in the group cdrecord use these three utilities with root priviledges. And my user is in the group 'cdrecord'. There are symlinks from /dev/dvd and /dev/cdrom to /dev/sr0 and from /dev/cdrecorder to /dev/sr1.
I try burning a CD and *still* I get the error. Once again the message seems to say I have no permissions for /dev/pg1.
You've used k3bsetup successfully. What did you do? I notice that on the CD-RW drive the permissions are given as 666 root.disk whereas on my dvd drive they are given as 666 kmp.disk. Is this right? I can't see how you change them in k3bsetup. I thought then that perhaps kmp needed to be in group disk. I added disk to my groups using YAST but it made no difference to k3b.
I think you need to log out and back in to ensure k3b picks up the change in the groups. Hope this helps a little, Jason
On Friday 21 November 2003 07:45 am, FX Fraipont wrote:
Kenneth Payne wrote:
I relaunch k3b. Only the message about ATAPI is still present. So I assume that this refers either to my DVD drive or to my Seagate tape drive and will not be a problem.
It will. Use hdc=ide-scsi hdd=ide-scsi in /boot/grub/menu.lst, it will save a lot of trouble.
I try burning a CD and *still* I get the error. Once again the message seems to say I have no permissions for /dev/pg1.
You've used k3bsetup successfully. What did you do? I notice that on the CD-RW drive the permissions are given as 666 root.disk whereas on my dvd drive they are given as 666 kmp.disk. Is this right? I can't see how you change them in k3bsetup. I thought then that perhaps kmp needed to be in group disk. I added disk to my groups using YAST but it made no difference to k3b.
My permissions are set like this:
brw-rw-rw- 1 root disk 11, 0 2003-09-23 19:59 /dev/sr0 brw-rw-rw- 1 root disk 11, 1 2003-09-23 19:59 /dev/sr1
Have you checked that you as a user were a member of the disk group?
What is the result of cdrecord -scanbus run as normal user?
These are my permissions for cdrecord:
-r-sr-xr-x 1 root root 389463 2003-09-23 19:38 /usr/bin/cdrecord
FX =============
Do not do this! Making yourself a member of the "disk" group gives anyone else using your system access to your disks! There is no need for the user to be a member of the "disk" group. User gets hacked, hacker kills disks, user loses all info and has to reinstall whole system. Being a member of "disk" group plays no part in how K3B works at all. Jason gave the most information about how your setup should be and what the settings should be. You are only interested in cdrecord, cdrdao & mkisofs for using K3B. As Jason pointed out, those 3 programs should be suid and root.cdrecording permissions. I set mine up when k3bsetup was a separate program, but from looking at the Control Center options, it looks pretty simple to just check all those things and click on Apply. Doing that should change everything for the user to have permission to use them as well. Again, I can't verify this as mine were already set. If not, it's easy enough to change them. cdrdao is only used in k3b for making drive to drive copies. That's not a good idea on IDE cdroms. CDrecord recognizes IDE/ATAPI drives now, but k3b has not fully transitioned everything to it yet. If you must make a drive to drive copy, try XCDroast for it fully uses cdrecord for that. If you did a fresh install, your cdrw was setup to emulate scsi already with an entry in the GRUB menu.lst, so no further changes should be needed for that. A symlink for /dev/cdrecorder > /dev/sr0 should have been created as well, thus making your cdrw usable by k3b and cdrecord. As you pointed out, you can write as root, so that indicates all is right except for the permissions on your programs. Set those as Jason pointed out and you should be good to go. Be sure to check those off in your K3bsetup 2 area in the control center too. Lee -- --- KMail v1.5.4 --- SuSE Linux Pro v8.2 --- Registered Linux User #225206 On any other day, that might seem strange...
Hi all - Right. Let's start again. Taking on board the valuable suggestions of Jason and Bandipat I've removed myself from "disk" and created a new group called "burning" I'm sorry if I've been slow but I'm only now beginning to understand the role and purpose of k3bsetup. Intuitive it aint. Anyway, I've used k3bsetup to create the necessary permissions for the "burning" group. If I run k3bsetup now - without going into administrator mode - k3bsetup gives the following information (and it seems spot on to me) : ================================== Use burning group : burning SAMSUNG CD-R/RW /dev/sr0 660 root.burning no change SAMSUNG DVD-ROM /dev/hdd 660 kmp.burning no change cdrdao /usr/bin/cdrdao 4710 root.burning no change cdrecord /usr/bin/cdrecord 4710 root.burning no change readcd /usr/bin/readcd 4710 root.burning no change ==================================== Note there's nothing for mkisofs - otherwise it seems perfect. I've logged out and back in. I'm definitely in the "burning" group. When I run k3b it gives the usual ATAPI message but otherwise seems happy. When it comes to burning though I still get a no permissions for /dev/pg0 and it stops. /dev/pg0 is set like this: crw-rw-rw- 1 root disk 97, 0 2003-09-23 19:01 /dev/pg0 Should I change its group to "burning"? Otherwise I'm all out of ideas. By the way cdrecord -scanbus as user still produces cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. If cdrecord is running suid, shouldn't it produce the same output as it does for root? Best wishes - Ken
I am having a problem accessing the Web interface for CUPS. I am running 9.0 Professional. Printing is fine, just want to access the web interface to CUPS. When I access http://localhost:631/admin with either Mozilla, Firebird, or Konqueror, I am prompted to enter the username and password for "CUPS". According to the documentation in /usr/share/packages/cups, "root" and the "rootpassword" should work. I have tried root and the root password, admin and the rootpassword, my username and passwod, and I can't log in. Anyone know what I should answer? i saw something about disabling the password authentication, but I would rather not do that. Thanks. Mike -- Michael A. Coan Woodlawn Foundation 524 North Avenue, Suite 203 New Rochelle, NY 10801-3410 tel 914-632-3778 fax 914-632-5502
Hello, On Nov 21 11:27 Mike Coan wrote (shortened):
9.0 Professional ... want to access the web interface to CUPS.
http://portal.suse.com/sdb/en/2003/09/jsmeix_print-einrichten-90.html Regards Johannes Meixner ----------------------------------------------------------- SUSE LINUX AG, Deutschherrnstr. 15-19 Mail: jsmeix@suse.de 90429 Nuernberg, Germany WWW: http://www.suse.de/ -----------------------------------------------------------
On Nov 21 11:27 Mike Coan wrote (shortened):
9.0 Professional ... want to access the web interface to CUPS.
http://portal.suse.com/sdb/en/2003/09/jsmeix_print-einrichten-90.html
Regards Johannes Meixner ----------------------------------------------------------- SUSE LINUX AG, Deutschherrnstr. 15-19 Mail: jsmeix@suse.de 90429 Nuernberg, Germany WWW: http://www.suse.de/ -----------------------------------------------------------
Thank you very much for the immediate and accurate response to my CUPS problem. All is fine I did search the support database using the words cups and password, but got zero hits. don't know why I didn't get the above link. -- Michael A. Coan Woodlawn Foundation 524 North Avenue, Suite 203 New Rochelle, NY 10801-3410 tel 914-632-3778 fax 914-632-5502
Hello, On Nov 21 11:45 Mike Coan wrote (shortened):
I did search the support database using the words cups and password, but got zero hits.
Unfortunately the new portal has a different search interface than the old support database but there was (and there is) no user information. Therefore most of you who are used to use the old support database serach interface may wonder where all the articles seem to have gone. I think it is a good idea to use the "Feedback" link on the search form of the new portal. In the old support database there was a keyword search and when you search for "foo" and "bar" you would enter foo bar In the new portal you must use an explicit "and" to search for "foo" and "bar" - i.e. you must enter foo and bar As far as I know the perfect syntax is "<#AND>" i.e.: foo <#AND> bar but at least for me the plain "and" works well. The same with "or" and "<#OR>". But it is not all bad with the new portal. The new portal has a very quick full text search engine. Therefore you would have found the article by using the full text search and enter cups and password Because "password" is not a keyword of the particular article you would not have found it by using the keyword search: cups and password Regards Johannes Meixner ----------------------------------------------------------- SUSE LINUX AG, Deutschherrnstr. 15-19 Mail: jsmeix@suse.de 90429 Nuernberg, Germany WWW: http://www.suse.de/ -----------------------------------------------------------
On Friday 21 November 2003 12:17, Johannes Meixner wrote:
stuff omitted
Unfortunately the new portal has a different search interface than the old support database but there was (and there is) no user information.
stuff omitted
Tahnsk for the info. I have added portal.suse.com to my bookmarks Mike -- Michael A. Coan Woodlawn Foundation 524 North Avenue, Suite 203 New Rochelle, NY 10801-3410 tel 914-632-3778 fax 914-632-5502
Mike just to let you know, you have unwittingly breached article 2 of the criminal code of SuSE Linux lists - you hijacked a thread, and in due course you will be accused and indicted and forced to recant. Not that I give a monkeys. Article 1, if anyone doesn't know, is about ... On Friday 21 November 2003 4:27 pm, Mike Coan wrote:
I am having a problem accessing the Web interface for CUPS.
... top posting
On Friday 21 November 2003 4:01 pm, Kenneth Payne wrote:
When I run k3b it gives the usual ATAPI message but otherwise seems happy. When it comes to burning though I still get a no permissions for /dev/pg0 and it stops. /dev/pg0 is set like this:
crw-rw-rw- 1 root disk 97, 0 2003-09-23 19:01 /dev/pg0
Should I change its group to "burning"? Otherwise I'm all out of ideas.
Sorry. I meant the problem is on /dev/pg1 crwxrwxrwx 1 root disk 97, 1 2003-09-23 19:01 /dev/pg1 Also if I run cdrecord -scanbus dev=0,1,0 I get scsidev: '0,1,0' scsibus: 0 target: 1 lun: 0 cdrecord: Permission denied. Cannot open '/dev/pg1'. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Best wishes - Ken
Hi all - I'd like to point out the solution to my k3b permissions problem as a courtesy to all those who helped me with it and for the benefit of anyone else who runs into the same issue. Briefly, I could burn CDs as root but not as a user - despite all the correct permissions on the devices involved. The solution came from an exchange between John Andersen and Ben Rosenberg on this list. The problem lay with resmgr. I needed to add the following line to /etc/pam.d/login session required pam_resmgr.so Now I can burn CDs as a user. Best wishes. Have a great Christmas everybody. - Ken
Kenneth Payne wrote:
By the way cdrecord -scanbus as user still produces
cdrecord: No such file or directory. Cannot open SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root. cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
If cdrecord is running suid, shouldn't it produce the same output as it does for root?
Best wishes
- Ken
I am still convinced that the problem comes from cdrecord permissions. Have you tried upgrading to the latest available version for SuSE (http://packman.links2linux.org/?action=316)? Second, I remember a thread a couple of weeks ago started by Viktor, eloquently titled "cdrecord and damn pg1" in which he seemed to be having the very same problem you are having. I've copied and pasted from lists.suse.com:
rom: Viktor <viktor@valamo.fi> Subject: Re: [SLE] cdrecord and damn pg1 [SOLVED] (sort of...)
Viktor wrote: /> / /> I just installing suse9, swiching from rh7.x. / /> / /> Some things is quite annoying. This is one, which I cannot find solution. / /> / /> Cdrecord, when I run cdrecord --scanbus, it find my recorder and cd-player. / /> / /> But, when I try make cd's, cdrecord woes "cdrecord: Permission denied. / /> Cannot open '/dev/pg1'. Cannot open SCSI driver." / /> / /> I have scsi-only -machine, all necessary modules is loaded and / /> permissions is right. / /> / /> Why cdrecord wants open /dev/pg1, all pg* -devices is parallel-port / /> things. / /> / /> Anyone, solution for this? /
Okay, I have solution, but this is not easy for less experienced users.
I build new cdrecord, mkisofs, cdda2waw and cdrecord-devel packages an another machine, which is RH8 installed.
Now works just I expect.
source: http://lists.suse.com/archive/suse-linux-e/2003-Nov/0757.html Third, google found this on linuxquestions:
Hi All,
i have Slackware 9.0 installed. i don't use LILO or anything like that. i have a boot diskette (got WinXP on another partition).
obviously this makes the boot process quite slow, and i'm a bit scared the diskette might get ruined some day. i decided to build a startup CD-ROM. got the images ready and all, but can't write to CD.
first when i go "cdrecord -scanbus" at the CLI, i get a message that says cannot open "/dev/pg*".
i tried "cdrecord dev=ATAPI -scanbus" i discovered that my CDRW device is listed as device 0,1,0.
Help please. thanks.
and the solution:
Cerbere You may or may not have to pass hdd=ide-scsi. Since cdrecord dev=ATAPI -scanbus finds your burner, and shows it as 0,1,0; you may be able to burn with a command similar to this:
cdrecord -v speed=[speed of burner] dev=ATAPI:1,0 -data [name of iso image]
On my system, cdrecord dev=ATAPI -scanbus shows that my burner is 0,0,0 and so this is the exact command I use to burn iso images to disk:
cdrecord -v speed=16 -overburn driveropts=burnfree dev=ATAPI:0,0 -pad -data [name of iso image]
Enjoy! --- Cerbere ghambis Thanks Cerbere, your method actually worked.
cheers all!!
source: http://www.linuxquestions.org/questions/archive/14/2003/09/4/95895 fx -- ______________________ Courtesy of SuSE Linux http://www.nibz.org
FX - Thanks for taking the trouble to do so much research into my problem.
I am still convinced that the problem comes from cdrecord permissions. Have you tried upgrading to the latest available version for SuSE (http://packman.links2linux.org/?action=316)?
Yes, I installed it this morning. It was a big improvement in that it actually gave me a k3bsetup module - something lacking in the original SUSE 9.0 version.
Second, I remember a thread a couple of weeks ago started by Viktor, eloquently titled "cdrecord and damn pg1" in which he seemed to be having the very same problem you are having.
Since the solution arrived at was compiling on a Red Hat machine, that is not going to work for me.
google found this on linuxquestions:
i tried "cdrecord dev=ATAPI -scanbus" i discovered that my CDRW device is listed as device 0,1,0.
Help please. thanks.
and the solution:
Cerbere You may or may not have to pass hdd=ide-scsi. Since cdrecord dev=ATAPI -scanbus finds your burner, and shows it as 0,1,0; you may be able to burn with a command similar to this:
cdrecord -v speed=[speed of burner] dev=ATAPI:1,0 -data [name of iso image]
On my system, cdrecord dev=ATAPI -scanbus shows that my burner is 0,0,0 and so this is the exact command I use to burn iso images to disk:
cdrecord -v speed=16 -overburn driveropts=burnfree dev=ATAPI:0,0 -pad -data [name of iso image]
Well, I tried cdrecord -scanbus dev=ATAPI and I got: scsidev: 'ATAPI' devname: 'ATAPI' scsibus: -2 target: -2 lun: -2 Warning: Using ATA Packet interface. Warning: The related libscg interface code is in pre alpha. Warning: There may be fatal problems. Using libscg version 'schily-0.7' scsibus0: 0,0,0 0) * 0,1,0 1) 'SAMSUNG ' 'CD-R/RW SW-216B ' 'Q001' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * scsibus1: 1,0,0 100) * 1,1,0 101) 'SAMSUNG ' 'DVD-ROM SD-616F ' 'F100' Removable CD-ROM 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * So I might well be able to get a cdrecord to work from the command line along the lines of the solution given above. However, I was rather hoping to get k3b to work rather than use the command-line. I tried adding dev=ATAPI:1,0 to the command line parameters for cdrecord in k3b but it didn't work. So I tried this (on a CD-RW disk) form the command line cdrecord -v speed=2 dev=ATAPI:1,0 -data kmp.iso and I got Cdrecord-Clone 2.01a18-dvd (i686-suse-linux) Copyright (C) 1995-2003 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to <warly@mandrakesoft.com>. Note: The author of cdrecord is not to be bothered with problems in this version. TOC Type: 1 = CD-ROM cdrecord: Warning: not running as root user, fs= option ignored. scsidev: 'ATAPI:1,0' devname: 'ATAPI' scsibus: 0 target: 1 lun: 0 Warning: Using ATA Packet interface. Warning: The related libscg interface code is in pre alpha. Warning: There may be fatal problems. Using libscg version 'schily-0.7' SCSI buffer size: 64512 atapi: 0 Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : Vendor_info : 'SAMSUNG ' Identifikation : 'CD-R/RW SW-216B ' Revision : 'Q001' Device seems to be: Generic mmc CD-RW. Current: 0x000A Profile: 0x0008 Profile: 0x0009 Profile: 0x000A (current) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R Drive buf size : 1359872 = 1328 KB FIFO size : 4194304 = 4096 KB Track 01: data 0 MB Total size: 0 MB (00:05.46) = 410 sectors Lout start: 1 MB (00:07/35) = 410 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 5 Reference speed: 2 Is not unrestricted Is erasable ATIP start of lead in: -11635 (97:26/65) ATIP start of lead out: 337350 (75:00/00) 1T speed low: 0 (reserved val 0) 1T speed high: 4 power mult factor: 4 6 recommended erase/write power: 3 A1 values: 02 4C B0 A2 values: 00 00 00 Disk type: Phase change Manuf. index: 3 Manufacturer: CMC Magnetics Corporation Blocks total: 337350 Blocks current: 337350 Blocks remaining: 336940 Forcespeed is OFF. Starting to write CD/DVD at speed 2 in real TAO mode for single session. Last chance to quit, starting real write 0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. trackno=0 BURN-Free is OFF. Performing OPC... Starting new track at sector: 0 Track 01: 0 of 0 MB written. Track 01: Total bytes read/written: 835584/835584 (408 sectors). Writing time: 9.008s Average write speed 0.9x. Fixating... cdrecord: Input/output error. close track/session: scsi sendcmd: no error CDB: 5B 00 02 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 04 00 00 00 00 0C 00 00 00 00 90 00 00 00 00 00 00 00 Sense Key: 0x4 Hardware Error, Segment 0 Sense Code: 0x90 Qual 0x00 (vendor unique sense code 0x90) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 30.256s timeout 480s cmd finished after 30.256s timeout 480s cdrecord: Cannot fixate disk. Fixating time: 30.262s cdrecord: fifo had 14 puts and 14 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%. kmp@ravenclaw:~> So it look like I'm getting there. I'll try again from the command line over the weekend. If I can get a command line version working I suppose I should be able to configure k3b to issue the correct cdrecord command. Best wishes - Ken
Kenneth Payne wrote:
Second, I remember a thread a couple of weeks ago started by Viktor, eloquently titled "cdrecord and damn pg1" in which he seemed to be having the very same problem you are having.
Since the solution arrived at was compiling on a Red Hat machine, that is not going to work for me.
Some reason, compiling never succeeded on my athlon machine, so, I tried it another machine which is pentium4, and it works. Then I change that machine also suse, and now it compile. Latest cderecord (2.019a), which i have now, is compiled with suse9. Viktor
Hi Richard - Unfortunately there's no k3bsetup option in the KDE Control Centre either under system administration or sounds and multimedia. Weird. Best wishes - Ken On Thursday 20 November 2003 4:34 pm, Richard Gelling wrote:
Not sure if this helps but I am running Slackware 9.1, and there is a K3b setup entry ,in KDE's control panle-> System Administration->k3bsetup.
I had similar problems with Slackware, and I was able to sort it from there.
Richard G.
On Thu, 2003-11-20 at 11:35, Kenneth Payne wrote:
John -
Hi, thanks for your help.
I remember k3bsetup on SuSE 8.1 but there's no such program in SuSE 9.0 as far as I can tell. It doesn't exist in /opt/kde3/bin nor can Yast2 find it in a package search. Strangely, there *are* png graphics for it in /opt/kde3/ share/apps/pics
Am I looking in the wrong place?
Best wishes
- Ken
It is in the program itself. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
Hi Ken - Thanks for your help. Could you expand on your remark "it's in the program itself"? There is a menu option "configure k3b". It leads to a dialog with a "devices" tab. Is this what you mean? The dialog shows my cd-writer as though it had been properly configured. Otherwise, there is no option anywhere in the menu system for running a separate "k3bsetup". The "configure devices" dialog actually says "run k3bSetup to set the correct permissions" but there is no button to launch any such program. I'm still confused. Best wishes - Ken On Thursday 20 November 2003 4:54 pm, Kenneth Schneider wrote:
On Thu, 2003-11-20 at 11:35, Kenneth Payne wrote:
John -
Hi, thanks for your help.
I remember k3bsetup on SuSE 8.1 but there's no such program in SuSE 9.0 as far as I can tell. It doesn't exist in /opt/kde3/bin nor can Yast2 find it in a package search. Strangely, there *are* png graphics for it in /opt/kde3/ share/apps/pics
Am I looking in the wrong place?
Best wishes
- Ken
It is in the program itself. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Thu, 2003-11-20 at 12:48, Kenneth Payne wrote:
Hi Ken -
Thanks for your help.
Could you expand on your remark "it's in the program itself"?
There is a menu option "configure k3b". It leads to a dialog with a "devices" tab. Is this what you mean? The dialog shows my cd-writer as though it had been properly configured.
Otherwise, there is no option anywhere in the menu system for running a separate "k3bsetup".
The "configure devices" dialog actually says "run k3bSetup to set the correct permissions" but there is no button to launch any such program.
I'm still confused.
Best wishes
- Ken
Dag burn it, I guess they removed that between the version I had in SuSE 8.2 and what is in SuSE 9.0. But I can say that I have used it quite a bit without any permissions problems. You didn't by chance ever run it after a su to root did you? This would have put files into your home directory owned by root. You can verify this by running ll -R|grep root in your home directory and seeing if you have any results. If you do you need to change the ownership to you first. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
Hi Ken I checked for root-owned files but - though I had more than I thought - none seem to have anything to do with k3b. The output from the k3b's error log is : ==================================== System ----------------------- K3b Version: 0.10 KDE Version: 3.1.4 QT Version: 3.2.1 cdrecord ----------------------- /usr/bin/cdrecord: Warning: not running as root user, fs= option ignored. scsidev: '0,1,0' scsibus: 0 target: 1 lun: 0 /usr/bin/cdrecord: Permission denied. Cannot open '/dev/pg1'. Cannot open 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-Clone 2.01a18-dvd (i686-suse-linux) Copyright (C) 1995-2003 Jörg Schilling Note: This version is an unofficial (modified) version with DVD support Note: and therefore may have bugs that are not present in the original. Note: Please send bug reports or support requests to <warly@mandrakesoft.com>. Note: The author of cdrecord is not to be bothered with problems in this version. TOC Type: 1 = CD-ROM cdrecord comand: ----------------------- /usr/bin/cdrecord -v gracetime=2 dev=0,1,0 speed=1 -dao -eject -data /tmp/ kde-kmp/K3b data project.iso =========================================== As you can see, it seems to be complaining about /dev/pg1 - but that device file has read write and execute permissions now for everyone! Any ideas? By the way, I've been a SuSe user since 5.3. So you outrank me - just. Best wishes - Ken
You didn't by chance ever run it after a su to root did you? This would have put files into your home directory owned by root. You can verify this by running ll -R|grep root in your home directory and seeing if you have any results. If you do you need to change the ownership to you first.
-- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
On Thu, 2003-11-20 at 13:58, Kenneth Payne wrote:
Hi Ken
I checked for root-owned files but - though I had more than I thought - none seem to have anything to do with k3b.
The output from the k3b's error log is :
==================================== System ----------------------- K3b Version: 0.10 KDE Version: 3.1.4 QT Version: 3.2.1
You may want to revert back to the version that's on the CD'Cd's/DVD. It is the one I am using with out error, even made copies of DVD's for the company propaganda yesterday with out too much error. IIRC I tried the .10 version from apt-get (synaptic) and had problems so reinstalled the one from the DVD. Aha, same first name, only the faces have been changed to protect the innocent. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
Ken - My version *is* the version on the SUSE 9.0 DVD. I suppose I could install an earlier version from 8.1 or 8.2. Best wishes - Ken On Thursday 20 November 2003 7:05 pm, Kenneth Schneider wrote:
On Thu, 2003-11-20 at 13:58, Kenneth Payne wrote:
QT Version: 3.2.1
You may want to revert back to the version that's on the CD'Cd's/DVD. It is the one I am using with out error, even made copies of DVD's for the company propaganda yesterday with out too much error. IIRC I tried the .10 version from apt-get (synaptic) and had problems so reinstalled the one from the DVD.
Aha, same first name, only the faces have been changed to protect the innocent.
-- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
Kenneth Payne wrote:
Hi Ken
I checked for root-owned files but - though I had more than I thought - none seem to have anything to do with k3b.
Hi! Just same problem. Solution, grab fresh sources from cdrecord and compile. Viktor
In a previous message, Kenneth Payne <kmp@atrium.fsnet.co.uk> wrote:
I remember k3bsetup on SuSE 8.1 but there's no such program in SuSE 9.0 as far as I can tell. It doesn't exist in /opt/kde3/bin nor can Yast2 find it in a package search. Strangely, there *are* png graphics for it in /opt/kde3/ share/apps/pics
Here (8.2) it's in /opt/kde3/bin. So I don't know what might have happened to it :-( John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Knossos: escape the ever-changing labyrinth before the Minotaur catches you!
On Thursday 20 November 2003 16:43, Kenneth Payne wrote:
Hi -
I can't burn CD's in k3b as a user. I can burn successfully as root. It's obviously a permissions problem but I can't see where.
As a user is sr0 user disk and what do you have in fstab /dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 is it something like that. Ian
If I look at k3b's error log it seems to be complaining about not having permissions for /dev/pg1 but I've set every permission possible on this device file but still I get the same error.
Here's some details
k3b gives the device as
Samsung cd-r/rw sw-216b /dev/sr0 (0,1,0) interface generic scsi write modes sao, tao, raw raw/r96r
permissions set are
lrwxrwxrwx 1 root root 3 2003-10-29 22:28 /dev/cdrecorder -> sr0
brw-rw-rw- 1 root disk 11, 0 2003-09-23 18:59 /dev/sr0 crw-rw-rw- 1 root disk 21, 0 2003-09-23 18:59 /dev/sg0 crwxrwxrwx 1 root disk 97, 1 2003-09-23 19:01 /dev/pg1
Can anyone tell me what else I have to set?
Best wishes
- Ken
Ian 0 Thanks for the suggestion, but my fstab reads like yours. The settings for /dev/sr0 are these, by the way kmp@ravenclaw:~> ls -l /dev/sr0 brw-rw-rw- 1 root disk 11, 0 2003-09-23 18:59 /dev/sr0 kmp@ravenclaw:~> Best wishes - Ken On Thursday 20 November 2003 11:24 pm, Ian David Laws wrote:
As a user is sr0 user disk and what do you have in fstab
/dev/cdrecorder /media/cdrecorder auto ro,noauto,user,exec 0 0 is it something like that.
Ian
participants (12)
-
BandiPat
-
FX Fraipont
-
Ian David Laws
-
Jason
-
Johannes Meixner
-
John Pettigrew
-
Kenneth Payne
-
Kenneth Schneider
-
Mike Coan
-
Richard Gelling
-
Viktor
-
Vince Littler