Am I the only KDE4 user on Freebsd?

[Raphael Kubo da Costa]

Heino Tiedemann <rotkaps_spam_trap at gmx.de> writes:

> ahab:/home/rotkap> systemsettings(22920): Couldn't start kglobalaccel from kglobalaccel.desktop:  "Dienst ?kglobalaccel.desktop? nicht auffindbar."
>
> systemsettings(22920) KGlobalAccelPrivate::getComponent: Failed to
> connect to the kglobalaccel daemon
> QDBusError("org.freedesktop.DBus.Error.NameHasNoOwner", "Could not get
> owner of name 'org.kde.kglobalaccel': no such name")
> systemsettings(22920) KGlobalAccelPrivate::getComponent: Failed to
> connect to the kglobalaccel daemon
> QDBusError("org.freedesktop.DBus.Error.NameHasNoOwner", "Could not get
> owner of name 'org.kde.kglobalaccel': no such name")
> systemsettings(22920) KGlobalAccelPrivate::getComponent: Failed to
> connect to the kglobalaccel daemon
> QDBusError("org.freedesktop.DBus.Error.NameHasNoOwner", "Could not get
> owner of name 'org.kde.kglobalaccel': no such name")
> systemsettings(22920): Couldn't start knotify from knotify4.desktop:  "Dienst ?knotify4.desktop? nicht auffindbar."
>
> systemsettings(22920)/kdeui (KNotification)
> KNotification::slotReceivedIdError: Error while contacting notify
> daemon "The name org.kde.knotify was not provided by any .service
> files"
> systemsettings(22920)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
> systemsettings(22920) KGlobalShortcutsEditor::undo: Undo the changes

As Olivier wrote, you do seem to have some D-Bus-related issue, and
other KDE4 users (including me) usually communicate over the kde-freebsd
mailing list.

If you try to manually start `kglobalaccel' on a terminal, what output
do you get?

I also notice an error message about knotify4. Can you make sure
kde4-runtime is properly installed and knotify4.desktop is present on
your system?