Hi, If more than one activity is created, the screen remains black after the KDE splash screen (KDE logo). Deletes in the $HOME of the user the directories .config, .kde and .local is a login possible again but of course you have an initial desktop. As soon as you create an additional activity, the error reappears. The error occurs reproducibly whether the installation runs in a virtual machine or on real hardware. Reproducible: Always Steps to Reproduce: Create a second activity Actual Results: Can not login to the KDE desktop My system (Siduction) has current packages from Debian Unstable. Kernel version: 4.8.2-towo.1-siduction-amd64 I would like to provide additional information about my installation as long as it is needed. What can be done against this error?
More Information: The error only occurs if the Miniprogramms activity monitoring is placed in the window bar or on the desktop background with more than one created activity. In this action, the screen becomes black and you can not get out of this state. In addition, it seems despite a "black screen" that the KDE desktop running in the background still, because after a few minutes of the "Black Sreen" the dialog box of the screen lock. If you do not touch the mini-program "Activity monitoring" you do not have problems with several created activities.
> Miniprogramms activity monitoring Can you explain what is Miniprogramms activity?
Hi Ivan, let me explain ;-) Rightclick on the desktop, then in the context menu "Add Miniprogramme" (in German: Miniprogramme hinzufügen), then the Miniprogramme "Activity monitoring" (in German: Aktivitätenüberwachung) to the control bar pull by mouse. At this point, the desktop becomes black. Sorry for my insufficient English. I hope I have now expressed myself clearly. greetings Michael
I'm going to assume that "Miniprogramme" is "Widgets" in the English version. Now, the question is what is "Activity monitoring"? Is that some widget you installed from kde-look, or is it shipped with your distribution? Can you post the output of the following command: grep plugin ~/.config/plasma-org.kde.plasma.desktop-appletsrc | sort -u I'm guessing the problem is in a specific widget that blocks plasma to load, but we will see :) > Sorry for my insufficient English. I hope I have now expressed myself clearly. No need for apologies :)
Hi Ivan, Thank you for your quick response. Now the KDE desktop temporarily changed to English to find the correct identifiers. "Aktivitätenüberwachung" is in english the "Activity Pager" ;-) The "Activity Pager" is installed by default and has nothing to do with my used Linux distribution siduction. Here the output from the command: $ grep plugin ~/.config/plasma-org.kde.plasma.desktop-appletsrc | sort -u plugin=org.kde.desktopcontainment plugin=org.kde.panel plugin=org.kde.plasma.clipboard plugin=org.kde.plasma.devicenotifier plugin=org.kde.plasma.digitalclock plugin=org.kde.plasma.kickoff plugin=org.kde.plasma.notifications plugin=org.kde.plasma.pager plugin=org.kde.plasma.private.systemtray plugin=org.kde.plasma.systemtray plugin=org.kde.plasma.taskmanager plugin=org.kde.plasma.volume wallpaperplugin=org.kde.image I hope now the error report becomes clearer and understandable to you ;-) greetings Michael
I have another question - can you run plasmashell from terminal (first kill it) and then paste the output here?
Here is the output: $ ps -ef|grep plasmashell michael 2294 2272 4 18:21 ? 00:00:05 plasmashell --shut-up $ kill 2294 $ plasmashell --shut-up file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27: Unable to assign [undefined] to QStringList file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37: TypeError: Cannot read property 'DateTime' of undefined file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item. Notifications service registered file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null Plasma Shell startup completed file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null QXcbConnection: XCB error: 2 (BadValue), sequence: 1926, resource id: 83886082, major code: 142 (Unknown), minor code: 3
Without the --shut-up argument - it tries to silence the output, and we want the full output :)
p.s. (the output needs to be of plasma started to show the blank screen)
Here is the output from "plasmashell" ;-) $ plasmashell file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27: Unable to assign [undefined] to QStringList file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37: TypeError: Cannot read property 'DateTime' of undefined file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item. Notifications service registered file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null Plasma Shell startup completed file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
Damn, it still does not write anything useful - I have a few more steps for you :) 1. can you install plasma and plasma-related packages with debugging symbols, and start kdebugdialog5 and check every box that mentions plasma (there is a search bar on top)? 2. What happens if you put the activity pager on the panel and restart plasma? 3. When you start plasma (from terminal) in an activity that is not blank, and then press enter a few times in the terminal, just to move the cursor, what is written out when you try to switch to a 'blank' activity? p.s. Backup your plasma settings before doing this - ~/.config/plasma* :)
Hi Ivan, To 1.) kdebugdialog5 I have installed. Afterwards as user started and the indicated packages "plasma" and "libplasma" activated by checkbox. To 2.) I have pulled the ActivityPager on the bar, nothing has happened. No black screen, to 3.) You mean probably start the plasma shell from a terminal. I did that (before a kill on the plasmashell process) and the screen was briefly black. Then again in the terminal the Plasmashell started, it was everything as before. The ActivityPager was still in the bar and all activities were accessible by mouse. I now have the original error probably no more. It could be the Debian Unstable, however, newer plasma packages have fixed the error.
Ok, I'll close this. If it appears again, just reopen this report. Thanks for testing all this - you are one of the best bug reporters I have had recently!
Seems I forgot to close this.