| Summary: | kde-misc/kdeconnect-24.05.1: Full path needs set in org.kde.kdeconnect.service for d-bus activation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Kris Scott <kris> |
| Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | hyrurg, repomansez |
| Priority: | Normal | Keywords: | UPSTREAM |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugs.kde.org/show_bug.cgi?id=489343 | ||
| See Also: | https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/647 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info kdeconnect
emerge --info kdeconnect |
||
Why you no show us `emerge --info kdeconnect`? Created attachment 896448 [details]
emerge --info kdeconnect
I'm not the original poster, but I have the same issue and the same workaround helps. emerge --info kdeconnect is attached
Created attachment 896449 [details]
emerge --info kdeconnect
Confirming this bug as well. Plasma 6.1.0
Confirmed in KDE Connect kdeconnect.app 24.05.1
Error message:
error activating kdeconnectd: QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute program org.kde.kdeconnect: No such file or directory")
error activating kdeconnectd: QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute program org.kde.kdeconnect: No such file or directory")
kdeconnect.interfaces: dbus interface not valid
qrc:/qt/qml/org/kde/kdeconnect/app/FindDevicesPage.qml:13:1: QML FindDevicesPage: Created graphical object was not placed in the graphics scene.
emerge --info: repomansez .xyz / files/00PMFkTL.txt (spaces because new account)
|
KDE Connect is unable to start kdeconnectd via dbus. The app starts, but no devices are discoverable or connectable. Reproducible: Always Steps to Reproduce: Either start KDE connect from a terminal (using kdeconnect-app) or from the menus in the desktop. Actual Results: The kde connect app appears, but you are unable to see or connect to any devices. The output is as follows: error activating kdeconnectd: QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute program org.kde.kdeconnect: No such file or directory") error activating kdeconnectd: QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute program org.kde.kdeconnect: No such file or directory") kdeconnect.interfaces: dbus interface not valid error activating kdeconnectd: QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute program org.kde.kdeconnect: No such file or directory") error activating kdeconnectd: QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute program org.kde.kdeconnect: No such file or directory") kdeconnect.interfaces: dbus interface not valid qrc:/qt/qml/org/kde/kdeconnect/app/FindDevicesPage.qml:13:1: QML FindDevicesPage: Created graphical object was not placed in the graphics scene. kdeconnect.interfaces: dbus interface not valid error activating kdeconnectd: QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute program org.kde.kdeconnect: No such file or directory") qrc:/qt/qml/org/kde/kdeconnect/DBusProperty.qml:48: ReferenceError: write is not defined Expected Results: Devices should be detectable and discoverable via kdeconnectd. If I edit /usr/share/dbus-1/services/org.kde.kdeconnect.service, and change the Exec line to the full path of kdeconnectd (/usr/bin/kdeconnectd) I am able to run kde-connect with no issues. Not sure what the underlying cause is though. Either dbus is not getting the correct $PATH, or there's been a change where the full path is required. This is on full ~amd64 using kde plasma 6.1, and kdeconnect 24.05.1. Also on wayland if that makes a difference, did not try on xorg.