https://bugs.winehq.org/show_bug.cgi?id=49617
Bug ID: 49617 Summary: Wine regression with gog galaxy 2.0 Product: Wine Version: 5.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: ryan@rnrcarpet.com Distribution: ---
Gog galaxy 2.0 fails to start and freezes during splash screen with 5.13.
---------- 2020-07-25 10:18:48.557 [Information][SubSystem shortTasks thread (64)] [TID 262][galaxy_client]: Starting ClientTask: InitializationMultiTask 2020-07-25 10:18:48.558 [Information][SubSystem shortTasks thread (64)] [TID 262][galaxy_client]: Starting ClientTask: UpgradeDatabaseTask
**5.13 stops here without error in standard log. 5.5 and others continue**
2020-07-25 10:18:48.569 [Information][ (0)] [TID 9][galaxy_client]: Starting Communication Service on login. 2020-07-25 10:18:48.595 [Information][ (0)] [TID 9][galaxy_client]: Starting Communication Service. 2020-07-25 10:18:48.622 [Information][SubSystem shortTasks thread (64)] [TID 262][galaxy_client]: Galaxy DB is up to date. Version: 26. ----------
Reproduce:
1) Install distro wine 5.13 (Fedora 32) $ dnf install wine 2) Install gog galaxy via Lutris install script 3) Run gog galaxy 2.0 successfully 3) Switch to system wine 5.13 (distro) 4) Gog galaxy freezes during splash screen
Install wine 5.5 (eg $ dnf install wine*5.5*). Check system wine 5.5 is in use. Start gog galaxy and it runs successfully.
Reinstall wine 5.13, check, still freezes on start.
Notes:
Fedora 32 doesn't have anything between these two available via dnf so I can't quickly check which version the regression starts at.
Possibly could be an issue with the distro provided version of wine? I don't have an answer here if that's possible or not. Have a feeling its with wine itself.
Possible future entry:
Am trying to get at a more detailed log but its really massive and apparently ultra slow to obtain.
https://bugs.winehq.org/show_bug.cgi?id=49617
Anya maniikarabera@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maniikarabera@protonmail.ch
https://bugs.winehq.org/show_bug.cgi?id=49617
--- Comment #1 from ryan@rnrcarpet.com --- Whoops. Slightly the wrong lines. This is the exact spot:
2020-07-25 15:54:18.083 [Information][ (0)] [TID 9][galaxy_client]: Starting Communication Service on login. 2020-07-25 15:54:18.118 [Information][ (0)] [TID 9][galaxy_client]: Starting Communication Service.
***5.13 stops here. 5.5, etc continues here***
2020-07-25 15:54:18.141 [Information][SubSystem shortTasks thread (64)] [TID 262][galaxy_client]: Galaxy DB is up to date. Version: 26. 2020-07-25 15:54:18.146 [Information][SubSystem shortTasks thread (64)] [TID 262][galaxy_client]: ClientTask finished: UpgradeDatabaseTask
https://bugs.winehq.org/show_bug.cgi?id=49617
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Wine regression with gog |Gog galaxy 2.0 fails to |galaxy 2.0 |start Keywords| |regression
--- Comment #2 from Austin English austinenglish@gmail.com --- Please run a regression test: https://wiki.winehq.org/Regression_Testing
https://bugs.winehq.org/show_bug.cgi?id=49617
--- Comment #3 from ryan@rnrcarpet.com --- Thanks, will look into that. For the moment:
So 5.13 is causing a systemd coredump here. Hopefully this is of use.
https://www.freedesktop.org/software/systemd/man/systemd-coredump.html
wine debug: 16538.870:0088:009c:trace:mountmgr:udisks_filter changed "/org/freedesktop/systemd1/unit/systemd_2dcoredump_2esocket"
core dump: Storage: /var/lib/systemd/coredump/core.wineserver.1000.203cdc594e97495e9287b8a93d9f9972.144148.1595706719000000000000.lz4 Message: Process 144148 (wineserver) of user 1000 dumped core.
Stack trace of thread 144148: #0 0x00007effe5f46aa0 __libc_free (libc.so.6 + 0x8caa0) #1 0x00000000004135ba inode_close_pending (wineserver64 + 0x135ba) #2 0x00000000004144bd remove_lock (wineserver64 + 0x144bd) #3 0x0000000000414565 fd_destroy (wineserver64 + 0x14565) #4 0x0000000000422cd0 release_object (wineserver64 + 0x22cd0) #5 0x0000000000422cd0 release_object (wineserver64 + 0x22cd0) #6 0x000000000041abee close_handle (wineserver64 + 0x1abee) #7 0x000000000041b2bb req_close_handle (wineserver64 + 0x1b2bb) #8 0x00000000004377d8 call_req_handler (wineserver64 + 0x377d8) #9 0x000000000043e360 thread_poll_event (wineserver64 + 0x3e360) #10 0x000000000041493b main_loop_epoll (wineserver64 + 0x1493b) #11 0x0000000000414ba2 main_loop (wineserver64 + 0x14ba2) #12 0x0000000000404242 main (wineserver64 + 0x4242) #13 0x00007effe5ee1042 __libc_start_main (libc.so.6 + 0x27042) #14 0x00000000004042be _start (wineserver64 + 0x42be)
It does that then has the 1st:
16538.870:00cc:00e4:trace:winsock:__WSAFDIsSet (socket 0078, fd_set 0x166fcc4, count 0) <- 0
A few random things:
16538.870:0020:0350:trace:msvcrt:_lock (19) 16538.870:0020:0350:trace:msvcrt:_unlock (19)
And ends with this or something like that:
16538.870:0088:009c:trace:mountmgr:udisks_filter changed "/org/freedesktop/systemd1/unit/systemd_2dhostnamed_2eservice"
Have seen some thread blocked by other thread to try again in n seconds following all this.
Whatever is causing this, I don't know what it is. If its a commit, just not seeing what it would be.
https://bugs.winehq.org/show_bug.cgi?id=49617
--- Comment #4 from ryan@rnrcarpet.com --- Ah, the regression testing needs wine source to be built yes?
This is a 32 bit application. I have previously failed to build 32 bit wine on Fedora 32 due to major issues with that. Ubuntu works fine, Fedora does not.
So, can't do it that way. Will have to do regression testing on Fedora 32 a bit different.
https://bugs.winehq.org/show_bug.cgi?id=49617
--- Comment #5 from ryan@rnrcarpet.com --- So its starting with 5.13.
I have downloaded and installed all wine distro packages for 5.10 and 5.12 and there's no issue with either of those.
Did the exact same for 5.13 and that still has this problem. At least that narrows it down substantially.
https://bugs.winehq.org/show_bug.cgi?id=49617
--- Comment #6 from ryan@rnrcarpet.com --- For some reason I'm a bit confused on "sudo dnf install winehq-devel" for the devel track.
This appears to still allow the application to work correctly but it also looks to be missing something compared to distro supplied and I haven't figured that out yet.
In any case, it looks to work fine that way so I take it that means its distro package related if I have that right?
Sorry, I just never noticed that before. Done everything but that :-O
https://bugs.winehq.org/show_bug.cgi?id=49617
ryan@rnrcarpet.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG
--- Comment #7 from ryan@rnrcarpet.com --- Am closing this as I expect this is as I believe it is.
https://bugs.winehq.org/show_bug.cgi?id=49617
soredake broaden_acid002@simplelogin.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|broaden_acid002@simplelogin | |.com |
-
WineHQ Bugzilla