5.42.0 now asks for keyring when starting up

[jrw]

• I have searched open and closed issues for duplicates

• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

---

Bug Description

I just upgraded to Signal desktop 5.42.0 (on Linux Mint 20). When I stop and restart Signal, it is now asking "Choose password for new keyring"

Steps to Reproduce

1. Close Signal application via window decoration X close application
2. Restart Signal application via desktop shortcut
3. Choose "Cancel" on keyring dialog and again on following keyring dialog

Actual Result:

When I stop and restart Signal, it is now asking "Choose password for new keyring" "An application wants to create a new keyring called "Default keyring". Choose the password you want to use for it." This dialog locks up the entire user interface. I am able to cancel it (it comes back again immediately, but I can cancel it a second time), after which Signal starts as normal and I am able to use it normally. This repeats the next time I stop/restart Signal.

Expected Result:

When I stop and restart Signal, the application interface starts as normal and I am able to interact with it without answering any dialogs.

Screenshots

Platform Info

Signal Version: 5.42.0

Operating System: Linux Mint 20

Linked Device Version:

Link to Debug Log

https://debuglogs.org/desktop/5.42.0/59524b819542f797d3cb686e4cfe91c0b23e13bf37ddeebcc2d3b1019d1aee91.gz

[scottnonnenberg-signal]

Hm. This is quite odd - what if you try to start Signal with this command-line argument? --password-store=basic

[scottnonnenberg-signal]

(found this forum thread: https://forums.linuxmint.com/viewtopic.php?t=312289)

[jrw]

Thanks for your reply Scott!

Using --password-store=basic makes the problem disappear. It must be related somehow to the issue you found with Chromium, because I see that I also get that popup for Chromium (which I don't use very often).

I haven't investigated (much) the Chromium issue via your link, but I can add the "password-store" thing to my launcher for Signal and for Chromium. However, why should this have appeared with the latest release of Signal? Do you think it's a Linux Mint thing, or did something in that Signal release trigger it somehow? And what is causing Signal and Chromium to be related in this weird way?

[scottnonnenberg-signal]

We updated to Electron 18 in 5.42, and that came with an updated version of Chromium.

[jrw]

OK. Thanks!
So, is adding the --password-store option the right fix? Does the Signal installer need to add that option to the launcher command line?

[scottnonnenberg-signal]

It certainly might; it's interesting, though, because we haven't seen this report from many folks. I guess they have a default keyring already set up?

[jrw]

Maybe others have a default keyring because of using chromium? I use chromium only when I have to (which is very seldom)

[jrw]

I've found one more place this would need to be changed if there is an update: the Startup Applications command line for Signal under the Preferences grouping. (The original one was the Signal launcher command line.)

[tillschaefer]

Can conform the issue on KDE, where I have to grant access to my wallet for each application individually.

[Geblaat]

I have the same issue on Debian 11. I don't use Chromium so never setup a keyring.

[beantaco]

I also experience this issue on Debian 11. I have never seen the keyring password window until the recent software update.