| Summary: | 'No such file or directory' error starting dbus service for kdeconnect | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | pallaswept <pallaswept> |
| Component: | plasmoid | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | asturm, dwawlyn, sam |
| Priority: | NOR | ||
| Version: | 24.05.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/714 | Version Fixed In: | |
| Sentry Crash Report: | |||
|
Description
pallaswept
2024-06-27 22:53:38 UTC
Likely regressed in: https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/647 (In reply to pallaswept from comment #0) > I'm on Tumbleweed, but found the 'fix' for this via a gentoo bug report: > https://bugs.gentoo.org/934785 and have seen various reports of it on other > distros. Our downstream bug report was reportedly fixed after 24.05.2, but the lack of changes in kdeconnect itself suggests there was a fix somewhere down the dependency chain. Can you confirm? (In reply to Andreas Sturmlechner from comment #2) > Our downstream bug report was reportedly fixed after 24.05.2 Now that is interesting, thanks for looking into this Andreas! Sadly it's still broken here on tumbleweed, with kdeconnectd at 24.05.2. It does all suggest that the root cause and fix lie elsewhere. I wonder if gentoo has also had a dbus update, or similar, in that timeframe? I was double-checking that TW don't patch this source (they don't), and noticed that in the package change log, there was only one change noted for the 24.05.1 release: "Add Qt::DBus dependency to kdeconnect_runcommand_config". That was quite possibly when this broke for me. I can't be sure, but the timelines match up. Maybe this lends a hint? Hi, I think I just encountered this bug on ubuntu-based "tuxedo-OS": https://discuss.kde.org/t/kdeconnect-suddenly-stopped-working-gives-errors-like-qdbuserror-org-freedesktop-dbus-error-spawn-execfailed-failed-to-execute-program-org-kde-kdeconnect-no-such-file-or-directory/20865 but like, the bug just suddenly appeared without any upgrade to kdeconnect apparently? No other users of tuxedo-OS have reported experiencing the same https://www.reddit.com/r/tuxedocomputers/comments/1f8kc1j/kdeconnect_suddenly_stopped_working_gives_errors/? This is what I'm calling the solution for now: https://discuss.kde.org/t/kdeconnect-suddenly-stopped-working-gives-errors-like-qdbuserror-org-freedesktop-dbus-error-spawn-execfailed-failed-to-execute-program-org-kde-kdeconnect-no-such-file-or-directory/20865/3?u=dwawlyn but yeah, no idea *why* this bug suddenly happened for me, but if anyone wants any information from me that might be useful, ask away... |