https://bugs.kde.org/show_bug.cgi?id=489343

            Bug ID: 489343
           Summary: 'No such file or directory' error starting dbus
                    service for kdeconnect
    Classification: Applications
           Product: kdeconnect
           Version: 24.05.1
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: plasmoid
          Assignee: albertv...@gmail.com
          Reporter: pallasw...@proton.me
  Target Milestone: ---

***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
KDE connect fails to start, with error:
error activating kdeconnectd:
QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute
program org.kde.kdeconnect: No such file or directory")

This can be 'fixed, by editing the dbus service, changing the path to the
kdeconnect binary, to be a full absolute path; ie, edit
/usr/share/dbus-1/services/org.kde.kdeconnect.service , changing the
'kdeconnect' to be '/usr/bin/kdeconnect'

STEPS TO REPRODUCE
1. Upgrade from a working system to KDE 6.1


OBSERVED RESULT
KDE Connect fails to start, with error:
 "error activating kdeconnectd:
QDBusError("org.freedesktop.DBus.Error.Spawn.ExecFailed", "Failed to execute
program org.kde.kdeconnect: No such file or directory")"

EXPECTED RESULT
KDE Connect continues to start at boot without any interaction.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.10
KDE Frameworks Version: 6.3
Qt Version: 6.7.2

ADDITIONAL INFORMATION
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to