Bug 463638 - Wallet manager does not work until libkf5wallet-bin is manually installed
Summary: Wallet manager does not work until libkf5wallet-bin is manually installed
Status: RESOLVED DUPLICATE of bug 456968
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages Unstable Edition (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-30 20:14 UTC by Oded Arbel
Modified: 2023-01-03 14:36 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oded Arbel 2022-12-30 20:14:40 UTC
SUMMARY
The org.kde.kwalletd5 DBus service is provided by the Neon package libkf5wallet-bin, which is only required by the optional kwalletcli package - so it isn't installed by default.

Without the org.kde.kwalletd5 service, wallet manager doesn't work - it has no UI (just a blank page and a menu with options that don't do anything) and the terminal has logs like "The name org.kde.kwalletd5 was not provided by any .service files".

Also other things that apparently rely on the org.kde.kwalletd5 do not work - such as wireless network password storage.

STEPS TO REPRODUCE
1. Install a new Neon unstable system
2. Log in
3. Run kwalletmanager --shot

OBSERVED RESULT
The wallet manager shows but it has no UI to manage wallets.

EXPECTED RESULT
The wallet manager should have a UI to manage wallets

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.26.80
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7

ADDITIONAL INFORMATION
Another reproduction showing a problem is to open the KDE Wallet KCM (from System Settings) and see that the "select wallet to use as default" has no available options.

I haven't actually installed a new Neon unstable system (I upgraded to it from Kubuntu). But even if libkf5wallet-bin is installed on your system, the problem can be seen by running `apt purge libkf5wallet-bin` and noticing that kwalletmanager isn't one of the packages that apt would like to remove as part of the process.
Comment 1 Paul Worrall 2022-12-31 09:31:29 UTC
On my Neon Unstable, libkf5wallet-bin was uninstalled by the update on 16 Dec and wallet manager still works.
Comment 2 Oded Arbel 2023-01-02 21:23:52 UTC
(In reply to Paul Worrall from comment #1)
> On my Neon Unstable, libkf5wallet-bin was uninstalled by the update on 16
> Dec and wallet manager still works.

Interesting.

Can you please check for me - does your system currently has a running instance of kwalletd5, and if so - what package does it come from?

If it doesn't have a kwalletd5 running - when you run kwalletmanager5 from the console, does it causes kwalletd5 to run, or do you get error messages like so:

---8<---
Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kwalletd5 was not provided by any .service files")
kf.wallet.api: The kwalletd service is still not registered
kf.wallet.api: Invalid DBus reply:  QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kwalletd5 was not provided by any .service files")
Couldn't start kwalletd:  QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kwalletd5 was not provided by any .service files")
kf.wallet.api: The kwalletd service is still not registered
---8<---

For me, after running kwalletmanager5 and getting these errors, clicking the "Wallet Manager" icon in the system tray opens a small dialog with a menu but that is otherwise empty and non-functioning. Manually installing the package libkf5wallet-bin solves the problem for me (notably, to test this I removed the libkf5wallet-bin package, after which kwalletd5 continued working and everything looked fine - until I killed kwalletd5 and kwalletmanager5, after which none would start properly - of course).
Comment 3 Paul Worrall 2023-01-03 09:45:46 UTC
Ah, when I run kwalletmanager5 it somehow finds and runs a locally-compiled version of kwalletd5 (even though it's not on the PATH).

If I remove that I get the behaviour you report.
Comment 4 Oded Arbel 2023-01-03 14:36:19 UTC
Seems like a duplicate of bug #456968, so I'm moving this discussion there.

*** This bug has been marked as a duplicate of bug 456968 ***