I’m an ex-Fedora 41 user that recently switched to OpenMandriva, I’m sure by now everybody knows the reason for the recent increase in users so I wont go into that lol
OpenMandriva Lx 25.01 x86_64 Gnome 47.2
So far the transition has been pretty smooth switching from Fedora 41 to OpenMandriva but I have experienced one small issue as I like to use multiple browsers I install the stable, beta and nightly builds of Brave Browser from the official Brave Stable/Beta/Nightly install instructions page.
Obviously as OM uses ‘dnf’ to install packages I followed the Fedora steps and it has installed fine, it launches, but I get the following keyring error in an insert password to unlock dialog box:
Authentication required
The login keyring did not get unlocked when you logged into your computer.
and it doesn’t indicate that the app is running in the taskbar, it shows an ‘unknown’ app icon with the indicators for each running instance next to that instead.
Thanks.
Appreciate the teams efforts on OM.
As one of the principles of this project are to keep politics out of software, OM might just be the first Linux distro that I donate to as I know that my money will go to supporting good software development and not political activism!
Such a breath of fresh air.
Welcome @EmmanuelGoldstein we are certainly happy to see all the new users.
This seems more likely to be a Brave problem except for the “Where do I fix this in OMLx Gnome”.
Do not know if these will help, if not some more internet searching might:
I do not use Gnome so do not know if there is a utility there to do this, but there probably is. In KDE it looks like this is done with the KWalletManager.
Unfortunately the instructions provided on there caused the browser to fail to sync and after clearing all of the local files (under .config/BraveSoftware) and reinstalling the browser it still failed to sync properly.
So unfortunately as that is technically my main browser, I’ll have to leave OpenMandriva and return to Fedora for the time being as my primary browser fails on OM presently.
FYI, the issue with the icon in the taskbar (dash to panel) not showing the correct indicator and instead showing the ‘unknown app’ icon still exists. The keyring password popup stopped occurring, but given all of the other bugs that came with that workaround, I’d suggest anybody reading this avoids the suggested solutions as they created the problems noted above for me.
Of course your choice.
May I ask if the Brave Browser is the only (or the more serious) issue you encountered? Tbh I may have missed or forgotten some bits from you if there are any.
Either way you may want to check later if this problem have been solved and maybe to give OM another try.
Thanks for reporting, anyway. It will be investigated soon.
I may try to resume using it next weekend and see if I can resolve the issues, but as I have work tomorrow I need to wrap up and have concluded it is not ready to use daily for this next week at least.
Sadly my day job requires me to have Skype open and that application had the same issues with the keyring and the additional issue with the icon indicator that the Brave Browser had in the taskbar.
Most of the experience was fine I was able to recreate much of the experience that I liked about using Fedora and overall I would say that if it wasn’t for the browser failing to sync after those changes were made to try and solve the keyring problem, I’d have made OM my new daily driver on all of my workstations.
I remember having keyring issues on Arch a while back. I can’t recall if I got it solved, though. But I know I tried something about PAM from the Arch wiki. Maybe you could try step 4 from the arch wiki: GNOME/Keyring - ArchWiki
I’ve since reinstalled the OS and this time used the AppImages from this GitHub page (Nightly and Stable builds also available from the same provider): https://github.com/srevinsaju/Brave-AppImage/releases/tag/beta.
This AppImage approach to installing each of the apps in question also suffers from the same keyring popup upon each launch of the application despite using an alternative approach to installing the apps and as with the previous install approach it also shows the running app indicator as an unknown app rather than highlighting the actual pinned app icon for the respective app.
Totally uneducated guess on my part so please forgive me if this isn’t accurate, but given that it also affected the Skype app, I’m curious if it has something to do with ‘Electron’ based apps specifically (I’m not sure if Skype is Electron based, hence I stated this is an uneducated guess on my part).
I think you mean the GPG key issue with the Chrome repo. No, this is something else. The GPG issue is when you want to install Chrome, but the keyring issue is when you start the program.
The keyring issue is that the keyring does not get unlocked when you log into your OS with your user credentials and thus brave asks you for your credentials again to unlock the keyring when you start it. And in your case also Skype asks, probably because it also makes use of the keyring.
It has something to do with the KDE Wallet or PAM or something. I am no Linux pro, so I can’t assist more than that. As I said, I had this issue on an Arch install, but can’t remember if I solve it and how I would have solved it?
Yeah that best describes my issue, although I’m using Gnome rather than KDE.
Just to add, during the install setup, I selected the option to make the user & admin password the same and to ensure that it requires password on boot (I heard that if you disable password on boot the keyring problem may occur, but in my case even with the password on boot the problem still occurs).
I don’t think that is a bug, is it? Seems like a good idea for those that don’t manage their passwords in some other container. I have it disabled to get around that.
But I don’t have this issue now on OM. It just works. I don’t know what’s the differnce.
Differences are that I now don’t have LUKS enabled, I might have used brave from AUR on Arch and now with the brave repo (but I am not sure) and I used this time a GPG key for the wallet instead of a password. I can’t think of anything else.
That is what it should do - “unlock automatically on login”, but that is exactly was it doesn’t do. At least it didn’t for me on Arch, but does on OM and here I did nothing and it unlocks automatically and on Arch I couldn’t get it to work, even with following guides like the one you posted.
Maybe I checked an additional checkbox when creating the keyring that I can’t remember? Something must be different.
It’s probably disabled in System Settings. To me, it seems redundant. The bypass was supposed to be if the password is set the same as the user password. Perhaps that is the same with you. Then again, if that is the case, disabled is probably just as good. Someone getting into your box at the keyboard would have gotten access to that information anyway. It’s not adding another layer of security if the data at rest isn’t encrypted.
