https://bugs.kde.org/show_bug.cgi?id=506391
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|NEEDSINFO |REPORTED --- Comment #4 from [email protected] --- sorry for missing details: i am using the bootc containerimage of quay.io: rpm-ostree rebase ostree-unverified-registry:quay.io/fedora-ostree-desktops/kinoite:42.20250701.0-x86_64 And in user-journal we find (running in a virtualbox) Jul 01 14:32:51 fedora dbus-broker-launch[1568]: Ready Jul 01 14:32:51 fedora systemd[1304]: Started plasma-kcminit.service - KDE Config Module Initialization. Jul 01 14:32:51 fedora systemd[1304]: Starting plasma-ksmserver.service - KDE Session Management Server... Jul 01 14:32:51 fedora systemd[1304]: Started plasma-kwallet-pam.service - Unlock kwallet from pam credentials. Jul 01 14:32:51 fedora systemd[1304]: Starting plasma-kded6.service - KDE Daemon 6... Jul 01 14:32:51 fedora pam_kwallet_init[1583]: 2025/07/01 14:32:51 socat[1583] W address is opened in read-write mode but only supports read-only Jul 01 14:32:51 fedora kded6[1581]: VMware: No 3D enabled (0, Success). Jul 01 14:32:51 fedora kded6[1581]: libEGL warning: egl: failed to create dri2 screen Jul 01 14:32:51 fedora kded6[1581]: VMware: No 3D enabled (0, Success). Jul 01 14:32:51 fedora kded6[1581]: libEGL warning: egl: failed to create dri2 scre The effect being, that the wallet needs to be explicitly opened when going to systemsettings > kde wallet > launch wallet manager On a normal fedora installation and, as you tested already, standard ostree based official image, this works. Not on the (i admit, generated by ci-test / https://gitlab.com/fedora/ostree/ci-test and put into quay-registry) - not official yet - version. I am running this on gitlab myself (with some additions to the base-installations, other repos and the like) but the result is the same as in quay.io Still necessary to fix esp. when fedora atomic desktops switches over to bootc... -- You are receiving this mail because: You are watching all bug changes.
