https://bugs.kde.org/show_bug.cgi?id=513595
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #12 from [email protected] --- I can reproduce this on Debian (sid/trixie) as well, so it doesn't look Manjaro-specific. This also directly answers comment #5 ("is there a user-facing portal problem, or just the log message?") - yes, there is. Versions: - Plasma: 6.6.5 - xdg-desktop-portal-kde: 6.6.5-2 - KIO (KF6): 6.23.0 - Qt: 6.10.2 - Ark: 26.04.0 Symptom: Ark's "Open destination folder after extraction" silently does nothing - Dolphin never opens, no error is shown to the user. `xdg-open "$HOME"` from a terminal opens Dolphin fine, so the inode/directory -> Dolphin association itself is correct; this is purely about the portal-mediated launch. Reproduction: 1. Right after login, plasma-xdg-desktop-portal-kde.service logs the usual: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID") 2. Open Ark, extract an archive, click "open destination folder". Nothing happens. 3. At that exact moment, the SAME plasma-xdg-desktop-portal-kde process additionally logs: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError kf.kio.core: Connection::send() called with connection not inited (x2) 4. Workaround: `systemctl --user restart plasma-xdg-desktop-portal-kde.service xdg-desktop-portal.service`. After this, repeating step 2 works correctly for the rest of the session - until next login, when the cycle repeats. Hypothesis: the failed app-ID registration at startup (step 1) seems to leave the daemon's internal KIO Connection permanently in a "not inited" state, breaking any later KIO operation the daemon performs on behalf of OpenURI/OpenDirectory portal calls (which Ark's "open destination folder" goes through). A fresh process (restart) gets a working KIO connection and the symptom disappears until next login. Happy to provide more logs if useful. Given this confirms a real user-facing regression tied to step 1, would it make sense to reopen? -- You are receiving this mail because: You are watching all bug changes.
