Can't burn wiht k3b

alkos333 · 03-31-2007, 03:28 PM

Thank you all for your effort and time. I'm glad everything is working now!

{BBI}Nexus{BBI} · 03-31-2007, 04:13 PM

Happy Burning

alkos333 · 03-31-2007, 07:51 PM

Quote:

Originally Posted by {BBI}Nexus{BBI}

Happy Burning

That was a good suggestion, I should have thought of that earlier.

pyrow · 03-31-2007, 11:51 PM

k3bsetup2 is what you want to use.. if your using kde. this is what you have to do: go into a terminal as your own user type

$ kdesu k3bsetup2

that will run the program to get things up and running. set it up for all users.

alkos333 · 04-01-2007, 10:37 AM

The problem is already solved. k3bsetup2 didn't work too well with 0.12.17. It worked find with 1.0. If you go to Settings > k3b Setup, it will do exactly what your line does there.

Crashbox · 02-27-2008, 09:19 PM

Quote:

Originally Posted by alkos333

Code:

 
/opt/kde/bin/k3bsetup: line 20: kdesu: command not found

Hey everyone...I was in the same place as alkos and it all started with that error. After a recent upgrade from an IDE CDRW to a SATA DVDRW, I attempted to update k3b and it all went to hell.

Anyway, with the help of this thread and a little work, I solved it. Or it at least I came up with a solution which works for me. I also grabbed the latest k3b source (v 1.0.4), but instead of using Pat's slackbuild, I opted to go it alone.

As always, I started with a

Code:

./configure --help

and I noticed the following option:

Code:

--without-cdrecord-suid-root
                          
enable or disable K3b's suid root check for
cdrecord/cdrdao/wodim (default=enabled)

hmmm...sounds like this is a problem the k3b team is aware of...so I figured it was worth a shot and did my config with:

Code:

./configure --without-cdrecord-suid-root

The config finished fine, although it did throw back a message about how that option is not the preferred. 'Make' and 'Checkinstall' went fine and K3b is working well.

It occurs to me that the reason alkos'a solution worked is because Pat has this option disabled in the slackbuild, but I thought I should include this in this thread for the non-slackers who may wander in.