[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#858408: /usr/bin/xrandr: Can no longer set 1920x1080 resolution manually



Package: x11-xserver-utils
Version: 7.7+7+b1
Severity: normal
File: /usr/bin/xrandr

Dear Maintainer,
I normally connect to my monitor via a passive DisplayPort to HDMI adapter. X sets my resolution to 1024x768 I suspect this is a quirk of the adapter, because despite this my monitor supports 1080p.  Normally I get around this by setting 1080p manually via the following script:

#!/bin/bash
output=`xrandr|grep primary|cut -d " " -f 1`
xrandr --newmode "1080p"  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync
xrandr --addmode $output 1080p
xrandr --output $output --mode 1080p
kdialog --title "Resolution Changed" --passivepopup "Your screen resolution is now `xrandr  | grep \* | cut -d' ' -f4`"
-------------------------------------------------

This method worked until my last update 3 or four nights ago. Now, When I run the script, My monitor blinks off for a couple of seconds, but returns as 1024x768 with no stdout output. any subsequent attempts to run the script produce the following output:

X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  16 (RRCreateMode)
  Serial number of failed request:  40
  Current serial number in output stream:  40

My xrandr output afterwards is this:

Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
eDP-1 connected (normal left inverted right x axis y axis)
   1366x768      59.99 +  40.00  
   1360x768      59.80    59.96  
   1024x768      60.04    60.00  
   960x720       60.00  
   928x696       60.05  
   896x672       60.01  
   960x600       60.00  
   960x540       59.99  
   800x600       60.00    60.32    56.25  
   840x525       60.01    59.88  
   800x512       60.17  
   700x525       59.98  
   640x512       60.02  
   720x450       59.89  
   640x480       60.00    59.94  
   680x384       59.80    59.96  
   576x432       60.06  
   512x384       60.00  
   400x300       60.32    56.34  
   320x240       60.05  
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-2 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00* 
   800x600       60.32    56.25  
   848x480       60.00  
   640x480       59.94  
   1080p         59.96  
DP-1-3 disconnected (normal left inverted right x axis y axis)  

Note: DP-1-2 is my primary monitor display, eDP1 is my inactive laptop screen. Note also that x added the 1080p line, but the refresh rate is wrong. attempts to switch to the 1080p modeline don't work. 

The bottom line is that I can no longer use 1080p at all on that display. Are there any workarounds I can try?


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages x11-xserver-utils depends on:
ii  cpp          4:6.3.0-1
ii  libc6        2.24-9
ii  libice6      2:1.0.9-2
ii  libx11-6     2:1.6.4-3
ii  libxaw7      2:1.0.13-1+b2
ii  libxcursor1  1:1.1.14-1+b4
ii  libxext6     2:1.3.3-1+b2
ii  libxi6       2:1.7.9-1
ii  libxmu6      2:1.1.2-2
ii  libxmuu1     2:1.1.2-2
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxt6       1:1.1.5-1
ii  libxxf86vm1  1:1.1.4-1+b2

x11-xserver-utils recommends no packages.

Versions of packages x11-xserver-utils suggests:
pn  cairo-5c        <none>
pn  nickle          <none>
ii  xorg-docs-core  1:1.7.1-1

-- no debconf information


Reply to: