February 2023 - Wine-Bugs - list.winehq.org

[Bug 48068] New: Mostly black window in Epic Games Launcher
by WineHQ Bugzilla Aug. 27, 2024

Aug. 27, 2024

https://bugs.winehq.org/show_bug.cgi?id=48068 Bug ID: 48068 Summary: Mostly black window in Epic Games Launcher Product: Wine Version: 4.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: michelle(a)iheartmichelle.com Distribution: --- Created attachment 65617 --> https://bugs.winehq.org/attachment.cgi?id=65617 Output of % wine {Prefix}/drive_c/Program Files (x86)/Epic Games/Launcher/Portal/Binaries/Win64/EpicGamesLauncher.exe -SkipBuildPatchPrereq I have installed the Epic Games Launcher. It opens up with a mostly black window. However, the app draws its own window controls, such as minimize and close, and those work. Also, there's a "Settings" icon in the corner. When I click that, it takes me to a settings screen which appears to work. However, the rest of the window is black and I cannot install the untitled goose game, as I so desperately want to do. I'm using wine 4.19-staging. The Epic Games Launcher version ... well, I have a story about that: While I was gathering info for this bug report, I started the launcher and this time, the "Settings" icon had a dot on it. So I clicked the Settings icon, and it said there was a new version of the launcher and I should click here to install the new version and restart the launcher, and I did and it worked. So at least that much of the app is working. Anyway, the version (which is visible from the Settings screen) is now 10.9.1-10088168+++Portal+Release-Live I don't think this is related to the ancient #40376 since that was last updated 2 years ago and seems to be caused by a bug which was fixed in a prior version of 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 20

[Bug 54561] New: Google Chrome unable to load widevine_cdm.dll 4.10.2557.0 (and up)
by WineHQ Bugzilla Aug. 26, 2024

Aug. 26, 2024

https://bugs.winehq.org/show_bug.cgi?id=54561 Bug ID: 54561 Summary: Google Chrome unable to load widevine_cdm.dll 4.10.2557.0 (and up) Product: Wine Version: 8.2 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: --- Created attachment 74101 --> https://bugs.winehq.org/attachment.cgi?id=74101 WINEDEBUG=warn+all /usr/bin/wine-vanilla-9999 GoogleChromePortable64/App/Chrome-bin/chrome.exe --no-sandbox Google Chrome is currently unable to load widevine_cdm.dll as of version 4.10.2557.0. Version 4.10.2449.0 of widevine_cdm.dll (for instance shipped/bundled with Google Chrome 105.0.5195.127) will load just fine, but is now useless, since most streaming services have blocked this old version by now. I've tested with wine 8.2 (I'm currently using git master from about a week ago, built 20.02.2023), but the behavior shows also up with older wine versions, down to 7.0. My main use case is to watch content on Amazon Prime in Full HD resolution - which is now impossible. I'm also attaching a warn+all log, but the relevant part, as far as I can tell, is this one: 033c:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised 033c:warn:module:process_attach Initialization of L"widevinecdm.dll" failed [824:828:0223/065058.326:ERROR:cdm_module.cc(114)] CDM at C:\users\ionic\AppData\Local\Google\Chrome\User Data\WidevineCdm\4.10.2557.0\_platform_specific\win_x64\widevinecdm.dll could not be loaded. [824:828:0223/065058.326:ERROR:cdm_module.cc(115)] Error: 998 Error 998, conveniently, is ERROR_NOACCESS, which doesn't seem surprising given the previous access violation. I honestly don't know if this issue is caused by wine itself, especially since older versions of the widevine library still load just fine. For testing this, I recommend installing the current version of Google Chrome, either normally or using the (64 Bit testing) version of Google Chrome Portable and starting video playback on https://www.nuevodevel.com/nuevo/showcase/drm , which embeds the free Big Buck Bunny video in a Widevine-based DRM setting. Note, however, that downgrading to widevine 4.10.2449.0 will make it work - but Amazon Prime will complain about an outdated browser version (which is a lie, because it really [also] checks the widevine version) and refuse to play any content. -- 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 48614] New: Windows 10 Opera browser hangs/freezes immediatly on install using Wine 4.1 linux x86/64bit
by WineHQ Bugzilla Aug. 26, 2024

Aug. 26, 2024

https://bugs.winehq.org/show_bug.cgi?id=48614 Bug ID: 48614 Summary: Windows 10 Opera browser hangs/freezes immediatly on install using Wine 4.1 linux x86/64bit Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stevedonato(a)gmail.com Distribution: --- trying to use windows 10 Opera browser because native linux browser nolonger can run Amazon Prime Videos. Tried playing NEW Amazon Prime tv series called "Hunter" at https://www.amazon.com/gp/video/detail/B07ZPF4DVK/ref=atv_dl_rdr?autoplay=1 Gets Digital rights error. Win 10 version of Opera works OK. Linux and Windows version of Opera have no option to enable DRM, also called "Widevine". The error msg text is"A later version of Opera is required for Prime Video. To check for updates, click the Opera menu, click About Opera, and then click Relaunch Now." But I am using latest Oper ver 66. also tried the Developer and Beta versions of Oper ver 67 and 68. Same error. Oddly, the windows 10 version of Opera was even older,at ver 63 but it worked? Something to do with HTML5 videos and DRM/Widevine ? -- 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 52539] New: foobar2000 undocking from system tray works randomly
by WineHQ Bugzilla Aug. 26, 2024

Aug. 26, 2024

https://bugs.winehq.org/show_bug.cgi?id=52539 Bug ID: 52539 Summary: foobar2000 undocking from system tray works randomly Product: Wine Version: 7.1 Hardware: x86-64 URL: https://www.foobar2000.org/getfile/foobar2000_v1.6.9.e xe OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: lukasz.wojnilowicz(a)gmail.com Distribution: Fedora Created attachment 71844 --> https://bugs.winehq.org/attachment.cgi?id=71844 foobar2000 undocked after 5 LMB clicks Steps to reproduce: 1) remove ~/.wine 2) install foobar2000 3) wine foobar2000.exe 4) in menubar select "Library->Configure" 5) in configuration tree select "Display->Default User Interface->Background and Notifications" 6) Under "Window minimize and close" select "Minimize hides, close exits" 7) Under "Notification area icon" select "Show only when foobar2000 is hidden" 8) In the right top corner press minimize icon 9) foobar2000 minimizes to the system tray 10) LMB click on an icon of foobar2000 in the system tray Behaviour: foobar2000 icon in the system tray flashes but its main window is not restored. After a couple of clicks it gets restored (see the attached movie). Expected behaviour: foobar2000 main window should be restored after first click on its system tray icon every time. Additional comment: 1) using KDE Plasma 5.23.5 X11 on Fedora 35 2) nothing shows in the terminal when docking/undocking foobar2000 3) "journalctl -f -g xembedsniproxy" gives kde.xembedsniproxy: adding damage watch for 85983387 kde.xembedsniproxy: Received click 1 with passed x*y 1052 784 kde.xembedsniproxy: Click point: QPoint(4,4) kde.xembedsniproxy: trying to undock window 85983387 kde.xembedsniproxy: trying to dock window 85983392 kde.xembedsniproxy: adding damage watch for 85983392 kde.xembedsniproxy: Received click 1 with passed x*y 1053 783 kde.xembedsniproxy: Click point: QPoint(4,4) kde.xembedsniproxy: trying to undock window 85983392 Until foobar2000 window is finally restored. -- 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 49390] New: ETaskbarException in CSS HTML Validator 2020 and Batch Wizard
by WineHQ Bugzilla Aug. 26, 2024

Aug. 26, 2024

https://bugs.winehq.org/show_bug.cgi?id=49390 Bug ID: 49390 Summary: ETaskbarException in CSS HTML Validator 2020 and Batch Wizard Product: Wine Version: 5.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: support(a)htmlvalidator.com Distribution: --- Created attachment 67458 --> https://bugs.winehq.org/attachment.cgi?id=67458 Screenshots of user email reporting the bug Download and install CSS HTML Validator Pro Trial 2020: https://www.htmlvalidator.com/css-html-validator-trial-setup.exe Perform the following steps to reproduce the exception which causes program malfunction: 1. Open CSS HTML Validator (version 20.03, under Wine 5.10 on Arch Linux, bare metal) 2. Main Menu Bar > Tools > Batch Wizard 3. In the Batch Wizard dialog, do Options > Force Toolbar 4. If necessary, increase width of the Batch Wizard dialog, so that the entire toolbar is visible. 5. Click the "Add Target" button. 6. Click the "Add file target(s)" option (or any other of the three options). 7. Select an HTML file, and click the "Open" button. 8. In the toolbar, click the "Start" button. 9. In the "HTML Validator: Confirm Job" dialog, click the "Start processing now" option. 10. The "ETaskbarException: Could not register tab." error window appears. 11. Program ceases to function properly after exception (i.e. cannot be closed properly). Also see attachments which are screenshots provided by a user. Sidenote: Toolbar (which contains the "New List" button) is still not displaying properly as it displays fully justified when it should display left justified. Can see this in the first screenshot (EmailPart1.png) in the attachment. -- 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 20456] New: FEAR's installer will not let me enter the serial number
by wine-bugs＠winehq.org Aug. 25, 2024

Aug. 25, 2024

