Graphical glitches when using AUI in KiCad/PrusaSlicer (Issue #26024)
VZ
vadz created an issue (wxWidgets/wxWidgets#26024)KiCad 9.0 on Ubuntu 25.10 is affected as well, see https://discourse.ubuntu.com/t/ubuntu-25-10-wayland-related-temporary-but-significant-trouble-with-kicad/70327/13
Originally posted by @pvantrap in #23906
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Amos Blanton
lightnin left a comment (wxWidgets/wxWidgets#26024)Issue described in Prusaslicer repository: prusa3d/PrusaSlicer#14956
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26024)See other relevant comments from the original issue:
- KiCad bug
- PrusaSlicer also affected
- Sample code which can apparently be used to reproduce the problem under Ubuntu 25.10 but which worked under 25.04.
- Another affected project.
- Last but not least, many comments, e.g. this one and that one mention that the problem only appears when multiple monitors are connected.
The last point is really concerning, as it really shouldn't matter how many monitors are connected, especially as long as only a single one is being used by the application.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26024)Something that is still not clear to me: does this happen when using Wayland, X11 or both?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Amos Blanton
lightnin left a comment (wxWidgets/wxWidgets#26024)Something that is still not clear to me: does this happen when using Wayland, X11 or both?
I believe I'm on Wayland, as I think that is the default for Ubuntu 25.10. It seems others have indicated seeing the problem on 25.10, and assuming they haven't done a lot of config changes, I guess we can assume they are on wayland too.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
pvantrap
pvantrap left a comment (wxWidgets/wxWidgets#26024)Thanks @vadz and sorry for reporting in the wrong issue, as I said I got directed there from one of the already existing issues such as https://gitlab.com/kicad/code/kicad/-/issues/22154 and https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2130248
Anyhow, the Kicad issues are indeed Gnome Wayland only, switching to X11 (e.g. KDE Plasma) fixes the issue on Ubuntu 2025.10. I think this is a regression from Ubuntu 2025.04 because I did not experience it there but maybe I was using Gnome with X11 on that version, I can't remember. If someone has still Ubuntu 2025.04 I would be great to test this to see if this is indeed a regression or not.
As discussed in the other topic, having a single monitor connected on Wayland also fixes the issue - reported by multiple users.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
PlumpCat19
PlumpCat19 left a comment (wxWidgets/wxWidgets#26024)Thanks @vadz and sorry for reporting in the wrong issue, as I said I got directed there from one of the already existing issues such as https://gitlab.com/kicad/code/kicad/-/issues/22154 and https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2130248
Anyhow, the Kicad issues are indeed Gnome Wayland only, switching to X11 (e.g. KDE Plasma) fixes the issue on Ubuntu 2025.10. I think this is a regression from Ubuntu 2025.04 because I did not experience it there but maybe I was using Gnome with X11 on that version, I can't remember. If someone has still Ubuntu 2025.04 I would be great to test this to see if this is indeed a regression or not.
As discussed in the other topic, having a single monitor connected on Wayland also fixes the issue - reported by multiple users.
I can confirm this issue is not present in Ubuntu 25.04 as I switched back when I encountered this error. I am using wayland. PrusaSlicer and KiCAD both work as expected using wayland under Ubuntu 25.04
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26024)Does anybody know if this issue also happens under distributions other than Ubuntu 25.10/Mutter 49? If it only happens with this version of this compositor it would strengthen the hypothesis that it's a bug in it, specifically (not that it would help us much...).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
pvantrap
pvantrap left a comment (wxWidgets/wxWidgets#26024)Does anybody know if this issue also happens under distributions other than Ubuntu 25.10/Mutter 49? If it only happens with this version of this compositor it would strengthen the hypothesis that it's a bug in it, specifically (not that it would help us much...).
I will try tomorrow (don't have access to that machine now) with KWin using KDE Plasma and wayland to see if indeed it can be attributed to Mutter only.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
emacnabber
emacnabber left a comment (wxWidgets/wxWidgets#26024)I am seeing this issue on Fedora 43 running Gnome 49 on a Framework 13 laptop. As with others, I am only seeing issues with a second monitor attached.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26024)This is still using Mutter 49. I'd like to eliminate the possibility that it's "just" a bug in it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
iambighead
iambighead left a comment (wxWidgets/wxWidgets#26024)I can reproduce the issue (when using dual monitor) on manjaro distro, gnome-shell/mutter version 49.2.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
pvantrap
pvantrap left a comment (wxWidgets/wxWidgets#26024)I cannot reproduce on KDE Plasma 6.4.5 (still Ubuntu 2025.10 with KiCad 9.0.6 with wxWidgets 3.2.8) using KWin compositor and Wayland. So it does really seem to be a Mutter-only bug..
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Marc Kolly
@pvantrap can you confirm, you were trying to reproduce it with a dual monitor setup as well?
I can reproduce the bug on Ubuntu 25.10 with mutter 49.0 and dual monitors. As soon as the window is resized or moved, panes are no longer loading/stay empty in both PrusaSlic3r and KiCAD.
It also does not happen on the same system, when only one monitor is enabled.
The interesting thing, not mentioned yet: it does not appear to happen, when the additional monitors are either enabled after the session has been started/logged-in, or also if they've been disabled and then re-enabled later on. In both cases, both apps work just fine and can be moved and resized freely, without any issues in the app (so far, at least. I will test that hypothesis for the rest of the day now).
In my case, disabling my secondary screen brings me to a single monitor setup, but not sure if that's necessary, eg. on a tripple monitor setup, where disabling/disconnecting would bring it to a dual monitor setup still
pvantrap
pvantrap left a comment (wxWidgets/wxWidgets#26024)In my case, disabling my secondary screen brings me to a single monitor setup, but not sure if that's necessary, eg. on a tripple monitor setup, where disabling/disconnecting would bring it to a dual monitor setup still.
It might be, that – outside of the obvious non-issue so far, on single monitor-only setups – enabling or disabling monitors on a multi monitor setup simply restarts or changes something, that makes the bug not appear?
Indeed still my dual monitor setup - DisplayLink with evdi driver but that seems not to have any impact.
I just tried what you found out and indeed re-enabling the 2nd monitor 'fixes' the problem also in my case! Actually I can't just use Gnome Display Settings to disable my 2nd monitor, I lose all screens in that case (another Mutter bug?) but physically reconnecting that monitor's cable does the trick.
Not sure how all this is helpful @vadz . Are you able to reproduce any of this? Should we rather open an issue at https://gitlab.gnome.org/GNOME/mutter/ ? I count currently 91 open issues with the 'Monitor configuration' label..
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
VZ
vadz left a comment (wxWidgets/wxWidgets#26024)Unfortunately it really looks like the bug is in Mutter. I say "unfortunately" because this means that this bug might take a long time to be fixed (I personally stopped using Mutter because it was just unusable on a system using monitors with different DPI for a long time due to this issue, which turned out to be due to Mutter issue, in spite of the simple fix being proposed) and this also makes it very unlikely that we can work around it at wx level.
This bug should still be reported to Mutter, of course, but I'm almost sure that they won't even look at it without a simple reproducer, which will probably be difficult to provide.
I'll try adding another monitor to my Ubuntu 25.10 VM to see if I can reproduce this and maybe make one, but I'm not sure if it's going to work (i.e. fail) in this setup.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Marc Kolly
makuser left a comment (wxWidgets/wxWidgets#26024)I just tried what you found out and indeed re-enabling the 2nd monitor 'fixes' the problem also in my case!
Unfortunately, that wasn't of great endurance. I tested and wrote that a bit more than an hour ago with the second monitor re-enabled and just now started seeing some issues again, like some parts not clickable in dialogs (eg. files and folders in the file picker in PrusaSlicer), even when re-opening the dialog multiple times.
Unfortunately it really looks like the bug is in Mutter. I say "unfortunately" because this means that this bug might take a long time to be fixed
That might be, but Ubuntu 26.04, Canonicals next LTS release is somewhat around the corner, so there might be more of an incentive to get such basic things resolved, no? I don't know, I haven't worked on or with Mutter yet, to have any experience based on which I could judge about this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Marc Kolly
makuser left a comment (wxWidgets/wxWidgets#26024)Unfortunately, that wasn't of great endurance. I tested and wrote that a bit more than an hour ago with the second monitor re-enabled and just now started seeing some issues again, like some parts not clickable in dialogs (eg. files and folders in the file picker in PrusaSlicer), even when re-opening the dialog multiple times.
After checking the logs, I figured out the culprit: the lockscreen. Locking the screen and unlocking/logging in with two monitors brings it back to the original problem, where the secondary screen then has to be disabled and re-enabled once again.
So.... I forgot, that I was away for a short period in between my two posts and essentially had to unlock the automatically locked system after I returned. 🙈🤦🏻♂️
At least, thanks to debugging for this this issue, along with #23906, https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2130248 and prusa3d/PrusaSlicer#14956, I now found a reliable way to work with these two applications!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Cosik
Cosik left a comment (wxWidgets/wxWidgets#26024)Hi, I spend some time reading all topics related to this issue. I'm not sure if it is correct place but a least I will leave a sign of solution. I was able to run my slicer with those parameters:
Exec=env WEBKIT_FORCE_COMPOSITING_MODE=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 flatpak run io.github.softfever.OrcaSlicer
I'm not sure what those flags are doing but maybe it will help somehow. I tested it on my debian testing with Gnome 49 with all behaviors described in above comments.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
pvantrap
pvantrap left a comment (wxWidgets/wxWidgets#26024)I'm working on a short wx application to trigger the issue; will report back if successful. I'm going for a mouse crosshair tracker which is in my case with kicad the first or easiest to spot indication of the rendering problems.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.