autofire372 Posted March 15 Posted March 15 (edited) On 3/13/2025 at 10:02 AM, Taku86 said: I'm using PKHeX on two machines, one with LXQt+OpenBox (running on X) and one with KDE Plasma (running on Wayland). I've never experienced this issue and I'm unable to reproduce. I've also tried to move them to different desktops, but it still works. Wine version 10.2 and .NET 9.0.2 here. Expand Might be a Wine regression, then. I just tried downgrading from .NET 9.0.3 to 9.0.2, and PKHeX was still bugged. EDIT: On second thought, downgrading wine-staging to 10.2 didn't fix the issue, either, so I dunno... EDIT #2: I just tried using KDE Plasma with Wayland in a virtual machine, and PKHeX was still broken. Maybe something is weird in my PKHeX settings... EDIT THE THIRD: Finally got PKHeX to behave correctly. I had to open winecfg and disable "Allow the window manager to control the windows" under the Graphics tab. Edited March 17 by autofire372
Taku86 Posted April 5 Author Posted April 5 On 3/15/2025 at 10:19 PM, autofire372 said: EDIT THE THIRD: Finally got PKHeX to behave correctly. I had to open winecfg and disable "Allow the window manager to control the windows" under the Graphics tab. Expand Thanks, I've added this to the OP. If anyone else can confirm this fixes the problem, that would be great. I've also tried Wine 10.3 and 10.4 recently and PKHeX crashes when launching it. I don't know if this is the case for you (and for others), but at the moment I recommend using version 10.2, which is now the recommended one in the OP. If the problem persists with the future versions of Wine I'll report the bug to the Wine devs.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now