On Tue, Jan 27, 2015 at 11:13:09AM GMT, Raf Czlonka wrote: > I had a similar issue, with the exact error message, while using > 'xrandr' to enable dual-screen mode. > > For some reason, it seems, like 'X/randr' "loses" the information > about its *primary* screen. I hope I remember it correctly - this > happened a while ago on another machine - will try to replicate it on > another laptop this evening (GMT). > > The odd behaviour, which I just described, could have been observed > "in more detail" by one of the '*randr' GUI tools (not sure whether it > was arandr), i.e. it would show that there's no primary output and you > couldn't arrange your outputs properly.
On this machine, everything seems to be working as expected - typical! I can't test it on the laptop I had the issue originally as it is in pieces - I'll try to re-assemble it back this weekend if I can find some spare time and will test it then. Just for the record, the GUI tool was indeed 'arandr' and, when ran on the other machine after enabling dual-screen with 'xrandr', under "Outputs" -> "LVDS1", "Active" was not selected - after doing so, all worked as intended. Regards, Raf
