wine-bugs September 2023

wine-bugs@winehq.org

1 participants
2292 discussions

[Bug 31786] New: Run the tests on real hardware
by wine-bugs＠winehq.org 09 Jul '24

09 Jul '24

http://bugs.winehq.org/show_bug.cgi?id=31786 Bug #: 31786 Summary: Run the tests on real hardware Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified It would be very useful to run some tests on real hardware. * This is the case for all the 3D graphics tests. For these we would even want to run them on both AMD and NVidia graphics cards(*). Currently they are essentially ignored by WineTestBot because the virtual graphic cards don't provide meaningful 3D support. * It could somewhat be useful for sound tests too, mostly to avoid timing issues, but also to ensure the results we get are not tainted by bugs in the emulated sound card. Also emulated sound cards typically don't support MIDI emulation. The problem is that it's very important to limit the test duration and to restore the test environment to a clean state after each test, no matter what happens, for two reasons: * Because it's not uncommon for tests to have side effects and for them to leave the test environment in an unusable state. Granted it happens much more often with older Windows releases as they are more prone to crashes. However graphics drivers also tend to be buggy and we would not want the tests to be tainted by a previous run (though a reboot should take care of most issues). * But also the Wine TestBot runs anything that gets posted by anonymous users on wine-patches. That's ok as long as such code is properly confined and not allowed to run for too long. That supposes thoroughly cleaning up the environment after a test has run, including anything that could happen at boot time. Virtual machines provide a simple solution to both of these issues which is why the TestBot relies on them heavily. With QEmu it's possible to let the guest OS access some peripherals directly via the 'passthrough' mode. This is normally done for network cards. If it worked for graphics cards that would be a great solution but it's not clear that it's feasible. Another option would be to play tricks with Grub scripts: have it boot from a clean Linux partition (or from the network?), restore the Windows partition from a clean disk image, reboot into that partition, and back on the clean partition with the next reboot. That still leaves the issue of forcing a reboot in case of a freeze or malware taking control of Windows (use a remote controlled power switch like in data centers?). (*) We currently have two such machines ready for this: http://www.winehq.org/pipermail/wine-devel/2012-February/094080.html -- 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 9

[Bug 33912] New: Remove All Wine Home Content - Button
by wine-bugs＠winehq.org 09 Jul '24

09 Jul '24

http://bugs.winehq.org/show_bug.cgi?id=33912 Bug #: 33912 Summary: Remove All Wine Home Content - Button Product: Wine Version: 1.6-rc4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: moceap(a)hotmail.com Classification: Unclassified This enhancement what I require that a button not remove only .wine folder in home , also delete all installed-by-wine-application desktop integration files Such as :: $HOME/.local/share/mime/packages/wine* $HOME/.local/share/applications/wine* And others . -- 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 7

[Bug 47099] New: [RFE Staging] Create EXT4 case-insensetive wineprefix on Linux 5.2
by wine-bugs＠winehq.org 09 Jul '24

09 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=47099 Bug ID: 47099 Summary: [RFE Staging] Create EXT4 case-insensetive wineprefix on Linux 5.2 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: timofeevsv1989(a)gmail.com Distribution: --- Case-sensetivity creates many problems on wineprefixes. Linux 5.2 can create case-insensetive empty folders with flag +F Please add this option to staging -- 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 47883] New: Enable explicit large address aware override
by WineHQ Bugzilla 09 Jul '24

09 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=47883 Bug ID: 47883 Summary: Enable explicit large address aware override Product: Wine Version: 4.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com Distribution: --- Some 32-bit games like Dragon Age: Origins start without sound in recent Wine versions (see for example bug 43685), due to running out of 2 GB memory limitations. One workaround is to use a patcher on the binary to enable large address aware bit. Such as: https://github.com/randomstuff/pe-set-laa This is cumbersome however. Please enable some explicit workaround (like some Wine environment variable for example), to avoid using patching on the binaries. -- 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 10

[Bug 48955] New: Use xdg basedir spec
by WineHQ Bugzilla 09 Jul '24

09 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=48955 Bug ID: 48955 Summary: Use xdg basedir spec Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: riptide(a)mundo-r.com Distribution: --- https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html Instead of ~/.wine, configuration should be in the $XDG_CONFIG_HOME/wine/ and cache (safely-deletable files) should be in $XDG_CACHE_HOME/wine/. The big boxes files should be in the $XDG_DATA_HOME/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.

1 9

[Bug 50058] New: Control (GOG) game crash
by WineHQ Bugzilla 09 Jul '24

