Hi
I run again in a bug with a corrupt suduers file and this time I did not set up a password for root, so most likely I have to install everything again.
The error is
sudo shutdown -r now sudo: /etc/sudoers.d/tde-secure-path is mode 0644, should be 0440
/etc/sudoers.d/README: /etc/sudoers.d/tde-secure-path near line 18 <<<
sudo: parse error in /etc/sudoers.d/README near line 18
Try Exe/Gnu 4.2, which is updated Debian Wheezy with Trinity 3.5.13.2 For me it's running fabulously well and has the advantage of traditional permissions where you either login as root or as a user, or use su. Audio worked out of the box. Slightly buggy Iceweasel is the only problem I've had so far. With Exe.Gnu >> Debian sudo is optional.
I also had very good results with a March 2014 version of the Ubuntu nightly build .iso with Trinity R14. Others on the list say R14 is slower than 3.5.13.2 but I didn't find this too noticeable. Nightlies are still Ubuntu 13.04. Audio worked fine on two PC's but failed on a third.
KDM is configurable to allow all users to shut down, to allow root login (via KDM) or not and to disable/enable SAK by editing /etc/trinity/kdm/kdmrc.
KDM's SAK feature (secure attention key) should possibly be disabled before shutdown after installation. On some machines the ctr+alt+delete command doesn't work making it impossible to log in. I'd like to see SAK disabled by default, since ctr+alt+delete almiost always fails in my experience.
On 6/12/14, Uwe Brauer oub.oub.oub@gmail.com wrote:
Hi
I run again in a bug with a corrupt suduers file and this time I did not set up a password for root, so most likely I have to install everything again.
The error is
sudo shutdown -r now sudo: /etc/sudoers.d/tde-secure-path is mode 0644, should be 0440
/etc/sudoers.d/README: /etc/sudoers.d/tde-secure-path near line 18 <<<
sudo: parse error in /etc/sudoers.d/README near line 18
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Try Exe/Gnu 4.2, which is updated Debian Wheezy with Trinity 3.5.13.2 For me it's running fabulously well and has the advantage of traditional permissions where you either login as root or as a user, or use su. Audio worked out of the box. Slightly buggy Iceweasel is the only problem I've had so far. With Exe.Gnu >> Debian sudo is optional.
I also had very good results with a March 2014 version of the Ubuntu nightly build .iso with Trinity R14. Others on the list say R14 is slower than 3.5.13.2 but I didn't find this too noticeable. Nightlies are still Ubuntu 13.04. Audio worked fine on two PC's but failed on a third.
KDM is configurable to allow all users to shut down, to allow root login (via KDM) or not and to disable/enable SAK by editing /etc/trinity/kdm/kdmrc.
KDM's SAK feature (secure attention key) should possibly be disabled before shutdown after installation. On some machines the ctr+alt+delete command doesn't work making it impossible to log in. I'd like to see SAK disabled by default, since ctr+alt+delete almiost always fails in my experience.
The default has already been switched to off. Does it always fail on R14 or was this data point obtained with 3.5.13.x?
Thanks!
Tim
The default has already been switched to off. Does it always fail on R14 or was this data point obtained with 3.5.13.x?
Thank you Tim, yes SAK is actually turned off on the R14/Ubuntu 13.04 nightly live CD I installed in March. That's the only R14 I've installed so far.
The SAK problem has always occurred with 3.5.13.2 and older, on 3 different PC's with two different keyboards. It occurred on a few of your (earlier) live Ubuntu CD's, Sparky Linux (3.5.13.x? on Wheezy) and on several apt installations on Lucid and Jessie.
I believe SAK came already turned off on all three versions of Exe/Gnu.
It did recur when I reinstalled KDM on 3.5.13.2/Debian Testing/Jessie a few weeks ago. (I used Wheezy repos for that one and it otherwise works flawlessly).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
The default has already been switched to off. Does it always fail on R14 or was this data point obtained with 3.5.13.x?
Thank you Tim, yes SAK is actually turned off on the R14/Ubuntu 13.04 nightly live CD I installed in March. That's the only R14 I've installed so far.
The SAK problem has always occurred with 3.5.13.2 and older, on 3 different PC's with two different keyboards. It occurred on a few of your (earlier) live Ubuntu CD's, Sparky Linux (3.5.13.x? on Wheezy) and on several apt installations on Lucid and Jessie.
I believe SAK came already turned off on all three versions of Exe/Gnu.
It did recur when I reinstalled KDM on 3.5.13.2/Debian Testing/Jessie a few weeks ago. (I used Wheezy repos for that one and it otherwise works flawlessly).
OK, that makes sense. The tsak daemon (the core the SAK functionality that actually "talks" to the keyboard) has been vastly improved in R14.
Tim
On Friday 13 of June 2014 23:53:11 Timothy Pearson wrote:
The default has already been switched to off. Does it always fail on R14 or was this data point obtained with 3.5.13.x?
Thank you Tim, yes SAK is actually turned off on the R14/Ubuntu 13.04 nightly live CD I installed in March. That's the only R14 I've installed so far.
The SAK problem has always occurred with 3.5.13.2 and older, on 3 different PC's with two different keyboards. It occurred on a few of your (earlier) live Ubuntu CD's, Sparky Linux (3.5.13.x? on Wheezy) and on several apt installations on Lucid and Jessie.
I believe SAK came already turned off on all three versions of Exe/Gnu.
It did recur when I reinstalled KDM on 3.5.13.2/Debian Testing/Jessie a few weeks ago. (I used Wheezy repos for that one and it otherwise works flawlessly).
OK, that makes sense. The tsak daemon (the core the SAK functionality that actually "talks" to the keyboard) has been vastly improved in R14.
Tim
I do not want to be croaker, but most of the patches related to SAK was backported to 3.5.13.2.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Friday 13 of June 2014 23:53:11 Timothy Pearson wrote:
The default has already been switched to off. Does it always fail on R14 or was this data point obtained with 3.5.13.x?
Thank you Tim, yes SAK is actually turned off on the R14/Ubuntu 13.04 nightly live CD I installed in March. That's the only R14 I've installed so far.
The SAK problem has always occurred with 3.5.13.2 and older, on 3 different PC's with two different keyboards. It occurred on a few of
your
(earlier) live Ubuntu CD's, Sparky Linux (3.5.13.x? on Wheezy) and on several apt installations on Lucid and Jessie.
I believe SAK came already turned off on all three versions of
Exe/Gnu.
It did recur when I reinstalled KDM on 3.5.13.2/Debian Testing/Jessie a few weeks ago. (I used Wheezy repos for that one and it otherwise works flawlessly).
OK, that makes sense. The tsak daemon (the core the SAK functionality that actually "talks" to the keyboard) has been vastly improved in R14.
Tim
I do not want to be croaker, but most of the patches related to SAK was backported to 3.5.13.2.
-- Slavek
OK, good to know. I figured that was the case, but wasn't sure if all the udev patches had gone in.
Tim
-
Chris Graham -
Lisi Reisz -
Slávek Banko -
Timothy Pearson -
Uwe Brauer