Monitor powercycling after login, renderer issues in KDE Plasma

Hey fam,

I'm sad about the KDE 5.26 update. It's screwed up my renderer and now my main monitor does not work after login. I wanted to ask here (i know it's not kde forum, but again, i figure i can't be the only one with the issue and someone's bound to have tried something) before I leap here about downgrading back to 5.25. I already tried a snapshot before my last garuda-update, and it did not restore functionality. I didn't expect it to, but i still wanted to try.

I did search the forum here, arch wiki and forums. I'll be honest i need someone to hold my hand because I have a deadline to meet by monday, so i just need to be rescued at this point... I shouldn't have run an update when i knew a new KDE Plasma was launching... :person_facepalming:

Will this work to downgrade? Should i be trying something different?:

pacman -U /var/cache/pacman/pkg/plasma-*5.25.5*.pkg.tar.zst /var/cache/pacman/pkg/kdeplasma-addons-5.25.5-1-x86_64.pkg.tar.zst /var/cache/pacman/pkg/kde*5.25.5*.pkg.tar.zst
garuda-inxi
ā•­ā”€[email protected] in /var/cache/pacman/pkgšŸ”’ took 85ms
ā•°ā”€Ī» garuda-inxi                                                                                       (base)
System:
Kernel: 6.0.1-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f6cccf9c-8580-435e-8f33-927e3e31bb2d rw [email protected]
quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
resume=UUID=2e9cba84-8fd3-4884-995e-6ac1c54716ad loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.26.0 tk: Qt v: 5.15.6 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF
serial: <superuser required>
Mobo: Gigabyte model: X570 AORUS ELITE v: x.x
serial: <superuser required> UEFI: American Megatrends LLC. v: F34
date: 06/10/2021
Battery:
ID-1: hidpp_battery_0 charge: 61% condition: N/A volts: 3.9 min: N/A
model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse type: N/A
serial: <filter> status: discharging
CPU:
Info: model: AMD Ryzen 9 3950X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache:
L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB
L3: 64 MiB desc: 4x16 MiB
Speed (MHz): avg: 3502 high: 3593 min/max: 2200/4761 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3500 2: 3500
3: 3500 4: 3500 5: 3500 6: 3500 7: 3593 8: 3500 9: 3500 10: 3500 11: 3500
12: 3500 13: 3500 14: 3500 15: 3500 16: 3500 17: 3500 18: 3500 19: 3500
20: 3500 21: 3500 22: 3500 23: 3500 24: 3500 25: 3500 26: 3500 27: 3500
28: 3500 29: 3500 30: 3500 31: 3500 32: 3500 bogomips: 223572
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
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 enabled with STIBP
protection
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:
always-on, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: Micro-Star MSI
driver: nvidia v: 520.56.06 alternate: nouveau,nvidia_drm non-free: 515.xx+
status: current (as of 2022-10) arch: Turing code: TUxxx
process: TSMC 12nm built: 2018-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 16
link-max: gen: 3 speed: 8 GT/s bus-ID: 0a:00.0 chip-ID: 10de:1e84
class-ID: 0300
Device-2: Focusrite-Novation Scarlett 2i2 Camera type: USB
driver: snd-usb-audio bus-ID: 7-2:2 chip-ID: 1235:8210 class-ID: 0102
serial: <filter>
Device-3: Logitech C922 Pro Stream Webcam type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 7-3.3:7 chip-ID: 046d:085c
class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 107 s-size: 608x342mm (23.94x13.46")
s-diag: 698mm (27.46")
Monitor-1: DP-0 pos: primary res: 2560x1440 dpi: 109
size: 598x336mm (23.54x13.23") diag: 686mm (27.01") modes: N/A
Monitor-2: DP-2 size-res: N/A modes: N/A
OpenGL: renderer: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA
520.56.06 direct render: Yes
Audio:
Device-1: YUAN High-Tech Development vendor: Corsair Memory driver: N/A
pcie: bus-ID: 7-2:2 gen: 1 chip-ID: 1235:8210 class-ID: 0102
speed: 2.5 GT/s serial: <filter> lanes: 1 bus-ID: 06:00.0
chip-ID: 12ab:0380 class-ID: 0480
Device-2: NVIDIA TU104 HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 0a:00.1 chip-ID: 10de:10f8 class-ID: 0403
Device-3: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-4: Focusrite-Novation Scarlett 2i2 Camera type: USB
driver: snd-usb-audio
Device-5: Logitech C922 Pro Stream Webcam type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 7-3.3:7 chip-ID: 046d:085c
class-ID: 0102 serial: <filter>
Device-6: Texas Instruments ATH-G1WL type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 7-3.4:8 chip-ID: 0451:16ba
class-ID: 0300 serial: <filter>
Sound API: ALSA v: k6.0.1-zen2-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.59 running: yes
Network:
Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: TP-Link UB500 Adapter type: USB driver: btusb v: 0.8
bus-ID: 7-4:4 chip-ID: 2357:0604 class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 4.57 TiB used: 905.48 GiB (19.3%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: SanDisk model: ADATA SX6000PNP
size: 953.87 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> rev: V9002s85
temp: 35.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital
model: WDS100T1XHE-00AFY0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 614600WD temp: 40.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 4B6Q scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD20EARX-00ZUDB0 size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: 0A80 scheme: GPT
Partition:
ID-1: / raw-size: 896.73 GiB size: 896.73 GiB (100.00%) used: 419.57 GiB
(46.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 592 KiB
(0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 896.73 GiB size: 896.73 GiB (100.00%) used: 419.57
GiB (46.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 896.73 GiB size: 896.73 GiB (100.00%) used: 419.57
GiB (46.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 896.73 GiB size: 896.73 GiB (100.00%) used: 419.57
GiB (46.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.28 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 34.49 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 42.2 C mobo: 31.0 C gpu: nvidia temp: 35 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 24%
Info:
Processes: 499 Uptime: 16m wakeups: 2 Memory: 31.28 GiB used: 3.91 GiB
(12.5%) Init: systemd v: 251 default: graphical tool: systemctl
Compilers: gcc: 12.2.0 alt: 11 clang: 14.0.6 Packages: pm: pacman
pkgs: 2530 libs: 564 tools: octopi,pamac,paru Shell: fish v: 3.5.1
default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.22
Garuda (2.6.8-1):
System install date:     2022-01-22
Last full system update: 2022-10-15
Is partially upgraded:   No
Relevant software:       NetworkManager
Windows dual boot:       Probably (Run as root to verify)
Snapshots:               Snapper
Failed units:

I forgot to put in some helpful info:

Monitor that's not working: ASUS VG27A on DisplayPort

The command i ran, i ran again after rebooting to show the packages it changed...

ā•­ā”€[email protected] in ~ via ī‰– v11.0.16.1
ā•°ā”€Ī» sudo pacman -U /var/cache/pacman/pkg/plasma-*5.25.5-1*.pkg.tar.zst /var/cache/pacman/pkg/kde*5.25.5-1*.pkg.tar.zst
[sudo] password for meredith:
loading packages...
warning: plasma-browser-integration-5.25.5-1 is up to date -- reinstalling
warning: plasma-desktop-5.25.5-1 is up to date -- reinstalling
warning: plasma-disks-5.25.5-1 is up to date -- reinstalling
warning: plasma-firewall-5.25.5-1 is up to date -- reinstalling
warning: plasma-integration-5.25.5-1 is up to date -- reinstalling
warning: plasma-nm-5.25.5-1 is up to date -- reinstalling
warning: plasma-pa-5.25.5-1 is up to date -- reinstalling
warning: plasma-systemmonitor-5.25.5-1 is up to date -- reinstalling
warning: plasma-thunderbolt-5.25.5-1 is up to date -- reinstalling
warning: plasma-vault-5.25.5-1 is up to date -- reinstalling
warning: plasma-workspace-wallpapers-5.25.5-1 is up to date -- reinstalling
warning: kde-cli-tools-5.25.5-1 is up to date -- reinstalling
warning: kde-gtk-config-5.25.5-1 is up to date -- reinstalling
warning: kdecoration-5.25.5-1 is up to date -- reinstalling
warning: kdeplasma-addons-5.25.5-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (15) kde-cli-tools-5.25.5-1  kde-gtk-config-5.25.5-1  kdecoration-5.25.5-1
kdeplasma-addons-5.25.5-1  plasma-browser-integration-5.25.5-1  plasma-desktop-5.25.5-1
plasma-disks-5.25.5-1  plasma-firewall-5.25.5-1  plasma-integration-5.25.5-1
plasma-nm-5.25.5-1  plasma-pa-5.25.5-1  plasma-systemmonitor-5.25.5-1
plasma-thunderbolt-5.25.5-1  plasma-vault-5.25.5-1  plasma-workspace-wallpapers-5.25.5-1

Total Installed Size:  115.78 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n]

did not work. I was hoping plasma-desktop was the ticket.... sad.

I think we need some more information here since its completely unclear why the display doesn't work :eyes:
sudo dmesg & journalctl -xe might be helpful.

Was the kernel also updated and did you try other kernels such as linux-lts yet?

1 Like

i didn't try LTS kernel (that was my planned next step after downgrading zen), but i did try downgrading zen kernel, which wouldn't boot. So i probably did it wrong. Then tried snapper again which allowed me to boot. While i was booting into my image before updating 2022.10.10, i got an hdmi cable to try it out...

The hdmi input worked fine, but then while i had my monitor working with HDMI, it suddenly detected 3 displays, (2 of them were the monitor that isn't working), so i switched to display port with crossed fingers, and it was working.

WHYYYYY??????

So i don't have time to figure this out since i have a looming deadline, but i'm posting my logs in case anyone else has time to comb them. I certainly wouldn't expect you too, but i realize if anyone has time it may benefit other users. I'll post my quick solution, and mark the thread as solved.

journalctl -xe
dmesg

2 Likes

Can't tell you why this worked, but it did.

  1. hook up both HDMI and DisplayPort, switch monitor to HDMI
  2. open "Configure Display Settings" gui (both inputs should show up)
  3. switch monitor to display port
3 Likes

Sounds like a very weird bug, good to know you got it solved though! :slight_smile:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.