Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 934785 - kde-misc/kdeconnect-24.05.1: Full path needs set in org.kde.kdeconnect.service for d-bus activation
Summary: kde-misc/kdeconnect-24.05.1: Full path needs set in org.kde.kdeconnect.servic...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo KDE team
URL: https://bugs.kde.org/show_bug.cgi?id=...
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks: gear-24.08.1-stable
  Show dependency tree
 
Reported: 2024-06-23 19:37 UTC by Kris Scott
Modified: 2024-12-04 01:22 UTC (History)
7 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info kdeconnect (kde-connect-emerge-info,25.34 KB, text/plain)
2024-06-26 08:38 UTC, Pavel Procopiuc
Details
emerge --info kdeconnect (kdeconnect-info.txt,7.99 KB, text/plain)
2024-06-26 08:45 UTC, Henry Paradiz
Details
emerge --info kde-connect (emerege --info kde-connect,7.47 KB, text/plain)
2024-09-21 18:08 UTC, Konstantin Zharov
Details
emerge --info kde-misc/kdeconnect (emerge-info-kdeconnect.txt,7.83 KB, text/plain)
2024-10-04 20:39 UTC, Stephen Bosch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kris Scott 2024-06-23 19:37:56 UTC
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.
Comment 1 Andreas Sturmlechner gentoo-dev 2024-06-24 15:52:07 UTC
Why you no show us `emerge --info kdeconnect`?
Comment 2 Pavel Procopiuc 2024-06-26 08:38:11 UTC
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
Comment 3 Henry Paradiz 2024-06-26 08:45:16 UTC
Created attachment 896449 [details]
emerge --info kdeconnect

Confirming this bug as well. Plasma 6.1.0
Comment 4 repomansez 2024-06-29 02:10:25 UTC
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)
Comment 5 repomansez 2024-07-05 22:28:56 UTC
Latest update (kde-misc/kdeconnect-24.05.2:6::gentoo [24.05.1:6::gentoo]) has solved the issue for me!
Comment 6 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-07-06 05:48:30 UTC
I can't figure out what would've fixed it (repomansez shared their qlop with me).
Comment 7 Andreas Sturmlechner gentoo-dev 2024-07-07 21:19:06 UTC
Yeah, also not a single code change from 25.04.1 to .2.
Comment 8 Andreas Sturmlechner gentoo-dev 2024-07-13 10:22:54 UTC
let's call it fixed, anyway?
Comment 9 Christophe PEREZ 2024-09-07 22:50:54 UTC
I have the same error with kde-misc/kdeconnect-24.05.2

$ kdeconnect-settings 
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")
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
Comment 10 Konstantin Zharov 2024-09-21 18:08:15 UTC
Created attachment 903552 [details]
emerge --info kde-connect
Comment 11 Konstantin Zharov 2024-09-21 18:09:22 UTC
Reproduced on 24.05.2 and ~24.08.1
~amd64

Always get the message:
error activating kdeconnectd: QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute program org.kde.kdeconnect: No such file or directory")
error: Failed to execute program org.kde.kdeconnect: No such file or directory
Comment 12 Stephen Bosch 2024-10-04 20:39:49 UTC
Created attachment 904913 [details]
emerge --info kde-misc/kdeconnect
Comment 13 Stephen Bosch 2024-10-04 20:40:30 UTC
I observe the same problem with 24.08.1:

