Unusual DE behavior on startup [Solved]

[chippy52]

Code: Select all

System:    Kernel: 6.0.0-6mx-amd64 [6.0.12-1~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.0.0-6mx-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: KDE Plasma 5.20.5 wm: kwin_x11 vt: 7 dm: SDDM 
           Distro: MX-21.3_KDE_x64 Wildflower January 15  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B350M-A v: Rev X.0x serial: <filter> 
           UEFI-[Legacy]: American Megatrends v: 5603 date: 07/28/2020 
CPU:       Info: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ family: 17 (23) 
           model-id: 8 stepping: 2 microcode: 800820D cache: L2: 4 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102189 
           Speed: 1550 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1550 
           2: 1550 3: 1550 4: 1550 5: 1550 6: 2683 7: 1550 8: 1550 9: 1550 10: 1550 11: 1550 
           12: 1550 13: 1550 14: 1550 15: 1550 16: 1550 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data status: Not affected 
           Type: retbleed mitigation: untrained return thunk; SMT vulnerable 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB 
           filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050] vendor: ASUSTeK driver: nvidia v: 520.56.06 
           bus-ID: 09:00.0 chip-ID: 10de:1c81 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: kwin_x11 driver: loaded: nvidia 
           unloaded: fbdev,modesetting,nouveau,vesa alternate: nv display-ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 93 s-size: 524x292mm (20.6x11.5") 
           s-diag: 600mm (23.6") 
           Monitor-1: DVI-D-0 res: 1920x1080 hz: 60 dpi: 94 size: 521x293mm (20.5x11.5") 
           diag: 598mm (23.5") 
           OpenGL: renderer: NVIDIA GeForce GTX 1050/PCIe/SSE2 v: 4.6.0 NVIDIA 520.56.06 
           direct render: Yes 
Audio:     Device-1: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus-ID: 09:00.1 chip-ID: 10de:0fb9 class-ID: 0403 
           Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus-ID: 0b:00.3 chip-ID: 1022:1457 class-ID: 0403 
           Sound Server-1: ALSA v: k6.0.0-6mx-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
           vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel port: f000 bus-ID: 07:00.0 
           chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.14 TiB used: 461.51 GiB (39.4%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: A-Data model: SX8200PNP size: 238.47 GiB 
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: 32B2T6TA temp: 31.9 C scheme: MBR 
           ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
           block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: CC43 scheme: GPT 
Partition: ID-1: / raw-size: 215.96 GiB size: 211.51 GiB (97.94%) used: 10.38 GiB (4.9%) fs: ext4 
           dev: /dev/nvme0n1p1 maj-min: 259:1 
           ID-2: /home raw-size: 14.65 GiB size: 14.32 GiB (97.74%) used: 1.58 GiB (11.0%) 
           fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:3 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 7.86 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/nvme0n1p2 maj-min: 259:2 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: note: see --pkg apt: 2479 lib: 1405 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mx.debian.nz/mx/repo/ bullseye main non-free
           2: deb http://mx.debian.nz/mx/repo/ bullseye ahs
Info:      Processes: 338 Uptime: 1m wakeups: 1 Memory: 7.7 GiB used: 1.27 GiB (16.5%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: BIOS (legacy, CSM, MBR)

From startup the DE populates fully then after a short period the screen goes blank & the DE re-populates. This message appears ( startkde: Could not start ksmserver. Check your installation. ) Not overly concerned as system works fine.
What needs correcting.

[dolphin_oracle]

we have a hack that restarts teh X server on KDE when running via sysVinit. its the only way we've found for the sddm shutdown and reboot buttons to work while running sysVinit. Its usually very difficult to see the restart because its usually very fast, but some users report seeing it.

note this does not affect the kde buttons for reboot and shutdown, only the sddm ones.

if the sddm buttons don't concern you, you can remove sddm-modified-init package and reinstall sddm

Code: Select all

sudo apt purge sddm-modified-init && sudo apt install --reinstall sddm

or you can boot with systemd instead of sysVinit.

you can also switch display manager (lightdm for instance), but sddm has some nice integration in the KDE settings.

[chippy52]

Thanks for the reply DO. Have tried the reinstall. The DE no longer reboots, but that message still appears. While doing this I noticed the DE closes but the system will not shut down.

[chippy52]

I have decided to use systemd as my default.