Skip to content
This repository has been archived by the owner on Sep 26, 2024. It is now read-only.

New Logos Version (in app) Install crash #217

Closed
noticons opened this issue Dec 7, 2023 · 10 comments
Closed

New Logos Version (in app) Install crash #217

noticons opened this issue Dec 7, 2023 · 10 comments
Labels
bug Something isn't working

Comments

@noticons
Copy link

noticons commented Dec 7, 2023

I'm running wine-8.21 using native on the install of logos. Everything has been running well. The December iteration of the Logos program was released in the past few days, when it was pushed out, the Logos program tried to update itself and declared that it failed to install the application upgrade.
I ran Logos from CLI, but never got any error messages whatsoever. This is a wine issue, I'm sure, but I just wanted to bring it up.

@thw26
Copy link
Collaborator

thw26 commented Dec 7, 2023

cf. #120 and #130.

@thw26 thw26 added bug Something isn't working not our bug This most likely belongs to upstream wine/proton labels Dec 7, 2023
@noticons
Copy link
Author

noticons commented Dec 7, 2023

I tried running logos.sh with the -l flag in order to get the logs, and received this error:
./Logos.sh: line 423: [: DISABLED: integer expression expected
./Logos.sh: line 425: [: DISABLED: integer expression expected
LOGS var improperly set. Disabling Logos logs and resetting the LOGS value.
======= disable LogosBible logging only: =======
reg: The operation completed successfully
======= disable LogosBible logging done! =======

Looking at the script, the lines referenced are:
if [ "${LOGS}" -eq "DISABLED" ]; then logsOn; elif [ "${LOGS}" -eq "ENABLED" ]; then logsOff;

@thw26
Copy link
Collaborator

thw26 commented Dec 7, 2023

You can also run it from the CLI with no need for logs; you would just copy it from the terminal. I'd have to dig into the code to see why this is triggering.

@noticons
Copy link
Author

noticons commented Dec 7, 2023

I did try that but it didn't give any output. This time, I ran it from terminal with the -D flag (debugging) and, though there was a lot of extraneous data concerning the typical running of the program, the events which occurred around the failed update are:

040c:fixme:file:NtLockFile I/O completion on lock not implemented yet
040c:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4
040c:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4
040c:fixme:wintrust:SOFTPUB_VerifyImageHash Cannot verify hash for pszObjId="1.3.6.1.4.1.311.2.1.30"
040c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
040c:err:msi:ITERATE_Actions Execution halted, action L"LaunchConditions" returned 1603
0410:fixme:ntdll:RtlGetCurrentProcessorNumberEx (00007F40BD49E6D0) :semi-stub
040c:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 0058FEBC
03bc:fixme:secur32:get_cipher_algid unknown algorithm 23
03bc:fixme:secur32:get_mac_algid unknown algorithm 200, cipher 23
03bc:fixme:secur32:get_cipher_algid unknown algorithm 23
03bc:fixme:secur32:get_mac_algid unknown algorithm 200, cipher 23
03bc:fixme:secur32:get_cipher_str unknown cipher 23
03bc:fixme:secur32:get_cipher_len unknown cipher 23

on failing the first time, it then tries to update a second time. This produced these events:

0438:fixme:file:NtLockFile I/O completion on lock not implemented yet
0438:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4
0438:fixme:cryptasn:CryptDecodeObjectEx Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4
0438:fixme:wintrust:SOFTPUB_VerifyImageHash Cannot verify hash for pszObjId="1.3.6.1.4.1.311.2.1.30"
0438:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0438:err:msi:ITERATE_Actions Execution halted, action L"LaunchConditions" returned 1603
0438:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 0058FEBC
03a4:fixme:winsock:GetAddrInfoExW Unsupported namespace 0
03a4:fixme:winsock:GetAddrInfoExW Unsupported cancel handle
01ac:fixme:winsock:setsockopt Ignoring SO_REUSE_UNICASTPORT
03b0:fixme:secur32:get_hash_str unknown mac 200

@thw26
Copy link
Collaborator

thw26 commented Dec 7, 2023

Any other error code? Usually a crash hash a backtrace.

@noticons
Copy link
Author

noticons commented Dec 7, 2023

image
This is the only visual cue that indicates failure, and there is no other error produced other than the debug output above.

@noticons
Copy link
Author

noticons commented Dec 7, 2023

I also run Logos on linux on a separate computer, which is running it via the devel appimage (wine-devel_8.19-x86_64), and the same error occurs there.

@thw26
Copy link
Collaborator

thw26 commented Dec 13, 2023

This is related to the Logos 30+ update.

We have a partial fix but need more work to fix this one.

@thw26 thw26 removed the not our bug This most likely belongs to upstream wine/proton label Dec 13, 2023
@noticons
Copy link
Author

Great! Thanks so much. I'm glad the program performs so well for all the work that has gone into it from you guys.

@thw26
Copy link
Collaborator

thw26 commented Dec 21, 2023

See #219.

@thw26 thw26 closed this as completed Dec 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants