I run Gnome on my Manjaro tower (stable channel) and seem to have two keyring apps which prompt me to enter a password every time I boot into Gnome. One is GTK based and I am not 100% sure about the other, might by Qt based - - I did have Plasma installed at some point but moved to Gnome some time ago.
My question is: How do I automate the keyring unlock without having to manually enter it twice? Ideally I wouldn’t even have to enter it once, it would just be automatic.
Additional note: The keyring password I enter for both prompts is the same but they are different from the user password I enter when signing in via GDM.
Before I created this topic, the forum referred me to other topics like this one:
It is possible to have more DE installed - but due to complications with background services - it is recommended to avoid Plasma and Gnome on the same file system.
If you build your system from the ground up; you can mix and match as you see fit; always know what implication your choice has; often you only know after you tried, so keeping a record of both successes and failures is important.
From my experience as developer and former ISO maintainer here is a couple of hints.
DE is a desktop environment which has a set tight knit packages and therefore work best within that set of packages.
Gnome
KDE/Plasma
Xfce
Gnome and Plasma (KDE) - has conflicting keyrings and conflicting display managers (GDM and SDDM) and will only create frustration.
Xfce and Gnome - watchout for the display manager (LightDM vs. GDM recommended to use LightDM) - the combination may create issues where screen lock will malfunction
Xfce and Plasma (conflicting keyrings and conflicting display managers) - recommended to use SDDM for access to Xfce as Plasma is tightly integrated with SDDM.
Techically Lxqt and Lxde could be labelled DE as they provide a panel and a session manager but more loosely coupled than e.g. Plasma because they are intended to extend the functionality of the Openbox window manager.
Both Gnome, Xfce and Plasma provides a window manager and compositor and any of those window managers can be used with e.g. Lxqt; the same can be said for the keyring applications - Lxqt will work with any of them.
The best place to look for conflicts is the /etc/xdg folder tree.
I went to go remove KDE Wallet (kwallet) and pacman checked the dependencies saying that they break other dependencies:
$ sudo pacman -R kwallet5 kwallet
[sudo] password for <user>:
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kwallet breaks dependency 'kwallet' required by kio
:: removing kwallet5 breaks dependency 'kwallet5' required by kio5
:: removing kwallet breaks dependency 'kwallet' required by plasma-workspace
Next I tried removing kio, kio5 and plasma-workspace:
sudo pacman -R kio kio5 plasma-workspace
checking dependencies…
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kio breaks dependency ‘kio’ required by ark
:: removing kio breaks dependency ‘kio’ required by baloo
:: removing kio breaks dependency ‘kio’ required by baloo-widgets
:: removing kio breaks dependency ‘kio’ required by dolphin
:: removing kio breaks dependency ‘kio’ required by ffmpegthumbs
:: removing kio breaks dependency ‘kio’ required by kactivitymanagerd
:: removing kio breaks dependency ‘kio’ required by kcmutils
:: removing kio breaks dependency ‘kio’ required by kde-cli-tools
:: removing kio5 breaks dependency ‘kio5’ required by kdeclarative5
:: removing kio breaks dependency ‘kio’ required by kglobalacceld
:: removing kio breaks dependency ‘kio’ required by kio-extras
:: removing kio breaks dependency ‘kio’ required by kio-fuse
:: removing kio5 breaks dependency ‘kio5’ required by knewstuff5
:: removing kio breaks dependency ‘kio’ required by knotifyconfig
:: removing kio5 breaks dependency ‘kio5’ required by knotifyconfig5
:: removing kio breaks dependency ‘kio’ required by konsole
:: removing kio breaks dependency ‘kio’ required by kparts
:: removing kio5 breaks dependency ‘kio5’ required by kparts5
:: removing kio breaks dependency ‘kio’ required by kscreenlocker
:: removing kio breaks dependency ‘kio’ required by ksystemstats
:: removing kio breaks dependency ‘kio’ required by ktexteditor
:: removing kio breaks dependency ‘kio’ required by libplasma
:: removing kio breaks dependency ‘kio’ required by plasma-integration
:: removing kio5 breaks dependency ‘kio5’ required by plasma5-integration
:: removing kio breaks dependency ‘kio’ required by plasma5support
:: removing kio breaks dependency ‘kio’ required by systemsettings
:: removing kio breaks dependency ‘kio’ required by xdg-desktop-portal-kde
:: removing plasma-workspace breaks dependency ‘plasma-workspace’ required by xdg-desktop-portal-kde
The above tracebacks clearly show what both @BG405 and @linux-aarhus expected: my system is broken due to remanents of previously mismanged Plasma DE packages. If you folks can suggest a few easy commands to resolve these broken dependnecnies, I am all ears. But it sounds like the required next step might be for me to nuke my root directory from orbit and reinstall Manjaro using the latest Gnome ISO. Is that correct?
You could try e.g. pacman -Rns (I’d deal with those three one at a time) which should take care of dependencies as long as they themselves aren’t depended on by anything else. You may have orphans to clean up afterwards, if it works.
Otherwise, it’s a case of going through them one by one … or reinstalling.
While I didn’t resolve dependency hell, I accomplished my objective as outlined in my original post.
Here was my winning 2 step process:
I installed kwalletmanager and kwalletd5 using pacman. Next I backed up ~/.local/share/kwalletd/kdewallet.kwl. I rebooted, logged in, and chose a new keyring password.
I used seahorse to reset Gnome’s keyring passsword.
…now when I login to Gnome I no longer get prompted to enter my 2 keyrings manully. Seamless!
