Skip to main content

arandr quick fix invalid literal for int with base 10

Very dirty fix

If you ever get this, be aware that it's a known bug, and it's because of the "i" in:
 [mihamina@dell-f17 ~]$ xrandr -q 
 Screen 0: minimum 320 x 200, current 2390 x 768, maximum 8192 x 8192 
 LVDS1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 
    1366x768       60.1*+ 
    1024x768       60.0   
    800x600        60.3     56.2   
    640x480        59.9   
 VGA1 connected 1024x768+1366+0 (normal left inverted right x axis y axis) 0mm x 0mm 
    800x600        60.3 +   85.1     72.2     75.0     56.2   
    1280x1024      60.0   
    1280x960       60.0   
    1280x800       74.9     59.8   
    1152x864       75.0     70.0   
    1280x768       74.9     59.9   
    1024x768       85.0*    75.1     70.1     60.0   
    1024x768i      43.5  <========== THERE!! 
    1024x576       60.0   
    848x480        60.0   
    640x480        85.0     72.8     75.0     60.0   
    720x400        85.0     70.1   
    640x400        85.1   
    640x350        85.1   
 HDMI1 disconnected (normal left inverted right x axis y axis) 
 DP1 disconnected (normal left inverted right x axis y axis) 
Upstream have to fix it, but waiting for that, edit xrandr.py line 150

  for d in details: 
                 # o.modes.append(Size(int(a) for a in d.strip().split(" ")[0].split("x"))) 
                 o.modes.append(Size(a for a in d.strip().split(" ")[0].split("x"))) 

This will make your arandr work again. A package update will overwrtite this.

A better than worst fix


In my sample repository, you can find the last version of my (still dirty) fix: http://goo.gl/fBAoY

Comments

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme. I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create. Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard: "Create with shared configuration" will allow me to select the project I want the new one to share configuration with. The new created project will use the same configuration as the project I select There will be no creation of Workflow and Issue Scheme that