April 2022 - wine-bugs

[Bug 26350] New: Dungeons demo doesn't run
by wine-bugs＠winehq.org 12 Apr '22

12 Apr '22

http://bugs.winehq.org/show_bug.cgi?id=26350 Summary: Dungeons demo doesn't run Product: Wine Version: 1.3.15 Platform: x86 URL: http://www.bigdownload.com/games/dungeons/pc/dungeons- demo/ OS/Version: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com If I use mono-2.10-1, it fails with an error that mono can't handle it: Method '<Module>:<CrtImplementationDetails>.DoDllLanguageSupportValidation ()' in assembly 'C:\Program Files\Kalypso Media\Dungeons Demo\Mogre.dll' contains native code that cannot be executed by Mono in modules loaded from byte arrays. The assembly was probably created using C++/CLI. Method '<Module>:<CrtImplementationDetails>.ThrowModuleLoadException (string,System.Exception)' in assembly 'C:\Program Files\Kalypso Media\Dungeons Demo\Mogre.dll' contains native code that cannot be executed by Mono in modules loaded from byte arrays. The assembly was probably created using C++/CLI. System.NullReferenceException: Object reference not set to an instance of an object With dotnet35, fails with: Unhandled Exception: System.MissingMethodException: Method not found: 'Void System.Runtime.GCSettings.set_LatencyMode(System.Runtime.GCLatencyMode)'. at Realmforge.MogreUtil.Application.MainApplication`3.Run() at Realmforge.Dungeons.DungeonsMain.Main(String[] args) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 16

[Bug 39699] New: WINE Crashed during setup of 'EDT for Windows'
by wine-bugs＠winehq.org 12 Apr '22

12 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=39699 Bug ID: 39699 Summary: WINE Crashed during setup of 'EDT for Windows' Product: Wine Version: 1.6-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: D.Kurtz(a)web.de Distribution: --- Created attachment 52941 --> https://bugs.winehq.org/attachment.cgi?id=52941 Saved Crashfile During running the Setup-Programm WINE crashed. I have Linux-Mint 17.2 and Wine !:1.6.2 You can get the Programm 'EDTW = EDT für Windows' at this Link: http://opg.de/download/edtw/setupedt.exe If possible please answer in German language because my english is very bad. Thanks Dietmar -- 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.

2 14

[Bug 52799] New: Can't add repository
by WineHQ Bugzilla 12 Apr '22

12 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52799 Bug ID: 52799 Summary: Can't add repository Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: slayersnet2012(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- Add Repository gives an error Message like this: Fehl:7 https://dl.winehq.org/wine-builds/ubuntu jammy/main i386 Packages Datei hat eine unerwartete Größe (4812 != 6744). Eventuell läuft gerade eine Spiegel-Synchronisierung? [IP: 151.101.114.217 443] Hashes of expected file: - Filesize:6744 [weak] - SHA512:a15c76a48f721f44fadd27eacd67513d98524685955d8cf59da3ab4d43a2916969169bb53f0e76582e6cd41e55a6294426a364bf62c4365b79669ae94bf9a515 - SHA256:6e3c6241b7a543f121a60c8e91642652113eea4e7ab898709d0e6e5a9211e765 - SHA1:f9853bd8bd6cd2361f6458911fdbcd9ba666f683 [weak] - MD5Sum:34607ca91b2aecc163babf031878cfa5 [weak] Release file created at: Sat, 09 Apr 2022 15:20:32 +0000 -- 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.

1 4

[Bug 52697] New: missing fonts in unity games
by WineHQ Bugzilla 12 Apr '22

12 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52697 Bug ID: 52697 Summary: missing fonts in unity games Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Before you ask, I've already seen some of those "install Arial/Arial Bold" 'solutions. But it's actually a bit more complicated. As a fallback font for not embedded font resources Unity is looking up Arial... Only it actually isn't. It starts with Arial name and any extra values like weight (which I suspect leads to Arial Bold - though just guessing that part), but actually assumes full font substitution is working behind the font. I assert that, cause I've run into a Japanese game that requested Arial, but expected it to have cjk glyphs. While Arial Unicode kind of worked, I'm pretty sure it was not what was originally requested. Also, Arial Unicode is suboptimal on quite a few levels. Though it might be that to start the process, a font file with font name containing 'Arial' needs to be present in drive_c/windows/fonts. One way or another, standard method of HKEY_CURRENT_USER\Software\Wow6432Node\Wine\Fonts\Replacements 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.

1 1

[Bug 52037] New: MaiDenSnow Eve trial crashes upon entering load menu
by WineHQ Bugzilla 12 Apr '22

12 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52037 Bug ID: 52037 Summary: MaiDenSnow Eve trial crashes upon entering load menu Product: Wine Version: 6.19 Hardware: x86-64 URL: https://trial.dlsite.com/doujin/RJ116000/RJ115762_tria l.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- I'm reporting against 6.19, but IIRC this predates 6.0. I have no proof that the problem stems from the code in win32u/gdiobj.c, as gdb backtraces report stack being corrupted. Yet after changing the warning in handle_entry to print handle value, I can see the handle (font) being accessed after being freed by free_gdi_handle. Also, 'all,-heap' somehow sidesteps the crash, for a price of a major slowdown. The crash is 'illegal instruction', so once again, stack corruption. To reproduce: - run the trial - pick the last option (fourth) in the menu - pick 'New Game' - go with the first option in the next menu - as the game starts, access menu (press X) and save (first option) - press F12 to quickly restart the game - back at the title screen pick 'Load Game' - ...get the crash (if at any point you get a splash screen with some text and a clock image, you need to press 'up,left,up,down,right' on the keyboard) -- 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.

1 15

[Bug 19841] New: Wolfenstein (2009): mouse cursor remains onscreen during FPS gameplay even after all menus are closed.
by wine-bugs＠winehq.org 12 Apr '22

12 Apr '22

http://bugs.winehq.org/show_bug.cgi?id=19841 Summary: Wolfenstein (2009): mouse cursor remains onscreen during FPS gameplay even after all menus are closed. Product: Wine Version: 1.1.28 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ben.r.xiao(a)gmail.com In Wolfenstein (2009), browsing the intelligence reports or upgrading weapons sometimes causes the mouse cursor to remain on screen even when the in-game menus are closed. In other words, during FPS gameplay, the cursor sits right where the crosshairs should be and does not disappear. Needless to say this is quite distracting. This cursor bug seems to appear randomly, but always after browsing an intelligence report or upgrading weapons. The only way to get rid of the cursor is to restart the game. I'll post an attachment showing this bug the next time I see it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 8

[Bug 52732] New: Garbage user-name crated with wine, not the proper user-name like in older versions.
by WineHQ Bugzilla 11 Apr '22

11 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52732 Bug ID: 52732 Summary: Garbage user-name crated with wine, not the proper user-name like in older versions. Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rencer(a)euromail.hu Distribution: --- I'm not sure exactly when (the latest 7.4 version or which previous version) this started to happen, because for a very long time I used Lutris to manage Wine-versions and my Windows programs. Because of Lutris,I don't even have Wine installed system-wide. Sadly with the newest system (Manjaro XFCE) update someting in Python is totally broken, and because of that Lutris won't work anymore, so I had to install wine from system repo. The latest version in 7.4 The problem is when I createa a new (or try to change an existing wineprefix to use this system version), the user name is not my real username that I logged in with. Now wine creates a strange garbage user name: "u@". Previously it was correct and alway created the proper user folder, with the user who logged in and run wine. Long time ago, before I started using Lutris (I'm not sure which wine version that was, around 4.x) I used command line to run wine, create prefixes, or run any Windows programs and never was this bug. Also most of the progrmas I installed with older versions and later never changed it, I think the last version that I used with Lutris is 6.something and it also don't had this user-name bug. Problem is that all programs in any existing Wine-prefixes that was created with Lutris, (with the PROPER user-name) are broken, settings are lost, saves won't find, etc.,etc.,etc. because all the settings/saves are located in the correct user-name folder and not in this new bugged garbage "@u" name. First I thouth I lost all my files, and when I checked them with file-manager, that is how I realised this strange behaviour. Copying the files to the new garbage name location in NOT working all the time, because many times programs store their settings, saved files, etc. in the registry-database, so, this bug really broke many things. -- 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.

1 13

[Bug 52598] New: Update instructions for repository key usage due to deprecation of apt-key
by WineHQ Bugzilla 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52598 Bug ID: 52598 Summary: Update instructions for repository key usage due to deprecation of apt-key Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- When using the repo, apt update produces such warning: W: https://dl.winehq.org/wine-builds/debian/dists/testing/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. >From man apt-key DEPRECATION Except for using apt-key del in maintainer scripts, the use of apt-key is deprecated. This section shows how to replace existing use of apt-key. If your existing use of apt-key add looks like this: wget -qO- https://myrepo.example/myrepo.asc | sudo apt-key add - Then you can directly replace this with (though note the recommendation below): wget -qO- https://myrepo.example/myrepo.asc | sudo tee /etc/apt/trusted.gpg.d/myrepo.asc Make sure to use the "asc" extension for ASCII armored keys and the "gpg" extension for the binary OpenPGP format (also known as "GPG key public ring"). The binary OpenPGP format works for all apt versions, while the ASCII armored format works for apt version >= 1.4. -- 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.

1 2

[Bug 46936] New: cannot upgrade to wine-devel 4.5~bionic ( libfaudio0 dependency missing)
by wine-bugs＠winehq.org 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=46936 Bug ID: 46936 Summary: cannot upgrade to wine-devel 4.5~bionic (libfaudio0 dependency missing) Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: a34ypool3voiz(a)t-online.de CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 64049 --> https://bugs.winehq.org/attachment.cgi?id=64049 log showing missing libfaudio0 deps I have installed winehq-devel 4.4 on Ubuntu 18.04 amd64. Currently version 4.5 is available, but installation fails. Trying the usual "apt-get update && apt-get upgrade && apt-get dist-upgrade" lists winehq-devel as package that has been kept back. Then I tried the following: sudo apt-get install winehq-devel wine-devel wine-devel-amd64 wine-devel-i386 -f Now two unmet dependencies are listed, which cause the failure: libfaudio0 and libfaudio0:i386. Those packages do not exist in the repository. -- 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.

2 39

[Bug 50251] New: Wrong public key from the repo prevents installation.
by WineHQ Bugzilla 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=50251 Bug ID: 50251 Summary: Wrong public key from the repo prevents installation. Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: kristijan.zic(a)gmail.com CC: dimesio(a)earthlink.net Distribution: --- Distro: Ubuntu 20.04 Followed instructions for Focal Fossa here: https://wiki.winehq.org/Ubuntu Got this error: Err:10 https://dl.winehq.org/wine-builds/ubuntu focal InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 76F1A20FF987672F Reading package lists... Done W: GPG error: https://dl.winehq.org/wine-builds/ubuntu focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 76F1A20FF987672F E: The repository 'https://dl.winehq.org/wine-builds/ubuntu focal InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -- 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.

1 5

[Bug 51920] New: Official package for Arch Linux
by WineHQ Bugzilla 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=51920 Bug ID: 51920 Summary: Official package for Arch Linux Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: joseskvolpe(a)gmail.com CC: dimesio(a)earthlink.net Distribution: ArchLinux Wine has packages on the Arch Linux multilib and community repository, they're currently maintained by Felix Yan (Wine) and Daniel Bermond (Wine-gecko & Wine-mono) Problem is... Sometimes there's a huge delay on these packages when they get an update. This is not a issue only with Wine, it occurs with many other packages that are maintained in these repositories. Wine has just released version 6.20, but these repositories are still in 6.16... If we had a official WineHQ repository for Arch Linux distributions like we got in Ubuntu and Debian, we could get updates for Wine much quicker. Additionally, having git versions on the official repository would also be neat to get nightly builds of Wine. ^w^ -- 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.

1 8

