search

eliasp / plasma-workspace-units

systemd user-session units for KDE Frameworks 5/Plasma 5
http://quickgit.kde.org/?p=plasma-systemd-integration.git
GNU General Public License v2.0
19 stars 4 forks source link

kdeconnectd and baloo services fails to start on Arch #24

Open AnAkkk opened 9 years ago

AnAkkk commented 9 years ago

There seem to be a problem with the kdeconnectd and baloo user services, they fail to start:

org.kde.baloo.busname - DBUS1: org.kde.baloo
   Loaded: loaded (/usr/share/dbus-1/services/org.kde.baloo.service)
   Active: failed (Result: service-failed-permanent) since jeu. 2015-09-03 10:28:48 CEST; 2h 52min ago
     Docs: man:systemd-dbus1-generator(8)

sept. 03 10:28:47 laptop systemd[1417]: Listening on DBUS1: org.kde.baloo.
sept. 03 10:28:48 laptop systemd[1417]: org.kde.baloo.busname: Unit entered failed state.
org.kde.kdeconnect.busname - DBUS1: org.kde.kdeconnect
   Loaded: loaded (/usr/share/dbus-1/services/org.kde.kdeconnectd.service)
   Active: failed (Result: service-failed-permanent) since jeu. 2015-09-03 10:28:50 CEST; 2h 52min ago
     Docs: man:systemd-dbus1-generator(8)

sept. 03 10:28:47 laptop systemd[1417]: Listening on DBUS1: org.kde.kdeconnect.
sept. 03 10:28:50 laptop systemd[1417]: org.kde.kdeconnect.busname: Unit entered failed state.
baloo.service - Baloo file indexer
   Loaded: loaded (/usr/lib/systemd/user/baloo.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since jeu. 2015-09-03 10:28:48 CEST; 2h 52min ago
  Process: 1591 ExecStop=/usr/bin/balooctl stop (code=exited, status=0/SUCCESS)
  Process: 1564 ExecStart=/usr/bin/baloo_file (code=exited, status=0/SUCCESS)
 Main PID: 1564 (code=exited, status=0/SUCCESS)

sept. 03 10:28:47 laptop systemd[1417]: Starting Baloo file indexer...
sept. 03 10:28:48 laptop baloo_file[1564]: Baloo File Indexing has been disabled
sept. 03 10:28:48 laptop systemd[1417]: Started Baloo file indexer.
sept. 03 10:28:48 laptop systemd[1417]: baloo.service: Start request repeated too quickly.
sept. 03 10:28:48 laptop systemd[1417]: Failed to start Baloo file indexer.
sept. 03 10:28:48 laptop systemd[1417]: baloo.service: Unit entered failed state.
sept. 03 10:28:48 laptop systemd[1417]: baloo.service: Failed with result 'start-limit'.
kdeconnectd.service - Connect your computer to your smartphone or tablet
   Loaded: loaded (/usr/lib/systemd/user/kdeconnectd.service; static; vendor preset: enabled)
   Active: failed (Result: start-limit) since jeu. 2015-09-03 10:28:50 CEST; 2h 53min ago
  Process: 1674 ExecStop=/usr/bin/kquitapp5 kdeconnectd (code=exited, status=1/FAILURE)
  Process: 1671 ExecStart=/usr/lib64/libexec/kdeconnectd (code=exited, status=203/EXEC)
 Main PID: 1671 (code=exited, status=203/EXEC)

sept. 03 10:28:50 laptop systemd[1671]: kdeconnectd.service: Failed at step EXEC spawning /usr/lib64/libexec/kdeconnectd: No such file or directory
sept. 03 10:28:50 laptop systemd[1417]: kdeconnectd.service: Main process exited, code=exited, status=203/EXEC
sept. 03 10:28:50 laptop kquitapp5[1674]: default unknown: "Application kdeconnectd could not be found using service org.kde.kdeconnectd and path /MainApplication."
sept. 03 10:28:50 laptop systemd[1417]: kdeconnectd.service: Control process exited, code=exited status=1
sept. 03 10:28:50 laptop systemd[1417]: Failed to start Connect your computer to your smartphone or tablet.
sept. 03 10:28:50 laptop systemd[1417]: kdeconnectd.service: Unit entered failed state.
sept. 03 10:28:50 laptop systemd[1417]: kdeconnectd.service: Failed with result 'exit-code'.
sept. 03 10:28:50 laptop systemd[1417]: kdeconnectd.service: Start request repeated too quickly.
sept. 03 10:28:50 laptop systemd[1417]: Failed to start Connect your computer to your smartphone or tablet.
sept. 03 10:28:50 laptop systemd[1417]: kdeconnectd.service: Failed with result 'start-limit'.

I'm using kdbus on a 4.2 kernel + systemd 224.

faho commented 8 years ago

@AnAkkk: In case you are still interested: