I just upgraded to 25.05, and now when I try to launch brave, I get this popup
I was getting this as well, after I downloaded some KDE/Qt app (I don’t remember the name at the moment). I had to run the following command to avoid the late start up:
$ systemctl --user stop app-dbus\\x2d:1.2\\x2dorg.kde.kwalletd6.slice app-dbus\\x2d:1.2\\x2dorg.kde.secretservicecompat.slice
Sadly that didn’t work for me. I have noticed that I now have kwalletd6 and kwallet-query in my path, both of which come from the kwallet package. But I can’t figure out where it’s coming from. I have checked my config’s environment.systemPackages as well as the users.users.<user>.packages and it’s not in either.
Okay, I figured out the issue. The spectacle package was renamed to kdePackages.spectacle. Somehow that one package, despite seemingly containing nothing to do with kwallet, pollutes my whole environment with it. Commenting it out and rebooting my system, my system behaves as it used to.
I would like to know how this works though. How can one package add another to your system, as well as seemingly some config to go along with it?
edit:
poking around in the result of the curret kdePackages.spectacle and the old libsForQt5.spectacle, I noticed something I have never seen before
nix-support/propagated-user-env-packages
Inside kdePackages.spectacle we find tons of junk
dbus-1.14.10
systemd-257.5
cups-2.4.11
kglobalaccel-6.14.0
kauth-6.14.0
kjobwidgets-6.14.0
kwallet-6.14.0
kio-6.14.0
kstatusnotifieritem-6.14.0
libaccounts-glib-1.27
signond-8.61-unstable-2023-11-24
whereas with the old version
kipi-plugins-23.08.5
libkipi-23.08.5
surely spectacle doesn’t need all this stuff to work… right?
I was hit by this too, added kdePackages.okular to my home.packages (home-manager standalone) and I started to get the same prompt.