[Bug 51933] New: 404 Not Found with sudo apt update
by WineHQ Bugzilla 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=51933 Bug ID: 51933 Summary: 404 Not Found with sudo apt update Product: Wine-staging Version: 6.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: osaka.niconico(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I get the error 404 Not Found with `sudo apt update` and can't install wine. please take a look LANG=en sudo apt update Get:1 https://dl.winehq.org/wine-builds/ubuntu impish InRelease [8043 B] Get:2 https://dl.winehq.org/wine-builds/ubuntu impish/main i386 Packages [6952 B] Get:3 https://dl.winehq.org/wine-builds/ubuntu impish/main amd64 Packages [6936 B] Hit:4 http://security.ubuntu.com/ubuntu impish-security InRelease Err:5 https://dl.winehq.org/wine-builds/ubuntu impish/main all Packages 404 Not Found [IP: 151.101.74.217 443] Err:5 https://dl.winehq.org/wine-builds/ubuntu impish/main all Packages 404 Not Found [IP: 151.101.74.217 443] https://gist.github.com/GitHub30/84364cd3d749b0a1da151e845383729e lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 21.10 Release: 21.10 Codename: impish uname -a Linux impish 5.13.0-20-generic #20-Ubuntu SMP Fri Oct 15 14:21:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 151.101.230.217(cache-hnd18751-HND) on Fastly is not working host -v dl.winehq.org Trying "dl.winehq.org" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59687 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;dl.winehq.org. IN A ;; ANSWER SECTION: dl.winehq.org. 111 IN CNAME osff.map.fastly.net. osff.map.fastly.net. 1 IN A 151.101.230.217 Received 80 bytes from 127.0.0.53#53 in 8 ms Trying "osff.map.fastly.net" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57706 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;osff.map.fastly.net. IN AAAA Received 37 bytes from 127.0.0.53#53 in 20 ms Trying "osff.map.fastly.net" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63933 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;osff.map.fastly.net. IN MX Received 37 bytes from 127.0.0.53#53 in 20 ms LANG=en wget -d https://dl.winehq.org/wine-builds/ubuntu/dists/impish/main/binary-all/Packa… DEBUG output created by Wget 1.21 on linux-gnu. Reading HSTS entries from /home/indri/.wget-hsts URI encoding = 'ANSI_X3.4-1968' converted 'https://dl.winehq.org/wine-builds/ubuntu/dists/impish/main/binary-all/Packa…' (ANSI_X3.4-1968) -> 'https://dl.winehq.org/wine-builds/ubuntu/dists/impish/main/binary-all/Packa…' (UTF-8) Converted file name 'Packages' (UTF-8) -> 'Packages' (ANSI_X3.4-1968) --2021-10-27 10:34:21-- https://dl.winehq.org/wine-builds/ubuntu/dists/impish/main/binary-all/Packa… Resolving dl.winehq.org (dl.winehq.org)... 151.101.230.217 Caching dl.winehq.org => 151.101.230.217 Connecting to dl.winehq.org (dl.winehq.org)|151.101.230.217|:443... connected. Created socket 3. Releasing 0x000055bbc1fc6ac0 (new refcount 1). Initiating SSL handshake. Handshake successful; connected socket 3 to SSL handle 0x000055bbc1fc78a0 certificate: subject: CN=*.winehq.org issuer: CN=GlobalSign Atlas R3 DV TLS CA 2020,O=GlobalSign nv-sa,C=BE X509 certificate successfully verified and matches host dl.winehq.org ---request begin--- GET /wine-builds/ubuntu/dists/impish/main/binary-all/Packages HTTP/1.1 User-Agent: Wget/1.21 Accept: */* Accept-Encoding: identity Host: dl.winehq.org Connection: Keep-Alive ---request end--- HTTP request sent, awaiting response... ---response begin--- HTTP/1.1 404 Not Found Connection: keep-alive Content-Length: 196 Server: Apache Strict-Transport-Security: max-age=31536000 Cache-Control: max-age=604800 Content-Type: text/html; charset=iso-8859-1 Via: 1.1 varnish, 1.1 varnish Fastly-Debug-Digest: 71bd9e11bef6b16fa199d390a7364dfd70068eba5cc79f273515095069aaf4ec Accept-Ranges: bytes Date: Wed, 27 Oct 2021 01:34:22 GMT Age: 1076405 X-Served-By: cache-ord1730-ORD, cache-hnd18738-HND X-Cache: MISS, HIT X-Cache-Hits: 0, 6 X-Timer: S1635298462.347604,VS0,VE0 Vary: Accept-Encoding ---response end--- 404 Not Found Registered socket 3 for persistent reuse. Parsed Strict-Transport-Security max-age = 31536000, includeSubDomains = false Updated HSTS host: dl.winehq.org:443 (max-age: 31536000, includeSubdomains: false) URI content encoding = 'iso-8859-1' Skipping 196 bytes of body: [<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL was not found on this server.</p> </body></html> ] done. 2021-10-27 10:34:21 ERROR 404: Not Found. Saving HSTS entries to /home/indri/.wget-hsts But 151.101.110.217(cache-tyo11944-TYO) or 151.101.74.217(cache-nrt18337-NRT) on Fastly is working host -v dl.winehq.org Trying "dl.winehq.org" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18470 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;dl.winehq.org. IN A ;; ANSWER SECTION: dl.winehq.org. 110 IN CNAME osff.map.fastly.net. osff.map.fastly.net. 30 IN A 151.101.110.217 Received 80 bytes from 127.0.0.53#53 in 24 ms Trying "osff.map.fastly.net" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52478 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;osff.map.fastly.net. IN AAAA Received 37 bytes from 127.0.0.53#53 in 20 ms Trying "osff.map.fastly.net" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9249 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;osff.map.fastly.net. IN MX Received 37 bytes from 127.0.0.53#53 in 20 ms LANG=en wget -d https://dl.winehq.org/wine-builds/ubuntu/dists/impish/main/binary-all/Packa… DEBUG output created by Wget 1.21 on linux-gnu. Reading HSTS entries from /home/indri/.wget-hsts URI encoding = 'ANSI_X3.4-1968' converted 'https://dl.winehq.org/wine-builds/ubuntu/dists/impish/main/binary-all/Packa…' (ANSI_X3.4-1968) -> 'https://dl.winehq.org/wine-builds/ubuntu/dists/impish/main/binary-all/Packa…' (UTF-8) Converted file name 'Packages' (UTF-8) -> 'Packages' (ANSI_X3.4-1968) --2021-10-27 10:33:04-- https://dl.winehq.org/wine-builds/ubuntu/dists/impish/main/binary-all/Packa… Resolving dl.winehq.org (dl.winehq.org)... 151.101.74.217 Caching dl.winehq.org => 151.101.74.217 Connecting to dl.winehq.org (dl.winehq.org)|151.101.74.217|:443... connected. Created socket 3. Releasing 0x00005562fd608aa0 (new refcount 1). Initiating SSL handshake. Handshake successful; connected socket 3 to SSL handle 0x00005562fd609880 certificate: subject: CN=*.winehq.org issuer: CN=GlobalSign Atlas R3 DV TLS CA 2020,O=GlobalSign nv-sa,C=BE X509 certificate successfully verified and matches host dl.winehq.org ---request begin--- GET /wine-builds/ubuntu/dists/impish/main/binary-all/Packages HTTP/1.1 User-Agent: Wget/1.21 Accept: */* Accept-Encoding: identity Host: dl.winehq.org Connection: Keep-Alive ---request end--- HTTP request sent, awaiting response... ---response begin--- HTTP/1.1 200 OK Connection: keep-alive Content-Length: 1758 Server: Apache Strict-Transport-Security: max-age=31536000 Cache-Control: max-age=604800 Last-Modified: Mon, 25 Oct 2021 12:12:48 GMT ETag: "6de-5cf2c477b5c33" Access-Control-Allow-Origin: * Via: 1.1 varnish, 1.1 varnish Fastly-Debug-Digest: 71bd9e11bef6b16fa199d390a7364dfd70068eba5cc79f273515095069aaf4ec Accept-Ranges: bytes Date: Wed, 27 Oct 2021 01:33:05 GMT Age: 132197 X-Served-By: cache-ord1731-ORD, cache-nrt18338-NRT X-Cache: HIT, HIT X-Cache-Hits: 2, 1 X-Timer: S1635298386.670273,VS0,VE0 ---response end--- 200 OK Registered socket 3 for persistent reuse. Parsed Strict-Transport-Security max-age = 31536000, includeSubDomains = false Updated HSTS host: dl.winehq.org:443 (max-age: 31536000, includeSubdomains: false) Length: 1758 (1.7K) Saving to: 'Packages' Packages 100%[================================================================================================================>] 1.72K --.-KB/s in 0s 2021-10-27 10:33:04 (31.8 MB/s) - 'Packages' saved [1758/1758] Saving HSTS entries to /home/indri/.wget-hsts -- 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.

1 6

[Bug 51849] New: Debian packaging: When building debian packages, HARDENING flags will be passed to cross-compiler
by WineHQ Bugzilla 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=51849 Bug ID: 51849 Summary: Debian packaging: When building debian packages, HARDENING flags will be passed to cross-compiler Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: cybermax(a)dexter.no CC: dimesio(a)earthlink.net Distribution: --- When packages are built on debian, the default "hardening" flags will be passed to wine/configure. The result from this is that wine/configure tries to do checks for cross-compiler (mingw-w64) with flags meant to be used for ELF binaries. The flags are -Wl,-z,relro This causes configure to fail several checks for cross-compiler. The logs from WineHQ official OBS builds here for Debian 11: https://build.opensuse.org/public/build/Emulators:Wine:Debian/Debian_11/x86… Failing these checks will cause mingw-w64 to create loads of warnings like: [ 1042s] In file included from dlls/cabinet/fdi.c:72: [ 1042s] dlls/cabinet/fdi.c: In function 'FDI_read_string': [ 1042s] dlls/cabinet/fdi.c:485:9: warning: format '%ld' expects argument of type 'long int', but argument 6 has type 'INT_PTR' {aka 'long long int'} [-Wformat=] [ 1042s] 485 | TRACE("(fdi == %p, hf == %ld, cabsize == %ld)\n", fdi, hf, cabsize); [ 1042s] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~ [ 1042s] | | [ 1042s] | INT_PTR {aka long long int} If you however build without passing -Wl,-z,relro to mingw-w64, configure will pass a lot more tests, and the compile is quite a lot less noisy: https://build.opensuse.org/build/home:SveSop/Debian_11/x86_64/wine-devel/_l… Is there a possibility to avoid passing this flag to the cross-compiler in wine/configure? From what i gather, the -Wl,-z,relro flag is meant for ELF binaries, but afaik wine mostly (if not only) uses mingw-w64 to build PE libs, and thus these flags fail. You can add export DEB_LDFLAGS_MAINT_STRIP = -Wl,-z,relro to debian/rules, but that ofc means the ELF binaries built by gcc will not get these hardening flags. -- 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.

1 5

[Bug 50891] New: Fedora 33 repository missing wine-*-common x86_64 packages
by WineHQ Bugzilla 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=50891 Bug ID: 50891 Summary: Fedora 33 repository missing wine-*-common x86_64 packages Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: blacknova(a)tut.by CC: dimesio(a)earthlink.net Distribution: --- After recent update of Fedora repository, all x64_64 versions of wine-*-common packages are missing. DNF upgrade command complain on broken dependencies: Problem 1: cannot install the best update candidate for package wine-staging64-1:6.4-1.1.x86_64 - nothing provides wine-staging-common = 1:6.5-1.2 needed by wine-staging64-1:6.5-1.2.x86_64 Problem 2: package winehq-staging-1:6.5-1.2.x86_64 requires wine-staging64 = 1:6.5-1.2, but none of the providers can be installed - cannot install the best update candidate for package winehq-staging-1:6.4-1.1.x86_64 - nothing provides wine-staging-common = 1:6.5-1.2 needed by wine-staging64-1:6.5-1.2.x86_64 Problem 3: problem with installed package wine-staging64-1:6.4-1.1.x86_64 - package wine-staging64-1:6.4-1.1.x86_64 requires wine-staging-common = 1:6.4-1.1, but none of the providers can be installed - cannot install both wine-staging-common-1:6.5-2.1.i686 and wine-staging-common-1:6.4-1.1.i686 - cannot install the best update candidate for package wine-staging-common-1:6.4-1.1.i686 - nothing provides wine-staging-common = 1:6.5-1.2 needed by wine-staging64-1:6.5-1.2.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.

1 9

[Bug 51354] New: WRC 7 needs ID3DUserDefinedAnnotation interface
by WineHQ Bugzilla 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=51354 Bug ID: 51354 Summary: WRC 7 needs ID3DUserDefinedAnnotation interface Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Shows WRC 7 window and immediately closes. 0110:trace:d3d11:d3d11_device_context_QueryInterface iface 00000000001E31E8, iid {b2daad8b-03d4-4dbf-95eb-32ab4b63d0ab}, out 00000000026DA770. 0110:warn:d3d11:d3d11_device_context_QueryInterface {b2daad8b-03d4-4dbf-95eb-32ab4b63d0ab} not implemented, returning E_NOINTERFACE. wine-6.11-158-g542175ab104 -- 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.

1 7

[Bug 46615] New: PC Building Simulator doesn't render fonts
by wine-bugs＠winehq.org 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=46615 Bug ID: 46615 Summary: PC Building Simulator doesn't render fonts Product: Wine Version: 4.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: luca.finizio.mgbx(a)hotmail.it Distribution: Mint I tried to play PC Building Simulator v9.3.4 but it's impossible to play the game because fonts are not rendered. I attached my console output (there are also errors). -- 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.

2 5

[Bug 44950] New: err:ntdll: RtlpWaitForCriticalSection. Supreme Commander FA
by wine-bugs＠winehq.org 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=44950 Bug ID: 44950 Summary: err:ntdll:RtlpWaitForCriticalSection. Supreme Commander FA Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: james.ytedmonds(a)gmail.com Distribution: --- This bug has affected Supreme Commander: Forged Alliance since pre-2.21. I have found this bug to affect multiple machines with clean wine prefixes. At some point during gameplay, the game will either stop entirely or the window for it will close. The terminal reads: " 007f:fixme:faultrep:ReportFault 0x153ece4 0x0 stub 0110:err:ntdll:RtlpWaitForCriticalSection section 0xfeec00 "?" wait timed out in thread 0110, blocked by 007f, retrying (60 sec) " The only option after this point is to kill the applications. I have found several things that seem to make the bug more likely: *Playing on large maps (definite correlation) *Using 6+ players (less certain) *High graphics settings (might affect timing of bug, but AFAIK cannot cause it) I have tried to override the "ntdll.dll" with one from real windows, but I believe wine at this time does not support overriding this DLL. The bug is easy to reproduce, on a large map (i.e. "Betrayal Ocean") it can occur within 5-10 minutes. I can get any details and logs needed, but I will need to be told how to get them (I am not experienced with debugging) -- 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.

2 12

[Bug 48847] New: dotnet471: often gets a critical section timeout
by WineHQ Bugzilla 10 Apr '22

10 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=48847 Bug ID: 48847 Summary: dotnet471: often gets a critical section timeout Product: Wine Version: 5.5 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- Created attachment 66764 --> https://bugs.winehq.org/attachment.cgi?id=66764 bt all I've been seeing this when running winetricks-test, for dotnet46* and dotnet471. This info is for dotnet471. austin@laptop ~ $ grep 'wait timed out' /tmp/out.txt | sort -u 0048:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 0048, blocked by 006e, retrying (60 sec) 006e:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 006e, blocked by 0174, retrying (60 sec) 00ad:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 00ad, blocked by 006e, retrying (60 sec) 00bb:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 00bb, blocked by 0174, retrying (60 sec) 00e2:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 00e2, blocked by 006e, retrying (60 sec) 0114:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 0114, blocked by 0174, retrying (60 sec) 0166:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 0166, blocked by 006e, retrying (60 sec) 0169:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 0169, blocked by 006e, retrying (60 sec) 016c:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 016c, blocked by 0174, retrying (60 sec) 0193:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c: loader_section" wait timed out in thread 0193, blocked by 006e, retrying (60 sec) winedbg bt all is attached. -- 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.

1 19

[Bug 6682] IrfanView's 4.44 Help -> About window is missing a picture on the left
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=6682 temp82(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |temp82(a)luukku.com --- Comment #75 from temp82(a)luukku.com --- (In reply to Artem S. Tashkinov from comment #74) > Can't reproduce in Wine 7.6, marking fixed. works here as well linuxmint Mate. wine 7.6. -- 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.

1 0

[Bug 6682] IrfanView's 4.44 Help -> About window is missing a picture on the left
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=6682 Artem S. Tashkinov <aros(a)gmx.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED URL|http://www.techspot.com/dow |https://web.archive.org/web |nloads/299-irfanview.html#d |/20170711052934/https://www |ownload_scroll |.irfanview.info/files/iview | |444.zip Resolution|--- |FIXED --- Comment #74 from Artem S. Tashkinov <aros(a)gmx.com> --- Can't reproduce in Wine 7.6, marking fixed. -- 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.

1 0

[Bug 50629] New: Old links on https://www.winehq.org/forums
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=50629 Bug ID: 50629 Summary: Old links on https://www.winehq.org/forums Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: jkfloris(a)dds.nl Distribution: --- Two old links on https://www.winehq.org/forums 1. "Users might also want to visit the Wine area at Linux Forums" has a link to http://www.linuxforums.org/forum/wine/ linuxforums.org is offline since May 2020 2. The wine-tests-results(a)winehq.org mailing list isn't used. -- 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.

1 2

[Bug 39379] New: test.winehq.org: Show a specific test history for a machine or platform
by wine-bugs＠winehq.org 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=39379 Bug ID: 39379 Summary: test.winehq.org: Show a specific test history for a machine or platform Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Currently it's possible to see at a glance how specific test fared across Wine commits and *all platforms*. For instance: https://test.winehq.org/data/tests/advapi32:service.html But if a platform has multiple test machines, one where the test has always failed and another where it has just started failing, one cannot see when the failures started on the above page. So it would be nice to have a similar page on a per-platform basis; or one with all the reports where that test failed regardless of platform. -- 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.

2 4

[Bug 48164] New: test.winehq.org should provide an efficient way to detect new failures
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=48164 Bug ID: 48164 Summary: test.winehq.org should provide an efficient way to detect new failures Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Problem ------- test.winehq.org does not allow performing the following tasks efficiently: 1. Detecting when a new failure slips past the TestBot. One can detect new failures on the per test unit page when specific columns turn red. But quite often the test unit already has failures so one has to look at the specific number of failures. Furthermore many test units currently have failures so this requires checking 80+ pages individually. 2. Detecting when the results on a VM degrade. After upgrading a machine it's useful to compare it to its previous results. But the results for each date are on separate pages. So again it's necessary to check the per-test-unit result pages. 3. Comparing the results of two machines of different platforms. For instance comparing the results of running Windows 8 to those of Windows 10 on the same hardware. Other things that got asked: 4. Sometimes it would be nice to have only the failures, and not all the lines with skipped tests and todos. 5. In some cases it would also be nice to have pages with only the failures that happen on TesBot VMs since these are usually easier to reproduce. Jeremy's page ------------- Jeremy's test summary page can help with some of that: https://www.winehq.org/~jwhite/latest.html But: * It's not integrated with test.winehq.org which makes it hard to find. * There are only two states: Success and Failed: So it does not help when a test goes from having 2 failures to 4, or when it has a set of systematic failures and a set of intermittent ones. * The failed / success pattern is not per VM which masks some patterns and does not help with point 2. Proposal -------- A modified version of Jeremy's page could be integrated with test.wnehq.org: * It would actually be a pair of 'Failures' pages, one for TestBot VMs and one for all test results. Both would be linked to from the top of the main index page, for instance using the same type of 'prev | next' text links used on the other pages. * Jeremy's result matrix would be extended from three to four dimensions; test units, test results, time, and number/type of failures. * As before the results would be grouped per test unit in alphabetical order. Only the test units having at least one error, recent or not, would be shown. This could again be in the form of an array ('full report' pages on test.winehq.org) or simply test unit titles (TestBot jobDetails page style) with the information about each test unit inside. Clicking on the test unit name would link to its 'test runs' page on test.winehq.org. * For each test unit there would be one line per test result having errors. The first part of the line would have one character per commit for the whole history available on test.winehq.org. That character would indicate if the test failed and more. The second part of the line would be the test result platform and tag. They would be sorted per platform and alphabetically. * Each test result would get a one character code: . Success F Failure C Crash T Timeout m Missing dll (foo=missing or other error code) e Other dll error (foo=load error 1359 and equivalent) _ No test (the test did not exist) ' ' No result (the machine did not run the tests that day) * These codes would be shown using a monospace font so they would form a pattern across time and test results: .....F..F...F..F.mmm Win8 vm1 .....FFFFeFFFFFFeFFF Win8 vm1-ja ...TTCC Win8 vm2-new ......eF...F...F..F. Win10 vm3 * Each character would have a tooltip containing details like the meaning of the letter, the number of failures, or the dll error message. They would also link to the corresponding section of the test report. * In addition to the character the background would be color coded to make patterns more visible. . Green F Green to yellow to red gradient C Dark red T Purple/pink m Cyan e Dark blue _ Light gray ' ' White * The green-yellow-red gradient would be what allows detecting changes in the number of test failures. That gradient must be consistent for all lines of a given test unit's pattern. Furthermore the gradient must not be computed based on the test result's number of failures. That is, if a test unit has either 100 or 101 failures, those must not have nearly indistinguishable colors. Instead the set of all different failure counts for the test unit should be collected. Zero should be added to that set. Then these values should be sorted and a color attributed for each *index*. Then the background color is selected based on the index of that result's failures count. It is expected that each set will be relatively small so that the colors will be reasonably far apart, making it easy to distinguish a shift from 4 to 6 failures even if there are 100 failures from time to time. Also note hat adding zero to the set essentially reserves green for successful results. Implementation feasibility -------------------------- * No changes in dissect. * In gather, generate a new testunits.txt file containing one line per test unit: - The data source would be the per-report summary.txt files. -> These don't indicate when a timeout has occurred so timeouts will appear as F instead which is acceptable for a first implementation. - The first line would contain a star followed by the tags of all the test runs used to build the file: - The other lines would contain the name of the test unit followed by space-separated pairs of result code/failure count and result tag (including the platform). - A line would be put out even if the test unit had no failure. For instance, the commit1 testunit.txt file could contain: * win8_vm1 win8_vm1-ja win8_vm2-new win10_vm3 foo:bar 43 win8_vm1-ja C win8_vm2-new e win10_vm3 foo:bar2 - In the example above win8_vm1 only appears on the first line. This means WineTest was run on that machine but had no failure at all. - If the results for commit2 refer to a win8_vm4 machine, we will know that the reason win8_vm4 does not appear in commit1 file is not because all the tests succeeded, but because WineTest was not run on win8_vm4 for commit1. This means that the result code for win8_vm4 for commit1 should be ' '. not '.' for all test units. - If commit2 has results for the foo:bar3 test unit, then we will know the reason it is not present in the commit1 file is not because all the test runs were successful, but because foo:bar3 did not exist yet. So its result code would be '_', not '.'. * Add a new build-failures script to generate both failures pages. - This script will need to read the testunits.txt file for all the commits. The simplest implementation will be to read all the data into memory before generating the page. This will avoid having to deal with keeping the current test unit synchronized between all of the testunits.txt files when a new test unit has been added. - The combined size of the testunits.txt files is expected to be reasonable, within a factor of 3 of the summary.txt files. For reference, here is some data about the sizes involved: $ du -sh data 21G data $ ls data/*/*/report | wc -l 2299 $ cat data/*/*/report | wc 34,087,987 231,694,407 2,104,860,095 $ cat data/*/*/report | egrep '(: Test failed:|: Test succeeded inside todo block:|done [(]258)|Unhandled exception:)' | wc 567,158 6,275,504 53,202,999 $ cat data/*/summary.txt | wc 186,219 3,046,363 30,596,901 - Having a function to generate the page will allow calling it twice in a row to generate both pages without having to load and parse the testunits.txt files twice. -- 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.

1 5

[Bug 51352] New: test.winehq.org should distinguish "too much data" errors from others
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=51352 Bug ID: 51352 Summary: test.winehq.org should distinguish "too much data" errors from others Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The new patterns page treats the "test printed too much data" failures like any other. It would be better to use another symbol and color when there is no other failure. -- 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.

1 4

[Bug 49058] New: https://source.winehq.org/git/website.git/ directs users to clone from http://, not https://
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=49058 Bug ID: 49058 Summary: https://source.winehq.org/git/website.git/ directs users to clone from http://, not https:// Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- austin@laptop /tmp $ git clone http://source.winehq.org/git/wine.git Cloning into 'wine'... warning: redirecting to https://source.winehq.org/git/wine.git/ Looks like this is in the website config: https://source.winehq.org/git/website.git/blob/dccd8b12e3bce9d7a9cc2112e511… note, applies to the other git repos as well. -- 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.

1 4

[Bug 52088] New: Update favicon to 32X32
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52088 Bug ID: 52088 Summary: Update favicon to 32X32 Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: 2ndforwine(a)inmano.com Distribution: --- The 16x16 looks very blurry when compared to other web-sites. -- 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.

1 3

[Bug 50630] New: Old link on https://www.winehq.org/news
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=50630 Bug ID: 50630 Summary: Old link on https://www.winehq.org/news Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: jkfloris(a)dds.nl Distribution: --- At the bottom of the page there is a link to World Wine News Archive - https://www.winehq.org/wwn The last "news" item is from 2017. Maybe it is an idea to remove this link. -- 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.

1 2

[Bug 51613] New: Broken link at https://wiki.winehq.org/Developer_Hints in conformance tests section
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=51613 Bug ID: 51613 Summary: Broken link at https://wiki.winehq.org/Developer_Hints in conformance tests section Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: tatidev1454(a)protonmail.com Distribution: --- Link to http://www.winehq.org/site/docs/winedev-guide/testing broken at "writing conformance tests" section in https://wiki.winehq.org/Developer_Hints -- 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.

1 2

[Bug 50516] New: Broken link 'https://wiki.winehq.org/Useful_Registry_Keys'
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=50516 Bug ID: 50516 Summary: Broken link 'https://wiki.winehq.org/Useful_Registry_Keys' Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: jose.relland(a)free.fr Distribution: --- Hi, thank you for your time. I noted that the linnk: "Wine Man Page" (at the bottom of the page) is broken. Send to 404 page error. Best 2021 year :) José from France -- 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.

1 4

[Bug 50512] New: Wiki /Bugs links broken, can't edit them
by WineHQ Bugzilla 09 Apr '22

09 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=50512 Bug ID: 50512 Summary: Wiki /Bugs links broken, can't edit them Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: ddascalescu+wine(a)gmail.com Distribution: --- I've created an account to edit the wiki. May I please have permission to do so? I'm User:Dandv on Wikipedia as well. Due to the extensive reorg of https://wiki.winehq.org/Wine_User's_Guide, the links at https://wiki.winehq.org/Bugs in "You installed and ran the application using Wine, not on your Windows installation" are broken. -- 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.

1 2

[Bug 52728] New: wine-7.5 build fails in Ubuntu 18.04
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52728 Bug ID: 52728 Summary: wine-7.5 build fails in Ubuntu 18.04 Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winealsa.drv Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net Distribution: --- Created attachment 72087 --> https://bugs.winehq.org/attachment.cgi?id=72087 Ubuntu 18.04 failed build log All the other builds were fine, but it failed in winealsa.drv in Ubuntu 18.04 [ 2042s] dlls/winealsa.drv/alsamidi.c:117:8: error: unknown type name 'uint64_t' [ 2042s] static uint64_t get_time_msec(void) [ 2042s] ^~~~~~~~ [ 2042s] dlls/winealsa.drv/alsamidi.c: In function 'get_time_msec': [ 2042s] dlls/winealsa.drv/alsamidi.c:123:17: error: 'uint64_t' undeclared (first use in this function); did you mean 'u_int64_t'? [ 2042s] return (uint64_t)now.tv_sec * 1000 + now.tv_nsec / 1000000; [ 2042s] ^~~~~~~~ [ 2042s] u_int64_t [ 2042s] dlls/winealsa.drv/alsamidi.c:123:17: note: each undeclared identifier is reported only once for each function it appears in [ 2042s] dlls/winealsa.drv/alsamidi.c:123:26: error: expected ';' before 'now' [ 2042s] return (uint64_t)now.tv_sec * 1000 + now.tv_nsec / 1000000; [ 2042s] ^~~ [ 2042s] dlls/winealsa.drv/alsamidi.c:126:22: error: expected ';' before 'now' [ 2042s] return (uint64_t)now.tv_sec * 1000 + now.tv_nsec / 1000000; [ 2042s] ^~~ [ 2042s] dlls/winealsa.drv/alsamidi.c:127:1: warning: control reaches end of non-void function [-Wreturn-type] [ 2042s] } [ 2042s] ^ [ 2042s] Makefile:130009: recipe for target 'dlls/winealsa.drv/alsamidi.o' failed [ 2042s] make[1]: *** [dlls/winealsa.drv/alsamidi.o] Error 1 -- 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.

1 7

[Bug 52698] New: JW Scheduler installer fails to start: "Requires Microsoft .NET Framework 4.5.2"
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52698 Bug ID: 52698 Summary: JW Scheduler installer fails to start: "Requires Microsoft .NET Framework 4.5.2" Product: Wine Version: 7.4 Hardware: x86-64 URL: https://jwscheduler.com/jw-christian-life-ministry-mee ting-scheduler/ OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- It checks for the reg key DWORD HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v4\Full\Servicing which is not present. After manually creating it, the app installs and starts for me I guess this should be fixed in Mono (?) -- 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.

1 6

[Bug 52658] New: Swisslog
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52658 Bug ID: 52658 Summary: Swisslog Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kvradio(a)seznam.cz Distribution: --- EndeavourOS Wine 7.4-1 Swisslog http://www.swisslogforwindows.com/download.html has stopped working and freezes logo on startup.. No error displayed. Version 7.3 and earlier works very well (If I try to replace the folder /usr/lib32/wine from 7.3 package works 7.4 again) -- 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.

1 7

[Bug 52660] New: chunk allocator for GL uniform buffers kills performance in World of Warships
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52660 Bug ID: 52660 Summary: chunk allocator for GL uniform buffers kills performance in World of Warships Product: Wine Version: 7.4 Hardware: x86-64 URL: https://worldofwarships.eu/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: janbraun(a)gmx.net Regression SHA1: 86f0ae8efb17ce688986971d24c3e25840a2beef Distribution: --- I've found and bisected a huge performance regresssion in World Of Warships: With 86f0ae8efb17ce688986971d24c3e25840a2beef "wined3d: Use the chunk allocator for GL uniform buffers." applied, my framerate is around 18-20fps during gameplay. With that patch reverted, it's back at >=60fps. The code moved around in the meantime, but simply commenting out the "case GL_UNIFORM_BUFFER:" in use_buffer_chunk_suballocation() restores performance on wine 7.4 (= current git HEAD) as well. I have the subjective impression that other games might be affected too (things feel a bit more sluggy), but certainly nowhere as severely as WoWS. I didn't further test/benchmark, however, because WoWS was such a nice reproducer. Running mesa-21.3.7 on amdgpu. Please holler if you need more info. -- 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.

1 9

[Bug 52638] New: The 64-bit winmm:mci fails and crashes in test_openCloseWAVE() in Wine
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52638 Bug ID: 52638 Summary: The 64-bit winmm:mci fails and crashes in test_openCloseWAVE() in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit winmm:mci crashes in test_openCloseWAVE() in Wine: mci.c:389: Test failed: mci sysinfo all quantity returned MCIERR_UNRECOGNIZED_COMMAND mci.c:398: Test failed: sysinfo all quantity string and command differ Unhandled exception: page fault on read access to 0x000000000000020d in 64-bit code (0x00000000709b9ca1). [...] Backtrace: =>0 0x00000000709b9ca1 _wcsicmp_l+0x91(str1=*** Invalid address 0x0000000000000002 *** Internal symbol error: unable to access memory location 0000000000000002, str2=*** Invalid address 0x0000000000000000 *** Internal symbol error: unable to access memory location 0000000000000000, locale=000000000064E980) [Z:\home\winetest\winetest\src\dlls\msvcrt\wcs.c:132] in ucrtbase (0x000000000004dd50) 1 0x00000000709b9d6c _wcsicmp+0xc(str1=<internal error>, str2=<internal error>) [Z:\home\winetest\winetest\src\dlls\msvcrt\wcs.c:158] in ucrtbase (0x00000000709b9d60) 2 0x0000000000bf8057 MCI_FindCommand+0x38(s2=<internal error>, s1=<internal error>) [Z:\home\winetest\winetest\src\dlls\winmm\mci.c:946] in winmm (0x00000000709b9d60) 3 0x0000000000bf8057 MCI_FindCommand+0x67(uTbl=<internal error>, verb=<register RDI not accessible in this frame>) [Z:\home\winetest\winetest\src\dlls\winmm\mci.c:938] in winmm (0x00000000709b9d60) 4 0x0000000000bfbcc7 mciSendStringW+0xc57(lpstrCommand=<internal error>, lpstrRet=[<register RSP not accessible in this frame>, uRetLen=[<register RSP not accessible in this frame>, hwndCallback=[<register RSP not accessible in this frame>) [Z:\home\winetest\winetest\src\dlls\winmm\mci.c:1460] in winmm (0x00000000003e0000) https://test.winehq.org/data/patterns.html#winmm:mci This only happens with the 64-bit build but as far as I can tell it is systematic and impacts all machines. A bisect pointed to the following commit as the trigger: commit 7c76aa05a9d27dd6f5705c4ef90c16862af14f3e Author: Jacek Caban <jacek(a)codeweavers.com> Date: Mon Mar 7 14:42:32 2022 +0100 win32u: Move class management implementation from user32. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 6

[Bug 52340] New: wine-mono + RMS Express: COM Port errors connecting to radios
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52340 Bug ID: 52340 Summary: wine-mono + RMS Express: COM Port errors connecting to radios Product: Wine Version: 7.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: eric.wheez(a)gmail.com Distribution: --- Hello again, I just wanted to report in a "not implemented" exception in wine-mono. I believe that "System.IO.Ports.SerialPort.set_ReceivedBytesThreshold" not implemented in wine-mono is causing RMS Express to not be able to control the radio (channel selection and "push-to-talk"/"PTT" switch) over USB connection. Normal behavior is for RMS Express to tell the radio what radio channel to send/receive on & when to transmit/listen (via PTT switch). This behavior is working on RMS Express via Windows. This behavior is also working with RMS Express on Debian 10 VM with wine & .NET 4.6 (I had to set `sudo adduser $USER dialout && sudo reboot` to set permissions for the COM port for the user account so before channels/PTT worked .NET 4.6 though). The not implemented exception pops up in the linux terminal with wine-mono exactly at the same time that the (known-working-with-.NET4.6) COM port is said to be inaccessible. I've included the short log of the wine-mono not implemented exception at the of this post. [Setup] OS: Debian 10 (VMware Workstation on a Windows laptop) Wine: wine-7.0-rc4 devel Wine Mono: wine-mono 2f50d2c (https://nightly.link/madewokherd/wine-mono/actions/artifacts/131614059.zip) Program: Winlink Express 1.5.44.0 Radio: Yaesu FT-891 transceiver (with dummyload attached directly to radio - no feed line so I don't accidentally send signals) Details: - FT-891 connected to PC via USB cable (and make sure VMWare has the USB line routed into the VM instead of the host PC) - I set the FT-891's on-board settings to data 'baud' 9600. - I set in/out audio devices in ARDOP settings on the PC. Thank you again! And here's to 2022 being better than the previous two years :) Cheers ---- wine-mono not implemented exception log: ``` WINE_MONO_TRACE=E:System.MissingMethodException MONO_INLINELIMIT=0 WINE_MONO_HIDETYPES=1 wine RMS\ Express.exe ... [00000024:] EXCEPTION handling: System.NotImplementedException: The method or operation is not implemented. "<unnamed thread>" tid=00000024 this=04570120 , thread handle : 01df5788, state : not waiting at System.IO.Ports.SerialPort.set_ReceivedBytesThreshold (int) [0x0000f] in <117354a27af94c36af91c072a84e6fb8>:0 at (wrapper remoting-invoke-with-check) System.IO.Ports.SerialPort.set_ReceivedBytesThreshold (int) [0x00032] in <117354a27af94c36af91c072a84e6fb8>:0 at RMS_Express.Radio.OpenControlPort () [0x000b3] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Radio.SetRadio () [0x0014f] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Radio.SetFrequency (int,string) [0x00021] in <25c56d5497bc4490bd1b5395b173c5df>:0 at (wrapper remoting-invoke-with-check) RMS_Express.Radio.SetFrequency (int,string) [0x00033] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.ArdopSession.Ardop_Activated (object,System.EventArgs) [0x00823] in <25c56d5497bc4490bd1b5395b173c5df>:0 at System.Windows.Forms.Form.OnActivated (System.EventArgs) [0x0001f] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.set_Active (bool) [0x000a6] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.WmActivate (System.Windows.Forms.Message&) [0x0001a] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.WndProc (System.Windows.Forms.Message&) [0x001b8] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.OnMessage (System.Windows.Forms.Message&) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.WndProc (System.Windows.Forms.Message&) [0x000b3] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00025] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00032] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) [0x00037] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper native-to-managed) System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) <0x00067> at <unknown> <0xffffffff> at (wrapper managed-to-native) System.Windows.Forms.SafeNativeMethods.ShowWindow (System.Runtime.InteropServices.HandleRef,int) <0x00012> at System.Windows.Forms.Control.SetVisibleCore (bool) [0x00061] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Form.SetVisibleCore (bool) [0x000d1] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.set_Visible (bool) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.Show () [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at RMS_Express.ArdopSession.ShowSession () [0x00000] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Main.StartSession () [0x005fd] in <25c56d5497bc4490bd1b5395b173c5df>:0 at RMS_Express.Main.mnuSession_Click (object,System.EventArgs) [0x00000] in <25c56d5497bc4490bd1b5395b173c5df>:0 at System.Windows.Forms.ToolStripItem.RaiseEvent (object,System.EventArgs) [0x0001b] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.OnClick (System.EventArgs) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripMenuItem.OnClick (System.EventArgs) [0x0001d] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.HandleClick (System.EventArgs) [0x00051] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.HandleMouseUp (System.Windows.Forms.MouseEventArgs) [0x000fd] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.FireEventInteractive (System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00053] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStripItem.FireEvent (System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00103] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.ToolStripItem.FireEvent (System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00033] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStrip.OnMouseUp (System.Windows.Forms.MouseEventArgs) [0x0007d] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.WmMouseUp (System.Windows.Forms.Message&,System.Windows.Forms.MouseButtons,int) [0x001c3] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message&) [0x005a0] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ScrollableControl.WndProc (System.Windows.Forms.Message&) [0x00043] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.ToolStrip.WndProc (System.Windows.Forms.Message&) [0x00128] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.MenuStrip.WndProc (System.Windows.Forms.Message&) [0x00056] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.OnMessage (System.Windows.Forms.Message&) [0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Control/ControlNativeWindow.WndProc (System.Windows.Forms.Message&) [0x000b3] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00025] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&) [0x00032] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) [0x00037] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper native-to-managed) System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr) <0x00067> at <unknown> <0xffffffff> at (wrapper managed-to-native) System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW (System.Windows.Forms.NativeMethods/MSG&) <0x00012> at System.Windows.Forms.Application/ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop (intptr,int,int) [0x001d7] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Application/ThreadContext.RunMessageLoopInner (int,System.Windows.Forms.ApplicationContext) [0x00282] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Application/ThreadContext.RunMessageLoop (int,System.Windows.Forms.ApplicationContext) [0x0001a] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.Application/ThreadContext.RunMessageLoop (int,System.Windows.Forms.ApplicationContext) [0x00033] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at System.Windows.Forms.Application.Run (System.Windows.Forms.ApplicationContext) [0x00006] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun () [0x00044] in <e344caf534bf4ffb982376a141ed987b>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel () [0x00035] in <e344caf534bf4ffb982376a141ed987b>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run (string[]) [0x0001b] in <e344caf534bf4ffb982376a141ed987b>:0 at RMS_Express.My.MyApplication.Main (string[]) [0x0000f] in <25c56d5497bc4490bd1b5395b173c5df>:0 at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) [0x00027] in <25c56d5497bc4490bd1b5395b173c5df>: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.

1 13

[Bug 42309] New: The Crew (Uplay) crashes at start
by wine-bugs＠winehq.org 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=42309 Bug ID: 42309 Summary: The Crew (Uplay) crashes at start Product: Wine Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 57043 --> https://bugs.winehq.org/attachment.cgi?id=57043 Unhandled page fault read access to 0x0 in 64-bit code backtrace After the loading screen has closed, the screen goes black and then wine crashes with a read access to 0x00000000 in 64-bit code. The terminal is also filled with DirectX 11 fixme's. Tested on wine 2.0 + staged patch from bug 41356. -- 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.

2 21

[Bug 52722] New: Winetricks dotnet installation hangs at wineserver -w
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52722 Bug ID: 52722 Summary: Winetricks dotnet installation hangs at wineserver -w Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: tatidev1454(a)protonmail.com Distribution: --- Created attachment 72082 --> https://bugs.winehq.org/attachment.cgi?id=72082 Logs of the affected function create_surrogate_server with 32 bits wine and WoW64 This bug only happens with 13064f991408ea5fa5e999705b13bda7bbd50e5b commit. 1. Run `winetricks dlls dotnet45` having a 32 bits build of wine in the PATH (or any other dotnet version which requires the installation of an older one) 2. Wait until dotnet40 installs. 3. Winetricks executes wineserver -w and it just hangs there. -- 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.

1 9

[Bug 52721] New: d3dx9_36:effect, d3dx11_42:d3dx11 and d3dx11_43:d3dx11 broken by use of vkd3d_shader_compile() for D3DCompile2()
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52721 Bug ID: 52721 Summary: d3dx9_36:effect, d3dx11_42:d3dx11 and d3dx11_43:d3dx11 broken by use of vkd3d_shader_compile() for D3DCompile2() Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- A recent patch to use vkd3d_shader_compile() to implement D3DCompile2() broke d3dx11_42:d3dx11 and d3dx11_43:d3dx11. In both cases it leads to a crash: d3dx11.c:580: Test failed: Got unexpected errors. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x70bb0990). [...] Backtrace: =>0 0x70bb0990 strrchr+0x10(str=0x000000000, c=0x5c) [Z:\home\winetest\winetest\src\dlls\msvcrt\string.c:3166] in ucrtbase (0x0031d9b8) 1 0x69d8bcc9 d3dcompiler_include_from_file_open+0x49(iface=<internal error>, include_type=<internal error>, filename=<internal error>, parent_data=<internal error>, data=<internal error>, bytes=<internal error>) [Z:\home\winetest\winetest\src\dlls\d3dcompiler_43\compiler.c:521] in d3dcompiler_47 (0x0031db28) https://test.winehq.org/data/patterns.html#d3dx11_42:d3dx11 https://test.winehq.org/data/patterns.html#d3dx11_43:d3dx11 d3dx9_36:effect got broken too but at least in this case it's because of successes in todos so it's probably a trivial fix: effect.c:8108: Test succeeded inside todo block: Unexpected error, hr 0x80004005. effect.c:8133: Test succeeded inside todo block: D3DXInclude test failed with error 0x80004005. https://test.winehq.org/data/patterns.html#d3dx9_36:effect The commit that caused these new failures is: commit 6a062afb75c1e026614403312f2e13207e359634 (HEAD, refs/bisect/bad) Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Thu Mar 3 20:25:26 2022 -0600 d3dcompiler: Implement D3DCompile2() using vkd3d_shader_compile(). Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51713 Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Matteo Bruni <mbruni(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 4

[Bug 52668] New: Sparx Enterprise architect v15.2 1560 crashing on wine 7.4
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52668 Bug ID: 52668 Summary: Sparx Enterprise architect v15.2 1560 crashing on wine 7.4 Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: viliam(a)tokarcik.eu Distribution: --- Hi, After upgrade wine from 7.3 to 7.4 Sparx enterprise architect v15.2 1560 start crashing while startup. 0024:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x3c0b989 wine ~/.wine32/drive_c/Program Files/Sparx Systems/EA/EA.exe -- 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.

1 3

[Bug 52628] New: game frozen after opening due to infinite loop in winmm.mmioDescend()
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52628 Bug ID: 52628 Summary: game frozen after opening due to infinite loop in winmm.mmioDescend() Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw Distribution: --- Created attachment 71949 --> https://bugs.winehq.org/attachment.cgi?id=71949 fix patch for infinite loop in winmm, mmio.c, function mmioDescend() around line 1232 there are a loop for mmioRead() mmioSeek() ... some old game using mmioDescend() and mmioRead() has a chance that always return -1 causing infinite loop. My only solution now is to skip that loop when mmioRead() return -1. This affect some old game like poppo, Silk Road ~Tale of the Star Island~ made by Sprite -- 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.

1 4

[Bug 51437] New: If Windows version changes from 7 to 10, Microsoft Edge calls unimplemented function uiautomationcore.dll.UiaRaiseAutomationPropertyChangedEvent
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=51437 Bug ID: 51437 Summary: If Windows version changes from 7 to 10, Microsoft Edge calls unimplemented function uiautomationcore.dll.UiaRaiseAutomationPropertyChanged Event Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: uiautomationcore Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Steps to reproduce: 1. Install Wine Staging (Edge will not start on vanilla Wine). 2. Run `wine MicrosoftEdgeSetup.exe` (make sure to download the installer for Windows 7). 3. Run `winecfg` and change the Windows version from 7 to 10. 4. Run `wine msedge`. If the Windows version is set to 10 from the beginning (and Edge's Windows 10 installer is used), the crash does not occur. However, it's a reasonable use case to install Edge with default Wine settings and then "upgrade" Wine to Windows 10 later. $ sha256sum MicrosoftEdgeSetup.exe c449a35ff96012ae26336ff630ced945d85f83b162b041606549c555b8a997c8 -- 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.

1 5

[Bug 52652] New: Adobe Photoshop 7.0 crashes on startup
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52652 Bug ID: 52652 Summary: Adobe Photoshop 7.0 crashes on startup Product: Wine Version: 7.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- 002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126). 0070:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1114 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0024:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet 00dc:fixme:imm:ImeSetActiveContext (0x264cd8, 0): stub 00dc:fixme:imm:ImmReleaseContext (00010020, 00264CD8): stub 0024:fixme:imm:ImeSetActiveContext (0x250860, 1): stub 0024:fixme:imm:ImmReleaseContext (00010056, 00250860): stub wine: Unhandled page fault on read access to 00000000 at address 7CD79479 (thread 0024), starting debugger... 0160:fixme:imm:ImeSetActiveContext (0x25a4a8, 1): stub 0160:fixme:imm:ImmReleaseContext (00020264, 0025A4A8): stub Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x7cd79479). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:7cd79479 ESP:0021de90 EBP:00000026 EFLAGS:00210206( R- -- I - -P- ) EAX:00000000 EBX:7ce90428 ECX:0021e050 EDX:4545524e ESI:00250158 EDI:00000008 Stack dump: 0x0021de90: 00000000 00000000 00000000 7ce90428 0x0021dea0: 00000001 00000000 00000009 7e768fbc 0x0021deb0: 7e798000 00000229 0021dee8 7e9729a6 0x0021dec0: 0001005e 00000000 00000000 51b96900 0x0021ded0: 00000000 00000000 00000000 7ce90428 0x0021dee0: 00250158 00000008 00000026 7cd7dd9d Backtrace: =>0 0x7cd79479 (0x00000026) 0x7cd79479: movl 0x0(%eax),%eax Modules: Module Address Debug info Name (40 modules) PE 00360000-0038d000 Deferred bib PE 00400000-013b8000 Deferred photoshop PE 013c0000-014ca000 Deferred agm PE 014d0000-01641000 Deferred cooltype PE 01650000-01700000 Deferred asn.er PE 03140000-0321b000 Deferred photoshop PE 03220000-03475000 Deferred psviews PE 051e0000-05203000 Deferred pdf image import.8bi PE 05210000-054e0000 Deferred pdfl50 PE 054e0000-054f7000 Deferred opp PE 10000000-10075000 Deferred ace PE 7b020000-7b027000 Deferred kernelbase PE 7b620000-7b685000 Deferred kernel32 PE 7bc20000-7bc24000 Deferred ntdll PE 7c860000-7c864000 Deferred shfolder PE 7c9d0000-7c9d4000 Deferred uxtheme PE 7cb10000-7cb14000 Deferred mpr PE 7cb40000-7cb46000 Deferred winspool PE 7cb80000-7cb96000 Deferred comdlg32 PE 7cc00000-7cc04000 Deferred sti PE 7cec0000-7cf01000 Deferred comctl32 PE 7d050000-7d054000 Deferred winex11 PE 7d100000-7d104000 Deferred imm32 PE 7d810000-7dfe9000 Deferred shell32 PE 7e110000-7e117000 Deferred oleaut32 PE 7e230000-7e234000 Deferred msacm32 PE 7e270000-7e27f000 Deferred winmm PE 7e2e0000-7e2e4000 Deferred rpcrt4 PE 7e370000-7e373000 Deferred combase PE 7e3f0000-7e418000 Deferred ole32 PE 7e520000-7e523000 Deferred shcore PE 7e660000-7e664000 Deferred shlwapi PE 7e6b0000-7e6b4000 Deferred version PE 7e810000-7e813000 Deferred win32u PE 7e870000-7e874000 Deferred gdi32 PE 7e920000-7e9fa000 Deferred user32 PE 7eb50000-7eb54000 Deferred ucrtbase PE 7ec40000-7ec43000 Deferred sechost PE 7eca0000-7eca4000 Deferred msvcrt PE 7ed60000-7ed64000 Deferred advapi32 Threads: process tid prio name (all IDs are in hex) 00000020 (D) C:\Program Files\Adobe\Photoshop 7.0\Photoshop.exe 00000024 0 <== 00000110 0 00000114 0 00000118 0 00000164 0 00000038 services.exe 0000003c 0 00000040 0 0000004c 0 00000050 0 00000078 0 0000007c 0 00000088 0 000000a8 0 000000c0 0 000000f4 0 00000044 winedevice.exe 00000048 0 00000054 0 00000058 0 0000005c 0 000000cc 0 00000080 winedevice.exe 00000084 0 0000008c 0 00000090 0 00000094 0 00000098 0 0000009c 0 000000a0 plugplay.exe 000000a4 0 000000ac 0 000000b0 0 000000b4 0 000000b8 svchost.exe 000000bc 0 000000c4 0 000000c8 0 000000d0 conhost.exe 000000d4 0 000000d8 explorer.exe 000000dc 0 000000e0 0 000000e4 0 000000ec rpcss.exe 000000f0 0 000000f8 0 000000fc 0 00000100 0 00000104 0 00000108 0 0000010c 0 System information: Wine build: wine-7.4 Platform: i386 Version: Windows XP Host system: Linux Host version: 5.15.19-az2 -- 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.

1 23

[Bug 50158] New: Oculus Runtime won't start: "Could not load file or assembly 'Daybreak'"
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=50158 Bug ID: 50158 Summary: Oculus Runtime won't start: "Could not load file or assembly 'Daybreak'" Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: criteria32(a)gmail.com Distribution: --- Created attachment 68674 --> https://bugs.winehq.org/attachment.cgi?id=68674 Crash log Can be downloaded at oculus.com/setup or with this direct link: https://www.oculus.com/download_app/?id=1582076955407037 -- 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.

1 17

[Bug 52781] New: Origin does not notice games exiting, does not allow them to be relaunched
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52781 Bug ID: 52781 Summary: Origin does not notice games exiting, does not allow them to be relaunched Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xiretza+winehq(a)xiretza.xyz Distribution: --- Created attachment 72163 --> https://bugs.winehq.org/attachment.cgi?id=72163 wine log of starting origin, launching game and quitting game Upon starting a game from Origin, the "Play" button gets grayed out and no further games can be launched. Normally, this is supposed to revert once the game exits, but Origin under Wine does not seem to notice this, and has to be quit and relaunched completely to play another game (or start the original game again). -- 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.

1 3

[Bug 52784] New: Double mouse cursor in Fahrenheit: Indigo Prophecy Remastered
by WineHQ Bugzilla 08 Apr '22

08 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52784 Bug ID: 52784 Summary: Double mouse cursor in Fahrenheit: Indigo Prophecy Remastered Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 72165 --> https://bugs.winehq.org/attachment.cgi?id=72165 example wine-7.5-264-g5a815669e8e -- 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.

1 1

[Bug 52780] New: The Evil Within has very slow performance
by WineHQ Bugzilla 07 Apr '22

07 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52780 Bug ID: 52780 Summary: The Evil Within has very slow performance Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 72161 --> https://bugs.winehq.org/attachment.cgi?id=72161 output wine-7.5-264-g5a815669e8e -- 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.

1 0

[Bug 45103] New: FlixGrab: Crashes on launch after showing the splash screen
by wine-bugs＠winehq.org 07 Apr '22

07 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=45103 Bug ID: 45103 Summary: FlixGrab: Crashes on launch after showing the splash screen Product: Wine Version: 3.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lucas.halbig(a)gmail.com Distribution: --- Created attachment 61276 --> https://bugs.winehq.org/attachment.cgi?id=61276 backtrace file when app crashed When attempting to launch https://www.freegrabapp.com/flixgrab after installation it failes to go past the splash screen. -- 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.

2 8

[Bug 50460] New: Regression on installing mdac28 on 6.0-rc5 was ok in 5.0.4
by WineHQ Bugzilla 07 Apr '22

07 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=50460 Bug ID: 50460 Summary: Regression on installing mdac28 on 6.0-rc5 was ok in 5.0.4 Product: Wine Version: 6.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pierre(a)couderc.eu Distribution: --- Created attachment 69085 --> https://bugs.winehq.org/attachment.cgi?id=69085 log of the trial Using : sudo rm -rI .wine/ WINEARCH=win32 winecfg winetricks mdac28 wine .wine/drive_c/windows/system32/odbcad32.exe fails on last version (from winehq-devel from deb https://dl.winehq.org/wine-builds/debian/ bullseye main debian) and is ok with default bullseye release (5.0.4). odbcad32.exe box is not displayed. Full (small...) listing in attachment I am not able to know if the problem is wine or winetricks. But I am surprised that msado15 is installed as ado is not needed for mdac adn odbs... -- 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.

1 9

[Bug 52530] New: dowonline: Crash at start with multiple error messages (needs dotnet452)
by WineHQ Bugzilla 06 Apr '22

06 Apr '22

https://bugs.winehq.org/show_bug.cgi?id=52530 Bug ID: 52530 Summary: dowonline: Crash at start with multiple error messages (needs dotnet452) Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: joseskvolpe(a)gmail.com Distribution: --- Created attachment 71830 --> https://bugs.winehq.org/attachment.cgi?id=71830 Screenshots and log This application crashes from beginning on Wine Mono 7.0.0, installing dotnet452 with winetricks is a working workaround I've used the ZIP version of the application. Version 2.8 Procedure: 1 - Run DowOnline.exe Download (Version v. 2.8): https://dowonline.ru SHA1 (ZIP): 101a1bf896b834cd8653127a985ae10c080dbeba SHA1 (Installer): f47f7a529f5fcb0449fad0a5d497f667292accea Note: I had TLS package decode errors during download, so i was unable to download it from a browser, use wget instead to download the file if that occurs -- 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.

1 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs April 2022