[Bug 49790] New: wine (staging) from 5.13 to current 5.16 - qclauncher hangs (on access to a lock file?)

WineHQ Bugzilla wine-bugs at winehq.org
Sun Sep 6 11:01:59 CDT 2020


https://bugs.winehq.org/show_bug.cgi?id=49790

            Bug ID: 49790
           Summary: wine (staging) from 5.13 to current 5.16 - qclauncher
                    hangs (on access to a lock file?)
           Product: Wine-staging
           Version: 5.16
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: winehq at lam.pl
                CC: leslie_alistair at hotmail.com, z.figura12 at gmail.com
      Distribution: ---

Because Bethesda.net Launcher doesn't work in WINE, qclauncher has been a great
tool to start Quake Champions in WINE for pure BNL accounts (non-Steam).

On Fedora (which uses wine-staging), I can't run qclauncher on any wine
(staging) newer than 5.12.

To reproduce qclauncher's problem, you don't need the game or Bethesda account.
All you need is to:
- grab the newest qclauncher.exe -
https://github.com/syncore/qclauncher/releases/tag/v1.06 and extract that into
a directory
- cd <said directory>
- touch data.qcl
- ./qclauncher.exe

Because the configuration file is 0 bytes, it should pop up an error saying
"Your data.qcl is from an old version (...) You must restart (...)". That's the
expected behavior for this test scenario. At least it was able to open the
file, see that it's empty and display a dialog. It will remove the empty
data.qcl file and you need to touch (re-create) it before test with a different
WINE version.

In current wine-staging, the pop-up never appears. Instead, wine apparently
hangs completely, doesn't show any window, doesn't react to ^C/^\, but can be
killed.

My history with this problem:
- 5.9 works
- 5.10 had the same issue
- not sure about 5.11
- 5.12 works
- 5.13, 5.14, 5.15, 5.16 (newest at the time of writing) all have the bug

Because I found a way to reproduce the hang without qclauncher ever trying to
launch the game, I'm now suspecting (actually, pretty convinced) that the hang
occurs during access to the data.qcl file. The program creates a file
"qcl.lock" and perhaps this locking mechanisms got broken?

This should be 100% reproducible without any requirements (other than grabbing
qclauncher from github), but please let me know if it somehow isn't. Many
thanks in advance!

-- 
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.



More information about the wine-bugs mailing list