external (xrandr) monitor support borked #32

Closed
mattharrison opened this Issue Nov 15, 2010 · 9 comments

Comments

Projects
None yet
5 participants
Contributor

mattharrison commented Nov 15, 2010

Am trying out qtile as primary wm now on my laptop. When I turn on my external monitor everything (both screens) go to that window.

I use the following command:

xrandr --output VGA1 --auto
xrandr --output LVDS1 --right-of VGA1 --auto

It seems like an x offset is not correct somewhere....

ps - I thought I had this bug filed before, but can't find it

Contributor

mattharrison commented Nov 15, 2010

Ok, I've messed around a bit, it now seems to work if I restart qtile.... (I remembered in the previous version that you said try starting qtile with the external monitor going. Which is hard since I start qtile from startx (.xinitrc)). But a restart appeared to do the trick.
I'm assuming that there is an event to hook to so restarting is unnecessary?

Owner

tych0 commented Nov 14, 2012

Can anyone else who uses xrandr confirm that calling Qtile.restart() (via qsh, if nothing else) after an xrandr reconfiguration solves the issue? If so, I think we can figure out when xrandr events happen and provide a hook for them.

Contributor

TimNN commented Nov 14, 2012

I can confirm that an external monitor configured with xrandr only works correctly after restarting qtile.

Owner

tych0 commented Nov 14, 2012

Ok, cool. Have you done it with Qtile.restart() (cmd_restart, I guess), or are you restarting your whole xsession?

Contributor

TimNN commented Nov 14, 2012

I'm restarting only qtile using cmd_restart()

Contributor

cjbarnes18 commented Nov 14, 2012

I can confirm that this works for me too.

On 14/11/2012, TimNN notifications@github.com wrote:

I'm restarting only qtile using cmd_restart()


Reply to this email directly or view it on GitHub:
#32 (comment)

Craig

Sin of the day.

import this
In the face of ambiguity, refuse the temptation to guess.

mictee commented Nov 15, 2012

Same here. As a matter of fact, this thing has been bugging me since I
first started using qtile. I thought the problem was that I didn't
keep my monitor setup persistent the right way. I always use
cmd_restart() (lazy.restart()) right after startup.

Can I do anything to help?

Owner

tych0 commented Nov 16, 2012

Hi all - can anyone verify that this commit solves the problem? tych0/qtile@19189ea

Contributor

cjbarnes18 commented Nov 16, 2012

I posted feedback on your branch.

On 16 November 2012 19:30, Tycho Andersen notifications@github.com wrote:

Hi all - can anyone verify that this commit solves the problem? tych0@
19189eahttps://github.com/tych0/qtile/commit/19189ea6dbe957026b7a319b8b88cc2f0e843d0a


Reply to this email directly or view it on GitHubhttps://github.com/qtile/qtile/issues/32#issuecomment-10458885.

@tych0 tych0 closed this in 3c90d4d Nov 19, 2012

tych0 added a commit to tych0/qtile that referenced this issue Nov 20, 2012

Add a hook for screen_change
Fixes #32 for real this time :-)

tych0 added a commit that referenced this issue Nov 21, 2012

Add a hook for screen_change
Fixes #32 for real this time :-)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment