One monitor getting spilled over into other monitor: how to do a 100% reset of gnome graphics configuration

Posted by Paul Nathan on Ask Ubuntu See other posts from Ask Ubuntu or by Paul Nathan
Published on 2011-10-05T17:32:37Z Indexed on 2011/11/18 2:03 UTC
Read the original article Hit count: 261

Filed under:
|
|

I had to kill a VMWare process and afterwards, my monitor's configuration is buggy.

I have 2 monitors in a side-by-side configuration. My right-hand monitor is the secondary monitor.

Upon its right-hand side there are about 50 pixels showing from the left side of the lefthand monitor (ie, as if it was wrapped around). Further, my mouse clicks are registering as about 50 pixels sideways from where they should be.

It's as if those 50 pixels between monitors got gobbled.

What have I done?

  • I've reset the screen configuration in multiple ways, using xrandr, multiple monitors app, etc. This persists in different side-by-side configurations, and also persists with another user.

  • It does not occur with XFCE.

  • Resetting the Window manager with the Compiz reset WM app does not fix this.

I've concluded the burn-to-the-ground approach is likely the best, and would like to do a 100% reset of my graphics settings. It's an Intel integrated chipset.

  • Removing ~/.config/monitors.xml did not work. Also, interestingly, the mouse can mouse-over the 50 errant pixels on the rhs of the right-hand monitor. I hypothesize that it's a compositing problem occurring at the layer where the background, selection, and clicks are caught. Also, inverting the right-hand monitor removes the issue, but renders the screen unusable.

Even more datapoints:

  • This happens in KDE as well

  • Sometimes logging into Gnome and running xrandr --output DVI1 --auto resets it, but the issue immediately reappears when I press alt-tab.

  • With Compiz Application Switch turned on, the workspace is 'pushed back' a bit, and the slice on the RHS follows it as well. I'm wondering if it's a flaw in the compiz workspace compositing configuration.


I suspect the error was in the compositing configuration.

I installed 11.10.

© Ask Ubuntu or respective owner

Related posts about 10.10

Related posts about xorg