I am using a dual monitor configuration and I keep my laptop monitor deactivated. If I unplug the external monitor, the display of the laptop remains deactivated, so I don't have any display to use! Reproducible: Always Steps to Reproduce: 1. Connect external monitor 2. Configure displays so that laptop monitor is disabled and use only external monitor 3. Unplug the external monitor Actual Results: The laptop display is black. Expected Results: The laptop display becomes active and can be used.
So confirmed bug. So huge for me :S After that bug happened i couldn't do much because i set my power button to display power menu, so i had to wait for laptop battery to go off :S After restart everything is fine. I'm using Arch Linux plasma 5.3.2. qt 5.5.0.
Hi Tom, At least for the next time, you can press CTRL+ALT+F1, login to the terminal and then do sudo reboot or sudo poweroff Not a nice solution, as you may have unsaved work, but better than waiting for the battery to drain :).
I use a laptop running KDE at work, and can confirm this is affecting me too. Laptop is a Dell Latitude E7250, running Kubuntu CI branch. Same occurred using Kubuntu 15.04 release. Any sequence which involves change to monitor arrangement causes the session to be reduced to a black screen with a mouse cursor: * Start docked, and undock = black screen on laptop * Start docked and suspend = Black screen on laptop, and external monitor "goes to sleep" * Start undocked and docked = Sometimes it works, sometimes session dies/restart. When it dies, I can no longer boot into my session until I delete relevant kscreen data in my home folder. * On desktop: Turn off Monitor, and turn back on = monitor no longer detected (sleeps). It will turn on if I switch to a console w/ctrl+alt+F1. Returning to session screen goes back off.
@Vincenzo well i tried that but it didn't work :) anyway, thx for advice
What does it take to make this "confirmed?" so that it has appropriate visibility? This is clearly a bug around kscreen and multimonitor/displayport combinations based on numerous related issues having been logged. If using anything but KDE, the problems cannot be reproduced. It's made KDE a no-go for me on my work laptop, and my skillset doesn't align to this so I haven't really looked into this myself.
I have same problem. When I unplug my laptop from dock, DE is working, but display on laptop is black. Plugging laptop back to the dock show screen corectly on external display. Tested with empty ".local/share/kscreen" and with clean profile - same problem. Changing via xrandr from terminal works fine. kscreen version: 5.3.2 plasma version: 5.4 gpu driver: intel mesa version: 10.6.5 distro: ArchLinux Reproducible: Always Steps to reproduce: 1. Start KF5 with docked laptop. 2. Set as Primary display external LCD on and laptop LCD off. 3. Undock laptop
I have the same issue. It is a complete blocker for me. It becomes even worse because more often than not changing the setting manually completely messes up the system (the desktop becoming fragmented unable to change the settings). Further manual changes often result in crashes in plasma and/or kwin. Last but not least, the dialog has a larger minimal vertical size than my laptop resolution, so its rather difficult to confirm a setting change... My system: lenovo x230 /w dual monitor at docking station, Archlinux
(In reply to kdebugs from comment #7) > I have the same issue. It is a complete blocker for me. > > It becomes even worse because more often than not changing the setting > manually completely messes up the system (the desktop becoming fragmented > unable to change the settings). Further manual changes often result in > crashes in plasma and/or kwin. Last but not least, the dialog has a larger > minimal vertical size than my laptop resolution, so its rather difficult to > confirm a setting change... > > My system: lenovo x230 /w dual monitor at docking station, Archlinux After switching via xradndr command You can restart plasmashell via "kquitapp plasmashell && kstart plasmashell" in terminal. For me it works. Little workaround...
This issue prevents use of KDE in laptops with external monitors. I use 2 external monitors on my desk, one horizontal and another vertical, and have the laptop screen off. I often put the laptop to sleep and wake it up as I move around. kscreen does not detect the changes in screen layout, which means that when I leave the desk, I had to login blindly on the laptop screen, run (alt-f2) xrandr --auto to get a working display and then in konsole run kwin_x11 --replace (crashed kwin) and kill and restart plasmashell. Gong back to the desk, I then have to reconfigure the whole screen layout again. intel driver 2:2.99.917+git20150910.2c08d723-0ubuntu0sarvatt~vivid kde 5.3 from kubuntu backports
Also happening the same here, with a laptop and an external monitor via displayPort. I'm using Fedora 22 with the latest updates, which includes Kscreen 5.3.2
Same problem with my laptop. With kde4 everythings works fine, with kde5 I need to turn on and off external monitor manually trough systemsettings. Before disconnect the second screen, I have to manually re-enable the laptop screen otherwise it remain black. Also, sequence switch with laptop hotkeys (fn+F7 in my case) from laptop screen of and external monitor on, have the same issue kscreen version: 5.4.1 plasma version: 5.4.1 gpu driver: intel mesa version: 10.6.7 distro: ArchLinux
*** Bug 352186 has been marked as a duplicate of this bug. ***
Hello, after some last updates display switching is working. But still it's not perfect. When display is changed, maximized windows takes full screen and part of this windows is under panel. Plasmashell restart and "kwin_x11 --replace" solve this problem. Distro Archlinux KDE Applications 15.08.2 KDE Frameworks 5.14.3 Plasma 5.4.2
Hello, I can confirm the empty screen thing and the "When display is changed, maximized windows takes full screen and part of this windows is under pane" -- on Kubuntu 15.10 / Qt 5.4.2 / Kscreen 5.4.2-0ubuntu1 intel driver, screen connected via DisplayPort (see specs in possibly related https://bugs.kde.org/show_bug.cgi?id=349482) - basically the most recent 15.10 packages as of this date. It makes KDE very difficult to use with external monitors and quite often results in a hard reset of the laptop. This is not good if you are running virtual dev machines for instance (think corrupted databases). The issues are: * upon resume from a suspend, quite often the external screen isn't activated but KDE thinks it is, and all the windows are on the external screen and can't be seen. Sticking a panel on both screens helps, right click on the application and choose "More Actions > Move" and you may be able to rescue the desktop that way if you can get Display Configuration open. * On unplug, sometimes the laptop screen is activated but then all the windows go under the panel even though the panels settings are "Visibility : Always Visible". You have to do the "More Actions > Move" thing to get access to the title bar (I have the panel on top) * Upon resume the non-primary screen is empty but active as described in https://bugs.kde.org/show_bug.cgi?id=349482 * Quite often I've had to delete the contents of ~/.local/share/kscreen/ to get a usable screen setup back. * If I unplug the DP cable and close the laptop lid, quite often plasmashell and krunner will crash leaving the laptop running and not suspended. Risk of cooking laptop in bag :( Might be general malaise with DisplayPort connections in KDE. I run one setup with the same laptop using an HDMI connection and rarely see issues. I would be interested in helping out with testing to get this general funkiness in external display support fixed.
(In reply to jamese from comment #14) > Might be general malaise with DisplayPort connections in KDE. I run one > setup with the same laptop using an HDMI connection and rarely see issues. Same issues here -- I dock into a Mini DisplayPort. Running: kscreen-5.4.2-1.fc22.x86_64
(In reply to liquid from comment #3) > * On desktop: Turn off Monitor, and turn back on = monitor no longer > detected (sleeps). It will turn on if I switch to a console w/ctrl+alt+F1. > Returning to session screen goes back off. Nice trick :) just confirming that it works for me too on both docked and undocked. (In reply to Honza Tvrznik from comment #13) > When display is changed, maximized windows takes full screen and > part of this windows is under panel. Plasmashell restart and "kwin_x11 > --replace" solve this problem. Just to add another bit of info here: if I move the task bar at the top maximize fits the window correctly.
Hi, I also have a similar issue, with a VGA monitor. If I plug or unplug it, nothing happens. The workaround is to start the Display Configuration. This automatically detects and restores the settings, I just have to close it and say Cancel to the change. (It was working in the past with kde 5) I have KDE 5.4.2-2 now.
I too have this problem regarding chaning from Dual Monitor to Single Monitor and experiencing issues. Details : 1. Laptop - Dell Latitude E5530 2. External monitor - Samsung SyncMaster S23B370 3. When docked, and using Shared Desktop, with laptop on the Left and Monitor on the Right, I use Monitor as Primary screen, with certain widgets and panels 4. When I undock, the Laptop does not become Primary again with all the appropriate panels etc. PS : What is required to make this bug "Confirmed" ?
(In reply to Laven Pillay from comment #18) > I too have this problem regarding chaning from Dual Monitor to Single > Monitor and experiencing issues. > Details : > 1. Laptop - Dell Latitude E5530 > 2. External monitor - Samsung SyncMaster S23B370 > 3. When docked, and using Shared Desktop, with laptop on the Left and > Monitor on the Right, I use Monitor as Primary screen, with certain widgets > and panels > 4. When I undock, the Laptop does not become Primary again with all the > appropriate panels etc. > > PS : What is required to make this bug "Confirmed" ? in the past we could vote! Now I can't find the option to, despite from being able to see my votes.
Hey guys, moving to confirmed, since more of you are able to reproduce the issue. Please run the following command in terminal: QT_LOGGING_RULES="*" kscreen-console monitor and reproduce the issue. Then get the output of the command and attach it here please. Also mention what GPU and drivers you have. Thanks.
UPDATE : Okay, the problem is not quite what I thought it was, and seems to be inconsistent. IMPORTANT : After some testing I see that my VGA cable connecting laptop to external is a bit unstable and possibly damaged. On one attempt, it was connected but showed up as a "VGA Monitor" instead of "Samsung Electric Company...". A disconnect-reconnect detected the monitor correctly and showed up as "Samsung...". So maybe similar things are happening to others ? Incorrect detection of external monitor or something ? Replicating original Problem : 1. Log into Linux (Korora 23 KDE) 2. Connect external monitor 3. Set External Monitor as Primary 4. Suspend/Shutdown laptop 5. Disconnect External Monitor 6. Restart laptop 7a. If laptop was Suspended - cannot log in due to keyboard not being detected (cannot replicate futher) 7b. If laptop was Shut Down - Experience issue where laptop screen is not primary New Test Results : 1. Log into Linux (Korora 23 KDE) 2. Connect external monitor 3. Set External Monitor as Primary 4. Disconnect External Monitor 5. Laptop (correctly) switches to Laptop screen as Primary 6. Re-Connect External Monitor 7. Laptop+Screen correctly switches to External as Primary So my current observations on my system are : 1. If External Monitors are connected/disconnected while both laptop and external are powered on, then everything seems to work fine - I see in Settings that the Display setting switches the Primary monitor correctly. 2. If external monitors are connected/disconnected while powered down, possible to have dual-monitor related issues.
Following the suggestion in comment 20: $ QT_LOGGING_RULES="*" kscreen-console monitor Remember to enable KSRandR or KSRandR11 in kdebugdialog so I did just that, enabling: konsole kdevelop (konsole part) kdevplatform (konsole) KSRandr followed by: undock laptop lift lid close lid redock laptop However, there was nothing displayed after the "Remember to enable KSRandr..." line above so I simply interrupted with Ctrl-C. Here's what '~/.xsession-errors' shows in case it helps: okular(20923)/KSRandr: BEGIN: RRNotify_OutputChange okular(20923)/KSRandr XRandRX11Helper::x11Event: Output: 69 okular(20923)/KSRandr XRandRX11Helper::x11Event: CRTC: 63 okular(20923)/KSRandr XRandRX11Helper::x11Event: Mode: 256 okular(20923)/KSRandr XRandRX11Helper::x11Event: Rotation: "RR_Rotate_0" okular(20923)/KSRandr XRandRX11Helper::x11Event: Connection: "RR_Connected" okular(20923)/KSRandr XRandRX11Helper::x11Event: Subpixel Order: 0 okular(20923)/KSRandr: END__: RRNotify_OutputChange [Took: 0.002s] Failed to register device: "device id 'xrandr-Dell Inc.-DELL U3014-P1V6N363139L' already exists" EDID ICC Profile already exists "/home/lelu/.local/share/icc/edid-e903b249edbcfc19b81d35794e219d2b.icc" powerdevil: Lid action was suppressed because an external monitor is present powerdevil: Lid action was suppressed because an external monitor is present QObject::connect: invalid null parameter QObject::connect: invalid null parameter QObject::connect: invalid null parameter QObject::connect: invalid null parameter QObject::connect: invalid null parameter QObject::connect: invalid null parameter QObject::connect: invalid null parameter QObject::connect: invalid null parameter QObject::connect: invalid null parameter QXcbConnection: XCB error: 3 (BadWindow), sequence: 20502, resource id: 98566152, major code: 18 (ChangeProperty), minor code: 0 kscreen: Failed to retrieve current config: "Backend invalidated" QXcbConnection: XCB error: 3 (BadWindow), sequence: 20513, resource id: 96469000, major code: 18 (ChangeProperty), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 20517, resource id: 100663304, major code: 18 (ChangeProperty), minor code: 0 kscreen: Failed to retrieve current config: "Backend invalidated" QXcbConnection: XCB error: 3 (BadWindow), sequence: 20521, resource id: 94371848, major code: 18 (ChangeProperty), minor code: 0 powerdevil: Lid action was suppressed because an external monitor is present QXcbConnection: XCB error: 3 (BadWindow), sequence: 35414, resource id: 33849906, major code: 20 (GetProperty), minor code: 0 QXcbConnection: XCB error: 3 (BadWindow), sequence: 36522, resource id: 33850149, major code: 20 (GetProperty), minor code: 0 While performing the switch to/from external monitor/laptop screen I've also noticed a couple of weird Konsole behaviors. These are also reported in bug 357552 that I've just filed. 1. If Konsole doesn't crash and there are several Konsole windows spread across multiple desktops *all* Konsole windows will get moved to the current desktop. I've tested with 3 Konsole windows opened on desktops 1 to 3. Changed to desktop 3 before undocking laptop followed by a Ctrl-Alt-F2 and Ctrl-Alt-F1 and all Konsole windows got moved to desktop 3. 2. A long 'ls' listing -- long enough to fill the screen top to bottom -- will result in only the few bottom lines actually srolling up with the rest of the screen remaining unchanged. A clear screen (Ctrl-L) will leave traces of output on the screen. Similar behavior if I scroll down in a 'vim' Konsole session or a 'man' page, or 'less' a file. None of the above behaviors happens with RoxTerm.
I don't have any output also and the Kscreen2 service is running on Background Services in systemsettings.
I think this bug is related to this one : https://bugs.kde.org/show_bug.cgi?id=359602
> > PS : What is required to make this bug "Confirmed" ? > > in the past we could vote! Now I can't find the option to, despite from > being able to see my votes. I think voting for disabled in the "kscreen" product. You can still manage votes for other products (e.g. kdelibs).
I am seeing this in Fedora 23 with the latest QT 5.6 updates :-(
This happens with every laptop I use. I'm unable to use any workaround like xrandr because it doesn't even detect the laptop display.
Given my huge issues with multi-monitors in general on multiple laptops. I've decided to try reproducing other people's issues first. I am running Arch Linux with enabled testing repositories, which is Qt: 5.6.0 Plasma Desktop: 5.6.4 KDE Applications: 16.04.1 KScreen and LibKscreen are from git master (c949f3d, d80fede) I have a intel Haswell card. I've followed the steps described in the original post with an external VGA monitor and could not reproduce the described state where all monitors are disabled. However, the plasmashell barely became active on the new monitor, with panels missing and wrong background. After some time (maybe after pressing Alt+F2), the panels popped up again. Reattaching the monitor resulted In the expected beaviour, disabling the Laptop monitor and only enabling the VGA screen. However, plasmashell behaved strangely again: While the wallpaper was now right, the panels were in the middle of the screen, probably at the positions from the old laptop screen. This was followed by a plasmashell crash, involving Kscreen in some kind: [KCrash Handler] #5 0x00007f894a69a7f0 in Plasma::Applet::actions() const () from /usr/lib/libKF5Plasma.so.5 #6 0x0000000000446303 in ?? () #7 0x000000000044647f in ?? () #8 0x00007f894622b71c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #9 0x00007f894b366d73 in KScreen::Output::apply(QSharedPointer<KScreen::Output> const&) () from /usr/lib/libKF5Screen.so.7 #10 0x00007f894b3480a4 in KScreen::Config::apply(QSharedPointer<KScreen::Config> const&) () from /usr/lib/libKF5Screen.so.7 #11 0x00007f894b354586 in KScreen::ConfigMonitor::Private::updateConfigs(QSharedPointer<KScreen::Config> const&) () from /usr/lib/libKF5Screen.so.7 #12 0x00007f894b356709 in KScreen::ConfigMonitor::Private::edidReady(QDBusPendingCallWatcher*) () from /usr/lib/libKF5Screen.so.7 #13 0x00007f894622b71c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #14 0x00007f894704167f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /usr/lib/libQt5DBus.so.5 #15 0x00007f8947041778 in ?? () from /usr/lib/libQt5DBus.so.5 #16 0x00007f894622c179 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #17 0x00007f89473b47bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #18 0x00007f89473b995f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #19 0x00007f89461fe280 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #20 0x00007f89462001fc in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #21 0x00007f89462542c3 in ?? () from /usr/lib/libQt5Core.so.5 #22 0x00007f8941db2dd7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0x00007f8941db3040 in ?? () from /usr/lib/libglib-2.0.so.0 #24 0x00007f8941db30ec in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0x00007f89462546cf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #26 0x00007f89461fc46a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #27 0x00007f8946204a0c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #28 0x000000000041c17c in ?? () #29 0x00007f8945875741 in __libc_start_main () from /usr/lib/libc.so.6 #30 0x000000000041c2e9 in _start () Why does plasma anything to do with libkscreen? In conclusion, maybe this is about the plasmashell not coming up again instead of the monitor change not executed? At least #3 described seeing the mouse cursor.
As a final data point, I've applied https://git.reviewboard.kde.org/r/125451/ on top of Plasma Desktop 5.6.4, and I have to say, this is godsend! No issues anymore regarding removing screens, suspend in dock, docking, and all combinations of it. Hell yeah!
https://git.reviewboard.kde.org/r/125451/ has been merged, so we can look forward to the next release!
I've found a problem in the code enabling outputs. Information about crtcs was outdated, which meant outputs failed to enable in certain cases, and were subsequently disabled. We're now querying the crtcs right before enabling an output, which seems to be much more reliable. I think this may well be the root cause for this bug, the symptoms would be consistent. I've tested suspending with dock attached quite extensively with a lenovo onelink+ dock, and it would fail in similar ways: screen stays black. Switching between these profiles (external and laptop panel) works reliably now. These patches are in libkscreen master, I hope to get them into Plasma 5.7.4 (which is the next bugfix update).
If there's an updated live version, I can test with my setup a Macbook pro retina with an external monitor via mini-displayPort or HDMI.
http://files.kde.org/neon/images/neon-devedition-gitunstable/current/? should contain those fixes.
A couple of causes for this bug have been fixed in the Plasma/5.8 branch. If problems persists with the latest code, please file a separate report to keep the debugging history clean (this bug-report mixes different causes and effects).
(In reply to Sebastian Kügler from comment #34) > A couple of causes for this bug have been fixed in the Plasma/5.8 branch. > > If problems persists with the latest code, please file a separate report to > keep the debugging history clean (this bug-report mixes different causes and > effects). Sorry Sebastian, would you please explain me how to install the latest Plasma5.8? This problem is driving me crazy and I've just started using Kubuntu. Thanks in advance!
@zanetti: KDE Neon has up to date packages: http://files.kde.org/neon/images/neon-devedition-gitunstable/current/ Keep in mind that these images are not production quality, but a snapshot from our development tree. Use at your own risk, but do let us know if thing work for you. :)
(In reply to Sebastian Kügler from comment #36) > @zanetti: KDE Neon has up to date packages: > http://files.kde.org/neon/images/neon-devedition-gitunstable/current/ > > Keep in mind that these images are not production quality, but a snapshot > from our development tree. Use at your own risk, but do let us know if thing > work for you. :) Hi Sebastian, it works like charm with my external monitor, however, as you said, it's an unstable version so it has some issues (I found that I can't modify Global Shortcuts, for example, when I open it and it starts in the Audio tab, I can't switch to the KWin tab). Will this update as the unstable version is being developed or I have to install the latest image every month if I want the latest features? Does the devStable version have this "external monitor fix"? Thanks for your help, really apreciated.
Very good to know, thanks for testing! As to your questions ... * the shortcut issue is of course unrelated, as you note, so it would be good if you could check if there's a bug reported for that * You can just pull in updates through apt, it doesn't matter which iso you installed from (as long as it's an iso which set up the right repos (basically means, if you don't change it, you'll continue to get updates from master. Don't be surprised if lots of package updates come in daily. * The dev/stable version will have it as soon as 5.8 is out (I've looked into backporting these fixes, but can't sensibly do that since it's a number of patches across different repositories and we have no way of testing that enough to go into a stable update, and we also have no further updates planned, so a regression introduced can't get fixed.