Summary: | After update to kernel 4.7 no panel after plasma login | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | MikeC <mike.cloaked> |
Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | kde |
Priority: | NOR | ||
Version: | 5.7.3 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Xorg log with kernel 4.7
Journal log with kernel 4.7 .xsession-error with kernel 4.7 |
Description
MikeC
2016-08-25 21:48:36 UTC
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. |