KDE Plasma Wayland session does not detect external monitor
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kwin (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
plasma-workspace (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
On my Thinkpad W530 the external monitor attached to the dock only is active until login. After login it disappears from available monitors, loses signal and the internal monitor is active only.
Workaround: Uses X11 session.
So I don't need a solution. But maybe the info gathered helps you fixing bugs.
I recently tried these
GRUB_CMDLINE_
GRUB_CMDLINE_
because I' having problems with ACPI and detection of DVD-Drive.
but I disabled them after my screen did not work any more after upgrade. (yeah I did the upgrade to impish rather late)
So I think this is not related.
My logfiles might be spammed with DVD read errors because I am currently reading bad DVDs. Just ignore them.
Release: 21.10
Wayland related version numbers. Package with wayland in name and not listed are not installed.
kwayland-data: 4:5.86.0-0ubuntu1
kwayland-
kwin-wayland: 4:5.22.5-0ubuntu1
kwin-wayland-
libkf5waylandcl
libkf5waylandse
libkwaylandserver5: 5.22.5-0ubuntu1
libqt5waylandcl
libqt5waylandco
libva-wayland2: 2.12.0-2
libwayland-client0: 1.19.0-2build1
libwayland-cursor0: 1.19.0-2build1
libwayland-egl1: 1.19.0-2build1
libwayland-server0: 1.19.0-2build1
plasma-
qtwayland5: 5.15.2-4
xwayland: 2:21.1.2-0ubuntu1.1
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: plasma-
ProcVersionSign
Uname: Linux 5.13.0-30-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: KDE
Date: Tue Mar 8 14:03:05 2022
SourcePackage: plasma-workspace
UpgradeStatus: Upgraded to impish on 2022-02-27 (9 days ago)
affects: | ubuntu → wayland (Ubuntu) |
Changed in kwin (Ubuntu): | |
status: | Incomplete → Won't Fix |
Changed in plasma-workspace (Ubuntu): | |
status: | Incomplete → Won't Fix |
I'm guessing the dock uses DisplayLink, in which case the compositor needs to have implemented special support for that (like mutter/gnome-shell already has). To confirm this theory, please tell us the model of dock as well as running:
lsmod > lsmod.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.