Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #182557

Re: Workaround {Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]}

From Felix Miata <mrmazda@earthlink.net>
Newsgroups linux.debian.user
Subject Re: Workaround {Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]}
Date 2017-06-23 21:50 +0200
Message-ID <tVCKC-6lJ-5@gated-at.bofh.it> (permalink)
References <tTlXA-7Hx-5@gated-at.bofh.it> <tTscF-3EW-1@gated-at.bofh.it> <tTFWj-3Ym-47@gated-at.bofh.it> <tUqiu-8w4-21@gated-at.bofh.it> <tVuWJ-1vQ-3@gated-at.bofh.it>
Organization less than infinite

Show all headers | View raw


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?

"You can additionally specify which output the options matches to.
To force the VGA output to be enabled and drive a specific mode say:
    video=VGA-1:1280x1024@60me

"Specifying the option multiple times for different ports is possible, e.g.:
    video=LVDS-1:d video=HDMI-1:D"
.
>> 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?. 										
Must it only be for one specific user? 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.

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:
>> #!/bin/sh
>> 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
.
> A bug report has been filed
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865535>
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

ARandR problems: Bug or opderator? Richard Owlett <rowlett@cloud85.net> - 2017-06-17 15:30 +0200
  Re: ARandR problems: Bug or opderator? Curt <curty@free.fr> - 2017-06-17 22:10 +0200
    Re: ARandR problems: Bug or opderator? Richard Owlett <rowlett@cloud85.net> - 2017-06-18 12:50 +0200
      One problem identified - was [Re: ARandR problems: Bug or opderator?] Richard Owlett <rowlett@cloud85.net> - 2017-06-20 14:20 +0200
        Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] JPlews <jw@plews.org.uk> - 2017-06-20 21:10 +0200
          Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] Richard Owlett <rowlett@cloud85.net> - 2017-06-20 22:30 +0200
            Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] JPlews <jw@plews.org.uk> - 2017-06-20 23:30 +0200
        Re: One problem identified - was [Re: ARandR problems: Bug or opderator?] deloptes <deloptes@gmail.com> - 2017-06-20 21:50 +0200
          Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] Richard Owlett <rowlett@cloud85.net> - 2017-06-20 22:40 +0200
        Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] Felix Miata <mrmazda@earthlink.net> - 2017-06-21 00:20 +0200
        Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] Jimmy Johnson <field.engineer@gmail.com> - 2017-06-21 02:30 +0200
          Re: One problem identified - was [Re: ARandR problems: Bug or  opderator?] Richard Owlett <rowlett@cloud85.net> - 2017-06-21 15:20 +0200
        Workaround {Re: One problem identified - was [Re: ARandR problems:  Bug or opderator?]} Richard Owlett <rowlett@cloud85.net> - 2017-06-23 13:30 +0200
          Re: Workaround {Re: One problem identified - was [Re: ARandR  problems: Bug or opderator?]} Felix Miata <mrmazda@earthlink.net> - 2017-06-23 21:50 +0200
            Re: Workaround {Re: One problem identified - was [Re: ARandR  problems: Bug or opderator?]} Richard Owlett <rowlett@cloud85.net> - 2017-06-24 13:50 +0200
              Re: Workaround {Re: One problem identified - was [Re: ARandR  problems: Bug or opderator?]} David Wright <deblis@lionunicorn.co.uk> - 2017-06-24 20:10 +0200

csiph-web