K3B is compiled to be part of KDE but that is a design decision of KDE developers, not Slackware: Patrick Volkerding or Eric Hameleers can't invent a compilation option that is not provided by the upstream developers, or they would have to re-write the application themselves.

So if you want that be changed, you will have to request it from the KDE developers. Good luck.

PS Or convince K3B developers to use only Qt, not KDE, for instance relying on other software to grant more privileges to (specific) regular users whenever needed.

2 members found this post helpful.

tside of the desktops, would be compiled so they can.[/QUOTE]


It is clear, here ?

https://en.wikipedia.org/wiki/K3b

If you do not want qt and kde, do not use k3b, you can use xfburn.

I have had this problem before and I have solved it with


(make sure the user is included in 'cdrom' group)

I hope it helps you.

1 members found this post helpful.

Or, if you do not want to install a biggish part of KDE, you could install xfburn from Salix.

my user is already in cdrom group.
Why would it be necessary to be changing the ownership of those binaries?
What's the official Slackware position on burning optical disks? Why is this still broken two decades later?

It isn't broken. On a full install, it works perfectly fine for root. Slackware doesn't presume to know what you are using the computer for or whether you want a user to have access to burn a CD/DVD. This is why permissions ship as they do. Then the administrator (usually you) can decide if you want others to be able to burn.

This is also why when you use adduser, it defaults to no additional groups, even though a user would need many of them for common functions within the OS.

Ultimately, it follows the principle of least privilege.

1 members found this post helpful.

Yes, this is probably the solution. It's (more fully) noted in CHANGES_AND_HINTS.TXT on the mirrors and ISO images:

2 members found this post helpful.

Brasero* for now? Unless your goal is just to fix it.

That was true a decade ago.
Nowadays most distros give users access to hardware like usb mounting of flash drives, cameras etc.
Optical disc burning is very much in that same type of usage.
So why do we still have to dick around with nonexistent groups and permissions instead of just having the cdburning group already there and available to users (when you hit tab when adding a user).
Printing, scanning, mounting of removable media, cd burning - basic use of computer hardware that just about every user will need at one time or another.

Brasero is for Gnome.
I've been alergic to Gnome since it went v.3
I've developed same alergies to KDE since v.4
Gnome is not even part of Slackware.

However, you can get Brasero without the whole GNOME desktop. It is available in the Salix repos and does no not have any dependency beyond a full Slackware installation:
http://slackware.uk/salix/x86_64/14.2/salix/gnome/
http://slackware.uk/salix/i486/14.2/salix/gnome/

1 members found this post helpful.

Ok, thank you.
I'll give it a try.

If you've noticed, Slackware doesn't always follow what other distros are doing. Slackware does not prompt for any users to be set up beyond setting a password for root. sudo is not set up. There is no dependency management. It starts in runlevel 3. There's no graphical installer. The installer doesn't prompt you to partition drives. Not to mention the various things out there that are quite controversial. And I can go on and on.

Slackware is the work of Patrick Volkerding. He makes the decisions on how it should be set up. He has taken the stance to not assume how users will use their machines and sets it up accordingly. He doesn't know if this will be a server that contains confidential information that regular users shouldn't be able to remove using thumbdrives or burning a cd -- or whether this will be a home desktop where the regular user is also the administrator of the machine. He provides a good default state and expects the user to change things to fit how the distro should work for them.

And if you feel that the basics of a computer include cd burning, just follow the advice of gauchao.

Make the group for cdrecord and cdrdao to be cdrom, adjust permissions so that group can read and execute those files, and move on. I don't know why this is such a big deal to you. The separate group that Robby recommended was only if you want some to have access to the cdrom without having the ability to burn. You'd need a separate group to differentiate between the two. You can stick with just the cdrom group in most other instances.

You're free to request changes, but it doesn't always happen. With Slackware, you can learn to "drink the koolaid" and enjoy it, try and fight for what you feel should take place in Slackware (but this can end up leaving you frustrated), or move to a distro that has ideals that better match yours (or you could even spin off Slackware and create a derivative that matches your ideals -- Salix is a pretty popular distro that has done just this). We love people using Slackware, but we also know that Slackware isn't for everyone (and that's ok).

5 members found this post helpful.

Here's a few more: https://slackbuilds.org/result/?search=burn&sv=14.2

Thanks gauchao
That worked for burning with both K3B and Simpleburn.
I missed the second line with the chmod at first.
And now 3 months later I revisited the issue as I really need to burn discs
It's solved.

1 members found this post helpful.