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

Groups > linux.debian.user > #182244 > unrolled thread

ARandR problems: Bug or opderator?

Back to article view | Back to linux.debian.user

Contents

  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

#182244 — ARandR problems: Bug or opderator?

I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too 
small and is in the "short and wide" category.
I prefer my 17" diagonal external with a nominal 4:3 aspect ratio.

I am using ARandR Screen Layout Editor 0.1.9.
It reports:
   laptop as        1366 x 768  and normal orientation
   vga monitor as   1280 x 1024 and normal orientation

With those settings it _can_ and *FREQUENTLY* does display what I want.
Generally it chooses not to :/

I have two problems which I presume to be closely intertwined.

After a cold boot, if I open a text file with pluma it fills the 
laptop's short and wide screen.

*HOWEVER* it falls off the right side of the external monitor and 
occupies *ONLY* about 70% of its available height.
If I click-n-hold on the top of that pluma window while dragging down it:
   1. instantaneously shrinks as if "restore window" had been clicked.
   2. then be caused to properly fill the large vga screen by then
      a. continuing to drag it down so its bottom edge passes below
         the bottom of the laptop's screen
      b. clicking the "maximize" button causes it to properly fill the
         vga screen. As would then be expected does not fill the laptop's
         screen and extends below its bottom edge.

The second problem/symptom is designating the vga or laptop as "primary" 
does not change the above.

Some apps if shut down displaying in proper full screen on the vga 
screen will on next opening display that way. These include KeepNote, 
Zim Desktop Wiki, and Tomboy Notes.

For others the above rigamarole has to be followed. These include MATE 
Terminal, Caja, and Penguin Freecell.

When booting the MATE Desktop Environment always appears properly 
fulling the vga screen.

Comments/suggestions?
TIA

[toc] | [next] | [standalone]

#182253

On 2017-06-17, Richard Owlett <rowlett@cloud85.net> wrote:
> I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too 
> small and is in the "short and wide" category.
> I prefer my 17" diagonal external with a nominal 4:3 aspect ratio.
>
> I am using ARandR Screen Layout Editor 0.1.9.
> It reports:
>    laptop as        1366 x 768  and normal orientation
>    vga monitor as   1280 x 1024 and normal orientation
>
> With those settings it _can_ and *FREQUENTLY* does display what I want.
> Generally it chooses not to :/

Frequently does but generally doesn't does not compute. 

[toc] | [prev] | [next] | [standalone]

#182270

On 06/17/2017 03:02 PM, Curt wrote:
> On 2017-06-17, Richard Owlett <rowlett@cloud85.net> wrote:
>> I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too
>> small and is in the "short and wide" category.
>> I prefer my 17" diagonal external with a nominal 4:3 aspect ratio.
>>
>> I am using ARandR Screen Layout Editor 0.1.9.
>> It reports:
>>    laptop as        1366 x 768  and normal orientation
>>    vga monitor as   1280 x 1024 and normal orientation
>>
>> With those settings it _can_ and *FREQUENTLY* does display what
>> I want.
>> Generally it chooses not to :/
>
> Frequently does but generally doesn't does not compute.
>

I'll stand by my summary statement as being literally true.

I'll rephrase it.

With those settings it _can_ display what I want.
[see procedure you snipped]
It FREQUENTLY it does display what I want.
[I had listed some.]
Generally it chooses not to :/
[More than 50% of the time it does not.]

This morning started off "worse" than usual.
However I've a gut feeling that I've wandered into at least a partial 
explanation. I suspect some variable is "path dependent" rather than 
"state dependent". I'll have to work out a test procedure to verity.

[toc] | [prev] | [next] | [standalone]

#182409 — One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 06/18/2017 05:45 AM, Richard Owlett wrote:
> On 06/17/2017 03:02 PM, Curt wrote:
>> On 2017-06-17, Richard Owlett <rowlett@cloud85.net> wrote:
>>> I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too
>>> small and is in the "short and wide" category.
>>> I prefer my 17" diagonal external with a nominal 4:3 aspect ratio.
>>>
>>> I am using ARandR Screen Layout Editor 0.1.9.
>>> It reports:
>>>    laptop as        1366 x 768  and normal orientation
>>>    vga monitor as   1280 x 1024 and normal orientation
>>>
>>> With those settings it _can_ and *FREQUENTLY* does display what
>>> I want.
>>> Generally it chooses not to :/
>>
>> Frequently does but generally doesn't does not compute.
>>
>
> I'll stand by my summary statement as being literally true.
>
> I'll rephrase it.
>
> With those settings it _can_ display what I want.
> [see procedure you snipped]
> It FREQUENTLY it does display what I want.
> [I had listed some.]
> Generally it chooses not to :/
> [More than 50% of the time it does not.]
>
> This morning started off "worse" than usual.
> However I've a gut feeling that I've wandered into at least a partial
> explanation. I suspect some variable is "path dependent" rather than
> "state dependent". I'll have to work out a test procedure to verity.
>

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?

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.

[toc] | [prev] | [next] | [standalone]

#182435 — Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 20/06/17 13:14, Richard Owlett wrote:
> I had understood ARandR would use it automatically. It evidently doesn't.

This is my experience too, including some of the randomness, after 
reboots the DE is setting things, I find Gnome really weak in this area.

The window oddness you describe reminds me of when displays are not in 
the natural order from the hardware, so your at a disadvantage if the 
primary display is not leftmost in many cases.

IMO use arandr-indicator, or put a script onto a global shortcut, it is 
somewhat fiddly but you can use xdotool for a few fix-ups in the screen 
layouts if you want a particular window moving to somewhere and it 
doesn't consistently do it itself, but do consider grepping xrandr 
output to not move things unless the extra display is actually 
connected. pacmd for audio can be nice here too.

AFAIK, but its been a few years, there's no nice method to spawn a 
script on monitor connections, but something like a mouse or usb hub can 
(again checking for connected displays first)

Hope that helps

JP

[toc] | [prev] | [next] | [standalone]

#182440 — Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 06/20/2017 02:06 PM, JPlews wrote:
> On 20/06/17 13:14, Richard Owlett wrote:
>> I had understood ARandR would use it automatically. It evidently doesn't.
>
> This is my experience too, including some of the randomness, after
> reboots the DE is setting things, I find Gnome really weak in this area.
>
> The window oddness you describe reminds me of when displays are not in
> the natural order from the hardware, so your at a disadvantage if the
> primary display is not leftmost in many cases.
>
> IMO use arandr-indicator, or put a script onto a global shortcut, it is
> somewhat fiddly but you can use xdotool for a few fix-ups in the screen
> layouts if you want a particular window moving to somewhere and it
> doesn't consistently do it itself, but do consider grepping xrandr
> output to not move things unless the extra display is actually
> connected. pacmd for audio can be nice here too.
>
> AFAIK, but its been a few years, there's no nice method to spawn a
> script on monitor connections, but something like a mouse or usb hub can
> (again checking for connected displays first)
>
> Hope that helps
>
> JP


To clarify:
My OS is Stretch
My DE is MATE
Although I'm using a laptop, it is my primary machine.
Therefore the VGA monitor is *ALWAYS* connected.

[toc] | [prev] | [next] | [standalone]

#182442 — Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 20/06/17 21:21, Richard Owlett wrote:
> On 06/20/2017 02:06 PM, JPlews wrote:
>> On 20/06/17 13:14, Richard Owlett wrote:
>>> I had understood ARandR would use it automatically. It evidently 
>>> doesn't.
>>
>> This is my experience too, including some of the randomness, after
>> reboots the DE is setting things, I find Gnome really weak in this area.
>>
>> The window oddness you describe reminds me of when displays are not in
>> the natural order from the hardware, so your at a disadvantage if the
>> primary display is not leftmost in many cases.
>>
>> IMO use arandr-indicator, or put a script onto a global shortcut, it is
>> somewhat fiddly but you can use xdotool for a few fix-ups in the screen
>> layouts if you want a particular window moving to somewhere and it
>> doesn't consistently do it itself, but do consider grepping xrandr
>> output to not move things unless the extra display is actually
>> connected. pacmd for audio can be nice here too.
>>
>> AFAIK, but its been a few years, there's no nice method to spawn a
>> script on monitor connections, but something like a mouse or usb hub can
>> (again checking for connected displays first)
>>
>> Hope that helps
>>
>> JP
> 
> 
> To clarify:
> My OS is Stretch
> My DE is MATE
> Although I'm using a laptop, it is my primary machine.
> Therefore the VGA monitor is *ALWAYS* connected.
> 
> 

Even if physically connected there could be a race somewhere that's 
leading to something starting before the hardware is ready or the 
monitor is fully woken.

Currently I'm using Antergos with Gnome and LightDM, it only activates 
one monitor to log in, I don't know how Debian does it (that system only 
have 1 display), but Ubuntu certainly activated all displays at this stage.

These options in LightDM seem interesting for this:

# display-setup-script = Script to run when starting a greeter session 
(runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as 
root)
# session-setup-script = Script to run when starting a user session 
(runs as root)

But then there is suspend to consider, which is part of the reason to 
suggest a manual fixup.


In terms of passive fixes your laptop I see has a DisplayPort, maybe 
that's worth a try with an adapter, the one I got for 5 quid seems 
perfectly fine.

[toc] | [prev] | [next] | [standalone]

#182436 — Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

> 
> 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?
> 
> 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.

perhaps you need to create xorg.conf (at least this is what I did) and set
up there the outputs in the order you want them.
Another perhaps better option is to get udev or whatever assigns the outputs
of the graphic card to do it constantly.

The DE most likely takes what it gets. Some DEs can talk to xrandr so you
can store and restore the settings, but I don't know arandr.

regards

[toc] | [prev] | [next] | [standalone]

#182441 — Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 06/20/2017 02:41 PM, deloptes wrote:
>
>>
>> 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?
>>
>> 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.
>
> perhaps you need to create xorg.conf (at least this is what I did)
> and set up there the outputs in the order you want them.
> Another perhaps better option is to get udev or whatever assigns the
> outputs of the graphic card to do it constantly.
>
> The DE most likely takes what it gets. Some DEs can talk to xrandr
> so you can store and restore the settings, but I don't know arandr.
>
> regards
>


To clarify:
My OS is Stretch
My DE is MATE
Although I'm using a laptop, it is my primary machine.
Therefore the VGA monitor is *ALWAYS* connected.

I looked at the xorg.conf and came out none the wiser.

[toc] | [prev] | [next] | [standalone]

#182445 — Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

Richard Owlett composed on 2017-06-20 07:14 (UTC-0500):

> How can I force it to always come up with the VGA monitor as primary?
.
If you are interested, might like to try to create an xorg.conf that will do
what you want. In order to make such attempt I will need:

1-to see an unadulterated[1] Xorg.0.log written while X is behaving as you wish

2-VGA display connectors actually available (or VGA display make and model)

3-cable type actually used for the VGA display

4a-to know the physical relationship between the displays, whether over/under or
left/right and which goes where

and/or

4b-screenshot showing desired behavior, preferably with a maximized web browser
window open in each display, with each containing:
http://fm.no-ip.com/Auth/dpi-screen-window.html
loaded or reloaded *after* maximizing

Whether success is even possible, given the T510's apparent hybrid gfx
specifications I found on C/Net, I'm not sure. Solving your problem may require
a driver switch, among Bumblebee, Optimus, Prime, Modesetting or Intel, and
possibly using a proprietary driver's own configuration utility.

[1] if you want, you can omit lines in the bottom that you can tell only apply
to input devices
-- 
"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/

[toc] | [prev] | [next] | [standalone]

#182447 — Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 06/20/2017 05:14 AM, Richard Owlett wrote:
> On 06/18/2017 05:45 AM, Richard Owlett wrote:
>> On 06/17/2017 03:02 PM, Curt wrote:
>>> On 2017-06-17, Richard Owlett <rowlett@cloud85.net> wrote:
>>>> I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too
>>>> small and is in the "short and wide" category.
>>>> I prefer my 17" diagonal external with a nominal 4:3 aspect ratio.
>>>>
>>>> I am using ARandR Screen Layout Editor 0.1.9.
>>>> It reports:
>>>>    laptop as        1366 x 768  and normal orientation
>>>>    vga monitor as   1280 x 1024 and normal orientation
>>>>
>>>> With those settings it _can_ and *FREQUENTLY* does display what
>>>> I want.
>>>> Generally it chooses not to :/
>>>
>>> Frequently does but generally doesn't does not compute.
>>>
>>
>> I'll stand by my summary statement as being literally true.
>>
>> I'll rephrase it.
>>
>> With those settings it _can_ display what I want.
>> [see procedure you snipped]
>> It FREQUENTLY it does display what I want.
>> [I had listed some.]
>> Generally it chooses not to :/
>> [More than 50% of the time it does not.]
>>
>> This morning started off "worse" than usual.
>> However I've a gut feeling that I've wandered into at least a partial
>> explanation. I suspect some variable is "path dependent" rather than
>> "state dependent". I'll have to work out a test procedure to verity.
>>
> 
> 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?
> 
> 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.

I would delete what you saved and then let arandr save the settings and 
see if that works.
-- 
Jimmy Johnson

Debian Sid/Testing - KDE Plasma 5.8.7 - Linux 4.9 - EXT4 at sda15
Registered Linux User #380263

[toc] | [prev] | [next] | [standalone]

#182471 — Re: One problem identified - was [Re: ARandR problems: Bug or opderator?]

On 06/20/2017 07:20 PM, Jimmy Johnson wrote:
> On 06/20/2017 05:14 AM, Richard Owlett wrote:
>> On 06/18/2017 05:45 AM, Richard Owlett wrote:
>>> On 06/17/2017 03:02 PM, Curt wrote:
>>>> On 2017-06-17, Richard Owlett <rowlett@cloud85.net> wrote:
>>>>> I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too
>>>>> small and is in the "short and wide" category.
>>>>> I prefer my 17" diagonal external with a nominal 4:3 aspect ratio.
>>>>>
>>>>> I am using ARandR Screen Layout Editor 0.1.9.
>>>>> It reports:
>>>>>    laptop as        1366 x 768  and normal orientation
>>>>>    vga monitor as   1280 x 1024 and normal orientation
>>>>>
>>>>> With those settings it _can_ and *FREQUENTLY* does display what
>>>>> I want.
>>>>> Generally it chooses not to :/
>>>>
>>>> Frequently does but generally doesn't does not compute.
>>>>
>>>
>>> I'll stand by my summary statement as being literally true.
>>>
>>> I'll rephrase it.
>>>
>>> With those settings it _can_ display what I want.
>>> [see procedure you snipped]
>>> It FREQUENTLY it does display what I want.
>>> [I had listed some.]
>>> Generally it chooses not to :/
>>> [More than 50% of the time it does not.]
>>>
>>> This morning started off "worse" than usual.
>>> However I've a gut feeling that I've wandered into at least a partial
>>> explanation. I suspect some variable is "path dependent" rather than
>>> "state dependent". I'll have to work out a test procedure to verity.
>>>
>>
>> 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?
>>
>> 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.
>
> I would delete what you saved and then let arandr save the settings
> and see if that works.

It didn't :{

All of my comments in this thread have been while working in my user 
account.

Things are worse in the root account. I don't seem to be able to 
permanently change not only which display is active but *ALSO* unable to 
save the resolution settings for the displays.

I now have:

As setup for user richard
   laptop as        1366 x 768  and normal orientation
   vga monitor as   1280 x 1024 and normal orientation

As set up for user root
   laptop as        1024 x 768  and normal orientation
   vga monitor as   1024 x 768  and normal orientation

[toc] | [prev] | [next] | [standalone]

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

On 06/20/2017 07:14 AM, Richard Owlett wrote:
> On 06/18/2017 05:45 AM, Richard Owlett wrote:
>> On 06/17/2017 03:02 PM, Curt wrote:
>>> On 2017-06-17, Richard Owlett <rowlett@cloud85.net> wrote:
>>>> I'm using Debian Testing on a Lenovo T510 Thinkpad whose screen is too
>>>> small and is in the "short and wide" category.
>>>> I prefer my 17" diagonal external with a nominal 4:3 aspect ratio.
>>>>
>>>> I am using ARandR Screen Layout Editor 0.1.9.
>>>> It reports:
>>>>    laptop as        1366 x 768  and normal orientation
>>>>    vga monitor as   1280 x 1024 and normal orientation
[snip]
>
> 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?
>
> 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?


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>

[toc] | [prev] | [next] | [standalone]

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

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/

[toc] | [prev] | [next] | [standalone]

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

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 ;}
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.

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.

>[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?
> 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.

There is an apparently garbled init script
q.v. <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865535>


>
> 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>

[toc] | [prev] | [next] | [standalone]

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

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.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web