LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-22-2018, 02:25 PM   #1
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 9,986

Rep: Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093
k3b permissions issue


I have recently upgraded to current, and k3b has stopped working - a permissions issue with cdrecord. I reinstalled k3b and cdrtools and the issue remains.

I badly wanted to burn one dvd here, so I started X as root and everything ran, but it's not the answer/ What ios the answer? I run XFCE btw.
 
Old 07-22-2018, 02:34 PM   #2
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,545

Rep: Reputation: Disabled
Try something like this.

Code:
# chown root:somegroup /usr/bin/cdrecord
# chmod 4710 /usr/bin/cdrecord
Then make sure your user is part of 'somegroup'.
 
1 members found this post helpful.
Old 07-23-2018, 03:53 AM   #3
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 9,986

Original Poster
Rep: Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093
Thanks, that sorted it.

4710 on cdrecord actually failed; I then tried 4755 and that worked. I probably only need 4750, but I'm really not bothered, as who knows what group k3b is in?
 
Old 07-23-2018, 08:52 AM   #4
sysfce2
Member
 
Registered: Jul 2009
Distribution: Slackware
Posts: 113

Rep: Reputation: 42
There is alsp k3bsetup which will set the permissions for you.
 
1 members found this post helpful.
Old 07-23-2018, 07:29 PM   #5
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.2
Posts: 7,809
Blog Entries: 58

Rep: Reputation: Disabled
A bit late, but I created a burning group and added myself to it. A method that's mentioned in CHANGES_AND_HINTS.
 
Old 07-24-2018, 01:31 AM   #6
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 9,986

Original Poster
Rep: Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093Reputation: 1093
Silly question, but why not fix it BEFORE they made the package? Come to think of it, why not release a new version? Current has so many changes it's already a new version.
 
Old 07-24-2018, 10:46 AM   #7
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,866

Rep: Reputation: 3583Reputation: 3583Reputation: 3583Reputation: 3583Reputation: 3583Reputation: 3583Reputation: 3583Reputation: 3583Reputation: 3583Reputation: 3583Reputation: 3583
Quote:
Originally Posted by business_kid View Post
Silly question, but why not fix it BEFORE they made the package? Come to think of it, why not release a new version? Current has so many changes it's already a new version.
It isn't broken. It is designed to have those permissions by default (and it's been that way for a LONG time), just as a user isn't automatically assigned to all the recommended groups. It allows you to have better control over who has access to burn discs (for example, a secure server that contains confidential information).

Whether or not those are "sane defaults" is a topic for another discussion, but it is working as intended.

Code:
If you have permission errors when attempting to burn a cdrom or dvd image,
  such as the following:
    /usr/bin/cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl
  then cdrecord almost certainly needs root privileges to work correctly.
  One potential solution is to make the cdrecord and cdrdao binaries suid root,
  but this has possible security implications.  The safest way to do that is 
  to make those binaries suid root, owned by a specific group, and executable
  by only root and members of that group.  For most people, the example below
  will be sufficient (but adjust as desired depending on your specific needs):
    chown root:cdrom /usr/bin/cdrecord /usr/bin/cdrdao
    chmod 4750 /usr/bin/cdrecord /usr/bin/cdrdao
  If you don't want all members of the 'cdrom' group to be able to execute the
  two suid binaries, then create a special group (such as 'burning' which is
  recommended by k3b), use it instead of 'cdrom' in the line above, and add
  to it only the users you wish to have access to cdrecord and cdrdao.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Plasma 5 K3b cdrecord user permissions issue RadicalDreamer Slackware 11 10-21-2018 05:40 PM
[SOLVED] K3B lost permissions waddles Linux - Software 3 02-24-2013 04:22 PM
k3b permissions issue reverend_hh Linux - Software 2 06-24-2008 06:27 AM
K3b permissions pilatus666 Mandriva 19 05-18-2007 05:12 AM
k3b permissions? smyle Linux - Software 4 12-15-2004 04:56 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:32 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration