You are not logged in.
I was away for two weeks for work and after updating my system today I'm having this issue occur when I have my second monitor connected. I believe I had been running on a 6.11 kernel (but maybe it was 6.12) which was updated to 6.13 today. The second monitor powers on and the backlight comes on, but I also never get a display output on it. I have the following in my journalctl logs when this issue occurs. The bold text are the lines I think are related to the issue. Though I'm using 100% scaling so I'm not sure why the gdkcursor errors are occurring.
Feb 10 17:37:20 archlinux kernel: amdgpu 0000:50:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn31_program_compbuf_size line:141
Feb 10 17:37:22 archlinux ghostty[35480]: ../gtk/gdk/wayland/gdkcursor-wayland.c:210 cursor image size (32) not an integer multiple of theme size (24)
Feb 10 17:37:30 archlinux kernel: amdgpu 0000:50:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn31_program_compbuf_size line:141
Feb 10 17:37:31 archlinux kernel: amdgpu 0000:50:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn31_program_compbuf_size line:141
Feb 10 17:37:36 archlinux kernel: amdgpu 0000:50:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn31_program_compbuf_size line:141
Feb 10 17:37:37 archlinux ghostty[35480]: ../gtk/gdk/wayland/gdkcursor-wayland.c:210 cursor image size (32) not an integer multiple of theme size (24)
Feb 10 17:37:38 archlinux sudo[39420]: john : TTY=pts/1 ; PWD=/home/john ; USER=root ; COMMAND=/usr/bin/journalctl -b
Feb 10 17:37:38 archlinux sudo[39420]: pam_unix(sudo:session): session opened for user root(uid=0) by john(uid=1000)
System info:
Operating System: Arch Linux
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.13.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 9900X 12-Core Processor
Memory: 60.4 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Graphics Driver: amdgpu
Manufacturer: ASRock
Product Name: B650M PG Riptide WiFi
This behavior is occurring in all DE and WM's I have, which are KDE Plasma (Wayland and X11), Hyprland, and Cosmic Alpha 5.1.
Last edited by Stokkolm (2025-02-10 23:04:19)
Offline
Oh, forgot to mention as well. I'm getting an error about fcitx (no idea what that is) and when I try to configure keyboard settings in KDE I get the following message:
You're currently running KDE, but KCModule for fcitx couldn't be found. The package name of this KCModule is usually kcm-fcitx5, kde-config-fcitx5, or fcitx5-configtool. Now it will open the configuration directory.
Edit: installing kcm-fcitx5 seems to have solved this, so it's likely not related.
Last edited by Stokkolm (2025-02-10 22:57:14)
Offline
Offline
That didn't resolve the issue. I am unable to take a screenshot or screen recording due to the way it's fluctuating between connected and disconnected so I took a video from my phone.
Offline
So this is all by kscreen/wayland perception - the output is never really used (and then just flickers)?
Switch the environment, run openbox on X11 (no kde stuff, notably not kscreen!), attach the output, run "xrandr -q", then enable it and immediately redraw the output list, "xrandr --output [DP-whatever] --auto; xrandr -q" then "xrandr -q"
Can you set it to a lower mode this way (xrandr --output […] --mode 1024x768"?
Finally please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
Offline
I had also tried it in Hyprland, Gnome and Cosmic Alpha 5 as well as Plasma X11, it did the same thing on all. I'll try modifying the output the way you described and report back.
Offline
Not having any experience with openbox, I booted from a Live ISO of LM/Cinnamon and experienced the same thing. I was able to verify that was definitely using x11. So, maybe it's actually a hardware limitation I'm running into with the iGPU on my Ryzen 9900x. I'll pull the Xorg log and post it anyway just in case.
Offline
Ok, so obviously from LM and not Arch, and I couldn't find a log file at the path you specified. These errors were in the ~/.xsessions.errors file though:
Gjs-Message: 03:30:34.431: JS LOG: [LookingGlass/info] Monitor Watch List updated: [0,1]
Gjs-Message: 03:30:45.271: JS LOG: [LookingGlass/info] Monitor Watch List updated: [0]
sys:1: Warning: ../../../gobject/gsignal.c:2685: instance '0x63fd376337f0' has no handler with id '8049'
Gjs-Message: 03:30:46.128: JS LOG: [LookingGlass/info] Monitor Watch List updated: [0,1]
Gjs-Message: 03:30:56.841: JS LOG: [LookingGlass/info] Monitor Watch List updated: [0]
sys:1: Warning: ../../../gobject/gsignal.c:2685: instance '0x63fd376337f0' has no handler with id '18708'
Gjs-Message: 03:30:57.701: JS LOG: [LookingGlass/info] Monitor Watch List updated: [0,1]
I'll work on figuring out openbox tomorrow and get the errors properly from my main Arch install.
Offline
The session errors are irrelevant, the xorg log will be in /var/log or ~/.local/share/xorg or in very doubt (only) in the system journal.
It btw. doesn't have to be openbox, any X11 session will do (I just suggested it as low profile alternative that won't clutter your system with dependencies)
And definitively try to set a lower resolution w/ xrandr.
So, maybe it's actually a hardware limitation I'm running into with the iGPU on my Ryzen 9900x.
… or the cable…
Offline
To close the loop on this, the issue was a failing CPU. A few days later it failed completely and wouldn't boot anymore. I ended up RMAing it with AMD and I'm back to normal. Thanks for the attempts at helping!
Offline