After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 756791 - Resolution list different from Wayland to X
Resolution list different from Wayland to X
Status: RESOLVED DUPLICATE of bug 744544
Product: mutter
Classification: Core
Component: wayland
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2015-10-18 19:59 UTC by Vincent Bolduc
Modified: 2015-10-19 12:54 UTC
See Also:
GNOME target: ---
GNOME version: 3.17/3.18



Description Vincent Bolduc 2015-10-18 19:59:51 UTC
When starting Gnome-shell with X, I have all the supported resolutions listed in the resolution list.

When I'm starting Gnome-shell under Wayland, it only list the native resolution, which is 3840 x 2160 (16:9).

I'm used to set the resolution to 1920 x 1080 under X due to scaling problems inside applications (eclipse, Atom,...). I can't set the Wayland session to this resolution.
Comment 1 Bastien Nocera 2015-10-18 20:03:05 UTC
The resolution listing is implemented in mutter, reassigning.
Comment 2 Rui Matos 2015-10-19 09:13:25 UTC
Please post the output of edid-decode. Something like

$ edid-decode /sys/class/drm/.../edid

You'll need to fill in '...' with the actual path on your system which depends on your GPU and the output connectors you have.
Comment 3 Vincent Bolduc 2015-10-19 12:31:45 UTC
Thank you, 

Here is the output of edid-decode :
$ edid-decode /sys/class/drm/card0-eDP-1/edid                                                        
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   4d 10 31 14 00 00 00 00 2c 18
version:         01 04
basic params:    a5 23 13 78 0e
chroma info:     de 50 a3 54 4c 99 26 0f 50 54
established:     00 00 00
standard:        01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    4d d0 00 a0 f0 70 3e 80 30 20 35 00 5a c2 10 00 00 18
descriptor 2:    4d d0 00 a0 f0 70 68 82 30 20 35 00 00 00 00 00 00 00
descriptor 3:    00 00 00 fe 00 54 59 33 58 43 80 4c 51 31 35 36 44 31
descriptor 4:    00 00 00 00 00 02 01 03 23 00 12 00 00 0b 01 0a 20 20
extensions:      00
checksum:        5f

Manufacturer: SHP Model 1431 Serial Number 0
Made week 44 of 2014
EDID version: 1.4
Digital display
8 bits per primary color channel
DisplayPort interface
Maximum image size: 35 cm x 19 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
Default (sRGB) color space is primary color space
First detailed timing is preferred timing
Established timings supported:
Standard timings supported:
Detailed mode: Clock 533.250 MHz, 346 mm x 194 mm
               3840 3888 3920 4000 hborder 0
               2160 2163 2168 2222 vborder 0
               -hsync -vsync
Detailed mode: Clock 533.250 MHz, 0 mm x 0 mm
               3840 3888 3920 4000 hborder 0
               2160 2163 2168 2776 vborder 0
               -hsync -vsync analog composite
ASCII string: TY3XC
Manufacturer-specified data, tag 0
Checksum: 0x5f (valid)
EDID block does NOT conform to EDID 1.3!
	Missing name descriptor
	Missing monitor ranges
	Detailed block string not properly terminated

I don't know if it can help you but the computer has two graphic card, an integrated Intel and an Nvidia card switched off with Bumblebee.
Comment 4 Rui Matos 2015-10-19 12:54:40 UTC
Your panel reports only one mode so the other modes you see available in X are the standard vesa modes which our native backend doesn't support yet.

*** This bug has been marked as a duplicate of bug 744544 ***