Using Tumbleweed and KDE with SDDM – clean install on a Lenovo Yoga 3 laptop.
The programs “w”, “who” and “last” do not register the presence of a user logged in to he desktop environment. If the user opens e.g. Konsole or logs in via ssh then the associated pts tty entries are shown. Previously a desktop login created a console tty.
This is a bit annoying as my shell scripts dating back up to 35 years no longer work. The only thing that I can think of is to parse “ps“ for "systemd --user” to determine who is logged in. Does anyone have a better suggestion (apart from using KDM)?
There must be something wrong with your install. Tried two TW machines, both show normal output of the commands.
BTW, one machine has been rolling TW for ages, the other was installed ~1 month ago.
I have one hybrid machine – Leap-42.1 with the Plasma5 environment from Tumbleweed. Also in the last few days I have installed TW on two more machines; both were clean installs via an openSUSE-Tumbleweed-NET-x86_64-Snapshot20160830-Media.iso on a micro-SD card. One is dual-boot (Win 8.1) and the others are single o.s. All three are Lenovo Yoga 3 Pro 1370 laptops. They all exhibit the same behaviour. They only repositories enabled are tumbleweed/repo/oss and packman/suse/openSUSE_Tumbleweed (for the Broadcom wireless drivers) from GWDG.
I use a reverse ssh tunnel to log into the dual-boot machine (yoga3p) via a server (ln1) from my personal laptop (y3).
With SDDM
rayh@y3:/repos/opensuse/tumbleweed/iso> ln1
Last login: Sat Sep 3 12:16:17 2016 from x.y.z
Have a lot of fun...
sysman@ln1:~> yoga3p
Last login: Sat Sep 3 13:22:23 2016 from ::1
Have a lot of fun...
sysman@yoga3p:~> w
12:18:30 up 2 days, 16:04, 3 users, load average: 0.18, 0.19, 0.09
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
sysman pts/0 ::1 12:18 4.00s 0.03s 0.00s w
clairej pts/1 :0 Sat12 4:52 0.04s 0.00s /usr/bin/sudo su -
clairej pts/2 :0 Sat12 35.00s 0.11s 0.02s /bin/bash
sysman@yoga3p:~> sudo ex /etc/sysconfig/displaymanager -c /DISPLAYMANAGER=/s/\"sddm\"/\"kdm\"/ +wq
sysman@yoga3p:~>
sysman@yoga3p:~> sudo systemctl reboot
sysman@yoga3p:~> Connection to localhost closed by remote host.
Connection to localhost closed.
sysman@ln1:~>
{wait for reboot and for Claire to login from KDM, then for ssh tunnel to reconnect}
sysman@ln1:~> yoga3p
Last login: Mon Sep 5 12:18:14 2016 from ::1
Have a lot of fun...
sysman@yoga3p:~>
sysman@yoga3p:~> w
12:36:09 up 14 min, 4 users, load average: 0.00, 0.00, 0.01
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
clairej console :0 12:22 14:02 0.00s 0.06s -:0
clairej pts/1 :0 12:22 13:28 0.04s 0.00s /usr/bin/sudo su -
clairej pts/2 :0 12:22 25.00s 0.10s 0.05s /bin/bash
sysman pts/3 ::1 12:35 0.00s 0.03s 0.00s w
sysman@yoga3p:~> cat /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20160831"
...
sysman@yoga3p:~> exit
logout
Connection to localhost closed.
sysman@ln1:~>
sysman@ln1:~>
sysman@ln1:~> Terminated
rayh@y3:/repos/opensuse/Tumbleweed/iso>
From the second (KDM) run of “w” a console login is displayed, but not on the first run with SDDM. (pts/1 and pts/2 are from an instance of Konsole with two tabs/sessions opening automatically.)
This is absolutely reproducible, and seems to be due to the way SDDM is launched. I do not think that it is due my install method – that should be easier to fix.