Window "behind" mosue cursor and resizing makes window black on multi monitor setup

Ask Fedora
1

I have a problem in Fedora 43.
It feels like when trying to interact with the windows of the program, the window is “behind” and therefore doesn’t interact. Also, when I resize, it draws a black border.
Currently only experiencing it on REAPER, when I discover the issue on another software in my current setup, I’ll add it here.

  • It has nothing to do with the program version; the same program works on my Laptop, also running Fedora
  • It has nothing to do with GNOME Extensions
  • The same exact issue happend to me when I upgraded from Fedora 42 to Fedora 43 Beta. After that, I thought it was due to the Beta being unstable. Then I reintalled and used Fedora 42. Now, I upgraded to Fedora 43 and the issue is back. I really would like to learn what the cause is
  • The same exact software with the same exact version also worked on my computer when it was running Fedora 42. After the upgrade, it is unusable due to the issues I described.
  • It’s currently happening in REAPER (reaper.fm) but it IS a Fedora issue so I thought it would be valid to post it here, even though it is a proprietary software.
    Screenshot From 2025-12-03 16-44-23
    Screenshot From 2025-12-03 16-44-231435×1004 81.1 KB
  • The issue is gone when I disable my additional monitors via the GNOME Display Settings. When I only have a single monitor setup, the issue is gone.
2

I would guess it is a problem with the video driver. Can you work around the problem by upgrading or downgrading your video driver or the Fedora Linux kernel?

3

May you help me? I don’t know how to do this. :slight_smile:

4

The easiest thing to try first would be to boot into a previous version of the Linux kernel.

Use uname -r to see what version of the Linux kernel you are currently running.

Use rpm -q kernel to see what kernels are available on your system.

Reboot your PC and hold down the Shift key to (hopefully) summon the boot menu. You should be able to pick an older kernel from your boot menu and then test things to see if they are working again.

5

I did this (uname -r now outputs “6.17.7-200.fc42.x86_64”, which is an older one) and it didn’t fix it.

6

I guess it is time to start looking for some sort of error message in a log somewhere then.

Can you launch your GUI application from a terminal window? Doing so will sometimes reveal the status/error messages that are being reported by the software.

Also, what video driver are you using? If you can share the output from the following command, that would be helpful.

lspci |  grep -i -E 'vga' | cut -b1-7 | xargs -i lspci -vnnks {}
7
  1. The output for the GUI was not very helpful
  2. Here is the output of the command you sent me:

0b:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] [1002:73df] (rev c5) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:05cb]
Flags: bus master, fast devsel, latency 0, IRQ 112, IOMMU group 18
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at e0000000 (64-bit, prefetchable) [size=2M]
I/O ports at e000 [size=256]
Memory at fc800000 (32-bit, non-prefetchable) [size=1M]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities:
Kernel driver in use: amdgpu
Kernel modules: amdgpu

Screenshot From 2025-12-03 17-25-34
Screenshot From 2025-12-03 17-25-341905×992 67.2 KB

8

Does the workaround reported in the following report work?

Namely:

sudo -i
echo low > /sys/class/drm/card1/device/power_dpm_force_performance_level
exit

That looked like the best match for the issue you are reporting with a quick skim, but there might be a better match if you search a little more.

You might also try leaving sudo journalctl -f running in a terminal window and then try to reproduce the problem and see if any error messages correlate with the problems.

9

Thanks your your help, but it didn’t fix it. I guess I’ll change distros