Arandr doesn't start

[Mboy]

Since last upgrade arandr doesn't start anymore. Error displayed:

Traceback (most recent call last):
  File "/usr/bin/arandr", line 25, in <module>
    main()
  File "/usr/lib/pymodules/python2.7/screenlayout/gui.py", line 302, in main
    force_version=options.force_version
  File "/usr/lib/pymodules/python2.7/screenlayout/gui.py", line 143, in __init__
    self.filetemplate = self.widget.load_from_x()
  File "/usr/lib/pymodules/python2.7/screenlayout/widget.py", line 77, in load_from_x
    self._xrandr.load_from_x()
  File "/usr/lib/pymodules/python2.7/screenlayout/xrandr.py", line 134, in load_from_x
    o.modes.append(Size(int(a) for a in d.strip().split(" ")[0].split("x")))
  File "/usr/lib/pymodules/python2.7/screenlayout/auxiliary.py", line 37, in __new__
    arg = tuple(arg)
  File "/usr/lib/pymodules/python2.7/screenlayout/xrandr.py", line 134, 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: '1024_videoseven'

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: arandr 0.1.4-1
ProcVersionSignature: Ubuntu 3.2.0-37.37-lowlatency 3.2.35
Uname: Linux 3.2.0-37-lowlatency x86_64
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Mon Feb 4 00:03:26 2013
InstallationMedia: Ubuntu-Studio 12.04 "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=de_DE:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: arandr
UpgradeStatus: No upgrade log present (probably fresh install)

[Hans Joachim Desserud (hjd)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 751085, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.