[Bug 48647] New: wine 5.0+ can't create Windows, "no driver" (previous versions could)
https://bugs.winehq.org/show_bug.cgi?id=48647 Bug ID: 48647 Summary: wine 5.0+ can't create Windows, "no driver" (previous versions could) Product: Wine Version: 5.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: patola(a)gmail.com Distribution: Ubuntu Created attachment 66505 --> https://bugs.winehq.org/attachment.cgi?id=66505 logs of running winecfg with wine 4.21 No graphical programs run under wine. They can't create Windows. This bug so far occured in all wine 5.0 and derivatives, from wine 5.0 stable (from repository) to Proton 5.0.2 and 5.0.3, to wine-staging 5.2, and does not occur in any wine or wine derivative numbered 4.something. My equipment: Ubuntu 18.04.4 with latest patches, kernel 5.0.0-lowlatency and sometimes 5.0.0-fmutex from Valve. NVIDIA driver 440.59, NVIDIA RTX 2070 SUPER, 32 GB RAM, using LVM on one SSD + 2 HDDs. I play a lot of games using wine, wine-staging and proton, I have libfaudio installed. PPAs: graphics-drivers, wine and faudio official PPAs. For comparison, I include the output of the latest working version of wine from the repositories, winehq-staging=4.21~bionic and the latest non-working version from repositories, winehq-staging=5.2~bionic. From the command line, I issue the following commands: -------- wine --version rm -rf ~/.wine WINEDEBUG=warn+all wineboot -u WINEDEBUG=warn+all winecfg -------- The output is stored via the "script" command, so the commands are in the log also. With wine-staging 4.21: winecfg's window appears. With wine-staging 5.2 (or 5.0, or wine-stable 5.0 etc.): no window ever appears. ---------------------- Wine staging 5.2 packages installed (via apt install --install-recommends winehq-staging): [11:23] [2200] [patola(a)risadinha patola]% dpkg -l | egrep -i 'wine|faudio' ii libfaudio0:amd64 20.02-bionic~1ppa1 amd64 XAudio sound processing reimplementation - library ii libfaudio0:i386 20.02-bionic~1ppa1 i386 XAudio sound processing reimplementation - library ii q4wine 1.3.6-2 amd64 Qt GUI for wine (WINE) ii wine-staging 5.2~bionic amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-staging-amd64 5.2~bionic amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-staging-i386:i386 5.2~bionic i386 WINE Is Not An Emulator - runs MS Windows programs ii winehq-staging 5.2~bionic amd64 WINE Is Not An Emulator - runs MS Windows programs ------------------------ wine-staging 4.21 packages installed: ii libfaudio0:amd64 20.02-bionic~1ppa1 amd64 XAudio sound processing reimplementation - library ii libfaudio0:i386 20.02-bionic~1ppa1 i386 XAudio sound processing reimplementation - library ii q4wine 1.3.6-2 amd64 Qt GUI for wine (WINE) ii wine-staging 4.21~bionic amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-staging-amd64 4.21~bionic amd64 WINE Is Not An Emulator - runs MS Windows programs ii wine-staging-i386:i386 4.21~bionic i386 WINE Is Not An Emulator - runs MS Windows programs ii winehq-staging 4.21~bionic amd64 WINE Is Not An Emulator - runs MS Windows programs ------------------------- -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #1 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- Created attachment 66506 --> https://bugs.winehq.org/attachment.cgi?id=66506 logs of trying to run winecfg with wine staging 5.2 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 Cláudio Sampaio (Patola) <patola(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|x86 |x86-64 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzhang(a)codeweavers.com --- Comment #2 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- This is weird. What filesystem are you using for your home directory? It seems that Wine can't find many of the files it needs. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #3 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- I am using ext4. These are my filesystems, all of them have plenty of free space. [15:16] [2324] [patola(a)risadinha patola]% mount -v | grep mapper /dev/mapper/ryzenvg-rootlv on / type ext4 (rw,noatime,errors=remount-ro) /dev/mapper/ryzenvg-usrlv on /usr type ext4 (rw,noatime) /dev/mapper/ryzenvg-shadercachelv on /shadercache type ext4 (rw,noatime) /dev/mapper/ryzenvg-optlv on /opt type ext4 (rw,noatime) /dev/mapper/ryzenvg-jogos2lv on /jogos2 type ext4 (rw,relatime) /dev/mapper/mijovg-tmplv on /tmp type ext4 (rw,relatime) /dev/mapper/mijovg-dadoslv on /dados type ext4 (rw,relatime) /dev/mapper/mijovg-homelv on /home type ext4 (rw,relatime) /dev/mapper/mijovg-varlv on /var type ext4 (rw,relatime) /dev/mapper/mijovg-jogoslv on /jogos type ext4 (rw,relatime) [15:16] [2325] [patola(a)risadinha patola]% df | grep mapper /dev/mapper/ryzenvg-rootlv 10255636 1239396 8475568 13% / /dev/mapper/ryzenvg-usrlv 24639824 21345240 2040884 92% /usr /dev/mapper/ryzenvg-shadercachelv 1802064 298360 1382464 18% /shadercache /dev/mapper/ryzenvg-optlv 5095040 1729920 3086592 36% /opt /dev/mapper/ryzenvg-jogos2lv 240221820 120774324 109113332 53% /jogos2 /dev/mapper/mijovg-tmplv 5095040 1442276 3374236 30% /tmp /dev/mapper/mijovg-dadoslv 78179012 39870120 34559604 54% /dados /dev/mapper/mijovg-homelv 77146884 69270212 4169328 95% /home /dev/mapper/mijovg-varlv 10255636 7868420 1867520 81% /var /dev/mapper/mijovg-jogoslv 3363773536 3187672756 34133612 99% /jogos -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #4 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- Also, I also verified that all wine* executables exist, belong to the packages and are in their right place: [15:40] [2334] [patola(a)risadinha patola]% for a in /usr/bin/wine* for> do for> ls -ld $a for> done lrwxrwxrwx 1 root root 26 nov 30 13:18 /usr/bin/wine -> /opt/wine-staging/bin/wine lrwxrwxrwx 1 root root 28 nov 30 13:18 /usr/bin/wine64 -> /opt/wine-staging/bin/wine64 lrwxrwxrwx 1 root root 38 nov 30 13:18 /usr/bin/wine64-preloader -> /opt/wine-staging/bin/wine64-preloader lrwxrwxrwx 1 root root 30 nov 30 13:18 /usr/bin/wineboot -> /opt/wine-staging/bin/wineboot lrwxrwxrwx 1 root root 31 nov 30 13:18 /usr/bin/winebuild -> /opt/wine-staging/bin/winebuild lrwxrwxrwx 1 root root 29 nov 30 13:18 /usr/bin/winecfg -> /opt/wine-staging/bin/winecfg lrwxrwxrwx 1 root root 33 nov 30 13:18 /usr/bin/wineconsole -> /opt/wine-staging/bin/wineconsole lrwxrwxrwx 1 root root 29 nov 30 13:18 /usr/bin/winecpp -> /opt/wine-staging/bin/winecpp lrwxrwxrwx 1 root root 29 nov 30 13:18 /usr/bin/winedbg -> /opt/wine-staging/bin/winedbg lrwxrwxrwx 1 root root 30 nov 30 13:18 /usr/bin/winedump -> /opt/wine-staging/bin/winedump lrwxrwxrwx 1 root root 30 nov 30 13:18 /usr/bin/winefile -> /opt/wine-staging/bin/winefile lrwxrwxrwx 1 root root 29 nov 30 13:18 /usr/bin/wineg++ -> /opt/wine-staging/bin/wineg++ lrwxrwxrwx 1 root root 29 nov 30 13:18 /usr/bin/winegcc -> /opt/wine-staging/bin/winegcc lrwxrwxrwx 1 root root 31 nov 30 13:18 /usr/bin/winemaker -> /opt/wine-staging/bin/winemaker lrwxrwxrwx 1 root root 30 nov 30 13:18 /usr/bin/winemine -> /opt/wine-staging/bin/winemine lrwxrwxrwx 1 root root 30 nov 30 13:18 /usr/bin/winepath -> /opt/wine-staging/bin/winepath lrwxrwxrwx 1 root root 36 nov 30 13:18 /usr/bin/wine-preloader -> /opt/wine-staging/bin/wine-preloader lrwxrwxrwx 1 root root 32 nov 30 13:18 /usr/bin/wineserver -> /opt/wine-staging/bin/wineserver -rwxrwxr-x 1 patola patola 826235 dez 29 12:37 /usr/bin/winetricks -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #5 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- What's the terminal output of `ls ~/.wine/drive_c/windows/system32` -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #6 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- Re-upgraded to wine-staging 5.2, removed ~/.wine, recreated it using wineboot -u, tried to run winecfg again (and it failed, as before). Then, ran the command: ls ~/.wine/drive_c/windows/system32 | pastebinit and the result is in http://paste.ubuntu.com/p/rdJxkDYHth/ -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #7 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- Just for the record, also tried with wine-devel=5.0rc1, it also fails to create a window. So the cause of failure was likely something which changed from wine 4.x series to 5.0. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #8 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- Any clue, WINEDEBUG channels or flags that I could use to diagnose the problem? After all, I DO want to use wine 5.x new features... :-/ I will also perform any test you might want me to do. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #9 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- Made a few more tests. Also tried Proton-GE-4.20, it also runs successfully, but any Proton-GE-5.x fails the same way. Changed NVIDIA drivers from 440.59 to 435.21 and rebooted, no change, the same things happen, 4.x and derivatives work and 5.x and derivatives don't. Tried to run the commands (rm -rf ~/.wine ; wineboot -u ; winecfg ) as root and as other newly created user, no change: 4.x works, 5.x doesn't. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #10 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- Performed a bisect of the wine codebase from 4.21 to 5.0-rc1 and found the patch which broke it: f2e5b8070776268912e1886d4516d7ddec6969fc is the first bad commit commit f2e5b8070776268912e1886d4516d7ddec6969fc Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Dec 12 19:19:12 2019 +0100 kernel32: Use the Get/SetComputerName functions from kernelbase. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 ba60044892e47da777fd00316aee29f5779654af 1f9766be875cf9e2e241f4a3da0a685ed617ff93 M dlls After this patch, no build of wine can create new windows (tested with winecfg). Before this patch, all builds work OK and create the winecfg window. Can you help me now? Please? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #11 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- Created attachment 66535 --> https://bugs.winehq.org/attachment.cgi?id=66535 WINEDEBUG=+seh,+delay winecfg (creates the window) This is the logfile when running a "good" build (that creates the window) from bisect. Command-line is WINEDEBUG=+seh,+delay winecfg (after removing ~/.wine) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #12 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- Created attachment 66536 --> https://bugs.winehq.org/attachment.cgi?id=66536 WINEDEBUG=+seh,+delay winecfg (can't create the window) This is the logfile for one of the "bad" builds of git bisect, wherein winecfg cannot create a window. Of course, before running that ~/.wine was removed, and the command-line is WINEDEBUG=+seh,+delay winecfg -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Regression SHA1| |f2e5b8070776268912e1886d451 | |6d7ddec6969fc -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #13 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- It's weird that f2e5b8070776268912e1886d4516d7ddec6969fc can cause this kind of damage. What's weirder is that it's only happening on your machine. This means something different on your machine triggered a bug and probably only you can find it. You can try to install Wine on your other machines if possible to find out the difference. Also, kernel 5.0.0-lowlatency usually means much less performance. It is intended for low latency media work if I remember correctly, but not for general/gaming usage. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #14 from Cláudio Sampaio (Patola) <patola(a)gmail.com> --- I found and fixed the problem in my machine, as posted in the forum: FIXED the problem based on what I read on the diffs. The problem is, I had a /etc/resolvconf/resolv.conf.d/head file which had the contents: nameserver 192.168.15.5 search patola.org As I had changed my internet, this nameserver does not work anymore, and also this domain is invalid for my intranet. Removed the file and restarted the internet, and then the window appears normally. Top -------------------- In my opinion, this is a clear regression. It is true that my internet had an invalid domain and nameserver, BUT wine should be more resilient than this, it was something *local*, and it worked before. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 bugzilla(a)ekriirke.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla(a)ekriirke.net -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #15 from bugzilla(a)ekriirke.net --- My WINE also stopped working very recently. Not even winecfg would work. However if I made a new prefix it would. My original would start and stall like so: $ winecfg 000f:err:service:process_send_command receiving command result timed out 000f:fixme:service:scmdatabase_autostart_services Auto-start service L"WineBus" failed to start: 1053 0027:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0027:err:winediag:nodrv_CreateWindow The explorer process failed to start. 0027:err:ole:apartment_createwindowifneeded CreateWindow failed with error 3 0027:err:ole:apartment_createwindowifneeded CreateWindow failed with error 0 0027:err:ole:apartment_createwindowifneeded CreateWindow failed with error 0 0009:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0009:err:winediag:nodrv_CreateWindow The explorer process failed to start. So I found the WineBus entry in system.reg [System\\CurrentControlSet\\Enum\\ROOT\\WINE\\WINEBUS] 1582966719 #time=1d5eede6f8dea64 "Class"="System" "ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}" "DeviceDesc"="Wine HID bus driver" "Driver"="{4D36E97D-E325-11CE-BFC1-08002BE10318}\\0000" "HardwareId"=hex(7):72,00,6f,00,6f,00,74,00,5c,00,77,00,69,00,6e,00,65,00,62,\ 00,75,00,73,00,00,00,00,00,00,00,00,00,46,00,61,00,69,00,6c,00,65,00,64,00,\ 20,00,74,00,6f,00,20,00,73,00,65,00 "Service"="winebus" Deleted it, and now WINE works great. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 Claude Heiland-Allen <claude(a)mathr.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |claude(a)mathr.co.uk --- Comment #16 from Claude Heiland-Allen <claude(a)mathr.co.uk> --- I experienced this (no GUI is displayed for any programs, while command line EXEs work fine). OS is Debian testing (next release is Bullseye). Packages: Working: winehq-stable 4.0.3~bullseye Not working: wine 5.0-3 wine-development 5.4-1 winehq-stable 5.0.0~bullseye Compiled from git tags: Working: wine-4.6 Not working: wine-4.7 In a Debian stable (Buster) chroot, wine 4.0-2 works. I will try to bisect to determine the commit that breaks it for me. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 Mikaël Cluseau <nwrk(a)nwrk.info> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwrk(a)nwrk.info --- Comment #17 from Mikaël Cluseau <nwrk(a)nwrk.info> --- Hi, I report the same problem under Gentoo. winecfg works with wine-staging 5.8; I didn't test it with 5.9 but other apps were working too. With 5.10, on an empty prefix winecfg starts, then if I just click Ok and try to restart on that same prefix (so freshly initialized), it fails: 00d0:err:virtual:free_ranges_remove_range range 0x10000000 - 0x10020000 is already partially mapped e: /var/tmp/portage/app-emulation/wine-staging-5.10/work/wine-5.10/dlls/ntdll/unix/virtual.c:581: free_ranges_remove_range: Assertion `range->base <= view_base && range->end >= view_end' failed. 00d8:err:virtual:free_ranges_remove_range range 0x10000000 - 0x100e0000 is already partially mapped /var/tmp/portage/app-emulation/wine-staging-5.10/work/wine-5.10/dlls/ntdll/unix/virtual.c:581: free_ranges_remove_range: Assertion `range->base <= view_base && range->end >= view_end' failed. 00c8:err:winecfg:WinMain failed to restart 64-bit L"C:\\windows\\system32\\winecfg.exe", err 1359 00c8:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 00c8:err:winediag:nodrv_CreateWindow The explorer process failed to start. Command I entered for this test: $ rm -fr $WINEPREFIX $ mkdir $WINEPREFIX $ winecfg (clic Ok) $ winecfg (fails) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #18 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- (In reply to Mikaël Cluseau from comment #17)
/var/tmp/portage/app-emulation/wine-staging-5.10/work/wine-5.10/dlls/ntdll/ unix/virtual.c:581: free_ranges_remove_range: Assertion `range->base <= view_base && range->end >= view_end' failed.
This is bug 49326 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 --- Comment #19 from Mikaël Cluseau <nwrk(a)nwrk.info> --- Thanks, yes, fixed by the referenced commit. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #20 from Alexandre Julliard <julliard(a)winehq.org> --- Most likely duplicate. *** This bug has been marked as a duplicate of bug 50084 *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48647 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #21 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Duplicate. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla