I have a desktop machine (Intel Ivybridge DQ77KB ) and running Arch linux. After update to kernel 4.7.0-1 with the usual pacman -Syu my desktop initially boots up fine and presents the sddm greeter screen as normal - but when logging in the usual splash screen appears on the monitor with the progress bar moving across, but at around 90% through this process, the plasma login seems hangs for many seconds - eventually the splash screen disappears and I end up with just the desktop background image - but no taskbar, and the mouse becomes active again after being unavailable whilst the progress bar and splash are on the screen. Once the mouse is active again and I can select the usual options with right click including the logout option. Rebooting makes no difference, and logging out and back in also makes no difference. After updating and booting the 4.7 kernel and entering the login details to the sddm greeter, there is a period of hang time with the splash image on the screen which eventually times out and gives just a desktop background image - at that point I used right click to unlock the widgets on the desktop, and added 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, and again just a desktop background image is 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, which works successfully again, then the login does show the new panel that I added when I had booted kernel 4.7 - which I can then remove and the original panel is there and working as normal! I don't know therefore if this might point to a bug in plasma workspace or kwin that has surfaced with the current version of the kernel 4.7, and which might be fixed in newer versions of plasma Reproducible: Always Steps to Reproduce: 1. Update machine to kernel 4.7 (including 4.7.2-1) 2. Reboot and login at the sddm prompt 3. Presented with desktop background image only, and no panel Actual Results: No panel after plasma login Expected Results: Expect plasma desktop with panel Also reported initially at https://bugs.freedesktop.org/show_bug.cgi?id=97354 but this looks like a possible plasmashell bug rather than a graphics or kernel driver bug. The versions of other key packages are: xorg-server 1.18.4-1 (xorg) xf86-video-intel 1:2.99.917+691+ga77397a-1 (xorg-drivers xorg) $ lspci -v | egrep VGA 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]) The problem remains with plasma-framework (5.24.0-1 -> 5.25.0-1) The problem remains with the update for xf86-video-intel (1:2.99.917+691+ga77397a-1 -> 1:2.99.917+697+g12c14de-1)
Created attachment 100762 [details] Xorg log with kernel 4.7
Created attachment 100763 [details] Journal log with kernel 4.7
Created attachment 100764 [details] .xsession-error with kernel 4.7
Thanks, it won't be the kernel version. It /should/ be fixed now? There were some updates on this area; we hit a major bug with kactivites that was fixed in Plasma 5.7.1? Please report if you still have any problems in the linked report *** This bug has been marked as a duplicate of bug 367828 ***
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.
Perhaps I should rephrase the comment - the login does complete but there is no panel.
Is there any diagnostics I can run to provide further information to enable this to be fixed?
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. Please therefore close this bug even though it is marked as a duplicate.