AppImage does not work

[PostPollux]

I just downloaded the current AppImage and I can't get it to run on my Linux PC. It is not an issue of the newest version, as I have the exact same behaviour with a previous version (4.36.0). Also other software packaged as AppImage is running just fine, so it is probably not an issue with AppImages in general.

Whenever I run the BitBox App image a window is opening. But that window then stays completely white and one processor thread is stuck working at 100% until I kill the application because nothing is happening.

Unfortunately I don't have lot's of debugging info. If I run the AppImage through the terminal this is all I get:

./BitBox-4.41.0-x86_64.AppImage 
Sandboxing disabled by user.
Loading log config from '/home/johannes/.config/bitbox/logging.json'.
Logging into '/home/johannes/.config/bitbox/log.txt' from 'debug'.

An this is all that is in the log file:

time="2024-03-10T22:56:35+01:00" level=info msg="Started Qt application" args="[./BitBox-4.41.0-x86_64.AppImage]" group=server
time="2024-03-10T22:56:35+01:00" level=info msg="--------------- Started application --------------" group=server
time="2024-03-10T22:56:35+01:00" level=info msg=environment goarch=amd64 goos=linux group=server version=4.41.0
time="2024-03-10T22:56:35+01:00" level=info msg="Arguments: &{mainDirectoryPath:/home/xxx/.config/bitbox bitbox02DirectoryPath:/home/xxx/.config/bitbox/bitbox02 cacheDirectoryPath:/home/xxx/.config/bitbox/cache notesDirectoryPath:/home/xxx/.config/bitbox/notes appConfigFilename:/home/xxx/.config/bitbox/config.json accountsConfigFilename:/home/xxx/.config/bitbox/accounts.json testing:false regtest:false devservers:false gapLimits:<nil> log:0xc00012cf00}" group=arguments
time="2024-03-10T22:56:35+01:00" level=info msg="backend config: {Proxy:{UseProxy:false ProxyAddress:} DeprecatedBitcoinActive:true DeprecatedLitecoinActive:true DeprecatedEthereumActive:true Authentication:false BTC:{ElectrumServers:[btc1.shiftcrypto.io:443:s btc2.shiftcrypto.io:443:s]} TBTC:{ElectrumServers:[tbtc1.shiftcrypto.io:443:s tbtc2.shiftcrypto.io:443:s]} RBTC:{ElectrumServers:[127.0.0.1:52001:p 127.0.0.1:52002:p]} LTC:{ElectrumServers:[ltc1.shiftcrypto.io:443:s ltc2.shiftcrypto.io:443:s]} TLTC:{ElectrumServers:[tltc1.shiftcrypto.io:443:s tltc2.shiftcrypto.io:443:s]} ETH:{DeprecatedActiveERC20Tokens:[]} TETH:{} RETH:{} FiatList:[USD EUR CHF] MainFiat:USD UserLanguage: BtcUnit:default}" group=backend
time="2024-03-10T22:56:35+01:00" level=info msg="frontend config: map[guideShown:false]" group=backend
time="2024-03-10T22:56:35+01:00" level=info msg="ReconfigureHistory: coins=[]; fiats=[\"USD\" \"EUR\" \"CHF\"]" group=rates

My System:
Linux Manjaro with XFCE (Fully updated)
Tested with two different Kernels: 5.10.211-1 and 6.6.19-1
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
UHD Graphics 620 (KBL GT2)

[benma]

Did it use to work before and this is a new problem, or it never worked?

[PostPollux]

I tried it for the first time today, as I just bought a BitBox. But as I said, I also tried some older version of the AppImage that I downloaded here from the Github Releases. I went all the way back to v 4.0.0. None of them works for me unfortunately. From 4.0.0 to 4.29.0 the window is white, then shortly flickers with a very slight grey and then stays like this. So I actually dont see anything, but at least the application is not stuck and I can close the application just normally. From 4.30.0 on it only stays white and I have the issue that the application is completely stuck and normal closing does not work.

Just to verify I tried the TrezorSuite as AppImage again and it works fine.

[benma]

The only comparable issue we've seen in the past was a corrupted database, where opening it would eat up CPU and RAM. It's very rare but it would explain the symptom.

Could you please delete the app folder in ~/.config/bitbox and try again with the latest version?

[PostPollux]

I tried deleting that folder. Unfortunately it did not help. I tried the newest and several old versions everytime deleting that folder. Still behaves exactly the same.

[benma]

The logs don't show the issue, and it's hard to debug the issue without being able to reproduce it. I am currently out of ideas - we didn't see this issue before (except for the corrupted database which you ruled out by deleting the app folder).

If you are a developer, you could build and run the backend part of the app (make servewallet) and try to pinpoint the issue.

[PostPollux]

Thanks for your effort. Yes, I am a developer, but not a webdeveloper. I just built the backend with make servewallet and the frontend with make webdev. I then opened http://localhost:8080/ in my browser and I can see the interface. It is communicating with the backend so in this setup it works.
Is there a way I can see more logs with the AppImage? I tried to set the debug level from "debug" to "verbose" in ~/.config/bitbox/loggin.json, but that didn't work. Or is debug already the most verbose logging setting?

[thisconnect]

@PostPollux maybe could you try to extract the Appimage and run from there?

https://superuser.com/questions/1301583/how-can-i-extract-files-from-an-appimage#1389548

[rkfg]

@PostPollux can you run it like this: QTWEBENGINE_REMOTE_DEBUGGING=23456 ./BitBox-4.42.0-x86_64.AppImage (try the latest version) and then open http://127.0.0.1:23456 in Chrome/-ium. See if there are any errors in that devtools console.

If there's something about invalid MIME type, can you try running grep -r '\*\.js\b' /usr/share/mime/packages and see if there's more than one result? See #2684 for details, in theory it shouldn't be the same issue but who knows.