Hi folks,
I am running openSUSE Leap 15.1 (Linux localhost 4.12.14-lp151.28.32-default #1 SMP Wed Nov 13 07:50:15 UTC 2019 (6e1aaad) x86_64 x86_64 x86_64 GNU/Linux).
When I log in, PLASMA only shows a black desktop, no task bar or anything. I can run applications using Alt+F2, but the whole plasma environment is missing.
Any ideas?
Thanks
Is this a fresh installation which you have not yet updated? Are you able to launch an IceWM session instead successfully?
Do you see a mouse pointer? What color & shape? Can you move the pointer?
Does right-clicking anywhere on the black screen show the Desktop context menu? (»Open with Dolphin«, »Configure Desktop« etc)
Maybe it has to do with a missing desktop image, or with those newfangled »Activities…« I’ve never used, or with a KDE widget/plasmoid like Weather waiting for a network connection?
Maybe the compositing doen’t work correctly with your video driver? (systemsettings5 → Display and Monitor → Compositor; try disabling it.)
Yes, actually, I encountered the problem and decided to try a fresh installation. So I did a system upgrade (conserving my home directory), updated all packages - and ended up with the same situation.
And yes, IceWM works. It seems to be KDE/Plasma problem.
Yes, I see a normal mouse pointer (white standard pointer). I can also move it normally and the background is completely black. As soon as I return home, I will check the Compositor setting. One interesting thing to note is that it suddenly happened without changing any settings.
and thereby conserving all your old (potentially faulty) Plasma-settings.
Does the problem occur with a newly created user as well?
Regards
susejunky
Meanwhile, I checked this: the context menu is not shown.
I also disabled Compositor now. Now it shows the standard background, but still no taskbar and no functionality…
Yes, I was aware of the risk to conserve faulty settings - but I wanted to keep all my data safe…
Anyway, I now created a new user - and see exactly the same behavior…
Any ideas? Thank you very much for any hints…
That’s fine but it is necessary to figure out whether the problem is caused by some settings of the individual user or is a more fundamental one.
So to me this looks like a more fundamental problem.
Could you please use
# zypper lr -uEP
to produce a list of your current repositories and show the result here.
What does
# journalctl -b 0 -p 4
report?
Regards
susejunky
Thanks for you help. Here are the outputs:
chris@localhost:~$ zypper lr -uEP
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | URI
---+---------------------+-----------------------------+---------+-----------+---------+----------+------------------------------------------------------------------
6 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/distribution/leap/15.1/repo/non-oss/
7 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/distribution/leap/15.1/repo/oss/
10 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/update/leap/15.1/oss/
11 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/update/leap/15.1/non-oss/
chris@localhost:~$ journalctl -b 0 -p 4
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q toturn off this notice.
-- Logs begin at Fri 2018-01-12 08:39:29 CET, end at Sat 2019-11-30 16:01:47 CET. --
Nov 30 15:59:17 localhost klauncher[1986]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Nov 30 15:59:17 localhost kdeinit5[1989]: org.kde.wacomtablet.common: d->name.isEmpty? true
Nov 30 15:59:17 localhost kdeinit5[1989]: org.kde.wacomtablet.common: d->name.isEmpty? true
Nov 30 15:59:17 localhost ksmserver[2055]: Qt: Session management error: networkIdsList argument is NULL
Nov 30 15:59:17 localhost kdeinit5[1989]: QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.10'
Nov 30 15:59:17 localhost polkit-kde-authentication-agent-1[2161]: kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing.
Nov 30 15:59:17 localhost kdeinit5[1989]: kscreen.kded: PowerDevil SuspendSession action not available!
Nov 30 15:59:18 localhost org_kde_powerdevil[2263]: QDBusArgument: read from a write-only object
Nov 30 15:59:18 localhost org_kde_powerdevil[2263]: QDBusArgument: read from a write-only object
Nov 30 15:59:18 localhost org_kde_powerdevil[2263]: QDBusArgument: read from a write-only object
Nov 30 15:59:18 localhost plasmashell[2159]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Nov 30 15:59:18 localhost plasmashell[2159]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activata>
Nov 30 15:59:18 localhost pulseaudio[2254]: [pulseaudio] module.c: module-combine is deprecated: Please use module-combine-sink instead of module-combine!
Nov 30 15:59:18 localhost pulseaudio[2254]: [pulseaudio] module-combine.c: We will now load module-combine-sink. Please make sure to remove module-combine from your configuration.
Nov 30 15:59:18 localhost pulseaudio[2254]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.>
Nov 30 15:59:18 localhost org_kde_powerdevil[2263]: powerdevil: No outputs have backlight property
Nov 30 15:59:18 localhost org_kde_powerdevil[2263]: powerdevil: Xrandr not supported, trying ddc, helper
Nov 30 15:59:18 localhost /hp-systray[2275]: hp-systray[2275]: error: option -s not recognized
Nov 30 15:59:18 localhost org_kde_powerdevil[2263]: powerdevil: Handle button events action could not check for screen configuration
Nov 30 15:59:18 localhost plasmashell[2159]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontai>
Nov 30 15:59:18 localhost plasmashell[2159]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontai>
Nov 30 15:59:19 localhost plasmashell[2159]: trying to show an empty dialog
Nov 30 15:59:19 localhost plasmashell[2159]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML Text: Binding loop detected for pr>
Nov 30 15:59:19 localhost plasmashell[2159]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML Text: Binding loop detected for pr>
Nov 30 15:59:19 localhost plasmashell[2159]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML Text: Binding loop detected for pr>
Nov 30 15:59:19 localhost plasmashell[2159]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML Text: Binding loop detected for pr>
Nov 30 15:59:19 localhost plasmashell[2159]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML Text: Binding loop detected for pr>
Nov 30 15:59:19 localhost plasmashell[2159]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML Text: Binding loop detected for pr>
Nov 30 15:59:19 localhost plasmashell[2159]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML Text: Binding loop detected for pr>
Nov 30 15:59:20 localhost plasmashell[2159]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML Text: Binding loop detected for pr>
Nov 30 15:59:20 localhost plasmashell[2159]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML Text: Binding loop detected for pr>
Nov 30 15:59:20 localhost plasmashell[2159]: file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:302:17: QML Text: Binding loop detected for pr>
Nov 30 15:59:20 localhost plasmashell[2159]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Nov 30 15:59:20 localhost plasmashell[2159]: Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
Nov 30 15:59:20 localhost plasmashell[2159]: Both point size and pixel size set. Using pixel size.
Nov 30 15:59:20 localhost plasmashell[2159]: Both point size and pixel size set. Using pixel size.
Nov 30 15:59:20 localhost plasmashell[2159]: Both point size and pixel size set. Using pixel size.
Nov 30 15:59:20 localhost kwin_x11[2126]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 943, resource id: 14680068, major code: 18 (ChangeProperty), minor code: 0
Nov 30 15:59:20 localhost plasmashell[2159]: trying to show an empty dialog
Nov 30 15:59:20 localhost kdeinit5[1989]: kf5.kded: found kded module "touchpad" by prepending 'kded_' to the library path, please fix your metadata.
Nov 30 15:59:20 localhost plasmashell[2159]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.panel/content>
Nov 30 15:59:20 localhost plasmashell[2159]: trying to show an empty dialog
Nov 30 15:59:20 localhost kdeinit5[1989]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Nov 30 15:59:20 localhost kdeinit5[1989]: org.kde.bluez: GetManagerJob Error: "Cannot find org.bluez.Media1 object!"
Nov 30 15:59:20 localhost /hp-systray[2338]: hp-systray(qt5)[2338]: warning: value_int() Failed to convert data[1427397675.51712]:invalid literal for int() with base 10: '1427397675.51712'
Nov 30 15:59:20 localhost plasmashell[2159]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifi>
Nov 30 15:59:21 localhost /hp-upgrade[2356]: hp-upgrade[2356]: error: HPLIP upgrade is disabled by openSUSE for security reasons, see https://bugzilla.novell.com/show_bug.cgi?id=853405 - i>
Nov 30 15:59:21 localhost kwin_x11[2126]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1016, resource id: 6291487, major code: 18 (ChangeProperty), minor code: 0
Nov 30 15:59:22 localhost plasmashell[2367]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Nov 30 15:59:22 localhost plasmashell[2367]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activata>
Nov 30 15:59:22 localhost plasmashell[2367]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontai>
Nov 30 15:59:22 localhost plasmashell[2367]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontai>
Nov 30 15:59:22 localhost plasmashell[2367]: trying to show an empty dialog
Looks OK to me.
Sorry, my fault. I should have told you that you need to run this command as root (using sudo or root-shell) or you have to add your user to the group ‘systemd-journal’. Otherwise you will not see any system level errors.
So please could you run (as “root”)
# journalctl -b 0 -p 3
This will concentrate on the errors (no warnings shown).
What displaymanager (sddm, lightdm, …) are you using and have you tried to use a different one?
Regards
susejunky
I don’t know whether this is related, but I find clicking on a menu item with a drop-down list sometimes gives a box which is the same shape as the drop-down list but completely black. Moving the cursor slightly then reveals the list content.
Back in August 2018 I also mentioned another problem - https://forums.opensuse.org/showthread.php/532606-Firefox-window-rendering-problem/page2 - involving graphics being rendered black:
Firefox on my system has acquired an intermittent window-rendering problem since some recent update (now 60.1.0) whereby the buttons on the titlebar (but not the Firefox logo) are displayed as black squares. The buttons on the right should be displayed as white underline, square, and cross graphics using the “MS Windows 9x” widget style and “Plastik” theme.
Both issues occur with Leap 15.1, but not frequently. The second also occurred under Leap 42.3 and there was a lot of discussion in the thread quoted above about possibly causes, but I’m well out of my depth when it comes to drivers and graphics implementation.
David L.
Oh yes, this shows serious errors:
localhost:/home/chris # journalctl -b 0 -p 3
-- Logs begin at Thu 2018-01-11 19:49:41 CET, end at Sun 2019-12-01 06:37:57 CET. --
Dec 01 06:35:18 localhost kernel: Bluetooth: hci0: Failed to send firmware data (-38)
Dec 01 06:35:30 localhost dhclient[2020]: Timeout too large reducing to: 2147483646 (TIME_MAX - 1)
Dec 01 06:35:31 localhost kernel: mei_wdt mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02: Could not reg notif event ret=-22
Dec 01 06:35:39 localhost pulseaudio[2407]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.>
Dec 01 06:35:44 localhost /hp-systray[2417]: hp-systray[2417]: error: option -s not recognized
Dec 01 06:35:46 localhost /hp-upgrade[2466]: hp-upgrade[2466]: error: HPLIP upgrade is disabled by openSUSE for security reasons, see https://bugzilla.novell.com/show_bug.cgi?id=853405 - i>
Dec 01 06:36:20 localhost systemd-coredump[2507]: Process 2484 (plasmashell) of user 1000 dumped core.
Stack trace of thread 2484:
#0 0x00007f05d56aa160 n/a (n/a)
Dec 01 06:36:21 localhost systemd-coredump[2518]: Process 2504 (plasmashell) of user 1000 dumped core.
Stack trace of thread 2504:
#0 0x00007fc563db5620 _ZN8JobModel9updateJobEiRK8KCupsJob (/usr/lib64/libkcupslib.so)
Dec 01 06:37:16 localhost systemd-coredump[2817]: Process 2363 (plasmashell) of user 1000 dumped core.
Stack trace of thread 2363:
#0 0x00007ff53d53e160 n/a (n/a)
What displaymanager (sddm, lightdm, …) are you using and have you tried to use a different one?
Regards
susejunky
I must admit, I do not even know which one I am using and how to change that…
update-alternatives --config default-displaymanager both shows current, and allows switching. Also yast > miscellaneous > alternatives.
This could be the reason why your desktop does not behave as expected.
However i guess user 1000 is the user which uses “old settings”. Just to make sure that we do not see problems caused just by those “old” settings please do the following:
# journalctl -b 0 -p 4 -t plasmashell -t sddm -t systemd-coredump
and show us the result.
Some information about your graphics hardware might be helpful so please show us the result of
# hwinfo --gfxcard
as well.
Regards
susejunky
Here we go:
-- Logs begin at Thu 2018-01-11 19:49:41 CET, end at Mon 2019-12-02 07:09:55 CET. --
Dec 02 07:08:50 localhost plasmashell[1943]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Dec 02 07:08:50 localhost plasmashell[1943]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
Dec 02 07:08:51 localhost plasmashell[1943]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/LayoutManager.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js")
Dec 02 07:08:51 localhost plasmashell[1943]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/FolderTools.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js")
Dec 02 07:08:51 localhost plasmashell[1943]: trying to show an empty dialog
Dec 02 07:08:51 localhost plasmashell[1943]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Dec 02 07:08:51 localhost plasmashell[1943]: Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
Dec 02 07:08:51 localhost plasmashell[1943]: Both point size and pixel size set. Using pixel size.
Dec 02 07:08:51 localhost plasmashell[1943]: Both point size and pixel size set. Using pixel size.
Dec 02 07:08:51 localhost plasmashell[1943]: Both point size and pixel size set. Using pixel size.
Dec 02 07:08:51 localhost plasmashell[1943]: trying to show an empty dialog
Dec 02 07:08:51 localhost plasmashell[1943]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.panel/contents/code/LayoutManager.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/LayoutManager.js")
Dec 02 07:08:51 localhost plasmashell[1943]: trying to show an empty dialog
Dec 02 07:08:52 localhost plasmashell[1943]: log_klipper: Failed to load history resource. Clipboard history cannot be read. : History file does not exist
Dec 02 07:08:52 localhost plasmashell[1943]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/code/uiproperties.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/uiproperties.js")
Dec 02 07:08:53 localhost plasmashell[2120]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Dec 02 07:08:53 localhost plasmashell[2120]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
Dec 02 07:08:53 localhost plasmashell[2120]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/LayoutManager.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js")
Dec 02 07:08:53 localhost plasmashell[2120]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/FolderTools.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js")
Dec 02 07:08:54 localhost plasmashell[2120]: trying to show an empty dialog
Dec 02 07:08:54 localhost plasmashell[2120]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Dec 02 07:08:54 localhost plasmashell[2120]: Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
Dec 02 07:08:54 localhost plasmashell[2120]: Both point size and pixel size set. Using pixel size.
Dec 02 07:08:54 localhost plasmashell[2120]: Both point size and pixel size set. Using pixel size.
Dec 02 07:08:54 localhost plasmashell[2120]: Both point size and pixel size set. Using pixel size.
Dec 02 07:08:54 localhost plasmashell[2120]: trying to show an empty dialog
Dec 02 07:08:54 localhost plasmashell[2120]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.panel/contents/code/LayoutManager.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/LayoutManager.js")
Dec 02 07:08:54 localhost plasmashell[2120]: trying to show an empty dialog
Dec 02 07:08:54 localhost plasmashell[2120]: log_klipper: Failed to load history resource. Clipboard history cannot be read. : History file does not exist
Dec 02 07:08:54 localhost plasmashell[2120]: Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/code/uiproperties.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/uiproperties.js")
Dec 02 07:08:57 localhost systemd-coredump[2136]: Process 2120 (plasmashell) of user 1002 dumped core.
Stack trace of thread 2120:
#0 0x00007fea22419620 _ZN8JobModel9updateJobEiRK8KCupsJob (/usr/lib64/libkcupslib.so)
Dec 02 07:09:55 localhost systemd-coredump[2234]: Process 1943 (plasmashell) of user 1002 dumped core.
Stack trace of thread 1943:
#0 0x00007f18b2a45160 n/a (n/a)
Some information about your graphics hardware might be helpful so please show us the result of
# hwinfo --gfxcardas well.
That would be this one:
12: PCI 02.0: 0300 VGA compatible controller (VGA)
[Created at pci.386]
Unique ID: _Znp.9TemtVPWpL9
SysFS ID: /devices/pci0000:00/0000:00:02.0
SysFS BusID: 0000:00:02.0
Hardware Class: graphics card
Model: "Intel Skylake GT2 [HD Graphics 520]"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x1916 "Skylake GT2 [HD Graphics 520]"
SubVendor: pci 0x17aa "Lenovo"
SubDevice: pci 0x2233
Revision: 0x07
Driver: "i915"
Driver Modules: "i915"
Memory Range: 0xf0000000-0xf0ffffff (rw,non-prefetchable)
Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable)
I/O Ports: 0xe000-0xe03f (rw)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 125 (4645 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v00008086d00001916sv000017AAsd00002233bc03sc00i00"
Driver Info #0:
Driver Status: i915 is active
Driver Activation Cmd: "modprobe i915"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Primary display adapter: #12
Thanks!
I ran some searches for this
and found
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044
You should read it (your English might be better than mine). As far as i understand uninstalling the package kde-print-manager could solve your problem. If it works you can even try to re-install kde-print-manager again. However i can not reproduce your problem on any of my machines so i don’t know whether that will really solve your problem. On the other hand there should not be any harm in trying it.
If this really solves your problem then you should consider to file a bug report (https://bugzilla.opensuse.org/index.cgi).
Another thing worth doing is to make sure that all your installed software is up-to-date.
# zypper dup
(as root in a console) should do the trick. But beware that only the repositories you mentioned in your post #10 should be enabled for this.
Regards
susejunky
Great, thank you very much! Removing kde-print-manager indeed solved the problem. Well done!
Good to hear (but after all it was not me who did the job;) but the search engine and those ubuntu users).
Just out of curiosity:
Does the problem reappear when you install kde-print-manager again?
Regards
susejunky
I just reinstalled kde-print-manager, rebooted - and plasma crashed again with the same behavior. I then removed it again, rebooted - and everything is fine again.
So, it is reproducible.