so whenever I switch from wayland to niri I am logged out of all my browsers, vscode and other apps
How can I fix that
so whenever I switch from wayland to niri I am logged out of all my browsers, vscode and other apps
How can I fix that
You probably don’t have a secrets manager running when you log into Niri.
Whichever DE/WM you are logged into before logging into Niri probably has a secrets manager set up and running.
The simplest one to use is gnome-keyring. You need to place it in your autostart file for Niri, or whatever equivalent to an autostart file Niri has.
See here: https://wiki.archlinux.org/title/GNOME/Keyring
Also check the Niri docs for general configuration: https://wiki.archlinux.org/title/Niri
PS: Wayland is not a DE (desktop environment) or WM (window manager).
I went down this rabbit hole a while back - short answer, you can’t fix it.
It is the xdg-desktop-portal-{de/wm} change that causes the issue - workaround - install a password manager extension (I use bitwarden) so you can at least log in quicker.
Dms Is just a shell but wc a to wc b start a new wayland compositor you use niri alsonwith dms niri?
I doubt this can be correct. What about just manually starting the keyring after logging into Niri? Maybe even setting a keyboard shortcut for it as well?
Like:
gnome-keyring-daemon
Or setting it to autostart with PAM?
Of course, you’d need to install the needed packages first:
sudo pacman -Syu gnome-keyring xdg-desktop-portal-gnome xdg-desktop-portal-gtk
Additionally, I’ve had this happen several times just switching from KDE to Openbox and vice versa. But it only happened with Chromium-based browsers. Firefox-based ones were okay.
One way around the Chromium issue is to use launch arguments. This is what I use:
vivaldi --password-store=gnome-libsecret --enable-blink-features=MiddleClickAutoscroll %U
brave --password-store=gnome-libsecret --enable-blink-features=MiddleClickAutoscroll %U
You can remove -enable-blink-features=MiddleClickAutoscroll if you don’t need it.
Do you run multiple DE/WMs? Just try it:
Going to demonstrate with screen shots, will come back and edit:
First MangoWM:
Next Plasma (BRB)
Image 1 - logged in to forum, logged out to plasma.
Image 2 - Always get this, clicked continue with data loss
Image 3 - Logged out of forum…
Am running kwallet, tried gnome-keyring and recently tried oo7 - same issues. Cannot find the article I read that said the desktop portal switch was the issue.
and finally back to Mango:
IIRC if I flip from one wlroots compositor to another, this does not happen. I have another wlroots compositor installed, but it is not configured much, as I use it as a DM (labwc & atrium), so cannot test as the labwc config is tied down to one keybind.
Configured a keybind to launch a terminal in labwc:
Confirmed, wlroots → wlroots does not have this issue, couldn’t get a screenshot, but was not logged out of forum (in both directions). I had to unlock the keyring in labwc, but that is due to the minimal setup.
Yes, I’m like you when it comes to multiple DEs/WMs. I use Openbox, KDE, i3, Hyprland, and Labwc, and the fix I mentioned skips that dialog to switch profile or continue with possible data loss. AND I don’t have to log back in to every site I was logged into.
In my $HOME/.local/share/applications/vivaldi-stable.desktop, I have the following:
Exec=vivaldi --password-store=gnome-libsecret --enable-blink-features=MiddleClickAutoscroll %U
And in Openbox, I have the same thing (minus Exec=) in my sxhkdrc keybinds.
For Brave, the same launch arguments are in the keybinding rather than the .desktop file, and it works just the same. I put it in the .desktop file because I use Vivaldi for work, so I have not intention of changing it, and I want to ensure that if I click the Vivaldi icon in a menu, it won’t come up with that warning.
Also, looking at my configs, I don’t actually set gnome-keyring to autostart. This means it starts up once an application requests it. In my case, that is either Vivaldi or my custom BORG/Syncthing script that I’m working on.
Just found out something surprising. Apparently, gnome-keyring does not require libsecret as a dependency. What is the output of the following on your end?
pacman -Q | grep -A 0 -E "secret|keyring|polkit"
Mine is:
archlinux-keyring 20260909-1
chaotic-keyring 20251028-1
gnome-keyring 1:50.0-1
libsecret 0.21.8.2-1
polkit 127-3
polkit-kde-agent 6.7.5-1
polkit-qt5 0.201.1-1
polkit-qt6 0.201.1-1
vlc-plugin-libsecret 3.0.23_2-16
xfce-polkit 0.3-1
The thing that I have in my autostart configs isxfce-polkit.
From the Wiki:
gnome-keyring is a member of the gnome group and is thus usually present on systems running GNOME. The package can otherwise be installed on its own.
libsecret should also be installed to grant other applications access to your keyrings.
Although libgnome-keyringAUR is deprecated (and superseded by libsecret), it may still be required by certain applications.
The gnome-keyring-daemon is automatically started via a systemd user service upon logging in. It can also be started upon request via a socket.
archlinux-keyring 1:20260909-1
archlinuxcn-keyring 20260505-1
--
cachyos-keyring 20240331-1
--
chaotic-keyring 20251028-1
--
endeavouros-keyring 20231222-1
--
keepsecret 26.08.1-1.1
--
libsecret 0.21.8.2-1.1
--
polkit 127-3.1
polkit-kde-agent 6.7.5-1.1
polkit-qt6 0.201.1-1
--
python-keyring 25.7.0-3
python-keyrings-alt 1:5.0.2-3
--
python-proton-keyring-linux 0.2.3-1.1
--
python-secretstorage 3.5.0-1
I am trying oo7 again so I just dumped gnome-keyring.
For a sanity check, I just logged in and out of Openbox, KDE, and Labwc. In all cases, both Brave and Vivaldi allowed me to select my profiles with no warning or need to log back into anything. Something somewhere that I did months ago is helping me.
Again, though, gnome-keyring doesn’t need to be autostarted for the keyring to work in different DEs/WMs. Not sure about James Bond.
Got oo7 working, fairly straight forward, need to find a GUI frontend like kwallet or seahorse.
sorry guys for late replies.
you guys commented so much that I lost what to do. So please dont mind me for asking clear steps what to do.
also I dont know if kde and danklink is window manager or wayland compositor
The short answer is: Pick one, niri, hyprland, sway or on of the other wayland compositors that are supported by DMS. If you’re still undecided and are still exploring things, such inconveniences will go away when you’ve decided which wayland compositor suits your liking the most.
Don’t let this person with no whimsy subdue your will to go on the Great Linux Adventure known as Finding Nemo! If you would like to explore, then explore!
Install the needed packages.
sudo pacman -Syu gnome-keyring xdg-desktop-portal-gnome xdg-desktop-portal-gtk libsecret
vivaldi-stable.desktopExec=”--password-store=gnome-libsecret after the name of the browser
Exec=vivaldi --password-store=gnome-libsecret %UIf all else fails, as a newbie, it’s usually better to get your flippers wet by using a traditional DE like KDE or Cinnamon. Then when you know the different terms, you branch out to WMs like Niri, Hyprland, etc.
PS: @1093i3511. I’m joking ![]()