Comment # 3 on bug 1020226 from David Kerkhof

Reading bug 1020227 I see it's the same bug, don't know what to do, continue
here or there?

Anyway, my wife started an update and when I got home saw the same dbus thing
:(

Since her desktop has a wired connection it apparently had still an internet
connection so I run zypper dup --no-allow-vendor-change in a konsole and it
updated all kinds of stuff.

Because my laptop was pretty messed up I restored a partition image and did the
update in a konsole without a problem, so it may have to do with the update app
in Plasma.

Reboot was fine except logging in gave lot's of difficulties. I logged in via
ssh and saw in .xsession-errors-:0 errors with bluez, and since it doesn't have
bluetooth I uninstalled bluez and after a reboot could log in.

Next day same problem again, so did zypper verify which told me to remove
dbus-1, which I did, and then it worked more or less fine.

More or less, because since the 170117 update both pc's, mine and the desktop,
have stability issues. Like now, my task bar is frozen here while I type, and 5
minutes ago had to restart the desktop via ssh because it had the same issue.
Both with Plasma workspace.

My laptop has Intel graphics and the desktop is older and has Radeon 2400
Graphics.