FS#59374 - [kwallet] PLEASE ENTER SUMMARY
Attached to Project:
Arch Linux
Opened by Damjan Georgievski (damjan) - Tuesday, 17 July 2018, 21:01 GMT
Last edited by Antonio Rojas (arojas) - Monday, 23 July 2018, 22:38 GMT
Opened by Damjan Georgievski (damjan) - Tuesday, 17 July 2018, 21:01 GMT
Last edited by Antonio Rojas (arojas) - Monday, 23 July 2018, 22:38 GMT
|
Details/usr/share/dbus-1/services/org.kde.kwalletd.service |
This task depends upon
Closed by Antonio Rojas (arojas)
Monday, 23 July 2018, 22:38 GMT
Reason for closing: Works for me
Additional comments about closing: that service file is needed, it's the application's job to make sure to call the right service.
Monday, 23 July 2018, 22:38 GMT
Reason for closing: Works for me
Additional comments about closing: that service file is needed, it's the application's job to make sure to call the right service.
The title should've been [kwallet] Remove legacy KDE4 dbus service.
Details:
the kwallet 5.48.0-1 package includes 2 dbus .service files, /usr/share/dbus-1/services/org.kde.kwalletd5.service and /usr/share/dbus-1/services/org.kde.kwalletd.service, the later refers to a legacy KDE4 version registering Name=org.kde.kwalletd and starting Exec=/usr/bin/kwalletd. This program doesn't exist in the kwallet package, and it seems that it breaks programs (owncloud) that try to invoke it.
The issue I've seen is: I login into plasma, owncloud-client (2.4.1) pops up with a message it can't get the password from kwallet, at the same time the user log shows:
systemd[559]: Created slice dbus\x2d:1.2\x2dorg.kde.kwalletd.slice.
systemd[559]: Started dbus-:1.2-org.kde.kwalletd@0.service.
systemd[704]: dbus-:1.2-org.kde.kwalletd@0.service: Executable /usr/bin/kwalletd missing, skipping: No such file or directory
I've removed the offending /usr/share/dbus-1/services/org.kde.kwalletd.service and owncloud-client now works out-of-the-box.
/etc/pam.d/sddm has:
-auth optional pam_kwallet5.so
-session optional pam_kwallet5.so auto_start
and /usr/bin/kwalletd5 runs and works fine
So, if your environment variables are correctly set, it's not qtkeychain what's calling it.