Restart leads to login-screen in latest UNSTABLE


#1

With the latest UNSTABLE when I choose ‘Restart’ from the TrueOS-Menu I am redirected to the login-screen instead of shutdown/reboot. Of course that’s much faster and leads to an almost similar result - but can I change this to a real restart in any settings?


#2

Happens since trueos version trueos-desktop-201711180935


#3

==================

boot environment now (N) … 12.0-CURRENT-up-20180105_133645 NR 2018-01-05
after restart ® … 12.0-CURRENT-up-20180105_133645 NR 2018-01-05
boot loader …………………………………… BSD
type ……………………… BIOS
CPU ………………………………………………………… Intel® Core™ i5-3320M CPU @ 2.60GHz
number of cores ……………… 4
host ……………………………………………………… trueos-4013
memory ………………………………………………… 16384 MB available, 9690 MB free
OS git branch ……………………………………………………………………………………… trueos-master
OS git revision ………………………………………………………………………………… 7a0a0994e
OS kernel build time ………………………………………………………… Sun 2017 Dec 3 15:25:30 UTC
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 12.0-CURRENT
OS version and patch level …… (freebsd-version) 12.0-CURRENT
TrueOS package set ………………… UNSTABLE
TrueOS version …………………………… TrueOS-Desktop-201711180935
uptime ………………………………………………… 5 mins
user ……………………………………………………

More (TrueOS Desktop):

desktop environment …… Lumina
sound card driver ………… pcm0: <Realtek ALC269 (Analog)> (play/rec) default
wireless driver ……………… iwn0
X11 drivers ………………………… modesetting_drv.so

#4

I had that problem once. Fixed it like this:
sudo chmod 4555 /sbin/shutdown
Now it just works :slightly_smiling_face:


#5

Wondering why this should change anything. Tried it nevertheless. In fact it does not help to allow others the execution of /sbin/shutdown, nor I want to do so.


#6

Did you try it after rebooting your system? If not, try again…


#7

Yes, tried it again, wasted time, and I am still not ready to grant shutdown-right to ‘others’


#8

It seems the cause of the problem was found and the devs just fixed it. Wait a bit until the new update is ready. Then roll back to a known good BE and do this:

sudo rm -rf /usr/local/pkg-cache
(Just to make sure you use the right packages)

Finally try updating again :+1:


#9

See the README on the front page, concerning the shutdown issue


#10

sudo rm -rf /usr/local/pkg-cache

Had the same problem with the latest stable inside VirtualBox. Fix worked, thanks.