Results 1 to 10 of 10

Thread: compiz vs xrandr - bug or expected problem

Hybrid View

  1. #1
    Join Date
    May 2011
    Beans
    3

    compiz vs xrandr - bug or expected problem

    Samsung N210, Ubuntu 11.04

    I'm not sure if the problem I am having is a bug or just the expected behaviour given the bodge I am using. I have a netbook with a native 1024x600 resolution. Sometimes I need to switch to a higher non-native resolution 1280x750 or 1365x800.

    I use a little script that issues the command with all the variables calculated.

    Code:
    xrandr --fb $H"x"$V --output $device --scale $scale"x"$scale --panning $H"x"$V
    This works perfectly in Gnome but fails to work properly in Unity.

    In unity issuing the command leaves a black strip across the top and down the right side of the screen that does not get drawn correctly. Only the top panel and the unity launcher are draw in these black areas. A rectangle in the bottom left that would be 1024x600 worth of the 1280x750 does get drawn correctly.

    Is it possible that compiz is getting the values for screen geometry from two different sources?

    Is this a bug or am I just doing something that shouldn't work? Has anyone had success using zrandr to get higher than native resolution in unity.

  2. #2
    Join Date
    May 2011
    Beans
    3

    Re: compiz vs xrandr - bug or expected problem

    I thought the attached screen shots might aid my poor explanation.
    Attached Images Attached Images

  3. #3
    Join Date
    Dec 2010
    Beans
    4
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: compiz vs xrandr - bug or expected problem

    Exactly the same problem and, oddly, same laptop running 11.04 (fresh install).

    In 10.10 (running Unity as well) I was able to run:

    xrandr --output LVDS1 --mode 1024x600 --scale 1.25x1.25

    to get 1280x750.

    Now I get the same black sections as you.

    I've looked on the Voria forums to see if anyone else has the same problem.

  4. #4
    Join Date
    Dec 2010
    Beans
    4
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: compiz vs xrandr - bug or expected problem

    Aha, potential solution: run unity --replace (via ALT-F2) after running xrandr.
    Last edited by dknight212; May 18th, 2011 at 04:03 PM.

  5. #5
    Join Date
    May 2011
    Beans
    3

    Re: compiz vs xrandr - bug or expected problem

    That does seem to work. This would suggest that we need to launch unity after xrandr. I will investigate running xrandr early in the start up.

    Ideally I would like the setup I had in 10.10. I would work with native resolution and run my script by hitting a function key to switch to 1280x750 when needed. Not an option if xrandr needs to be in place before unity

  6. #6
    Join Date
    Dec 2010
    Beans
    4
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: compiz vs xrandr - bug or expected problem

    Yep, unity --replace is not the best or fastest solution but it's workable. Not sure why I could do without --replace when running xrandr on unity on 10.10, can't remember if I was running 2d or the full thing as I played around a lot.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •