November 2020 - Wine-bugs - list.winehq.org

[Bug 42095] New: winamp needs to be restarted for skins to change
by wine-bugs＠winehq.org 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=42095 Bug ID: 42095 Summary: winamp needs to be restarted for skins to change Product: Wine Version: 2.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winetest(a)luukku.com Distribution: --- This winamp version can be used for testing. https://winamp.en.softonic.com/download -- 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 50096] New: Performance Regression in Secondhand Lands
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50096 Bug ID: 50096 Summary: Performance Regression in Secondhand Lands Product: Wine Version: 5.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: escomk3(a)hotmail.com Distribution: --- Created attachment 68573 --> https://bugs.winehq.org/attachment.cgi?id=68573 Good and Bad Terminal Output (+xranrd) After 9905a5a8 [1], the maximum FPS reached in Secondhand Lands can be around 5, when it is around 30-120 (120 being the maximum limit) depending on the situation before this commit. Running some quick profiling, there doesn't seem to be obvious (to me) differences between the good and the bad in that regard. Adding some TRACEs into the new code, I couldn't notice yet if anything there was being called a lot, but I did notice something that may or may not be a bit odd: In 'xrandr14_get_gpus2' [2] I'm seeing 'new_gpus: 4' and 'count: 3265744', which seems a "little bit" excessive (though I'm not sure if I'm doing things right at all, nor do I necessarily understand the code at all). This is how I was counting them: *new_gpus = gpus; TRACE("new_gpus: %d.\n"); *count = provider_resources->nproviders; TRACE("count: %d.\n", count); ret = TRUE; Download (no account is needed as the issues is visible in the main title menu already): - https://www.secondhandlands.com/download.php Some Winetricks are required to get the game running at all: - d3dx9_43 - d3dcompiler_43 Latest Wine version tested: - wine-5.20-234-gb793799d3d5 1. https://source.winehq.org/git/wine.git/commitdiff/9905a5a81d6baf59e992c5b2a… 2. https://source.winehq.org/git/wine.git/blob/9905a5a81d6baf59e992c5b2a8ea92e… -- 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 44524] New: skyrim keypad 0~9,'*','/' is not working causing some shortcut not work.
by wine-bugs＠winehq.org 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=44524 Bug ID: 44524 Summary: skyrim keypad 0~9,'*','/' is not working causing some shortcut not work. Product: Wine Version: 3.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw Distribution: --- when I playing, I notice one thing that keypad always not working in skyrim. It work on winecfg itself. It is annoy that I actually have some shortcut is set on keypad. without it, that shortcut is never work. -- 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 6

[Bug 50134] New: Steam terminates/crashes in clean prefix.
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50134 Bug ID: 50134 Summary: Steam terminates/crashes in clean prefix. Product: Wine Version: 5.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ionic(a)ionic.de Distribution: Gentoo Created attachment 68625 --> https://bugs.winehq.org/attachment.cgi?id=68625 Terminal output for Steam.exe, wine 5.21. I was hit by #50072, so decided to install Steam into a clean wine prefix with wine 5.21 to test this in a more reproducible environment. For convenience, I installed steam using "winetricks --no-isolate steam" into a non-existing prefix, thus creating it. The installer worked fine, but the subsequent self-update mechanism of Steam had to be started multiple times to finish. Afterwards, I started Steam with the "-no-cef-sandbox" parameter (not sure if it still has any effect nowadays) and *disabled* the accelerated web content rendering, then restarted Steam. Upon restart, even though no applications were installed and there's no visual indication of a download, the library window can be seen briefly, but shortly after, Steam just closes or crashes. The same behavior can be seen when using wine 5.17. I explicitly tested with this version to rule out any issues caused by some big core changes to DLL loading in 5.18. Just to make sure, I used the "corefonts" verb to pull in fonts needed by Chromium, but that likewise didn't change the outcome. -- 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 50197] New: cmd and winedbg: Unable to insert some chars (*, _) with de-adnw keyboard layout
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50197 Bug ID: 50197 Summary: cmd and winedbg: Unable to insert some chars (*, _) with de-adnw keyboard layout Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: joachim.priesner.bugs(a)web.de Distribution: --- To reproduce: $ setxkbmap de adnw Press Caps Lock + "G" (on a US keyboard) -> An asterisk "*" is inserted. $ wine winedbg or $ wine cmd Press Caps Lock + "G" again. Expected: An asterisk "*" is inserted Actual: The input is ignored. The same thing happens when trying to copy-paste an asterisk character from another application. Effectively, I am unable to insert some characters like _ and * in winedbg. I bisected the issue to the following commit: commit 54e117018cd4cc58c258da92686bfad13946bde2 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Mon Sep 21 17:07:29 2020 +0200 kernelbase: Use conhost to handle Unix consoles. Maybe the following lines in programs/conhost/conhost.c are responsible: + if (ir.Event.KeyEvent.uChar.UnicodeChar && !(ir.Event.KeyEvent.dwControlKeyState & LEFT_ALT_PRESSED)) + edit_line_insert( console, &ir.Event.KeyEvent.uChar.UnicodeChar, 1 ); introduced by commit 01d203eebf60a4f07be658e6a66d50909c90cf75 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Mon Sep 14 18:46:04 2020 +0200 conhost: Introduce IOCTL_CONDRV_READ_CONSOLE ioctl. It seems that the LEFT_ALT_PRESSED flag is set for that particular key combination although I did not press the left alt key (but rather Caps Lock). -- 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 50176] New: Tracing with 'msvcrt' debug channel causes any application to fail with stack overflow in Wine 5.22
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=50176 Bug ID: 50176 Summary: Tracing with 'msvcrt' debug channel causes any application to fail with stack overflow in Wine 5.22 Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, I was about to file a report when I saw it already fixed today with commit https://source.winehq.org/git/wine.git/commitdiff/1b053519755242a561feec91d… ("msvcrt: Remove traces from printf."). Still worth to track with a bug report because official Wine 5.22 release is affected (broken in between 5.21 and 5.22). --- snip --- $ wine --version wine-5.22 $ WINEDEBUG=+msvcrt wine notepad 0044:trace:msvcrt:DllMain stack overflow 2480 bytes in thread 0044 addr 0x7bc5005f stack 0x120650 (0x120000-0x121000-0x220000) 003c:trace:msvcrt:DllMain stack overflow 1156 bytes in thread 003c addr 0xf7ce8acf stack 0x220b7c (0x220000-0x221000-0x320000) 004c:trace:msvcrt:DllMain stack overflow 2288 bytes in thread 004c addr 0x7bc5005f stack 0x120710 (0x120000-0x121000-0x220000) --- snip --- Regards -- 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 15301] New: Biliardo 2 installer terminates on launch
by wine-bugs＠winehq.org 04 Dec '20

04 Dec '20

http://bugs.winehq.org/show_bug.cgi?id=15301 Summary: Biliardo 2 installer terminates on launch Product: Wine Version: CVS/GIT Platform: PC URL: http://web.tiscali.it/chiesi/software/ita/biliardo2.html OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nodisgod(a)yahoo.com Created an attachment (id=16125) --> (http://bugs.winehq.org/attachment.cgi?id=16125) Biliardo 2 relay log (rzipped) With current Git (wine-1.1.4-392-gaf78a7b), when attempting to launch the Biliardo 2 installer, a window momentarily appears, but the installer terminates without any further messages. From examination of relay traces, there seems to be an exception being raised while the installer runs, possibly causing the termination. -- 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 17

[Bug 21881] New: iScreensaver Designer 3.5 has encountered a problem.
by wine-bugs＠winehq.org 04 Dec '20

04 Dec '20

http://bugs.winehq.org/show_bug.cgi?id=21881 Summary: iScreensaver Designer 3.5 has encountered a problem. Product: Wine Version: unspecified Platform: x86 OS/Version: Mac OS X 10.5 Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: reedercolin(a)gmail.com A window comes up saying that iScreensaver.exe encountered a serious problem. -- 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 15

[Bug 35272] New: Mortal Kombat Komplete Edition (Steam) crashing to desktop within graphics autoconf.
by wine-bugs＠winehq.org 04 Dec '20

04 Dec '20

http://bugs.winehq.org/show_bug.cgi?id=35272 Bug ID: 35272 Summary: Mortal Kombat Komplete Edition (Steam) crashing to desktop within graphics autoconf. Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: linards.liepins(a)gmail.com CC: wine-bugs(a)winehq.org Classification: Unclassified Created attachment 47044 --> http://bugs.winehq.org/attachment.cgi?id=47044 Terminal output See attached terminal output. Linux Mint 16 Petra Cinnamon x64 ; AMD Radeon 5750 ; Wine 1.7.8 -- 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 49437] New: Segmentation fault (core dumped) even on winecfg or wineconsole on FreeBSD
by WineHQ Bugzilla 04 Dec '20

04 Dec '20

https://bugs.winehq.org/show_bug.cgi?id=49437 Bug ID: 49437 Summary: Segmentation fault (core dumped) even on winecfg or wineconsole on FreeBSD Product: Wine Version: 5.11 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com For the moment, I stick with wine-5.8 which is actually perfectly working for me. Since wine-5.9, it won't run anymore. It builds, it installs but it won't start and I really have no other message than "Segmentation fault (core dumped)" I build wine without any patch in case this creates the issue (already happened a few months ago). All information I succeeded to have is by using WINEDEBUG=all trace:virtual:NtAllocateVirtualMemory 0xffffffff 0x7ffe0000 00001000 3000 00000002 Segmentation fault (core dumped) That's all I get and I don't even know if it's related to the problem. -- 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 24