Avoid request to unlock key ring

[dccoder84]

Thanks in advance for your bug report!

• [x] Have you reproduced issue in safe mode?
• [x] Have you used the debugging guide to try to resolve the issue?
• [x] Have you checked our FAQs to make sure your question isn't answered there?
• [x] Have you checked to make sure your issue does not already exist?
• [x] Have you checked you are on the latest release of Pulsar?

What happened?

Every time I open Pulsar on Linux I get a pop up which asks for a password to unlock the standard key ring. Pulsar works fine if I click cancel but it is annoying. Of course typing in the correct password also works. This is a known security feature in Linux but the question is if we really need it.

Pulsar version

pulsar-1.128.2025081423-next

Which OS does this happen on?

🐧 Debian based (Linux Mint, Ubuntu, etc.)

OS details

Xubuntu 25.04

Which CPU architecture are you running this on?

x86_64/AMD64

What steps are needed to reproduce this?

Simply open Pulsar. No special requirements.

Additional Information:

No response

[confused-Techie]

Thanks a ton for submitting this issue, seems strange it's requesting it right on launch. If I had to assume, I'd guess PPM is causing this as it stores credentials there if you login to PPM with your Pulsar account.

Maybe we can see if we can cause it to only ever check if you are logged in right when it needs it, rather than at launch.

[savetheclocktower]

Might be worth seeing if it still happens when the github package is disabled? That's the only other package I can think of that might need to access your keychain on launch.

[dccoder84]

Over at VS Code is also the same bug report if that helps anybody.

@confused-Techie: If I should do any tests regarding PPM which seems to be the pulsar package manager then just tell me how.

@savetheclocktower: Thank you for this trick. Disabling the github package "solves" the issue. I think we should leave the bug report open because this is rather a workaround then a fix. Personally I guess I am fine with your workaround because I use git not via Pulsar but via external command line.

[savetheclocktower]

@savetheclocktower: Thank you for this trick. Disabling the github package "solves" the issue. I think we should leave the bug report open because this is rather a workaround then a fix. Personally I guess I am fine with your workaround because I use git not via Pulsar but via external command line.

I'm amazed this worked! I only mentioned it because I've been spending a lot of time in that cursed codebase recently and I know it does some keychain work. If I succeed in modernizing the github package, perhaps I can figure out how to bypass this check altogether, or at least defer it until it actually wants your credentials for something.