http://bugs.winehq.org/show_bug.cgi?id=20456 Summary: FEAR's installer will not let me enter the serial number Product: Wine Version: 1.1.32 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: wylda(a)volny.cz Hi, F.E.A.R. installer requires entering serial number. It has several fields for entering 4 characters (clasic 1234-5678-9abc-def0-1234). I can enter: * 4 "narrow" chars like 1111, iiii, etc. or * only 3 "fat" chars like AAA, CCC, etc. or * only 2 "extra fat" like WW There are other pepole affected in AppDB: http://appdb.winehq.org/objectManager.php?sClass=version&iId=5159&iTestingI… http://appdb.winehq.org/objectManager.php?sClass=version&iId=5159&iTestingI… Based on other confirmations in AppDB consider UNCONFIRMED->NEW. Tested wine versions: 0.9.50, 0.9.60, 1.0.1, 1.1.7, 1.1.10, 1.1.13, 1.1.22, 1.1.29, 1.1.31, 1.1.32 ...so it probably never worked correctly. This is show stopper. I own two original and none is usable under wine because of too wide chars in serial :-/ -- 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 67

[Bug 49623] New: winedevice high cpu load over all the time
by WineHQ Bugzilla Aug. 25, 2024

Aug. 25, 2024

https://bugs.winehq.org/show_bug.cgi?id=49623 Bug ID: 49623 Summary: winedevice high cpu load over all the time Product: Wine Version: 5.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dieter.ferdinand(a)gmx.de Distribution: Other hello, i have a big problem with winedevice of different versions of wine. after the last updates of my system, i see, that winedevice need over 90% (most 99%) of cpu-time over hours and days. so my system must run all the time with highest possible cpu-clock and i can't like this. so i try to find out why this happens and because udisksd need also much cpu-time, i kill it and lock it for automatic restart, so i can start it, if i need it. after that, i see, that winedevice no more need over 90% cpu-time. because i deaktivate udisks always in the past, i think, i don't have this problem with winedevice. but every update of udisks will reaktivate it again and after some days, i deaktivate it again. udisks is a nice program, but i can't like it, if one program kill all powersaving functions of my system which runs 24 hours a day. since i deaktive udisks, i have no more problems with winedevice. i will deactive usage of udisks for wine to solve this problem. goodby -- 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 51162] New: Xfce systray icons have a background of a next icon
by WineHQ Bugzilla Aug. 25, 2024

Aug. 25, 2024

https://bugs.winehq.org/show_bug.cgi?id=51162 Bug ID: 51162 Summary: Xfce systray icons have a background of a next icon Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fin4478(a)hotmail.com Distribution: --- Created attachment 70030 --> https://bugs.winehq.org/attachment.cgi?id=70030 Xfce4.16 systray bug Systray icons have a background of a next icon when running Ubisoft Connect, Steam and Epic Games launchers. Switching the desktop compositor on and off changes the background between blank and the next icon. The network icon is from connman-gtk. Version: xfce4-panel 4.16.2. OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.41.0 5.13.0-rc2 LLVM 12.0.0) v: 4.6 Mesa 21.2.0-devel (git-0df249f 2021-05-19 focal-oibaf-ppa) I inspected source code of the Xfce4 systray plugin and the problem is not solvable 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 3

[Bug 49990] New: Gray window for Minecraft Dungeons Launcher & Riot Client
by WineHQ Bugzilla Aug. 25, 2024

Aug. 25, 2024

https://bugs.winehq.org/show_bug.cgi?id=49990 Bug ID: 49990 Summary: Gray window for Minecraft Dungeons Launcher & Riot Client Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: iroalexis(a)outlook.fr Distribution: --- Created attachment 68393 --> https://bugs.winehq.org/attachment.cgi?id=68393 Wine log for Minecraft Dungeons Launcher It is impossible to launch applications that ask to display a "Windows interface" such as the login window Riot and/or Minecraft Dungeons Launcher. I get an empty gray window. The commit https://source.winehq.org/git/wine.git/commit/bd27af974a21085cd0dc78b37b715… provoc this 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 44

[Bug 43680] New: Epic Games Launcher crashes if tool-tip is shown in D3D11 mode
by wine-bugs＠winehq.org Aug. 25, 2024

Aug. 25, 2024

https://bugs.winehq.org/show_bug.cgi?id=43680 Bug ID: 43680 Summary: Epic Games Launcher crashes if tool-tip is shown in D3D11 mode Product: Wine Version: 2.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: plata(a)mailbox.org Distribution: --- Tested with Wine staging 2.16. How to reproduce: - run EpicGamesLauncher.exe (maybe you need the "-SkipBuildPatchPrereq" parameter) - wait until the login window is shown - everything seems to be ok - move the mouse over one of the fields where you can enter email/password - the window starts to flicker and finally EpicGamesLauncher.exe crashes If you launch EpicGamesLauncher.exe with "-OpenGL", you do not get the crash. Therefore I assume that it is a problem with D3D11. -- 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 2