Walletwasabi: Wasabi opens on Tails in locked mode after fresh install

[davterra]

I just downloaded & installed the most recent Wasabi release on Tails 4.3, and upon starting it immediately goes into "Locked Screen" mode, with no apparent way to slide the page up, or unlock.

I am not running Tails in persistent mode.

A check of UIconfig.json shows settings of:
{
"WindowState": "Maximized",
"Height": 840.0,
"Width": 1600.0,
"FeeTarget": 2,
"FeeDisplayFormat": 0,
"Autocopy": true,
"IsCustomFee": false,
"LurkingWifeMode": false,
"LockScreenActive": false,
"LockScreenPinHash": ""
}

[PulpCattel]

It seems similar to 2939.

Feels to me like a hardware related problem.

[nopara73]

I added this issue to the hard fork todo, not because it's a hard fork, but because we cannot give out a new hardfork that breaks the software, so the user could not update.

[davterra]

I just installed Tails in a VirtualBox VM running on the same hardware as in the original post, and Wasabi runs fine in that setup. No screenlock issue...

[PulpCattel]

If it works in VB, than it seems indeed the same issue as 2939. The problem to me seems related to Tails and some spec of your computer hardware, somehow they make Wasabi misbehave.
When Tails is managed by Ubuntu, or whatever, in a VM, the problem is not there.

I'm pretty curious about this error since I cannot reproduce with any of my hardwares.
Could be interesting if you @davterra have a different computer to test with Tails from USB, or if you have already tested from different machines.

[davterra]

If it works in VB, than it seems indeed the same issue as 2939. The problem to me seems related to Tails and some spec of your computer hardware, somehow they make Wasabi misbehave.
When Tails is managed by Ubuntu, or whatever, in a VM, the problem is not there.

I'm pretty curious about this error since I cannot reproduce with any of my hardwares.
Could be interesting if you @davterra have a different computer to test with Tails from USB, or if you have already tested from different machines.

Yeah, I do have another, older laptop that just runs one of my full nodes 24/7.
When I have a little time later, I had already planned on shutting it down and seeing what happened with this Tails install on my USB.

The older laptop with the node is an old Dell.
The one I'm using here, and with which I encountered the Tails issus is much a newer and better equipped HP.

[jsspanjer]

In my humble opinion (which I stated in https://github.com/zkSNACKs/WalletWasabi/issues/2939) you should always test Tails on hardware. Virtual is fine but not a final test.
There is a change in GUI since 1.1.9.2 which causes this strange behavior. Probably an update to specific library.

[Rice-from-data]

I can confirm that this problem is reproducible on a Thinkpad T440s running Tails 4.4 and Tails 4.4.1 using the WasabiLinux-1.1.10.3.tar.gz package.

Wasabi opens to a locked screen with the instruction to click and drag upwards to unlock, but this is impossible to do. Multiple restarts of Wasabi result in a segmentation fault error.

However, switching the tails live USB to a Dell XPS 13 9343 fixes the problem. Wasabi opens normally (using the WasabiLinux-1.1.10.3.tar.gz package), except the screen resolution is slightly off (again, probably a hardware issue).

[CoprinopsisAtramentaria]

I can confirm that this problem is also reproducible with the same behavior on a Thinkpad T420 running Tails 4.4.1 using the WasabiLinux-1.1.10.3.tar.gz package. Though, I've tried the exact set of software on a Thinkpad T460p and do not encounter the issue so it does not appear to be an issue across the entire Thinkpad T4** series.

I'm setting up a build environment and will be attempting to debug what occurs leading up to the segmentation fault sometime in the next few days.

[RiccardoMasutti]

I cannot reproduce. Everything works after a fresh install.

Maybe related to #3348?

[CoprinopsisAtramentaria]

@RiccardoMasutti

The issue seems to only present itself with a specific combinations of hardware/software and I have a suspicion it was introduced within the set of the following #2108 #2544 #2693 #2718. I'm hoping getting to the bottom of the issue on my hardware will lead to a fix of the problem for people generally but we'll see. I should be free'd up to debug the issue tonight.

I don't believe it's related to #3348.

[nopara73]

@danwalmsley the mentioned PRs were yours, maybe you have some guess here.

[CoprinopsisAtramentaria]

Interesting, I'm no longer able to reproduce this issue on a Thinkpad T420 running Tails 4.4.1 when using the new WasabiLinux-1.1.11.tar.gz package.

@Rice-from-data, have you tried this new release?

[stale[bot]]

This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.