https://bugs.winehq.org/show_bug.cgi?id=56408
Bug ID: 56408 Summary: Wine not running on an Asus Prime Product: Wine Version: 9.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: edward.leuf@gmail.com Distribution: ---
It would seem Wine is not a fan of an Asus Prime H610M-A motherboard. I tried to run it under Ubuntu 22.04 but no windows would show up. I was in the forums asking for help but did not get anything fixed. I was noticing other things I was not comfortable with under Ubuntu so after a long while I decided to go for a simpler dist of Debian 12. I have reinstalled the nvidia drivers and many other programs, then installed wine staging from the official WineHQ instructions, and I had the same problems.
What was concluded is that Wine somehow finds two types of monitors and tries to draw a window on the wrong one. First it add_monitor 0 (0,0)-(1024,768) (0,0)-(1024,768), then it add_monitor 0 (0,0)-(1920,1080) (0,24)-(1920,1056), then deduces the dimensions for a window of (0,0) - (0,0), finally saying no driver could be loaded to create a window.
Any and all logs and discussion can be found in this forum post: https://forum.winehq.org/viewtopic.php?t=38168
https://bugs.winehq.org/show_bug.cgi?id=56408
Edward edward.leuf@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|9.3 |9.4
https://bugs.winehq.org/show_bug.cgi?id=56408
Edward edward.leuf@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|9.4 |9.6
https://bugs.winehq.org/show_bug.cgi?id=56408
--- Comment #1 from Edward edward.leuf@gmail.com --- Upon looking around for answers, I decided to do the heinous thing and run "sudo winecfg" and it did not error out! I got a GUI! This makes me think this might not be so much a hardware problem but more of a permissions problem. I have noticed other permission problems now and again. Has the new update to Ubuntu 22 or Debian 12 added too much security? What is it that wine needs that the system is not granting?
The .wine folder is on an ext4 filesystem (being home), the folder and subfolders belong to me, and the fstab options are "default".
https://bugs.winehq.org/show_bug.cgi?id=56408
Edward edward.leuf@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Edward edward.leuf@gmail.com --- OK! After a lot of this way and that way, I figured out the problem. For some reason my .fonts folder had duplicates in it - the unsorted in its root, and sorted inside a subfolder called Library - and wine was trying to cache it all. I know this because when I "removed" the .fonts folder wine started up very quickly (GUI and everything). When I put it back and took out the Library folder wine started up with a bit of a delay. Putting back the Library folder and removing the unsorted fonts wine started up with a slightly less delay.
Now I am wondering if there is a possibility for wine to have a -switch to prevent it from pre-loading the .fonts, or dig into the program being run to get exactly what fonts it needs and only load those from the .fonts folder?
https://bugs.winehq.org/show_bug.cgi?id=56408
--- Comment #3 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=56408
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Austin English austinenglish@gmail.com --- Actually closing.
-
WineHQ Bugzilla