April 2019 - Wine-bugs - list.winehq.org

[Bug 40104] New: ReplayGain by Foobar
by wine-bugs＠winehq.org 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=40104 Bug ID: 40104 Summary: ReplayGain by Foobar Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adl-88(a)posteo.de Distribution: --- ReplayGain by Foobar gains only with standardoptions and it ignores every change. So if I want to write with "+0.0db" to get "89db" on a track he will do this. But if I want to write with "+6,00" to get "95db" on a track he also writes with "0,0db". It seems that its a debian versions problem. Ubuntu versions works fine. But I dont use ubuntu anymore. -- 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 9901] New: GetMonitorInfo returns wrong work area
by wine-bugs＠winehq.org 27 Aug '22

27 Aug '22

http://bugs.winehq.org/show_bug.cgi?id=9901 Summary: GetMonitorInfo returns wrong work area Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-x11driver AssignedTo: wine-bugs(a)winehq.org ReportedBy: lich(a)math.spbu.ru GetMontorInfo always returns rcWork equal to rcMonitor, but it must take panels and taskbars into account. The only solution I can see is to use SystemParametersInfo(SPI_SETWORKAREA) during initialization time, but I do not know how to deal with different monitors. P.S. It is needed to properly implement maximum dimensions of console window. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 30

[Bug 43193] New: MinGW-w64 GUI installer fails 66 per cent through its file-installation page.
by wine-bugs＠winehq.org 25 Aug '22

25 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=43193 Bug ID: 43193 Summary: MinGW-w64 GUI installer fails 66 per cent through its file-installation page. Product: Wine-staging Version: 2.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: irwin(a)beluga.phys.uvic.ca CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- My platform is Debian Jessie, and I am using the WineHQ repository for that distro following the advice at <https://wine-staging.com/installation.html>. I installed the latest version (2.10) of winehq-staging and set the environment variables export WINEVERSION=2.10_jessie_wine_staging export WINEPREFIX=/home/wine/wine_staging/.wine-$WINEVERSION export WINEDEBUG='fixme-all' and ran winecfg taking defaults for everything. Then wine(a)raven> wine --version wine-2.10 (Staging) wineserver -p nice -19 wine msys2-x86_64-20161025.exe Welcome screen, set prefix (added date string to default location), start menu shortcuts left as they were, then install page went to the 66 per cent level and then generated a Program Error GUI box with the message The program bash.exe has encountered a serious error and needs to close. We are sorry for the inconvenience. Program error details page on GUI was empty. stderr (or stdout) had the following messages on the konsole instance I was running: err:ole:CoCreateInstanceEx apartment not initialised err:ole:CoCreateInstanceEx apartment not initialised err:ole:CoCreateInstanceEx apartment not initialised wine: Unhandled page fault on read access to 0x00000020 at address 0x7bc4b478 (thread 0045), starting debugger... The installer GUI details showed the install failed (at the ~66 per cent mark) while installing nansi.sys. This is definitely a wine-staging bug because the equivalent experiment with vanilla wine-2.10 (obtained by purging winehq-staging and installing winehq-devel) had no troubles with that install page of the GUI (although the above "apartment" warnings were produced), but failed in other ways on the final page of that GUI. Note it is likely this current wine-staging bug with the initial file installation has been introduced in the past year since <https://github.com/TeaCI/tea-ci/wiki/Msys2-on-Wine> implies MSYS2 works on Wine-staging, and that page was last updated in July last year. However, introduction of this wine-staging bug is not extremely recent because I replicated this bug also for wine-staging 2.4 (the earliest version [released March 2017] currently available for the winehq Debian Jessie 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 14

[Bug 29614] New: WinRAR viewer crashes on a particular file
by wine-bugs＠winehq.org 22 Aug '22

22 Aug '22

