Welcome to awesome bug tracking system.

FS#498 - primary output change via xrandr is not recognized

Attached to Project: awesome
Opened by Ulrich Dangel (mru) - Friday, 17 April 2009, 13:36 GMT
Last edited by Uli Schlachter (psychon) - Sunday, 04 November 2012, 20:44 GMT
Task Type Feature Request
Category Core
Status Unconfirmed
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version 3.2
Due in Version 4.0
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


Changing the primary output (xrandr --output LVDS --primary) isn't recognized by awesome
so you have to restart it.
I think awesome should act like resizing/adding a screen.
Comment by Maarten Maathuis (madman2003) - Friday, 17 April 2009, 13:59 GMT
The "problem" here is that awesome triggers a restart on root window change. Obviously that isn't happening here. It would have to listen to randr-specific output change events.
Comment by Uli Schlachter (psychon) - Sunday, 14 March 2010, 14:38 GMT
Uhm, awesome doesn't really have a concept of primary output, does it?
The restart would just cause them to be sorted differently in screen[], no?
Comment by Uli Schlachter (psychon) - Saturday, 11 December 2010, 13:34 GMT
Does the attached patch make awesome restart automatically?

This enables way too many notifies from randr, but I'm too lazy to figure out right now which ones would be correct. :)
   patch (1.1 KiB)
Comment by Uli Schlachter (psychon) - Thursday, 18 October 2012, 22:16 GMT
<klaernie> psychon: I tried out each of the notifies for itself, and XCB_RANDR_NOTIFY_MASK_SCREEN_CHANGE suffices to restart awesome when the primary screen changes
Comment by Uli Schlachter (psychon) - Sunday, 04 November 2012, 20:37 GMT
Hm, that patch (if restricted to ScreenChange notifies) causes restart loops. Something is fishy here.