https://bugs.winehq.org/show_bug.cgi?id=57635
Bug ID: 57635 Summary: Battle.net Launcher invisible/black with the Wayland driver Product: Wine Version: 10.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs@winehq.org Reporter: wine@xarov.net Distribution: ArchLinux
Created attachment 77764 --> https://bugs.winehq.org/attachment.cgi?id=77764 Black window with Wayland driver
Works fine with the X11 driver. Is completely black with the Wayland driver.
https://bugs.winehq.org/show_bug.cgi?id=57635
--- Comment #1 from wine@xarov.net --- The UI elements still exist underneath the black window, as the mouse cursor changes to a hand and finger when hovered over those elements. They're clickable too.
If I click exactly where the "Play" button is for World of Warcraft, the game launches and it's using the Wayland driver. No issues playing the game, both keyboard and mouse inputs work.
Just the launcher is black, that's the issue.
https://bugs.winehq.org/show_bug.cgi?id=57635
wine@xarov.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|10.0-rc4 |10.0-rc5
https://bugs.winehq.org/show_bug.cgi?id=57635
wine@xarov.net changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=57336
https://bugs.winehq.org/show_bug.cgi?id=57635
wine@xarov.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|10.0-rc5 |10.0-rc6
https://bugs.winehq.org/show_bug.cgi?id=57635
Giacomo Orlandi gia_@inwind.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gia_@inwind.it
--- Comment #2 from Giacomo Orlandi gia_@inwind.it --- I wonder if this is the same issue as Bug 56014
https://bugs.winehq.org/show_bug.cgi?id=57635
--- Comment #3 from wine@xarov.net --- (In reply to Giacomo Orlandi from comment #2)
I wonder if this is the same issue as Bug 56014
Interesting. I didn't think of that. I actually am using WoW64. I might try without it and see if the issue persists.
Would that mean it's a WoW64 issue or still a Wayland issue if that's the case?
https://bugs.winehq.org/show_bug.cgi?id=57635
wine@xarov.net changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=56014
https://bugs.winehq.org/show_bug.cgi?id=57635
wine@xarov.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|10.0-rc6 |10.0
https://bugs.winehq.org/show_bug.cgi?id=57635
--- Comment #4 from wine@xarov.net --- I can confirm that the issue is not related to WoW64, as non-WoW64 Wine also exhibits this problem.
https://bugs.winehq.org/show_bug.cgi?id=57635
wine@xarov.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|10.0 |10.1
http://bugs.winehq.org/show_bug.cgi?id=57635
Joachim joachim.ionoff@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joachim.ionoff@gmail.com
--- Comment #5 from Joachim joachim.ionoff@gmail.com --- I'm experiencing same issue with wine 10.7 and 10.8.
http://bugs.winehq.org/show_bug.cgi?id=57635
Joachim joachim.ionoff@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|joachim.ionoff@gmail.com |
http://bugs.winehq.org/show_bug.cgi?id=57635
Joachim joachim.ionoff@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joachim.ionoff@gmail.com
--- Comment #6 from Joachim joachim.ionoff@gmail.com --- Still same issue on wine 10.12
http://bugs.winehq.org/show_bug.cgi?id=57635
Joachim joachim.ionoff@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|joachim.ionoff@gmail.com |
http://bugs.winehq.org/show_bug.cgi?id=57635
--- Comment #7 from Ken Sharp imwellcushtymelike@gmail.com --- Do you have to log in to test this?
http://bugs.winehq.org/show_bug.cgi?id=57635
--- Comment #8 from wine@xarov.net --- (In reply to Ken Sharp from comment #7)
Do you have to log in to test this?
Yes. Because the initial login window box is displaying correctly. The launcher is the issue. It's completely black. After logging in.
However, it is fixed by using the `--in-process-gpu` argument for the executable. It's an Electron flag and I'm guessing the launcher is Electron or Chromium based.
http://bugs.winehq.org/show_bug.cgi?id=57635
Patrick patrick.vliex@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |patrick.vliex@protonmail.ch
--- Comment #9 from Patrick patrick.vliex@protonmail.ch --- (In reply to John Smith from comment #8)
(In reply to Ken Sharp from comment #7)
Do you have to log in to test this?
Yes. Because the initial login window box is displaying correctly. The launcher is the issue. It's completely black. After logging in.
However, it is fixed by using the `--in-process-gpu` argument for the executable. It's an Electron flag and I'm guessing the launcher is Electron or Chromium based.
Using '%command% --in-process-gpu' in steam also fixes Warframe Launcher https://bugs.winehq.org/show_bug.cgi?id=56463
Could potentially also fix https://bugs.winehq.org/show_bug.cgi?id=58041 not tested.
http://bugs.winehq.org/show_bug.cgi?id=57635
John Smith wine@xarov.net changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://blizzard.com/apps/b | |attle.net/desktop
--- Comment #10 from John Smith wine@xarov.net --- (In reply to Patrick from comment #9)
(In reply to John Smith from comment #8)
(In reply to Ken Sharp from comment #7)
Do you have to log in to test this?
Yes. Because the initial login window box is displaying correctly. The launcher is the issue. It's completely black. After logging in.
However, it is fixed by using the `--in-process-gpu` argument for the executable. It's an Electron flag and I'm guessing the launcher is Electron or Chromium based.
Using '%command% --in-process-gpu' in steam also fixes Warframe Launcher https://bugs.winehq.org/show_bug.cgi?id=56463
Could potentially also fix https://bugs.winehq.org/show_bug.cgi?id=58041 not tested.
It does not fix Ubisoft Launcher, that's for sure.
http://bugs.winehq.org/show_bug.cgi?id=57635
John Smith wine@xarov.net changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=56463
http://bugs.winehq.org/show_bug.cgi?id=57635
John Smith wine@xarov.net changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=58041
http://bugs.winehq.org/show_bug.cgi?id=57635
John Smith wine@xarov.net changed:
What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=58543