http://bugs.winehq.org/show_bug.cgi?id=29614 Bug #: 29614 Summary: WinRAR viewer crashes on a particular file Product: Wine Version: 1.3.37 Platform: x86 URL: http://www.rarlabs.com/rar/wrar401.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: t.artem(a)mailcity.com Classification: Unclassified Created attachment 38365 --> http://bugs.winehq.org/attachment.cgi?id=38365 Test file When trying to view the attached file, WinRAR crashes. Steps to reproduce, download the file, install and run WinRAR, click Commands -> View File (Alt + V). (Viewer settings: view as Windows text, word wrap enabled). caret.c:208: ME_GetCursorCoordinates: Assertion `~para->member.para.nFlags & 0x01' failed. wine: Assertion failed at address 0xb776f424 (thread 0046), starting debugger... Unhandled exception: assertion failed in 32-bit code (0xb776f424). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:b776f424 ESP:00322904 EBP:0032291c EFLAGS:00000202( - -- I - - - ) EAX:00000000 EBX:00006589 ECX:00006589 EDX:00000006 ESI:b758b74a EDI:b75c7ff4 Stack dump: 0x00322904: 0032291c 00000006 00006589 b746d2f1 0x00322914: b75c7ff4 00322a3c 00322a44 b746ed5e 0x00322924: 00000006 003229bc 00000000 b75c7ff4 0x00322934: 00000060 00000001 00322a54 00322980 0x00322944: 00000000 00000068 0000005c b75c93a0 0x00322954: b75c7ff4 0000005c 0000005b 00322a2c Backtrace: =>0 0xb776f424 __kernel_vsyscall+0x10() in [vdso].so (0x0032291c) 1 0xb746d2f1 gsignal+0x50() in libc.so.6 (0x0032291c) 2 0xb746ed5e abort+0x17d() in libc.so.6 (0x00322a44) 3 0xb7465c08 __assert_fail+0xf7() in libc.so.6 (0x00322a8c) 4 0x7dbc5657 ME_MoveCaret+0x496() in riched20 (0x00322b5c) 5 0x7dbd79c2 ME_PaintContent+0xc1() in riched20 (0x00322c0c) 6 0x7dbd399d RichEditWndProc_common+0x3bc() in riched20 (0x00322ccc) 7 0x7dbd3ccc RichEditWndProcW+0x2b() in riched20 (0x00322cfc) 8 0x7ec2b4ea WINPROC_wrapper+0x19() in user32 (0x00322d2c) 9 0x7ec2bc3c call_window_proc+0x5b() in user32 (0x00322d7c) 10 0x7ec2e10d WINPROC_call_window+0x10c() in user32 (0x00322dcc) 11 0x7ebf0b0e DispatchMessageW+0x9d() in user32 (0x00322ebc) 12 0x0049aa76 in winrar (+0x9aa75) (0x00328308) 13 0x7dbcf53b ME_HandleMessage+0xcba() in riched20 (0x00328c48) 14 0x7dbd3764 RichEditWndProc_common+0x183() in riched20 (0x00328d08) 15 0x7dbd3ccc RichEditWndProcW+0x2b() in riched20 (0x00328d38) 16 0x7ec2b4ea WINPROC_wrapper+0x19() in user32 (0x00328d68) 17 0x7ec2bc3c call_window_proc+0x5b() in user32 (0x00328db8) 18 0x7ec2e10d WINPROC_call_window+0x10c() in user32 (0x00328e08) 19 0x7ebeec61 call_window_proc+0x90() in user32 (0x00328e78) 20 0x7ebf5456 send_message+0x205() in user32 (0x00328ef8) 21 0x7ebf58cc SendMessageW+0x4b() in user32 (0x00328f48) 22 0x0049dbf5 in winrar (+0x9dbf4) (0x7ebf5880) 23 0x458b48ec (0x83e58955) 0xb776f424 __kernel_vsyscall+0x10 in [vdso].so: popl %ebp Modules: ... Backtrace: =>0 0xb776f424 __kernel_vsyscall+0x10() in [vdso].so (0x0032291c) 1 0xb746d2f1 gsignal+0x50() in libc.so.6 (0x0032291c) 2 0xb746ed5e abort+0x17d() in libc.so.6 (0x00322a44) 3 0xb7465c08 __assert_fail+0xf7() in libc.so.6 (0x00322a8c) 4 0x7dbc5657 ME_MoveCaret+0x496() in riched20 (0x00322b5c) 5 0x7dbd79c2 ME_PaintContent+0xc1() in riched20 (0x00322c0c) 6 0x7dbd399d RichEditWndProc_common+0x3bc() in riched20 (0x00322ccc) 7 0x7dbd3ccc RichEditWndProcW+0x2b() in riched20 (0x00322cfc) 8 0x7ec2b4ea WINPROC_wrapper+0x19() in user32 (0x00322d2c) 9 0x7ec2bc3c call_window_proc+0x5b() in user32 (0x00322d7c) 10 0x7ec2e10d WINPROC_call_window+0x10c() in user32 (0x00322dcc) 11 0x7ebf0b0e DispatchMessageW+0x9d() in user32 (0x00322ebc) 12 0x0049aa76 in winrar (+0x9aa75) (0x00328308) 13 0x7dbcf53b ME_HandleMessage+0xcba() in riched20 (0x00328c48) 14 0x7dbd3764 RichEditWndProc_common+0x183() in riched20 (0x00328d08) 15 0x7dbd3ccc RichEditWndProcW+0x2b() in riched20 (0x00328d38) 16 0x7ec2b4ea WINPROC_wrapper+0x19() in user32 (0x00328d68) 17 0x7ec2bc3c call_window_proc+0x5b() in user32 (0x00328db8) 18 0x7ec2e10d WINPROC_call_window+0x10c() in user32 (0x00328e08) 19 0x7ebeec61 call_window_proc+0x90() in user32 (0x00328e78) 20 0x7ebf5456 send_message+0x205() in user32 (0x00328ef8) 21 0x7ebf58cc SendMessageW+0x4b() in user32 (0x00328f48) 22 0x0049dbf5 in winrar (+0x9dbf4) (0x7ebf5880) 23 0x458b48ec (0x83e58955) -- 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 32

