Bug 398460 - Screen hotplug not working under Wayland
Summary: Screen hotplug not working under Wayland
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.13.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2018-09-10 14:06 UTC by Mayeul C.
Modified: 2020-01-08 04:33 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mayeul C. 2018-09-10 14:06:50 UTC
Not sure this is the right place.

I use a docking station with my computer (dell lattitude 5580, dell wd15). Intel graphics, Mesa 18.2.8 (Arch). The docking station is connected over USB C, DP alternate mode, and everything works fine under X.

Under Wayland, though, the screens are not detected when I plug the docking station in. Everything else works fine: keyboard, mouse, network, charging, audio, USB.

The extra screens remain blank, there is no OSD to pick the layout, and the screens don't appear in the KCM, only the laptop's.

Moreover, when logging out, there might be a problem with SDDM or kwin (dmesg says kwin_wayland[31085]: segfault at 556790bdc740 ip 0000556790bdc740 sp 00007ffeca4c4798 error 15) during shutdown, as the three screens are blank, and I can't switch to a VT (even with Sysrq+R). I need to REISUB my way out of this (S and U are logged to the screen in text mode, though).
Comment 1 Jan Kundrát 2019-05-09 18:27:36 UTC
I'm getting this behavior on a Thinkpad T460s with kernel 5.1.0, Qt 5.13 from git, and this week's Plasma from latest git. I checked output of `kscreen-console`, and no additional screens were listed there. I have not seen any relevant message in output of `journalctl -f`.

Do you need more information? Is this supposed to be working? How do I debug this?
Comment 2 Aleix Pol 2019-12-09 20:34:58 UTC
It's working for me, you might have a special hardware configuration. If you get any pointers after trying a stable version, please reopen.
Comment 3 Bug Janitor Service 2019-12-24 04:33:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2020-01-08 04:33:07 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!