$ kdeconnect-app 
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")
qml: failed call DaemonDbusInterface(0x55ef9cddc0c0) announcedName announcedNameChanged Failed to execute program org.kde.kdeconnect: No such file or directory
Comment 14 Christophe PEREZ 2024-10-04 20:46:22 UTC
(In reply to Stephen Bosch from comment #13)
> I observe the same problem with 24.08.1:
> 
> $ kdeconnect-app 
> 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")
> qml: failed call DaemonDbusInterface(0x55ef9cddc0c0) announcedName
> announcedNameChanged Failed to execute program org.kde.kdeconnect: No such
> file or directory

$ cat /etc/portage/patches/kde-misc/kdeconnect/dbus_service.patch 
diff '--color=auto' -ur kdeconnect-kde-24.05.2.orig/daemon/org.kde.kdeconnect.service.in kdeconnect-kde-24.05.2/daemon/org.kde.kdeconnect.service.in
--- kdeconnect-kde-24.05.2.orig/daemon/org.kde.kdeconnect.service.in    2024-06-28 17:08:24.000000000 -0400
+++ kdeconnect-kde-24.05.2/daemon/org.kde.kdeconnect.service.in 2024-09-09 19:37:48.779486870 -0400
@@ -1,3 +1,3 @@
 [D-BUS Service]
 Name=org.kde.kdeconnect
-Exec=kdeconnectd
+Exec=/usr/bin/kdeconnectd

worked for me
Comment 15 Stephen Bosch 2024-10-04 20:50:15 UTC
(In reply to Christophe PEREZ from comment #14)
> $ cat /etc/portage/patches/kde-misc/kdeconnect/dbus_service.patch 
> diff '--color=auto' -ur
> kdeconnect-kde-24.05.2.orig/daemon/org.kde.kdeconnect.service.in
> kdeconnect-kde-24.05.2/daemon/org.kde.kdeconnect.service.in
> --- kdeconnect-kde-24.05.2.orig/daemon/org.kde.kdeconnect.service.in   
> 2024-06-28 17:08:24.000000000 -0400
> +++ kdeconnect-kde-24.05.2/daemon/org.kde.kdeconnect.service.in 2024-09-09
> 19:37:48.779486870 -0400
> @@ -1,3 +1,3 @@
>  [D-BUS Service]
>  Name=org.kde.kdeconnect
> -Exec=kdeconnectd
> +Exec=/usr/bin/kdeconnectd
> 
> worked for me

Thanks, Christoph, I had done that and it works, but the package also needs to be fixed so that the correct path is written to daemon/org.kde.kdeconnect.service.in.
Comment 16 Christophe PEREZ 2024-10-04 20:56:49 UTC
(In reply to Stephen Bosch from comment #15)
> Thanks, Christoph, I had done that and it works, but the package also needs
> to be fixed so that the correct path is written to
> daemon/org.kde.kdeconnect.service.in.

Of course.

https://develop.kde.org/docs/features/d-bus/dbus_autostart_services/
tells :

"Unlike .desktop files, though, the Exec line must contain the full path to the application that is to be started."

So Exec must be filled with full pathname to kdeconnectd

$ cat /usr/share/dbus-1/services/org.kde.kdeconnect.service
[D-BUS Service]
Name=org.kde.kdeconnect
Exec=/usr/bin/kdeconnectd

So that's a package bug and it should be reopened.
Comment 17 Andreas Sturmlechner gentoo-dev 2024-10-04 20:58:41 UTC
The upstream bug is still open as far as I can see.
Comment 18 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-10-05 08:45:12 UTC
(In reply to Christophe PEREZ from comment #16)
> (In reply to Stephen Bosch from comment #15)
> > Thanks, Christoph, I had done that and it works, but the package also needs
> > to be fixed so that the correct path is written to
> > daemon/org.kde.kdeconnect.service.in.
> 
> Of course.
> 
> https://develop.kde.org/docs/features/d-bus/dbus_autostart_services/
> tells :
> 
> "Unlike .desktop files, though, the Exec line must contain the full path to
> the application that is to be started."
> 

FWIW, I don't see this in the dbus spec at https://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-starting-services.

It also doesn't explain why it works for some people and not others.

> So Exec must be filled with full pathname to kdeconnectd
> 
> $ cat /usr/share/dbus-1/services/org.kde.kdeconnect.service
> [D-BUS Service]
> Name=org.kde.kdeconnect
> Exec=/usr/bin/kdeconnectd
> 
> So that's a package bug and it should be reopened.

No evidence has been given for it being a _packaging_ bug.
Comment 19 Larry the Git Cow gentoo-dev 2024-10-05 09:04:44 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=422637fbf570af764c6856a1650368841314479b

commit 422637fbf570af764c6856a1650368841314479b
Author:     Sam James <sam@gentoo.org>
AuthorDate: 2024-10-05 09:03:29 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2024-10-05 09:03:29 +0000

    kde-misc/kdeconnect: fix DBus service file
    
    Closes: https://bugs.gentoo.org/934785
    KDE-bug: https://bugs.kde.org/show_bug.cgi?id=489343
    Signed-off-by: Sam James <sam@gentoo.org>

 .../files/kdeconnect-24.08.1-dbus-path.patch       |  66 ++++++++++++
 kde-misc/kdeconnect/kdeconnect-24.08.1-r1.ebuild   | 111 +++++++++++++++++++++
 2 files changed, 177 insertions(+)
Comment 20 Kari Maru 2024-12-04 01:22:28 UTC
good