[Bug 37873] New: Pokemon TCGO version 4.5.5 crashes during startup
by wine-bugs＠winehq.org 21 Aug '22

21 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=37873 Bug ID: 37873 Summary: Pokemon TCGO version 4.5.5 crashes during startup Product: Wine Version: 1.7.3 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lppoulin(a)gmail.com Distribution: --- Pokemon TCGO version 4.X.X used to work perfectly. In December 2014, after an auto-update to version 4.5.5 it started to crash at startup. Has anyone been able to make it 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 13

[Bug 47016] New: MS Office 365 installer stops midway with error 30175-4
by wine-bugs＠winehq.org 18 Aug '22

18 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=47016 Bug ID: 47016 Summary: MS Office 365 installer stops midway with error 30175-4 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 64173 --> https://bugs.winehq.org/attachment.cgi?id=64173 Log for 4.5 staging Trying to install MS Office 365 ja_JP/Business retail edition. Installer starts and runs until around the 68% mark, where it reports error 30175-4 and closes. A quick search found that this error indicates that the installer is trying to upgrade Office 2013 to Office 2016, which it seems to be trying to do when wine is set to Windows 7. Tested with 4.5 staging, log attached. Did not use winetricks except to add japanese fonts to registry. -- 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 28750] New: Access violations and OLE errors using a WebBrowser based sample application
by wine-bugs＠winehq.org 17 Aug '22

17 Aug '22

http://bugs.winehq.org/show_bug.cgi?id=28750 Bug #: 28750 Summary: Access violations and OLE errors using a WebBrowser based sample application Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: mshtml AssignedTo: wine-bugs(a)winehq.org ReportedBy: idw.doc(a)t-online.de Classification: Unclassified PLease download and run my sample application for duplicating the crash(es), I'm not using Wine myself, but user's of my sample application reported several fatal errors when launching it: It's a simple HTML editor based on the IWebBrowser and MSHTML interfaces, available at <http://idw-doc.homepage.t-online.de/PMUtils/IEWriter.zip>. A single URL parsing issue (in shlwapi) has already been fixed, see <http://source.winehq.org/patches/data/79958>. -- 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 25817] New: FlashGet 1.73 dropzone is broken
by wine-bugs＠winehq.org 15 Aug '22

