September 2024 - Wine-Bugs - list.winehq.org

[Bug 57155] Gigapixel ai crashes on startup in win7 mode

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57155 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Gigapixel ai crashes on |Gigapixel ai crashes on |startup |startup in win7 mode -- 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.

Sept. 5, 2024

[Bug 57159] Ctrl+C stops the "wineboot" process and causes problems

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57159 --- Comment #1 from BugSeeker <rikul(a)inbox.ru> --- If I delete the ~/.wine/.update-timestamp file, wineboot will force an update to the config directory -- 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.

Sept. 5, 2024

[Bug 57159] New: Ctrl+C stops the "wineboot" process and causes problems

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57159 Bug ID: 57159 Summary: Ctrl+C stops the "wineboot" process and causes problems Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rikul(a)inbox.ru Distribution: --- To reproduce the problem, you need to run "wineboot" and after a few seconds (until the configuration creation window closes) press the key combination Ctrl+C - this will stop the "wineboot" process with an incompletely prepared WINEPREFIX. If you try to run "wineboot" or any other program again, it will result in an error: error: could not load kernel32.dll, status c0000135 Yes, I know that removing WINEPREFIX and restarting "wineboot" will work, but it will be better if second run of "wineboot" can recover configuration directory by itself. -- 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.

Sept. 5, 2024

[Bug 57158] HID devices not detected after removal until Wine processes restart

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57158 Chiitoo <chiitoo(a)gentoo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression -- 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.

Sept. 5, 2024

[Bug 57158] New: HID devices not detected after removal until Wine processes restart

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57158 Bug ID: 57158 Summary: HID devices not detected after removal until Wine processes restart Product: Wine Version: 9.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Regression SHA1: 13a44865586f7697bb47bb48664ac0a90590a643 Distribution: Gentoo After 13a44865586 [1], at least dinput/xinput HID devices are not being re-detected until everything running in the specific Wine prefix has been terminated (winedevice?). Have not tested if Wine preocesses running on other prefixes have an effect as well. First observed with Final Fantasy XI Online, using a Sony DualShock 2 and 4 gamepads, bisected using a default clean prefix with 'wine control/joy.cpl' (for DualShock 4 hidraw is disabled due to 173ed7e61b5 [2]). Steps used to re-produce: - Run 'wine control' and 'Game Controllers' therein. - Select the 'XInput' tab for convenience. - Re-plug the gamepad. - At this point due to no automation for it being used in my set-up, adjust permissions on '/dev/input/event*' which corresponds to the device. - Observe the gamepad not re-appearing in the 'XInput' tab until every process from that prefix is terminated. It may take a few re-plugs for the issue to show itself; sometimes the devices will appear again, but once they don't, the Wine processes need to be restarted. Thank you! 1. https://gitlab.winehq.org/wine/wine/-/commit/13a44865586f7697bb47bb48664ac0… 2. https://gitlab.winehq.org/wine/wine/-/commit/173ed7e61b5b80ccd4d268e80c5c15… -- 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.

Sept. 5, 2024

[Bug 57157] winedbg: can't attach to windows process

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57157 Eric Pouech <eric.pouech(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech(a)gmail.com --- Comment #2 from Eric Pouech <eric.pouech(a)gmail.com> --- (In reply to Joe Breuer from comment #0) > I'm trying to debug a hang/freeze concerning Fallout 1 (it's still available > on Epic for free for a couple of hours, if someone should want to replicate > specifically). > > Got myself to a point to run winedbg against the game, provoke the hang (in > my case, I just need to press Escape to open the in-game save/options/... > menu). > > Now, I want to have a look where all threads of the game are. > > Wine-dbg>info process > pid threads executable (all id:s are in hex) > 00000168 6 'falloutwHR.exe' > 0000008c 3 'explorer.exe' > 00000038 8 'services.exe' > 000000e0 6 \_ 'rpcss.exe' > 000000c0 3 \_ 'svchost.exe' > 000000a8 4 \_ 'plugplay.exe' > 00000068 8 \_ 'winedevice.exe' > 00000044 8 \_ 'winedevice.exe' > 00000020 1 'start.exe' > 0000010c 1 \_ 'winedbg.exe' > =0000011c 1 \_ 'winedbg.exe' > >00000124 9 \_ 'Launcher.exe' > 00000114 1 \_ 'Launcher.exe' > 00000104 2 \_ 'conhost.exe' > > OK, so, switch to falloutwHR.exe first, I guess: > > Wine-dbg>attach 00000168 > syntax error > Wine-dbg>attach 168 > syntax error > > Um. What am I doing wrong? Or is there something really weird broken? - I > see that there's a testing package of wine 9.16 for my distro (gentoo), I'll > try that next. you need 'attach 0x168' instead of 'attach 168' -- 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.

Sept. 5, 2024

[Bug 57154] THQ Up demo crashes on start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57154 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com --- Comment #1 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- FYI: It starts fine here, no crash, but I haven't got a joystick attached so maybe you search in that direction -- 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.

Sept. 5, 2024

[Bug 57155] Gigapixel ai crashes on startup

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57155 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com --- Comment #3 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Levan from comment #2) > Strange thing is that changing wine to windows 7 fixed the issue Could you attach a (compressed) debug log in win10 mode (i.e. run with WINEDEBUG=+relay,+seh wine Topaz\ Gigapixel\ AI.exe &>debuglog.txt)? -- 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.

Sept. 5, 2024

[Bug 57155] Gigapixel ai crashes on startup

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57155 --- Comment #2 from Levan <levanchelidze(a)gmail.com> --- Strange thing is that changing wine to windows 7 fixed the issue -- 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.

Sept. 5, 2024

[Bug 57157] winedbg: can't attach to windows process

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57157 --- Comment #1 from Joe Breuer <winehq(a)jmbreuer.net> --- Using wine 9.16, I get a number of additional diagnostics concerning debug symbols, but ultimately the same error / focus does not switch to the falloutwHR.exe process: Wine-dbg>info process pid threads executable (all id:s are in hex) 00000174 6 'falloutwHR.exe' 00000088 4 'explorer.exe' 00000038 9 'services.exe' 000000ec 6 \_ 'rpcss.exe' 000000cc 3 \_ 'svchost.exe' 000000b4 4 \_ 'plugplay.exe' 00000068 9 \_ 'winedevice.exe' 00000044 8 \_ 'winedevice.exe' 00000020 1 'start.exe' 00000118 1 \_ 'winedbg.exe' =00000128 1 \_ 'winedbg.exe' >00000130 9 \_ 'Launcher.exe' 00000120 1 \_ 'Launcher.exe' 00000110 2 \_ 'conhost.exe' Wine-dbg>attach 00000174 012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file in module L"kernelbase" 012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file in module L"winhttp" 012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file in module L"advapi32" [...] 012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file in module L"netutils" 012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file in module L"schannel" 012c:err:dbghelp:pe_load_msc_debug_info -Debug info stripped, but no .DBG file in module L"rsaenh" syntax error Wine-dbg>info process pid threads executable (all id:s are in hex) 00000174 6 'falloutwHR.exe' 00000088 4 'explorer.exe' 00000038 9 'services.exe' 000000ec 6 \_ 'rpcss.exe' 000000cc 3 \_ 'svchost.exe' 000000b4 4 \_ 'plugplay.exe' 00000068 9 \_ 'winedevice.exe' 00000044 8 \_ 'winedevice.exe' 00000020 1 'start.exe' 00000118 1 \_ 'winedbg.exe' =00000128 1 \_ 'winedbg.exe' >00000130 9 \_ 'Launcher.exe' 00000120 1 \_ 'Launcher.exe' 00000110 2 \_ 'conhost.exe' Wine-dbg> -- 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.

Sept. 5, 2024