[amdgpu] Wayland sessions detect 4K screens (3840x2160) as only 1280x800.

Bug #1826316 reported by Miroslav Spehar
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)
Won't Fix
Low
Unassigned
xserver-xorg-video-amdgpu (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

i have 2 monitor setup, both are hidpi monitors:
when 1 monitor (either one) is connected to the pc, resolution of the monitor is properly recognized.
when 2 monitors are connected, maximum of 1200x800 is recognized.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: mutter 3.32.0+git20190410-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 07:46:32 2019
InstallationDate: Installed on 2019-04-24 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Miroslav Spehar (mspehar) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please:

1. Run: lspci -k > lspcik.txt
   and send us the file 'lspcik.txt'.

2. Run: strings -f /sys/class/drm/*/edid > edids.txt
   and send us the file 'edids.txt'.

3. Run: dmesg > dmesg.txt
   and send us the file 'dmesg.txt'.

4. Run: journalctl -b0 > journal.txt
   and send us the file 'journal.txt'.

Changed in mutter (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please also:

5. Run: xrandr --verbose > xrandr.txt
   and send us the file 'xrandr.txt'.

Revision history for this message
Miroslav Spehar (mspehar) wrote :

dmesg.txt

Revision history for this message
Miroslav Spehar (mspehar) wrote :

edids.txt

Revision history for this message
Miroslav Spehar (mspehar) wrote :

journal.txt

Revision history for this message
Miroslav Spehar (mspehar) wrote :

lspci.txt

Revision history for this message
Miroslav Spehar (mspehar) wrote :

about xrandr.txt... this happens with wayland session (the bug is tagged properly i think)
honestly, i didnt try the xorg session... so the file is empty

root@r7:/home/mspehar# xrandr --verbose > xrandr.txt
No protocol specified
Can't open display :0

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: [amdgpu] two 4K monitor setup - resolution not properly recognized

Please run that as yourself in a regular desktop terminal window:

  xrandr --verbose > xrandr.txt

summary: - two monitor setup - resolution not properly recognized
+ [amdgpu] two 4K monitor setup - resolution not properly recognized
tags: added: amdgpu
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

And ideally run it in a Xorg session.

Revision history for this message
Miroslav Spehar (mspehar) wrote :

xrandr-xorg.txt

Revision history for this message
Miroslav Spehar (mspehar) wrote :

xrandr-wayland.txt

description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks!

It looks like the problem is indeed confined to Wayland sessions, if it is a problem at all.

If you have display scaling set to a value of around 300% then a reported desktop resolution of 1280xSomething is expected and not a bug.

In a Wayland session, please open [Settings > Devices > Screen Display] and take a screenshot of that window. Then attach it here.

Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: New → Incomplete
Revision history for this message
Miroslav Spehar (mspehar) wrote :
Revision history for this message
Miroslav Spehar (mspehar) wrote :
Revision history for this message
Miroslav Spehar (mspehar) wrote :

so, wayland started working properly.

steps:
1. fresh ubuntu install
2. 1st login done in wayland -> max resolution wrongly recognized to be rather low (1200x800); scaling is disabled because of that
3. logout
4. login to xorg -> resolution properly recognized; i could set scaling to 200%
5. logout
6. login to wayland -> resolution properly recognized (i.e. physical monitor resoultion can now be seen in the dropdown menu), but default values for resolution (1200x800) and refresh rate (30) wrongly set; only one monitor (secondary) was usable because the primary was having wrong refresh rate -> when i set refresh rate to 60, primary monitor started to work again.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK, so this is a real bug...

Next please report the bug to the GNOME developers here:

  https://gitlab.gnome.org/GNOME/mutter/issues

and then tell us the new bug ID.

summary: - [amdgpu] two 4K monitor setup - resolution not properly recognized
+ [amdgpu] Wayland sessions detect 4K screens (3840x2160) as only
+ 1280x800.
Changed in mutter (Ubuntu):
status: Incomplete → New
Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: Incomplete → New
Revision history for this message
Miroslav Spehar (mspehar) wrote :
Changed in mutter (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Changed in mutter:
status: Unknown → New
Changed in mutter:
status: New → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

"Long story short - i cannot reproduce it:

Fedora booted properly
I reinstalled ubuntu and it this time it worked fine"

https://gitlab.gnome.org/GNOME/mutter/issues/574

Changed in mutter (Ubuntu):
status: Triaged → Incomplete
Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: Triaged → Incomplete
no longer affects: mutter
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please let us know if and when you can reproduce the bug. Otherwise it will automatically close in 60 days.

Revision history for this message
Miroslav Spehar (mspehar) wrote :

I managed to reproduce it on archlinux + kde. Not sure if this would help, but i can provide outputs from arch.

Revision history for this message
Miroslav Spehar (mspehar) wrote :

since it can be reproduced in certain scenarios with ubuntu, kubuntu and arch, is there some output that i should provide to try to track driver issues?

new situation:
- booted ubuntu iso
- resolution were wrong (aka small)
- due to inactivity screen was turned off
- when i reactivated the screen, resolution was recognized correctly

unfortunatelly, turning off the pc and rebooting does not play a role now. i managed to "break" it by installing archlinux. next boot showed problems with graphic card as described.

Changed in mutter:
status: Unknown → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in mutter (Ubuntu):
status: Incomplete → Won't Fix
Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: Incomplete → Won't Fix
Changed in mutter:
status: New → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The upstream bug was never fixed, just closed. So removing the task...

https://gitlab.gnome.org/GNOME/mutter/issues/574

no longer affects: mutter
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.