Bug#718366: ValueError: invalid literal for int() with base 10 in xrandr.py

[chrysn]

block 718366 by 740435
thank you

On Thu, Mar 20, 2014 at 03:37:28PM -0700, Hamish wrote:
 I'm seeing a similar but different thing on Wheezy:
 
   ValueError: invalid literal for int() with base 10: '1080i'

it's the same bug. i'm waiting for release team feedback on uploading a
fixed version to stable (see bug #740435).

(don't tell anybody i said this, as it is not recommended procedure for
security reasons, but there is an easy workaround: the arandr version in
testing works on stable as well, you can just download the deb and
install it).


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#718366: ValueError: invalid literal for int() with base 10 in xrandr.py

[Hamish]

Hi,

I'm seeing a similar but different thing on Wheezy:

  ...

  ValueError: invalid literal for int() with base 10: '1080i'



$ xrandr 
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 1920 x 1920
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected (normal left inverted right x axis y axis)
   1920x1080  60.0 +   60.0 24.0  
   1920x1080i 30.0 25.0  
   1600x1200  60.0  
...


thanks,
Hamish



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#718366: ValueError: invalid literal for int() with base 10 in xrandr.py

[Julius Seemayer]

Package: arandr
Version: 0.1.6-1
Severity: normal

Note: The given code area (xrandr.py:150) has changed in unstable, so this bug
is probably only relevant for Wheezy.


cvt(1)  suggest  mode  line names with a dot in it, which seems to make arandr
explode. No GUI window is shown, output see below:

$ xrandr # (I used xrandr --newmode/--addmode before, using the dot name)

CRT1 connected 1360x768+0+0 (normal left inverted right x axis y axis) 760mm x 
450mm

   1368x768_60.00   59.9  
$ arandr
Traceback (most recent call last):
  File /usr/bin/arandr, line 42, in module
main()
  File /usr/lib/python2.7/dist-packages/screenlayout/gui.py, line 318, in main
force_version=options.force_version
  File /usr/lib/python2.7/dist-packages/screenlayout/gui.py, line 159, in 
__init__
self.filetemplate = self.widget.load_from_x()
  File /usr/lib/python2.7/dist-packages/screenlayout/widget.py, line 93, in 
load_from_x
self._xrandr.load_from_x()
  File /usr/lib/python2.7/dist-packages/screenlayout/xrandr.py, line 150, in 
load_from_x
o.modes.append(Size(int(a) for a in d.strip().split( )[0].split(x)))
  File /usr/lib/python2.7/dist-packages/screenlayout/auxiliary.py, line 53, 
in __new__
arg = tuple(arg)
  File /usr/lib/python2.7/dist-packages/screenlayout/xrandr.py, line 150, in 
genexpr
o.modes.append(Size(int(a) for a in d.strip().split( )[0].split(x)))
ValueError: invalid literal for int() with base 10: '768_60.00'
$ 

As  mentioned  above: Probably the unstable package is not broken in that way.
I didn't figure out if this can be smoothly installed in stable.


Cheers,

Julius



-- Package-specific info:
Output of /usr/share/bug/arandr:
$ xrandr --version
xrandr program version   1.3.5
Server reports RandR version 1.3

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

Kernel: Linux 3.2.0-4-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

Versions of packages arandr depends on:
ii  python 2.7.3-4
ii  python-gtk22.24.0-3+b1
ii  python2.6  2.6.8-1.1
ii  python2.7  2.7.3-6
ii  x11-xserver-utils  7.7~3

arandr recommends no packages.

arandr suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org