Open alexanderadam opened 3 years ago
Same here :confused:
i see the same on my new installation... at some point, GOG Galaxy popped up an update window with the options to update later or update now... so i click on the update now button with some trepidation... much to my surprise, it appeared to do the work needed... new things were downloaded and installed and all seemed to be going fine... but then (i think) a window popped up saying the update failed... when i manually started GOG again, it was the same version...
i did find a bunch of logs and they do detail the update process taking place... everything looks good up until the log reports something about "No desktop shell is present." and the updater undoes all the work it did... TBH, i was surprised that it actually started and got as far as it did... it looked like it was attempting to update to version 2.0.37.384 (2021-03-26 16:14)...
i also noted in the logs it was saying "win7 64-bit, WINE 5.2" but during the initial install of the GOG snap, i know i saw it specifically say win10 in one of the installation windows...
so this is just to add some more detail that others might find interesting or necessary to figure out how to do the update to the latest version of GOG from the snap installed version 1.2.66...
Installing the newer updates to GOG should be ok, but you might have more luck with the candidate version of the snap:
Can you please try the release in candidate
to see if that helps alleviate the issues?
do we need to stop the currently running one first before doing the refresh?
Ideally, yes, that would be a good idea to ensure that the refresh doesn't break it - although the way that refreshes work it shouldn't be an issue if you don't shut the app down first, but you might miss some data migration.
thank you... have stopped the currently running instance and doing the refresh now...
ok, just some feedback... the refresh of the snap worked but the install of GOG 2.0 failed... i did not have my logging process established so from memory, the error was "no desktop shell available" or something like that... i mentioned it previously in one of my response above... when the process finished, my system was still running the old 1.2.66 version of GOG...
at this point, i exited the system, rebooted to be sure everything was clean, established a quick script to run gog-galaxy-wine with output redirection to a log file, and started gog-galaxy-wine again... without looking at the top of the log, i think it tried the update again but i'm not sure... in any case, i left it running (minimized in the tray) over night...
looking at the log this morning, i see that about 03:05 local time, the updater fired up and successfully pulled in everything needed for an update... it did also detect the libGLESv2.dll change that i had made and noted in issue #10 ... i noted in the log that it reports triggering the "update needed" dialog in the GUI but i have not yet opened the GUI... instead i'm waiting another few minutes to see what happens when the updater fires off again after 6 hours have passed... that should take place in maybe 10 minutes or so...
i'm happy to make the (currently 1.3Meg sized) log available if needed so the actual update process and errors can be seen and maybe solved...
this is the short script, ~/runGOG, that i whipped up to run GOG from a terminal and gather its output to a log...
#!/bin/bash
gog-galaxy-wine $@ |& tee ~/gog-galaxy-wine-$(date '+%Y%m%d%H%M').log
i will post more in this issue after the update attempt takes place in a few minutes...
ok, the prefetch ran again... not sure if it used the existing prefetched files or not... some were downloaded again... at the end, the log reports
Client update check performed.
Changing value of setting lastUpdateCheckTimestamp from '1629356859' to '1629378568'
Self-update check completed and found an update, next check at Thu Aug 19 10:07:04 2021.
Client update check shows there is one available.
Sending ShowSelfUpdateModal message to frontend for version '2.0.41.150'
at this point, i'm going to open the GUI and click on the update button and see what happens... :crossed_fingers:
same thing as before... it failed and undid everything... apparently it tried to restart but that also failed and the snap completely exited to the terminal...
[galaxy_updater]: Moving files complete for component 'desktop-galaxy-updater', total 45 files moved
[galaxy_updater]: Launching client data migration from 1.2.66.64.
[galaxy_updater]: Launching process. Command: C:\Program Files (x86)\GOG Galaxy\GalaxyClient.exe, Initial Directory: C:\Program Files (x86)\GOG Galaxy, Elevation Mode: Deelevate, Arguments: { /migrateDataFrom="1.22.66.64" /runWithoutUpdating }
[galaxy_updater]: Starting deelevation process (C:\Program Files (x86)\GOG Galaxy\GalaxyClient.exe) from an elevated one
[galaxy_updater]: Current process is not run by SYSTEM, Code: 0
[galaxy_updater]: De-elevating while running as admin user.
[galaxy_updater]: Failed to initialize the symbol handler; error code: 87, reason: UNKNOWN.
[galaxy_updater]: Failed to initialize the symbol handler; error code: 87, reason: UNKNOWN.
[galaxy_updater]: Could not launch Client data migration after update! Error Message: Failed to launch process C:\Program Files (x86)\GOG Galaxy\GalaxyClient.exe.
Root Exception: Error Message: No desktop shell is present.
Stack Trace
-----
Stack Trace
-----
[galaxy_updater]: Undoing update of component: 'desktop-galaxy-client'.
and it proceeds to revert everything back to 1.22 at which point it reports
[galaxy_updater]: Finished undoing update of component: 'desktop-galaxy-updater'.
[galaxy_updater]: Pruning ETags older than 604800 seconds.
[galaxy_updater]: Pruned 0 ETags.
[galaxy_updater]: Displaying error because of Launching migration Client failed..
[galaxy_updater]: Re-launching updater with DisplayError strategy.
[galaxy_updater]: Launching process. Command: C:\ProgramData\GOG.com\Galaxy\redists\GalaxyUpdater.exe, Initial Directory: C:\ProgramData/GOG.com/Galaxy/redists, Elevation Mode: Deelevate, Arguments: { /clientUpdatePath="C:\Program Files (x86)\GOG Galaxy" /disableUpdateMessageBox /globalRedistUpdatePath="C:\ProgramData/GOG.com/Galaxy/redists" /previousClientVersion="1.2.66.64" /redistUpdatePath="C:\ProgramData/GOG.com/Galaxy/redists" /updateClient /updateRedist /updateStrategy="DisplayError" }
[galaxy_updater]: Starting deelevated process (C:\ProgramData\GOG.com\Galaxy\redists\GalaxyUpdater.exe) from an elevated one
[galaxy_updater]: De-elevating while running as admin user.
[galaxy_updater]: Failed to initialise the symbol handler; error code: 87, reason: UNKNOWN.
[galaxy_updater]: Failed to initialise the symbol handler; error code: 87, reason: UNKNOWN.
[galaxy_updater]: Failed to run updater with strategy 'DisplayError': .
[galaxy_updater]: Launching process. Command: C:\Program Files (x86)\GOG Galaxy\GalaxyClient.exe, Initial Directory: C:\Program Files (x86)\GOG Galaxy, Elevation Mode: Deelevate, Arguments: { /runWithoutUpdating }
[galaxy_updater]: Starting deelevated process (C:\Program Files (x86)\GOG Galaxy\GalaxyClient.exe) from an elevated one
[galaxy_updater]: De-elevating while running as admin user.
[galaxy_updater]: Failed to initialise the symbol handler; error code: 87, reason: UNKNOWN.
[galaxy_updater]: Failed to initialise the symbol handler; error code: 87, reason: UNKNOWN.
[galaxy_updater]: Could not launch Client after update! Error Message: Failed to launch process C:\Program Files (x86)\GOG Galaxy\GalaxyClient.exe.
Root Exception: Error Message: No desktop shell is present.
Stack Trace
-----
Stack Trace
-----
[galaxy_updater]: GalaxyUpdater exited (Move), return code -53: Launching migration Client failed.
[galaxy_updater]: Destroying AuthenticatedHttpClient.
[galaxy_updater]: VACUUMing ETags DB.
[galaxy_updater]: Shutting down SSL manager.
i'm (still) slightly ""concerned"" that it is reporting win7 instead of win10 which i would expect these days...
grep -Ei -e "platform " gog-galaxy-wine-202108181758.log
2021-08-18 17:58:55.940 [Information][ (0)] [TID 192][galaxy_client]: Platform identification: win7 64bit
2021-08-18 17:59:00.529 [Information][ (0)] [TID 784][client_renderer]: Platform identification: win7 64bit
2021-08-18 17:59:00.677 [Information][ (0)] [TID 852][client_renderer]: Platform identification: win7 64bit
2021-08-18 17:59:00.737 [Information][ (0)] [TID 868][Process]: Platform identification: win7 64bit
2021-08-18 17:59:15.541 [Information][ (0)] [TID 1476][client_renderer]: Platform identification: win7 64bit
2021-08-18 21:04:28.177 [Information][ (0)] [TID 2000][galaxy_updater]: Platform identification: win7 64bit
2021-08-18 21:05:08.436 [Information][ (0)] [TID 2056][galaxy_updater]: Platform identification: win7 64-bit, WINE 6.0.1
2021-08-19 03:06:24.163 [Information][ (0)] [TID 1716][galaxy_updater]: Platform identification: win7 64bit
2021-08-19 03:07:02.765 [Information][ (0)] [TID 1780][galaxy_updater]: Platform identification: win7 64-bit, WINE 6.0.1
2021-08-19 09:08:10.778 [Information][ (0)] [TID 944][galaxy_updater]: Platform identification: win7 64bit
2021-08-19 09:08:49.843 [Information][ (0)] [TID 1000][galaxy_updater]: Platform identification: win7 64-bit, WINE 6.0.1
2021-08-19 09:16:48.056 [Information][ (0)] [TID 1740][galaxy_updater]: Platform identification: win7 64bit
2021-08-19 09:17:18.691 [Information][ (0)] [TID 1684][galaxy_updater]: Platform identification: win7 64bit
2021-08-19 09:17:19.043 [Information][ (0)] [TID 1780][galaxy_updater]: Platform identification: win7 64-bit, WINE 6.0.1
i remember, when starting after the snap refresh yesterday, there was a box that popped up saying it needed win7 SP1 but the box disappeared and the process continued... that was on the first run after the refresh which i did not have being logged at that time...
ok, i'm done... sorry for possible rambling... c0ffee is finished as is my testing and reporting for now... standing by awaiting further instructions :cat:
When I'm opening GOG Galaxy Snap, I'm getting an outdated warning at the bottom.
Now I'm curious how I should update the Snap accordingly. I might have missed this but I wasn't able to find anything documented regarding this.