The issue also occurs using X11. Applications, however, are running flawlessly.
The journald section that to me seems related to the issue is:
un 19 10:24:52 vision kded6[2155]: QDBusObjectPath: invalid path “/modules/plasma-session-shortcuts” Jun 19 10:24:52 vision kded6[2155]: kf.dbusaddons: The kded module name “plasma-session-shortcuts” is invalid!
Jun 19 10:24:52 vision kconf_update[2212]: kf.config.kconf_update: /usr/share/kconf_update/ark.upd defined Version=5 but Version=6 was expected
Jun 19 10:24:52 vision kconf_update[2212]: kf.config.kconf_update: /usr/share/kconf_update/dolphin_detailsmodesettings.upd defined Version=5 but Version=6 was e>
Jun 19 10:24:52 vision kconf_update[2212]: kf.config.kconf_update: /usr/share/kconf_update/dolphin_directorysizemode.upd defined Version=5 but Version=6 was exp>
Jun 19 10:24:52 vision kconf_update[2212]: kf.config.kconf_update: /usr/share/kconf_update/filepicker.upd defined Version=5 but Version=6 was expected
Jun 19 10:24:52 vision kconf_update[2212]: kf.config.kconf_update: /usr/share/kconf_update/konsole.upd defined Version=5 but Version=6 was expected
Jun 19 10:24:52 vision kconf_update[2212]: kf.config.kconf_update: /usr/share/kconf_update/okular.upd defined Version=5 but Version=6 was expected
Jun 19 10:24:52 vision kded6[2155]: org.kde.plasma.dataengine.geolocation: gpsd not found
Jun 19 10:24:52 vision kded6[2155]: “location”
Jun 19 10:24:52 vision kded6[2155]:
Jun 19 10:24:52 vision kded6[2216]: xsettingsd: Loaded 14 settings from /home/peter/.config/xsettingsd/xsettingsd.conf
Jun 19 10:24:52 vision kded6[2216]: xsettingsd: Created window 0x800001 on screen 0 with timestamp 20049
Jun 19 10:24:52 vision kded6[2216]: xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0
Jun 19 10:24:52 vision kded6[2216]: xsettingsd: Took ownership of selection _XSETTINGS_S0
Jun 19 10:24:52 vision dbus-daemon[1995]: [session uid=1000 pid=1995] Activating via systemd: service name=‘org.bluez.obex’ unit=‘dbus-org.bluez.obex.service’ r>
Jun 19 10:24:52 vision dbus-daemon[1995]: [session uid=1000 pid=1995] Activation via systemd failed for unit ‘dbus-org.bluez.obex.service’: Unit dbus-org.bluez.>
Jun 19 10:24:52 vision dbus-daemon[1995]: [session uid=1000 pid=1995] Activating via systemd: service name=‘org.gtk.vfs.Daemon’ unit=‘gvfs-daemon.service’ reque>
Jun 19 10:24:52 vision systemd[1979]: Starting Virtual filesystem service…
Jun 19 10:24:52 vision dbus-daemon[1995]: [session uid=1000 pid=1995] Successfully activated service ‘org.gtk.vfs.Daemon’
Jun 19 10:24:52 vision systemd[1979]: Started Virtual filesystem service. Jun 19 10:24:52 vision kded6[2155]: kf.bluezqt: PendingCall Error: “Unit dbus-org.bluez.obex.service not found.” Jun 19 10:24:53 vision plasmashell[2245]: /usr/bin/plasmashell: symbol lookup error: /usr/bin/plasmashell: undefined symbol: _ZN11PlasmaQuick15AppletQuickItem8t> Jun 19 10:24:53 vision systemd[1979]: plasma-plasmashell.service: Main process exited, code=exited, status=127/n/a Jun 19 10:24:53 vision systemd[1979]: plasma-plasmashell.service: Failed with result ‘exit-code’. Jun 19 10:24:53 vision systemd[1979]: Failed to start KDE Plasma Workspace.
Please, let me know, if there is any other information I can provide.
I found out I was mixing packages from different KDE repositories. Unfortunately I could not find any official recommendation, which standard KDE repositories (frameworks, applictions, extra but no testing/Beta stuff) to use on Tumbleweed.
Also, how would I proceed after replacing any of my current KDE repositories making sure my KDE stuff won’t get messed up again and won’t block each other from being started?
Thanks a lot for your instructions. Got two more questions: Do these repos include the KDE stuff I need? What about all these Tumbleweed-KDE repos mentioned on various OpenSuse/Tumbleweed pages?
As I do not know what your needs are all I can say is: Those are the only repos I use and my system works to my satisfaction.
Without any real example it is hard to tell what those repositories are good for. As a rule of thumb:
Any repository (except Oss, Non-Oss, update) is either a Factory repositories or a home-repository.
A Factory repository is where all the developement takes place. The content of such a repository is subject to constant change without notice. The current status of its software (working/failing) is unknown and not tested by openQA.
A home-repository is completely up to its owner. Only they really know the content and status (and the software is not tested via openQA).
If you want to use Factory or home repositories you should be able to handle the consequences.