w(1), who(1) and uptime(1) don't count the desktop user

[lucho]

Unlike the amd64 Ubuntu, here w(1), who(1) and uptime(1) don't count the user if logged through LXDE. (If logged torough SSH, they do.) To test, log in through LXDE, open LXterminal and type "w", "who", or "uptime". You won't be shown as a logged in user. (In the amd64 Ubuntu, you will be.) I think that this is a bug, but don't know whether it's a kernel bug or not.

[dukla2000]

If it is a bug I suggest LXDE. On openbox it knows about me (although I never used those commands before so have no idea how much sense they make - uptime is correct though.)

Code:

$ uname -a
Linux rpro64.dukla.net 4.4.132-1075-rockchip-ayufan-ga83beded8524 #1 SMP Thu Jul 26 08:22:22 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux
chris@rpro64:~$ w
 18:11:35 up 19:51,  1 user,  load average: 0.47, 0.56, 0.51
USER     TTY      FROM             LOGIN@   IDLE   JCPU   PCPU WHAT
chris    tty1     -                Sun22   19:50m  2:16m  0.00s xinit /home/chris/.xinitrc -- /etc/X11/xinit/xserverrc :0 vt1 -keeptty -aut
chris@rpro64:~$ who
chris    tty1         2018-08-12 22:20
chris@rpro64:~$ uptime
 18:11:44 up 19:51,  1 user,  load average: 0.55, 0.58, 0.51
chris@rpro64:~$ lsb_release -a
No LSB modules are available.
Distributor ID:    Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:    18.04
Codename:    bionic

[lucho]

Isn't Openbox the window manager of LXDE? My amd64 system that doesn't have the bug is also with LXDE, so if it's a bug in LXDE, it must be architecture-specific.

[dukla2000]

Yup openbox is a window manager, but it will run quite happily without a desktop manager (e.g. lightdm) or a desktop environment (e.g. kde, gnome, lxde - whatever their correct category is.) Which is a lot "lighter" in terms of resources.(My basic install on top of minimal is apt-get install xorg openbox at which stage startx works.)

[lucho]

OK, but do you start "openbox" after you have logged in, or do you login after "openbox" has started? If you start "openbox" after you have logged in, then it has nothing to do with the issue. By the way, here's the tail of my "utmpdump /var/log/wtmp" dump:

Code:

[5] [00597] [tyS2] [        ] [ttyS2       ] [                    ] [0.0.0.0        ] [2018-08-14T19:10:34,428420+0000]
[5] [00605] [tty1] [        ] [tty1        ] [                    ] [0.0.0.0        ] [2018-08-14T19:10:34,431654+0000]
[6] [00597] [tyS2] [LOGIN   ] [ttyS2       ] [                    ] [0.0.0.0        ] [2018-08-14T19:10:34,428420+0000]
[6] [00605] [tty1] [LOGIN   ] [tty1        ] [                    ] [0.0.0.0        ] [2018-08-14T19:10:34,431654+0000]
[7] [02882] [ts/0] [lucho   ] [pts/0       ] [192.168.0.104       ] [192.168.0.104  ] [2018-08-15T10:28:55,740498+0000]

Unlike the name "lucho", the name "LOGIN" doesn't show any information about the user.

P.S. The processes with numbers 597 and 605 in the above dump belong to "agetty(1)". Here's a part of the "ps ax" output:

Code:

 597 ttyS2    Ss+    0:00 /sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyS2 vt220
 598 ?        Ss     0:00 /usr/sbin/lxdm-binary
 601 ?        Ss     0:00 /usr/sbin/sshd -D
 605 tty1     Ss+    0:00 /sbin/agetty -o -p -- \u --noclear tty1 linux
 607 tty7     Ssl+   1:33 /usr/lib/xorg/Xorg :0 vt07 -nolisten tcp -novtswitch -auth /var/run/lxdm/lxdm-:0.auth

[dukla2000]

OK, but do you start "openbox" after you have logged in, or do you login after "openbox" has started? If you start "openbox" after you have logged in, then it has nothing to do with the issue.

Yeah - I login, then start openbox. So ignore me