2x 4k Multimonitor not working with Wayland/Gnome, but works with X11(Installer and KDE)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
New
|
Undecided
|
Unassigned |
Bug Description
Hardware:
- Dell XPS 13 Plus
- 32GB RAM
- 12th i7-1280P
- Dockingstation WD-22TB4
- 2x 4K Monitors Dell UltraSharp U4320Q, 42.5" @ 100dpi/no scaling 10bit support connected to WD-22TB4[1]
How to reproduce:
- Undocked: Reboot with recent Ubuntu 22.04.0 ubuntu-
- On First welcome screen, I docked the laptop. All monitors active with 24bit colordepth (Monitors shows this information)
- After install, USB disc removed and rebooted
- On boot, entered LUKS password, then Gnome Login is presented and after login
only one monitor is enabled.
What I tried:
- After logging in in Gnome/Wayland, went to Display settings and tried to reduce somehow color depth.
I knew that Windows starts the monitors with 24bits instead of max supported 30bits.
The second monitor just stays blank even though in Display settings it is activated.
- Only solution is to reduce resolution other than its native 4K resolution -> Not acceptable.
Workaround:
- I installed KDE because I know they use still X11
- With KDE I was able to use both monitors at maximum resolution.
A monitor information overlay tells 4K@24bits on both monitors - same as in Windows
- It is also possible to use even the laptop display as third display too like in Windows.
Please fix, that Gnome with Wayland can run at maximum resolution with 24bit.
My fear is that KDE in future will also not work, when they switch to Wayland.
There should be a possibility to reduce/limit colors generally at 24bit,
as the bandwith of Dockingstation / Motherboard is limited to 2x4k@24bit (kernel or driver?)
[1] https:/
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/2042968/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]