Swapped position of two displays, and now games are loading "confused"

Hello,

I just acquired a Framework 16 Laptop, and things were going great as I loaded it up with Manjaro KDE plasma on my table… I brought a DP monitor over and set the KDE settings with the DP monitor set on the left of the laptop. No problems.

Then once all my tweaks me were made and a couple games were happy, I moved the laptop over to my desk, and placed the same DP monitor on the right… updated KDE settings to this fact, and launched a game.

I’m not quite sure how to explain this, but the game launched (windowed) spanning the two monitors… I thought not much about it, and dragged it over to the right so it was fully on the DP monitor… and then things started acting weird. It was like an invisible line was drawn on my DP monitor… any part of the game window beyond that invisible line was not refreshed/redrawn (like an snapshot/picture)… nor were any mouse clicks recognized.

Basically, this is what I think is happening… possibly KDE or X11 is remembering the old position of the game on the 2560x1440 DP monitor when it was on the left. When the game loads, it looks spanned because it’s starting the game on the current left monitor (now the laptop) with a lesser 1680x1050 resolution… so when it draws the window out it spans over to the second monitor to retain the window size.

But why the “invisible line” exists where the mouse can’t click and the frames don’t update… really has me confused. It’s like it knows, this is where the right edge of 2560x1440 ends on the total screen, and because the DP monitor is on the right now (no screen beyond it), whatever happens passed this edge is no mans land.

When i launched the second game (fullscreen) it loaded on the left monitor (laptop). Hit alt-Enter to swap the game into a window, dragged it over to the right onto my DP monitor, and was unable to select anything in the game’s menu because the game’s cursor refused t move beyond the “invisible line”.

Then I got curious… what if I swapped the position of the monitors in KDE’s settings? Well, when I do that, both games launch fine, no invisible lines, and no freeze-frame areas… even if I drag the windowed game between the monitors.

Has anyone experienced something like this? If so, how did you resolve it? Are there KDE caches/files I need to be removing? I’ve unchecked the system settings => window management => window behavior => advanced => allows apps to remember the positions of their own windows, if they support it setting, but perhaps that doesn’t undo whatever was saved when the setting was checked.

Maybe i miss something, but which tool you used in the first place? nvidia xserver or a amd tool?

So KDE Monitor settings works, good for you or not?

I’m not sure what you mean by tool… but all my games are launched via steam/proton.

The laptop has an AMD iGPU and an AMD dGPU, and the DP monitor is direct connected to the dGPU. In steam, I would need to add a command line of DRI_PRIME=1 %command% to tell the dGPU to be used for the game. And as per the PRIME - ArchWiki I also installed vulkan-mesa-layers and lib32-vulkan-mesa-layers and it works well.

I am currently using X11, as Wayland brought a choppy experience to one of the games I’ve installed, and runs smooth in X11.

------- Update ------
I thought I’d test my theory about it being a setting/cache saved in my profile/account by making a new account… unchecked the “remember app window placements”, orientation defaulted to laptop on the left like I want, reduced laptop resolution to 1680x1050, ran steam, logged in, installed game, launched game, and it loaded spanning the monitors… so scrap that idea… it’s something global?

------- Update 2 -------
okay, looked back at my install/tweak notes and there was one thing I did related to SDDM/xrandr so that both the laptop and monitor would be displaying @ SDDM (pre-login to desktop); per SDDM - ArchWiki I added two lines to /usr/share/sddm/scripts/Xsetup

#!/bin/sh
# Xsetup - run as root before the login dialog appears

xrandr --output DisplayPort-1-0 --auto --primary
xrandr --output eDP-1 --right-of DisplayPort-1-0 --auto --noprimary

After I swapped the laptop to the desk and moved the DP monitor to the right of the laptop, I did update this file to…

#!/bin/sh
# Xsetup - run as root before the login dialog appears

xrandr --output DisplayPort-1-0 --mode 2560x1440 --primary
xrandr --output eDP-1 --mode 1680x1050 --left-of DisplayPort-1-0 --auto --noprimary

initially this update had --auto and was changed to use --mode once my brain realized I wanted the laptop at 1680x1050 instead of it’s default 2560x1600.

As part of troubleshooting my issue, I removed the two lines completely, but no joy.

Is it possible what I initially entered in the file was copied somewhere more permanent, like udev or systemd? I’m grasping at straws, but trying to think outside the box.

------- Update 3 -------
Just noticed as I was re-reading what I copy/pasted that the laptop xrandr command had both --mode and --auto so I corrected that, rebooted, and no joy.

#!/bin/sh
# Xsetup - run as root before the login dialog appears

xrandr --output DisplayPort-1-0 --mode 2560x1440 --primary
xrandr --output eDP-1 --mode 1680x1050 --left-of DisplayPort-1-0 --noprimary

You seem to be suffering these inconveniences due to just one game not performing to your expectations. Wayland is now the default in Manjaro KDE and is receiving the main attention from a development perspective throughout the Linux ecosystem, considering X11 is slowly being replaced.

I would suggest you follow suit and use Wayland. Instead, focus your efforts on solving the issues you’re having with that one game, whatever it may be.

That is all. Cheers.

initially when I installed Manjaro, I hadn’t noticed I defaulted to a wayland session, so I did start there… looking in pamac-gui for steam… I got interested in the steam-deckify package as I do own a steamdeck and do like the interface.

it was under this config that I saw poor performance in Dragon’s Dogma Dark Arisen. Not knowing if it was wayland or the steam-deckify package, I decided to uninstall it, install steam (runtime), and load into X11… and the game worked excellent.

So I just now booted back into a wayland session and can report that the “windowed” game that spanned two monitors, behaved normally… so that’s a positive step.

Then I launched DDDA, and it’s worse that with steam-deckify… In some attempts the video instantly froze blank/black, in some attempts I could see the cursor briefly before it froze in position with the blank screen, and in other attempts I got a notification that xwayland crashed closing the game and steam… and steam would not restart without a reboot.

So, wayland doesn’t look very promising to me, protondb lists no tinkering related to wayland specifically for DDDA, and having no experience with wayland leaves me in position of having no frame of reference to begin to start troubleshooting.

The only additional thing I can recall about uninstalling steam-deckify is that it didn’t go cleanly…

  • it left some of the session files it made in /usr/share/wayland-sessions that I removed manually, and
  • it left behind os-session-select that I removed via pamac-gui

True point about the main attention to wayland, but it still has more bugs or not?
I think we are at a point, where the playball is in the middle of the field somewhere and if you chose X11 or Wayland depends on the individual user situation right now.

@Daniel-I
I never use Dual Monitor function under Linux, i have no real experience that i can share with you.

It’s an unfortunate time, really: On the one hand, we have X11 with existing bugs that in many cases have existed for years; and now, will likely never get the attention needed due to the ‘overnight success’ (a decade in the making) of Wayland.

On the other hand, with Wayland gaining so much traction (fueled in part by the Red Hat decision to dump X11) the interest and enthusiasm for Wayland is expanding greatly, and issues are inevitable as devs and users alike begin playing with this new toy.

There has to be a transition period, much as you suggest; unfortunately for some it’s already started as development in general favours Wayand; and, with respect X11, the care factor seems low in comparison.

This leaves dependent software makers in limbo to some extent; users generally confused and annoyed; and the ballpark gaining disgruntled patronage, while distro-hopping probably reaches an all-time high among the clueless. :kangaroo:

:end-mini-rant

1 Like

But you say this with the background information for a AMD User like @Daniel-I?
Because AMD supports Wayland better than Nvidia, right now.

@Daniel-I
Sorry about a little Off-Topic, i don’t response after this dialog :slight_smile:

You’re experiencing a strange issue with your Manjaro KDE setup and a DP monitor. When the monitor is on the right, games launched in windowed mode have an “invisible line” where the display freezes and mouse clicks don’t register. This seems to be related to KDE remembering the window position from when the monitor was on the left (with a different resolution).

Swapping the monitor positions in KDE settings fixes the problem. Some users have reported success with disabling the setting “allows apps to remember the positions of their own windows” but it might not clear the saved data in your case.

Here’s what you can try:

  1. Keep the monitor positions swapped in KDE settings if it works.
  2. Try disabling and then re-enabling the “allows apps to remember…” setting.
  3. Search online for solutions related to KDE window management and specific game titles you’re playing.

No, I say this as a reponse to your comment. :wink:

I use amdgpu and will never use nvidia, if it can be avoided; but that’s even further off-topic, so I digress.

Thank you for the suggestions, but I was hoping I ruled out a cached/saved setting when I created a test user account (fresh profile), ensured that “remember positions” setting was unchecked right away, then launched steam, re-downloaded the game on the new account, launched it, and watched it behave exact;y the same on the fresh account.

I did however discover another scenario that behaves properly…

  1. Moved the DP cable to a side DP port (one driven by the iGPU)
  2. Set KDE settings display orientation so the laptop was on the left (mouse flows properly between displays; matching the physical layout)
  3. rem’d my extra lines in /usr/share/sddm/scripts/Xsetup since I knew they were not needed with the monitor on iGPU … that SDDM would load across both monitors without it.
  4. rebooted
  5. launched the games and they behaved properly?! good, but confused why
  6. got curious and thought I’d reverse the orientation in KDE settings… no problem