15 Aug '22

http://bugs.winehq.org/show_bug.cgi?id=25817 Summary: FlashGet 1.73 dropzone is broken Product: Wine Version: 1.3.11 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: igor-hkr(a)mail.ru Created an attachment (id=32902) --> (http://bugs.winehq.org/attachment.cgi?id=32902) screenshot FlashGet 1.73 dropzone doesn't has picture/logo of program. ( http://down6.flashget.com/fgf173.exe ) -- 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 29994] New: SDP Downloader: Marking URL in textbox doesn't work
by wine-bugs＠winehq.org 15 Aug '22

15 Aug '22

http://bugs.winehq.org/show_bug.cgi?id=29994 Bug #: 29994 Summary: SDP Downloader: Marking URL in textbox doesn't work Product: Wine Version: 1.4-rc5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: atalanttore(a)googlemail.com Classification: Unclassified Hi, there's another little problem within the GUI of SDP Downloader 2.3.0 [1], which is not present on Windows. 1) Start SDP Downloader 2.3.0 2) File -> Open 3) And an URL 4) OK 5) File -> Open -- 6a) Click once in the URL box and press Ctrl + A. 7a) On Windows, the URL is marked, but on Wine: nothing. --- 6b) Click three times in the URL box. 7b) On Windows, the whole URL is marked, but on Wine only a part of the URL or nothing will be marked. [1] http://sdp.ppona.com/ -- 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 43516] New: GCC march=native Flag Causes " Unhandled Pagefault on Write"
by wine-bugs＠winehq.org 15 Aug '22

15 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=43516 Bug ID: 43516 Summary: GCC march=native Flag Causes "Unhandled Pagefault on Write" Product: Wine Version: 2.14 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ben(a)xnode.org Distribution: --- I've run into a specific crash that only happens with using the "-march=native" GCC flag at build time (usage of -O3 or -O2 don't affect it). Removing "march" entirely stops the crash from occurring. This is on a Intel Broadwell i7-5775C using GCC 7.1.1. Triggering the crash is unfortunately a bit specific: The crash occurs when loading Mario Kart 8 in CEmu (1.8) under a 64bit Wine prefix. The exact moment it happens is once the game's splash screen appears - pressing A should then take you to the menu, but instead if Wine has been built with march=native, it'll throw an Unhandled Pagefault at this point instead: "wine: Unhandled page fault on write access to 0x7f7fda6f0080 at address 0x1400e1867 (thread 005f), starting debugger..." According to GCC, the flags it activates when using march=native on this platform are: -march=broadwell -mmmx -mno-3dnow -msse -msse2 -msse3 -mssse3 -mno-sse4a -mcx16 -msahf -mmovbe -maes -mno-sha -mpclmul -mpopcnt -mabm -mno-lwp -mfma -mno-fma4 -mno-xop -mbmi -mno-sgx -mbmi2 -mno-tbm -mavx -mavx2 -msse4.2 -msse4.1 -mlzcnt -mrtm -mhle -mrdrnd -mf16c -mfsgsbase -mrdseed -mprfchw -madx -mfxsr -mxsave -mxsaveopt -mno-avx512f -mno-avx512er -mno-avx512cd -mno-avx512pf -mno-prefetchwt1 -mno-clflushopt -mno-xsavec -mno-xsaves -mno-avx512dq -mno-avx512bw -mno-avx512vl -mno-avx512ifma -mno-avx512vbmi -mno-avx5124fmaps -mno-avx5124vnniw -mno-clwb -mno-mwaitx -mno-clzero -mno-pku -mno-rdpid --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=6144 -mtune=broadwell -fPIE -fstack-check=specific -fstack-protector-strong (in case any of those stand out as being an issue when used with 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.

2 4