On Sunday 03 September 2006 19:08, Francois Marier wrote:
> So what I am thinkin of doing is removing k3bsetup from the Debian package
> and replacing the cdrecord warning with a "do a dpkg-reconfigure cdrecord
> and set it as SUID if you are having problems" message (some people report
> success with a non-SUID cdrecord). Afterall, that's the proper fix on
> Debian.
>
I think its safer not having it suid, assuming groups and permissions are fine
you can happily use cdrecord non-suid. For kubuntu I recently patched k3b to
not perform this test. Not sure if this is of any use to you.
diff -Nurp clean/k3b-0.12.17/src/k3bsystemproblemdialog.cpp k3b-0.12.17/src/k3bsystemproblemdialog.cpp
--- clean/k3b-0.12.17/src/k3bsystemproblemdialog.cpp 2006-08-23 08:32:12.000000000 +0100
+++ k3b-0.12.17/src/k3bsystemproblemdialog.cpp 2006-08-25 17:21:20.000000000 +0100
@@ -207,18 +207,6 @@ void K3bSystemProblemDialog::checkSystem
i18n("Use K3bSetup to solve this problem."),
true ) );
}
- else if( !k3bcore->externalBinManager()->binObject( "cdrecord" )->hasFeature( "suidroot" ) && getuid() != 0 ) // not root
- problems.append( K3bSystemProblem( K3bSystemProblem::CRITICAL,
- i18n("%1 will be run without root privileges").arg("cdrecord"),
- i18n("It is highly recommended to configure cdrecord "
- "to run with root privileges. Only then cdrecord "
- "runs with high priority which increases the overall "
- "stability of the burning process. Apart from that "
- "it allows changing the size of the used burning buffer. "
- "A lot of user problems could be solved this way. This is also "
- "true when using SuSE's resmgr."),
- i18n("Use K3bSetup to solve this problem."),
- true ) );
#endif
}
