On Sat 24 Jun 2017 at 06:42:34 (-0500), Richard Owlett wrote: > On 06/23/2017 02:42 PM, Felix Miata wrote: > >Richard Owlett composed on 2017-06-23 06:25 (UTC-0500): > >. > >>>I've identified one problem source. > >>>At least sometimes after a power off shut down it comes up with the > >>>laptop display selected as primary. > >>>How can I force it to always come up with the VGA monitor as > >>>primary? > > > >Maybe https://www.kernel.org/doc/Documentation/fb/modedb.txt is > >what you need? > > Quite possibly. But perhaps not in the expected way ;}
Clever. That leaves us not knowing what you thought Felix might expect, nor what your own thoughts were, nor knowing whether you lent credence to those thoughts. > It led me to <https://www.kernel.org/doc/Documentation/fb/00-INDEX> > which has overview articles which should fill in gaps in my > background. > > My interests have an "end user" orientation. I took introductory > programming courses as an E.E. student in early 60's, but even > working for Digital Equipment in the 70's computers were a tool not > a goal. I've no idea what that was about. > My goal for this and related threads is the improvement of "ARandR > Screen Layout Editor". It sets out to meet my needs in what I find > to be an appropriate manner. I can contribute to its improvement by > gaining enough background to write useful coherent bug reports. Then you probably need to start by understanding exactly what it's intended to do so that you can measure how it meets those expectations. > >[snip] > >>>I created /home/richard/.screenlayout/VGA-as-master.sh with > >>>preferred settings back when I was experimenting. I had > >>>understood ARandR would use it automatically. It evidently doesn't. > >> > >>If that script is manually run after logging in as a particular user > >>both displays display as desired. > >> > >>My remaining problem is not knowing how to run the script > >>automatically > >>when a particular user logs in. [ARandR is designed as a 'per-user > >>function'] > >>How? Paste it into, or call it from, an appropriate startup script. As a long-time user of MATE, you're probably better qualified than I am to choose. As an X/fvwm user, I'd be using a host-specific sub-script of ~/.xsession (though one could also use $HOSTNAME in the ~/.screenlayout filename) to set things up after I call startx. > >Must it only be for one specific user? > > As I said above "[ARandR is designed as a 'per-user function']". > The directory </home/richard/.screenlayout/> is part of ARandR. > > >If so, then it needs to be called by any > >of several usual means for user-specific startup scripts. > >It won't be run simply because it exists. Agreed. There could be any number of different configurations within ~/.screenlayout/. > There is an apparently garbled init script > q.v. <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865535> I don't see anything garbled there. On my system, it reads: #!/bin/sh %(xrandr)s which seems quite sensible. It looks like a template determining what gets written into a layout file. The first line looks like a literal for writing the shebang; the second looks like a template for writing a string, the xrandr command that produces what you see on the screen(s) at the time you invoke SaveAs. > >If OTOH global application will suffice, put it in /etc/X11/Xsession.d, which > >will apply it as a consequence of using any GUI login greeter. If you wish it > >applied to include the greeter, you can convert its content into an > >xorg.conf, > >or maybe merge it into /etc/X11/ elsewhere somehow (which I've never managed > >to do). > >. > >>The content of the script file is: ↑↑↑↑↑↑ Script Properties > >>>#!/bin/sh There's line one from the properties template. > >>>xrandr --output VGA-1 --primary --mode 1280x1024 --pos 0x0 --rotate normal > >>>--output LVDS-1 --mode 1366x768 --pos 0x0 --rotate normal --output HDMI-3 > >>>--off --output HDMI-2 --off --output HDMI-1 --off --output DP-3 --off > >>>--output DP-2 --off --output DP-1 --off There's line two. > >>A bug report has been filed > >><https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865535> That report's title looks as if you expect arandr to have some sort of persistent effect which I don't see documented anywhere. All arandr does is to write horribly long xrandr command lines for you. (If only there were such a tool to write ffmpeg commands!) Cheers, David.
