Registered Member
|
Hi,
I recently switched from Ubuntu to Arch Linux. There I am running SDDM as my display manager and kde5 as my desktop environment. When I connect an external monitor to my notebook (Sandy Bridge Pentium with integrated graphics) everything works fine. However when I disconnect the monitor the resolution on the laptop dos not get restored correctly or the display turns black when the monitor was connected vi HDMI. Can someone help me with this? Does anyone have similar problems? Thanks Armagetron |
|
kscreen bug, should be fixed with 5.3.2 - see https://bugs.kde.org/show_bug.cgi?id=349123 (though it's NOT a kwin bug, please refrain from "me too" comments for some more details.
|
Registered Member
|
Hi,
thanks for your reply. 5.3.2 has not yet arrived in the Arch repos. Does this also solve the issue, that the screen turns black after disconnecting an HDMI monitor? The described behaviour only happend when I used a VGA monitor. |
|
What means "turns black"? Is the screen configured off or does just plasmashell crash? (basically: "is there a mouse cursor?")
|
Registered Member
|
I have a notebook and an HDMI monitor with the laptop screen being the primary display. When I disconnect the external monitor by pulling the plug the notebook screen goes dark and the shell must be crashing since I do not longer see a mouse cursor.
|
Registered Member
|
I am running the latest versions of Plasma 5.3.2 and KDE Applications 15.04.3 on Arch Linux with SDDM. I have a laptop with Intel graphics and an external monitor connected via HDMI. When I disconnect the monitor the screen on the laptop turn black. SDDM is still running at this point. This problem persists after reboot. I have to delete ~/.local/share/kscreen with its configurations to get the display working again. What may cause this?
|
|
When the shell crashes, you still have a mouse cursor.
When X11 crashes, you'd be represented with a login screen. Either the IGP kernel module has a bug (would be very big problem) or simply all screens are deactivated. => either try to switch to another virtual terminal (try "Ctrl+Alt+F2") or to log into the machine via ssh, then check the output of
on the present screen configuration. If you cannot access the machine from another VT or via ssh, it's a kernel issue. |
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft