Hi there,

now I have pure bug report:

done apt update + apt ugprade, GUI frozen, even no SSH, about an hour later (I was outside my house) (probably) restarted but up to multiuser, no GUI at all.

Howeve I CAN log over SSH, sthe issue "startx", but ONLY as ROOT. (much indesired, as ex web browser should never be started as root).

I can enable remote X in /etc/X11/xinit/xserverrc , then start remote X session.

Also "init 5" attempts to start X, but crashes.

 

How to diagnose and repair?

 

Laurent

 Oooops, 5 days and no one has idea?

On 4/9/2022 at 10:23 AM, laurentppol said:

Armbianmonitor:

http://ix.io/3UH5

Hi there,

now I have pure bug report:

done apt update + apt ugprade, GUI frozen, even no SSH, about an hour later (I was outside my house) (probably) restarted but up to multiuser, no GUI at all.

Howeve I CAN log over SSH, sthe issue "startx", but ONLY as ROOT. (much indesired, as ex web browser should never be started as root).

I can enable remote X in /etc/X11/xinit/xserverrc , then start remote X session.

Also "init 5" attempts to start X, but crashes.

 

How to diagnose and repair?

 

Laurent

 

There's a service called lightdm that you'll need to look at.   It launches X and the GUI login.

 

Hope that helps

I can see it fails to start.   Will look on this.

But now I have another question (want to ask before test: how to wake-up OPi4? ether-wake? As it does not have "power" button.

 

And for lightdm:

 

Quote

root@orangepi4:~# systemctl status lightdm.service
● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset:
   Active: failed (Result: exit-code) since Thu 2022-05-19 12:08:26 CEST; 59s ag
     Docs: man:lightdm(1)
  Process: 15661 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manag
  Process: 15663 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
 Main PID: 15663 (code=exited, status=1/FAILURE)

maj 19 12:08:26 orangepi4 systemd[1]: lightdm.service: Service RestartSec=100ms
maj 19 12:08:26 orangepi4 systemd[1]: lightdm.service: Scheduled restart job, re
maj 19 12:08:26 orangepi4 systemd[1]: Stopped Light Display Manager.
maj 19 12:08:26 orangepi4 systemd[1]: lightdm.service: Start request repeated to
maj 19 12:08:26 orangepi4 systemd[1]: lightdm.service: Failed with result 'exit-
maj 19 12:08:26 orangepi4 systemd[1]: Failed to start Light Display Manager.
maj 19 12:08:26 orangepi4 systemd[1]: lightdm.service: Triggering OnFailure= dep
root@orangepi4:~#

Quote

root@orangepi4:~# ls -l /etc/X11/default-display-manager
-rw-r--r-- 1 root root 18 cze 18  2021 /etc/X11/default-display-manager
root@orangepi4:~# cat /etc/X11/default-display-manager
/usr/sbin/lightdm
root@orangepi4:~#

 

What does in mean?

And for wake-up on LAN ether-wake didn't work.

Here is output from systemctl status:

 

root@orangepi4:~# systemctl status lightdm.service | more
● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset:
 enabled)
   Active: failed (Result: exit-code) since Fri 2022-06-10 06:00:37 CEST; 3h 2mi
n ago
     Docs: man:lightdm(1)
  Process: 2440 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manage
r 2>/dev/null)" = "/usr/sbin/lightdm" ] (code=exited, status=0/SUCCESS)
  Process: 2443 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
 Main PID: 2443 (code=exited, status=1/FAILURE)

cze 10 06:00:37 orangepi4 systemd[1]: lightdm.service: Service RestartSec=100ms 
expired, scheduling restart.
cze 10 06:00:37 orangepi4 systemd[1]: lightdm.service: Scheduled restart job, re
start counter is at 5.
cze 10 06:00:37 orangepi4 systemd[1]: Stopped Light Display Manager.
cze 10 06:00:37 orangepi4 systemd[1]: lightdm.service: Start request repeated to
o quickly.
cze 10 06:00:37 orangepi4 systemd[1]: lightdm.service: Failed with result 'exit-
code'.
cze 10 06:00:37 orangepi4 systemd[1]: Failed to start Light Display Manager.
cze 10 06:00:37 orangepi4 systemd[1]: lightdm.service: Triggering OnFailure= dep
endencies.
root@orangepi4:~# 

 

What should I look for?

 

Found this in logs:

 

root@orangepi4:~# tail -50 /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=2443
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf
[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:*], please update this configuration
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/10-slick-greeter.conf
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/11-armbian.conf
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG:   [LightDM] contains unknown option xserver-allow-tcp
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.04s] DEBUG: Monitoring logind for seats
[+0.04s] DEBUG: New seat added from logind: seat0
[+0.04s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.04s] DEBUG: Seat seat0: Starting
[+0.04s] DEBUG: Seat seat0: Creating greeter session
[+0.04s] DEBUG: Seat seat0: Failed to find session configuration slick-greeter
[+0.04s] DEBUG: Seat seat0: Failed to create greeter session
[+0.04s] DEBUG: Failed to start seat: seat0
root@orangepi4:~# 

 

[+0.00s] DEBUG:   [LightDM] contains unknown option xserver-allow-tcp

 

or this:

 

[+0.00s] DEBUG:   [SeatDefaults] is now called [Seat:*], please update this configuration

 

There is no [ERROR] only [DEBBUG].

 

Any ideas?