09 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=50058 Bug ID: 50058 Summary: Control (GOG) game crash Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iroalexis(a)outlook.fr Distribution: --- Created attachment 68513 --> https://bugs.winehq.org/attachment.cgi?id=68513 Wine log (winedbg) for Control Like as title, Control crashes every time at the start of the mission "Defeat the Anchor". I would like to add that from time to time the game crashes during launch for exactly the same reasons as in the attached logs (winedbg). >From the feedback I got on the VKx discord, the problem seems to be unique to the GOG version. There are no problems on the EGS and Steam versions. Here is what I use for launch the game : wine64 Control_DX11.exe. My graphic card is a NVIDIA GTX 1070 with Vulkan Beta Driver. -- 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 10

[Bug 46697] New: ntQueryDirectoryFileEx needed
by wine-bugs＠winehq.org 09 Jul '24

09 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=46697 Bug ID: 46697 Summary: ntQueryDirectoryFileEx needed Product: Wine Version: 4.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: springrat(a)protonmail.com Distribution: --- Mod Organizer 2 fails to load the userspace virtual file system (USVFS) .dll due to a lack of the function, "ntQueryDirectoryFileEx" in ntdll.dll. As a result, the program itself cannot be used for its intended purposes of organizing and loading mods directly, and some critical features such as using tools within the virtual environment break. -- 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 23

[Bug 49275] New: 60 FPS limit on 144Hz screen with v-sync turned off
by WineHQ Bugzilla 09 Jul '24

09 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=49275 Bug ID: 49275 Summary: 60 FPS limit on 144Hz screen with v-sync turned off Product: Wine Version: 5.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bobogu(a)seznam.cz Distribution: --- Linux 5.6.14-arch1-1 Since the last Wine version (5.9.1), in Call of Duty 4, I only get 60 FPS instead of 250 (capped in-game) which I was getting prior to the update. My screen is running at 144Hz which is also what I have my Xorg set to. Output from xrandr -q ... 1920x1080 60.00 + 144.00* 119.98 99.93 ... It's even weirder for me that the FPS are capped to 60 even though my screen refresh rate is 144 Hz. In the game, I don't have v-sync turned on, neither I have my FPS capped to 60. I haven't checked other games since CoD4 is the only game I have. I'm using Lutris as a game manager and with Proton runner, I get the 250 FPS just fine. I've tried setting `vblank_mode=0` and `__GL_SYNC_TO_VBLANK=0` but to no avail. -- 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 41668] New: wineboot mishandles user dir symlinks during update
by wine-bugs＠winehq.org 09 Jul '24

09 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=41668 Bug ID: 41668 Summary: wineboot mishandles user dir symlinks during update Product: Wine Version: 1.9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- In a standard wine prefix 'Desktop', 'My Documents', etc. are symlinks to ${HOME}. As are their localized versions. I consider the first a wrong choice and and make those normal dirs in the prefix; as for the second, I turn those into symlinks to their English counterparts. Yet... Upon 'wineboot' at each wine update, while the English dirs stay untouched, the localized symlinks get reset into ${HOME} symlinks. If it's WAD, it's a misfeature; otherwise, it's a bug. -- 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 15

[Bug 47015] New: Photoshop CC2019 Login screen does not render
by wine-bugs＠winehq.org 09 Jul '24

09 Jul '24

https://bugs.winehq.org/show_bug.cgi?id=47015 Bug ID: 47015 Summary: Photoshop CC2019 Login screen does not render Product: Wine Version: 4.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: funtimeschaos(a)rocketmail.com Distribution: --- Created attachment 64172 --> https://bugs.winehq.org/attachment.cgi?id=64172 Log for 4.5 staging Tested on 4.5 staging. PS was installed on windows. I believe I used "winetricks gdiplus vcrun2010 vcrun2012 vcrun2013 vcrun2015 msxml3 msxml6 atmlib corefonts fakejapanese" to get this far. Not using winetricks causes the launcher to output the following and exit immediately: ``` 002a:fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x4 002a:fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x4 002a:err:module:LdrInitializeThunk "CRClient.dll" failed to initialize, aborting 002a:err:module:LdrInitializeThunk Initializing dlls for L"Z:\\home\\jenia\\Desktop\\winestuff\\pf\\pf64\\Adobe\\APCC2019\\Photoshop.exe" failed, status c0000005 ``` When trying to launch PS, it does launch, however, there is a small window (which I assume is the creative cloud login screen) which does not render. X ing out of the small window closes PS. Log is attached. Looks to me like it is stuck trying (and failing) to render web content? This version of PS was installed on a Japanese system, so a language support issue might be related. -- 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

Jump to page:

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 September 2023