This scenario kinda suggests that when the dGPU port is used to drive a display, it wants to be on the left? And that’s basically the same as scenario one, except set to the left in the KDE settings with the monitor plugged directly to the dGPU.

Not sure if this is a workaround or a solution, but proper mousing between the displays is preferred; accepting the possibility that telling the game to use the dGPU while the monitor is connected to the iGPU may come with a 10% performance cost.

------- Update -------
I think I figured out another important detail… some steam games have a native linux version whereas many require PROTON to allow windows games to run on Linux. The two games focused on in my writings were not Linux native games, so PROTON / VULKAN / etc is involved. Launched a 3rd windowed game that has a Linux native version, and it launched/behaved properly.

I realized that what I said above was true for an X11 session and that I hadn’t launched a wayland session to see if it helped there are not as well… short story… it did!

  1. Keeping the DP connected to the side (iGPU) DP module, I logged out of my X11 session and logged into a wayland session
  2. Launched DDDA and I loaded with both audio and images… no more blank/black screen! I never went passed the title screen so I can’t comment on how well the game played, but this was positive progress

The other thing I can share is that when the DP module was plugged directly to the dGPU and the game loaded blank/black, there was a lot of kwin_wayland and kernel drm entries spamming journalctl

journalctl --since "2024-04-03 01:01:44" --until "2024-04-03 01:01:55" >> ~/DDDA-Wayland-dGPU-port.log
Apr 03 01:01:46 AMDRyzen7040 steam-runtime[439471]: /bin/sh\0-c\0DRI_PRIME=1 /home/daniel/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=367500 -- /home/daniel/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/home/daniel/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper'/_v2-entry-point --verb=waitforexitandrun -- '/home/daniel/.local/share/Steam/steamapps/common/Proton - Experimental'/proton waitforexitandrun  '/home/daniel/.local/share/Steam/steamapps/common/DDDA/DDDA.exe'\0
Apr 03 01:01:46 AMDRyzen7040 steam-runtime[451848]: ERROR: ld.so: object '/home/daniel/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Apr 03 01:01:46 AMDRyzen7040 steam-runtime[451848]: ERROR: ld.so: object '/home/daniel/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
Apr 03 01:01:46 AMDRyzen7040 kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input73
Apr 03 01:01:46 AMDRyzen7040 steam-runtime[451849]: ERROR: ld.so: object '/home/daniel/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Apr 03 01:01:46 AMDRyzen7040 steam-runtime[451849]: ERROR: ld.so: object '/home/daniel/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Apr 03 01:01:46 AMDRyzen7040 steam-runtime[451853]: ERROR: ld.so: object '/home/daniel/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Apr 03 01:01:48 AMDRyzen7040 steam-runtime[452033]: fsync: up and running.
Apr 03 01:01:51 AMDRyzen7040 steam-runtime[452031]: Setting breakpad minidump AppID = 367500
Apr 03 01:01:51 AMDRyzen7040 steam-runtime[452031]: Steam_SetMinidumpSteamID:  Caching Steam ID:  76561197996595002 [API loaded no]
Apr 03 01:01:52 AMDRyzen7040 steam-runtime[452203]: Fossilize INFO: Overriding serialization path: "/home/daniel/.local/share/Steam/steamapps/shadercache/367500/fozpipelinesv6/steamapprun_pipeline_cache".
Apr 03 01:01:53 AMDRyzen7040 steam-runtime[439471]: GameOverlay: started '/home/daniel/.local/share/Steam/ubuntu12_32/gameoverlayui' (pid 452361) for game process 452203
Apr 03 01:01:53 AMDRyzen7040 steam-runtime[452361]: 04/03 01:01:53 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20240329170910)/tid(452361)
Apr 03 01:01:53 AMDRyzen7040 steam-runtime[452361]: 04/03 01:01:53 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(452361)
Apr 03 01:01:53 AMDRyzen7040 steam-runtime[452361]: minidumps folder is set to /tmp/dumps
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Atomic commit failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kwin_wayland[438763]: kwin_wayland_drm: Presentation failed! Invalid argument
Apr 03 01:01:54 AMDRyzen7040 kernel: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -22

There was no such journal spam with the DP monitor connected to the side DP port. So the issue seems specific to trying to use the dGPU port.

Hopefully later today I’ll have time to see how well DDDA runs under the wayland session… successfully loading and presenting visuals is a great start.