Hi, When I git pull plasma-workspace, rebuilt it, then logout/login, there is NO panel available! And I tried to add a NEW empty panel or default panel: QQuickItem::stackBefore: Cannot stack before 0x553f9a0, which must be a sibling file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:100: TypeError: Cannot read property of null file:///usr/lib/qt/qml/QtQuick/Controls/Button.qml:100: TypeError: Cannot read property of null file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:80: TypeError: Cannot read property 'formFactor' of null file:///usr/lib/qt/qml/QtQuick/Controls/Slider.qml:220: TypeError: Cannot read property 'handleHeight' of null file:///usr/lib/qt/qml/QtQuick/Controls/Slider.qml:219: TypeError: Cannot read property 'handleWidth' of null file:///usr/lib/qt/qml/QtQuick/Controls/Slider.qml:220: TypeError: Cannot read property 'handleHeight' of null file:///usr/lib/qt/qml/QtQuick/Controls/Slider.qml:219: TypeError: Cannot read property 'handleWidth' of null file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Base/SliderStyle.qml:216: TypeError: Cannot read property 'height' of null file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Base/SliderStyle.qml:216: TypeError: Cannot read property 'height' of null file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Base/SliderStyle.qml:228: TypeError: Cannot read property 'width' of null Both point size and pixel size set. Using pixel size. ktp-common-internals: Current presence changed ktp-common-internals: Current presence changed Qt5.7.0 kf5 5.25.0 Reproducible: Always
There was recently problem with plasma-framework.. can you try to update plasma-framework and retry please?
*** Bug 367822 has been marked as a duplicate of this bug. ***
Which is the version number for plasma-framework which contains the fix please?
Hi Bhushan, Thanks for your reply! I also git pull kdeclarative and rebuilt it, because building plasma-framework master (shown as git log) thrown setTranslationDoamin not defined issue! commit cb6c63f9613a27dca47a285fb05614113d81b3c2 Author: andreas kainz <kainz.a@gmail.com> Date: Sat Aug 27 22:21:10 2016 +0200 fix stylesheet stuff in computer icon And now pasetTranslationDoaminnel is back ;-) Hi MikeC, I will simply backport plasma-framework v5.25.0 via diff -Naur plasma-framework-5.25.0 plasma-framework-master > tmp.patch and of course kdeclarative-master with setTranslationDoamin support, I will re-package KDE components http://koji.isoft-linux.org/koji/ Regards, Leslie Zhai
After the update to plasma frameworks 5.26.0-1 I am still unable to login with any kernel beyond 4.6.4-1 so this issue is not fixed for me. My plasma package set is 5.7.5-1. This is on my Ivybridge machine though I have two Haswell machines which are fine and don't exhibit this problem.
Is there any diagnostics I can run to provide further information to enable this to be fixed?
Created attachment 101134 [details] Journal log for the 4.7.4-1 kernel when the plasma login had no panel Are the lines in the log relevant with: Sep 17 09:53:21 home1 kernel: kactivitymanage[641]: segfault at 7f8e7697acf0 ip 00007f8e76992ce1 sp 00007fff0eb40ff8 error 4 in libQt5Sql.so.5.7.0[7f8e7697c000+46000] Sep 17 09:53:21 home1 kactivitymanagerd[641]: The X11 connection broke (error 1). Did the X11 server die? Sep 17 09:53:21 home1 kglobalaccel5[651]: The X11 connection broke (error 1). Did the X11 server die? Sep 17 09:53:21 home1 kscreen_backend_launcher[686]: The X11 connection broke (error 1). Did the X11 server die? Sep 17 09:53:21 home1 kdeinit5[599]: The X11 connection broke: I/O error (code 1) Is this an indication that kactivitymanager has a bug here?
In my system which still has no panel after logging in to plasma with kernel 4.7.4-1 in arch linux, the hardware for graphics is: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device 2036 Flags: bus master, fast devsel, latency 0, IRQ 32 Memory at f7800000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 I will attach the journal and Xorg logs immediately after booting to kernel 4.7.4-1, and with all packages up to date. Presumably some change to the Intel graphics driver in the kernel once 4.7 was released is not compatible with plasma frameworks up to and including version 5.26.0-1. This is also with the latest available plasma-desktop version 5.7.5-1 The system boots normally to the sddm greeter screen, but when I log in to the plasma desktop the progress bar stops at about 85% for 30 seconds, and then fades away with a second progress bar and splash visible for a short time before then fading away, and leaving only a desktop background bu no panel. Right clicking on the desktop does allow starting a konsole window at that point from which the log files can be stored, and other programs can be started normally, as well as choosing to logout or restart using right click.
Created attachment 101142 [details] Journal log booting kernel 4.7.4-1 when no panel appears after plasma login
Created attachment 101143 [details] xorg log when booting kernel 4.7.4-1 when no panel appears after plasma login
When I checked the .xsession-errors file it was dated September 2nd, and has not been recreated when the kernel 4.7.4-1 was booted. So that file is still for the previous kernel and not for the 4.7 kernels. Hence I have not added that file as an attachment. If there is any further diagnostics that I can run to help with triaging this please let me know.
In addition I don't know if the following is useful in helping to triage this issue but after booting the 4.7 kernel and entering the login details at the sddm greeter, there is the usual 30 seconds or so hang time with the splash on the screen eventually timing out and giving just a desktop background image - at that point I can use right click to unlock the widgets on the desktop, and add a new default panel which displays and works correctly. If at that point I logout and then log back in, then the splash screen hangs for the same extended period, and when it disappears the panel that I added after the previous login is no longer displayed but is again just a desktop background image with no panel on the screen. However, if I then log out using right click and selecting to leave plasma, and downgrade the kernel back to 4.6, which was previously working, and log back in to plasma, that works successfully again, and the desktop does then show the panel that I added when I had booted kernel 4.7 - which I can then remove and the original panel is also there and working as normal!
Created attachment 101155 [details] Output from $ qdbus org.kde.KWin /KWin supportInformation > kwin-support-info-2016sep17.txt
Created attachment 101157 [details] xrandr output for kernel 4.7.4-1
Created attachment 101158 [details] xrandr output for kernel 4.6.4-1
Any chance that for some reason plasma is trying to put the panel on the eDP1 display when booted to kernel 4.7.4-1 even though I have only a single HDMI monitor connected?
Is there any chance that this issue is connected to bug https://bugs.kde.org/show_bug.cgi?id=356225 even though I have only a single monitor and no additional monitor connected?
I tried to add in some lines to my xorg config to prevent it detecting the non-existent eDP1 monitor by using: Section "Monitor" Identifier "HDMI2" Option "Enable" "true" EndSection Section "Monitor" Identifier "eDP1" Option "ignore" "true" EndSection When booting the 4.7.4 kernel the login progress bar no longer waits for about 30 seconds during login to plasma and the splash screen disappears much more quickly but still no panel is displayed so the overall result is as before but without the 30 seconds delay. Is there any other test I could usefully run to diagnose this further or to find a workaround to test any hypothesised reason for the problem?
Created attachment 101163 [details] xrandr with the added xorg config to ignore the non-existent eDP1 monitor
Created attachment 101164 [details] kwin support info with the added xorg config to ignore the non-existent eDP1
I have finally been able to resolve this problem. It turned out that way back in the history of my machine when I originally set it up, I had used a DVI monitor, and then a few days later plugged in an HDMI monitor and had the two monitors connected for a short period whilst I configured the displays, and HDMI monitor after that has been the only monitor on the machine for the following three years until now. However removing the original DVI monitor that was originally plugged in as a second monitor gave a phantom screen, that was presented to KDE4 and then later to plasma as a unified screen output, and the original panel that was assigned to the old DVI monitor had been displayed within plasma just fine on the primary HDMI monitor until the kernel was upgraded to the 4.7 series. At that point the phantom monitor attached to the eDP1 screen was where the panel was being displayed and therefore no longer visible on the primary HDMI display. So in order to resolve this issue I logged on with kernel 4.6.4-1 running with the erroneously assigned panel still displayed on the primary real monitor. Then unlocking the plasma widgets, and removing the panel using the panel controls, I then created a new default panel, configured it, and locked the widgets again. Logging out and back in displayed the newly created panel correctly on the primary monitor. Then adjusting the xorg config to include the following lines allowed logging out and back in with no phantom screen detected: Section "Monitor" Identifier "HDMI2" Option "Enable" "true" EndSection Section "Monitor" Identifier "eDP1" Option "ignore" "true" EndSection Then upgrading the kernel to 4.7.4-1 and rebooting, allows the login from the sddm screen to proceed normally and completes without any problem including having the panel displayed on the only screen detected by kwin. The xrandr output before and after these changes shows that prior to the steps detailed above there was a phantom eDP1 screen, but afterwards there is only a single HDMI2 screen - and now all is well. I also found that Martin Graeslin has commented on the multi-screen issue in the past at https://blog.martin-graesslin.com/blog/2015/10/some-thoughts-on-the-quality-of-plasma-5/ and there is another post also mentioning this issue at: https://vizzzion.org/blog/2016/05/multiscreen-in-plasma-5-7-and-beyond/ So although the problem is resolved in my case, it looks like there are still possible remnants of problems for systems where more than one monitor has been connected and during multi-screen operation some screen configs have been changed which can become an issue when the additional monitors are later removed. Whether any progress can be made by the original poster of this bug report using a similar approach to that which fixed my issue will need to be answered by Leslie Zhai.
the report in particular was about a known problem occurred from a small behavior change in the framework, only affecting who had master. I'll keep it open for few days still, please keep an eye if this still happen on a release (the recent 5.8 beta) but should be fixed by now. the last comments are instead describing an unrelated problem
I have a similar problem when i start plasmashell. I tried removing all the configuration and cache files but i manage to start plasmashell correctly only once, then the same behaviour resurfaces (the panel doesn't load). Here's the output from running plasmashell from a terminal: ashmi@archimboldo ~> plasmashell file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:80: TypeError: Cannot read property 'formFactor' of null Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 Could not resolve property : radialGradient4857 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:46:29: Unable to assign [undefined] to bool file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:106:20: Unable to assign [undefined] to int file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:41: TypeError: Cannot read property 'length' of undefined file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/main.qml:28: TypeError: Cannot read property 'Layout' of null file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/main.qml:29: TypeError: Cannot read property 'Layout' of null file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/Tooltip.qml:43: TypeError: Cannot read property 'timeFormat' of null Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Containment id 6 that used to be a system tray was deleted Notifications service registered XSync seems available and ready XSync Inited Supported, init completed Even starting with an empty user, i managed to get plasmashell running just once, then the same thing happened. I have an intel (3rd generation) GPU on a laptop. I tried downgrading plasma, the intel xf86 driver, the kernel, kde frameworks libraries, nothing worked. Maybe the configuration or the caches are part of the issue? It seemed similar enough to this problem but i can open a new bug if it's unrelated. Lastly, here are the plasma/kframeworks versions i'm using: kde frameworks 5.26.0 plasma 5.7.5
> but should be fixed by now YES! fixed for me ;-) https://pbs.twimg.com/media/CsySCJaXgAAkHaH.jpg
this is a multiscreen-related issue (even if there is only one screen, is related to what screen is assigned to what containment) the management of screens is changed completely in 5.8, please reopen if this happens again on Plasma 5.8 or newer.