I'm using a laptop with an external monitor. Previously when using KDE4 on Fedora 19 this worked fine, however, I've found a number of regressions with the latest KDE on Fedora 23. Here's a list: 1) External monitor presence is no longer updated on suspend/resume For example, if the laptop is suspended, then I plug in an external monitor and open the laptop, KDE will only use the laptop panel and ignore the external monitor. As a workaround pressing Ctrl+Alt+F2 then Ctrl+Alt+F1 to briefly switch between VTs will cause the external monitor to be detected and the desktop extended. The reverse is also broken, with the same workaround needed. In this case, if the laptop is suspended while an external monitor is attached. if resuming without an external monitor, half the desktop is still on the external display and unusable. Again, Ctrl+Alt+F2/F1 gets things back a bit, however the taskbar/panel seems to disappear for good leaving the desktop environment unusable. The little menu thing in the top left (with options for "Show dashboard", "Activities"... is still present, so there is at least a way to reboot). 2) The task bar/panel frequently decides to appear on the external monitor. There seems to be no way to get it on the screen I want. I ignores the "Primary Output" setting. Sometimes through combinations of rebooting, disconnecting and connecting the external monitor I can end up with the task bar/panel on the screen I want, but I haven't found a reproducible sequence to make that happen. 3) Though the task bar/panel is on the external monitor, space is reserved on the laptop screen. Maximising a window on the laptop screen therefore leaves space at the bottow where the task bar is desired. Conversely maximising a window on the external monitor goes under the task bar and can make some dialogs and applications hard to use at full screen. Reproducible: Always
Same problems here, version 5.4.95; I can confirm basically all the reports above. Moreover, looking at .xsession-errors, some weird messages are present, like this one: kscreen: Primary output changed from KScreen::Output(Id: 70 , Name: "DP3" ) ( "DP3" ) to KScreen::Output(Id: 70 , Name: "DP3" ) ( "DP3" ) or even kscreen: Failed to retrieve current config: "Backend invalidated"
I've run into this as well. Usually restarting plasmashell solves the problem, but it makes you wonder what's going on: kquitapp plasmashell kstart plasmashell
3 Bugs in one. Here on Plasma 5.5.2 on openSUSE Leap on a Lenovo Thinkpad T400 I can confirm the 2nd bug - and I think this is also reported here: https://bugs.kde.org/show_bug.cgi?id=354386
The 2nd issue is also reported here https://bugs.kde.org/show_bug.cgi?id=356725
I can confirm all of the mentioned behavior including this one: https://bugs.kde.org/show_bug.cgi?id=353975. And additionally I've seen that the Application Launcher had different setup than mine (The favorites). I guess it was launching again in the test and was using another configuration (I don't know how, since I'm the only user. Maybe root.) My setup is Arch + Plasma 5.5.2. P.S: After reading Martin's blog, I guess these issues could persist even the plasma switches to 5.6.
Unfortunately dealing with drivers didn't help. I've installed some missing display drivers and the behavior is still there. And this time I got the app launcher in the wrong place (vertical offset). Switching to VT's didn't help at all. I had to press to the display switch button of the laptop to enable or disable plugged screens. I guess, for my particular case, Plasma 5.5.2 is not stable enough. I'll wait and see what happens, because KDE Plasma is my best DE by far.
Same problems here. And another one - sometimes, after laptop was shut down with dual-monitor config, it disables build in display after loging in when powered on again with no external screen attached. I have to delete kscreen config files to make it work again. System version - Arch linux. kscreen 5.5.3 plasma-desktop 5.5.3
"Erratic" is putting it nicely. How about "fundementally broken."
Also, it's frustrating not to be able to vote for this.
I wonder if KDE devs ever give talks at conferences with their Laptop.... then they would know how frustrating this bug is. Severity should be changed to "grave".
Please don't go that harsh on devs. There is a regression, no denial of that. But the main responsible might not be the KDE devs. Take a look at Martin's blog post: https://blog.martin-graesslin.com/blog/2015/10/some-thoughts-on-the-quality-of-plasma-5/ This could be a regression due to Qt 4 to 5 switch. Let's see what will happen on Feb (Qt 5.6 will be released).
I have discovered recently that under some scenarios where I am unable to project or connect to an external monitor because the monitor does not physically show up in Display Settings, that running xrandr (f23) someone allows the Display Settings to pick up the change in the physical external display. So together, restarting plasmashell and/or running xrandr, I have a complete workaround to all the different variations of issues that I run into around multi-monitor/projector support.
Interesting ; I've found that calling "kscreen-console bug" often makes it pick up the extra display and turn it on. My scenario is the laptop is suspended, I wake it up, plugin it into the dock and connect the second monitor to the laptop's display port (not the docks). By calling kscreen-console, then restarting plasmashell it seems work around it,
I am also affected by this bug. Moreover "kscreen-console monitor" segfaults when i disconnect laptop from dock. OS: Chakra kscreen/libkscreen version: 5.5.4 plasma-framework: 5.18.0
For anyone finding this bug, the following comments from KDE developer 'sebas' may be of interest: https://lwn.net/Articles/668712/ It sounds like we have to wait for Wayland for a fix. I personally now use LXDE. While not entirely automatic, I can configure the screens and the panel exactly as I want in about 30 seconds when changing configs. I don't miss much of the extra fluff and eye-candy KDE brought and still use some of the KDE applications (mainly Kate).
I don't understand one thing. How is the status of the bug stays as "UNCONFIRMED", which can be reproduced so easily? I think, at least an acknowledgement would be a relief...
I also have issues with multi-monitor support, however this is on a desktop system, where both screens are always connected. The setup is (as taken from xrandr output) DFP1 connected primary 1920x1200+1024+0 DFP2 connected 1024x1280+0+0 (rotated to the) right The panel *should* appear on DFP1, but even if i change the config, it lasts at most for one start of plasma and appears on DFP2 the next time. when plasmashell is started, randomly one of 3 things happen: 1. (sometimes on login, mostly on manual restart) Everything except the panel beeing on the wrong screen is fine 2. (sometimes on login, maybe 30% of the time on manual restart) Background is visible, but no panel or other widgets 3. (most likely on login) Plasma is pretty messed up, meaning: the Plasma root window on DFP2 has the dimensions, as if the screen was not rotated, leaving black space at the bottom and overflowing to DFP1. if i click the root of DFP1, its root goes to front, hiding that part of DFP2's plasma. https://bugs.kde.org/show_bug.cgi?id=337590 is probably related to this. When i maximize windows, instead of the screens height, their height is set to 1074 pixels (on both screens). Width is ok.
Created attachment 97232 [details] logfiles for the three cases
Technically this bug is older but 356727 has already seen replies by Plasma developers. *** This bug has been marked as a duplicate of bug 356727 ***
*** This bug has been marked as a duplicate of bug 356225 ***