Bug 188489 – app-cdr/k3b - remove USE=kde and k3bsetup from the ebuilds

• Product: Gentoo Linux
• Status: VERIFIED FIXED

[Description Jakub Moc (RETIRED) 2007-08-11 17:19:11 UTC]

Device permissions are handled by udev, binary permissions by portage. There's no need to use the k3bsetup(2) thing that makes the binaries setgid for no reason (and requires non-existant burning group in 1.0.3 even), this whole thing just confuses users.

The annoying warning can be disabled in preferences, just add a note on how to get rid of it instead.

Thanks.

[Comment 1 Carsten Lohrke (RETIRED) 2007-08-11 19:23:44 UTC]

Not a blocker, but might be sensible for the next version bump.

[Comment 2 Jakub Moc (RETIRED) 2007-08-11 19:32:14 UTC]

(In reply to comment #1)
> Not a blocker, but might be sensible for the next version bump.

Erm, I explicitely made it a blocker to make this part of the transition for stable users. It's a major version bump and this makes sense there. Doesn't make sense to suddenly change this on subminor version bumps and confuse users on stable even more.

[Comment 3 Tobias Heinlein (RETIRED) 2007-11-04 00:47:30 UTC]

Change performed with the version bump to 1.0.4.

[Comment 4 Chris Arndt 2007-11-21 13:30:04 UTC]

Even though this is marked as resolved, I would like to add that the lack of the kd3setup option actually also adds confusion, as you get strange error messages, when the backend tools like cdrecord lack the proper permissions.

The k3b setup option is actually very userfreindly, at least in my opinion.

[Comment 5 Jakub Moc (RETIRED) 2007-12-05 10:53:08 UTC]

(In reply to comment #4)
> Even though this is marked as resolved, I would like to add that the lack of
> the kd3setup option actually also adds confusion, as you get strange error
> messages, when the backend tools like cdrecord lack the proper permissions.

I don't see what do you mean by 'proper' permissions. Proper permissions are the ones as installed by cdrtools/cdrkit ebuilds, not as mangled by k3bsetup or similar tools that make them setuid for no valid reason whatsoever.

[Comment 6 Fabian Kislat 2007-12-17 14:48:51 UTC]

(In reply to comment #5)
> (In reply to comment #4)
> > Even though this is marked as resolved, I would like to add that the lack of
> > the kd3setup option actually also adds confusion, as you get strange error
> > messages, when the backend tools like cdrecord lack the proper permissions.
> 
> I don't see what do you mean by 'proper' permissions. Proper permissions are
> the ones as installed by cdrtools/cdrkit ebuilds, not as mangled by k3bsetup or
> similar tools that make them setuid for no valid reason whatsoever.
> 

If I leave the permissions as they are installed by the ebuild, I cannot burn CDs as a normal user:
/usr/bin/cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl.
/usr/bin/cdrecord: Operation not permitted. Cannot open or use SCSI driver.
What am I supposed to do?

[Comment 7 Jakub Moc (RETIRED) 2007-12-17 15:55:54 UTC]

(In reply to comment #6)
> /usr/bin/cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl.
> /usr/bin/cdrecord: Operation not permitted. Cannot open or use SCSI driver.
> What am I supposed to do?

Use cdrkit or bug Jörg Schilling to fix cdrtools. Nothing to be done here, messing with permisssions and making the thing needlessly SUID is plain broken.