How do I run K3b as root?

stf92 · 04-19-2012, 02:53 PM

Kernel 2.6.21.5, Slackware 12.0
K3b 1.0.2
cdrecord 2.01

Hi: when I run K3b, cdrecord complains about not having permissions. For instance,

Code:

/usr/bin/cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits./usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).

This is output when asking K3b to show the debugging output. How can I run K3b as root? Of course I could start X as root, but I would not want to do it.

business_kid · 04-19-2012, 03:14 PM

Try adding yourself to group cdrom.

usermod -G <stuff>
is the command - man usermod to find out the stuff

kingbeowulf · 04-19-2012, 10:42 PM

If you are in KDE, you can also use the kuser utility. I think you need to be in both plugdev and cdrom groups...but its been awhile

red_fire · 04-20-2012, 05:48 AM

alternatively, to run it as root,
use

$kdesu k3b

stf92 · 04-20-2012, 06:26 AM

I always belonged to the group 'users'. Now I did

Code:

usermod -G cdrom semoi

I hope I now belong to cdrom also. But still the same problem. I do not understand, because up to now, I think I always burned discs as semoi.

mRgOBLIN · 04-20-2012, 07:04 AM

Anytime you modify your Group membership, you need to log out and back in for them to take effect.

The problem with using usermod is that it explicitly sets the groups to the ones passed as arguments and removes the rest.

You should probably do the following.

Code:

usermod -G users,dialout,audio,video,cdrom,plugdev,power,netdev semoi

Then log out and back in. You can check your group membership with the "groups" command.

In future you might try the "gpasswd" command like this.

Code:

gpasswd -a semoi cdrom

CudaPrime · 03-03-2015, 12:42 AM

I'm using Kubuntu 14 (Debian jessie/sid)

Not sure if this is the 'proper' way to go about this, but, what I ended up doing is launching a konsole, #sudo su to log in as root
Then just ran the package with #k3b and it then launched k3b as root and I was then able to access the directories I wanted.

Hope that helps.

bassmadrigal · 03-03-2015, 06:39 AM

Quote:

Originally Posted by CudaPrime

I'm using Kubuntu 14 (Debian jessie/sid)

Not sure if this is the 'proper' way to go about this, but, what I ended up doing is launching a konsole, #sudo su to log in as root
Then just ran the package with #k3b and it then launched k3b as root and I was then able to access the directories I wanted.

Hope that helps.

You should not run GUI apps using sudo. You can cause a lot of issues with your system. The program sudo is for command line programs only and kdesu should be used if you need to run a GUI program as root.

https://help.ubuntu.com/community/Ro...Graphical_sudo

However, k3b should not need to be run as root if your permissions and groups are set up properly on your system.

Also, it is generally frowned upon to respond to old threads.

dugan · 03-03-2015, 11:10 AM

CudaPrime: no, that is not the proper way to do it on Slackware. The proper way to do it on Slackware is actually documented:

Quote:

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.

-- CHANGES_AND_HINTS.TXT

Fred-1.2.13 · 03-03-2015, 12:19 PM

Deleted

kikinovak · 03-03-2015, 01:15 PM

Quote:

Originally Posted by stf92

Kernel 2.6.21.5, Slackware 12.0
K3b 1.0.2
cdrecord 2.01

Hi: when I run K3b, cdrecord complains about not having permissions. For instance,

Code:

/usr/bin/cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits./usr/bin/cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).

This is output when asking K3b to show the debugging output. How can I run K3b as root? Of course I could start X as root, but I would not want to do it.

The answer is in the "Getting Started" section of the Slackware documentation.

http://docs.slackware.com/slackbook:users

slacker1337 · 03-03-2015, 08:35 PM

Code:

usermod -G users,dialout,audio,video,cdrom,plugdev,power,netdev semoi

I've always had great success, and found it easier to simply do:

Code:

usermod -aG cdrom username

You are still required to log out and back in to update your profile.