[Bug 58811] New: Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58811

Bug ID: 58811
           Summary: Steam: Unable to display the intended GUI windows due
                    to steamwebhelper being unresponsive.
           Product: Wine
           Version: 10.16
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: dwrite
          Assignee: [e-mail]
          Reporter: [e-mail]
   Regression SHA1: 2a2cc34db71a86899b69bf3ee1da52793c342019
      Distribution: Gentoo

Created attachment 79466
  --> http://bugs.winehq.org/attachment.cgi?id=79466
terminal

After 2a2cc34db71 [1], Steam appears to launch, showing its notification area
icon, but no window will appear.

After a while from clicking said icon, the "Steamwebhelper is not responding"
window [2] will appear, with a few different options to restart things with, of
which none do any better.

I believe the

src\vgui2\vgui_surfacelib\Win32Font.cpp (963) : Couldn't get string length

line shows up only when this problem can be seen, which could be a sort of a
hint at least.

Building before the mentioned commit, or reverting it, and efce37afd70 due to
conflicts, on current 'git master' will make it work again.

Hacking on it a bit, removing the 'wcsupr(refkey->name);' line also makes it
work, though maybe that is obvious in this case, and might more or less nullify
the point of the uppercasing intended.

(Did not try a fresh prefix and clean install of Steam yet due to the
cumbersome log-in process, but hopefully that is not necessary here.)

Last tested at 'wine-10.17'.

Thank you!

1.
https://gitlab.winehq.org/wine/wine/-/commit/2a2cc34db71a86899b69bf3ee1da527...
2. https://help.steampowered.com/en/faqs/view/6C3E-9504-CC20-AF49

[Bug 58811] Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58811

Chiitoo  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #79466|terminal                    |terminal output from a bad
        description|                            |run

[Bug 58811] Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58811

Chiitoo  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download, regression
                URL|                            |https://cdn.fastly.steamsta
                   |                            |tic.com/client/installer/St
                   |                            |eamSetup.exe

[Bug 58811] Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58811

--- Comment #1 from Zeb Figura  ---
*** Bug 58808 has been marked as a duplicate of this bug. ***

[Bug 58811] Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58811

--- Comment #2 from Zeb Figura  ---
*** Bug 58809 has been marked as a duplicate of this bug. ***

[Bug 58811] Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58811

--- Comment #3 from Zeb Figura  ---
*** Bug 58810 has been marked as a duplicate of this bug. ***

[Bug 58811] Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=58811

--- Comment #4 from Chiitoo  ---
Whoa, I did notice the bug report go out before I was ready, so maybe pressed
'return' accidentally while adding the attachment... and perhaps it was down
just long enough to manage creating all those...

Sorry about that!