[plug] Monitor resolution changes on opening a console terminal

[Kevin Shackleton]

My screen-resize problem was an "xrandr -s 1680x1050" in ~/.bashrc.
Actually where you would expect the command to be.

What threw me was that "grep 1680 ~/*" does not find it, so I didn't look
for it there.  "grep 1680 ~/.* does find it.

Thanks for the assistance.

Cheers,

Kevin.

On 8 September 2017 at 16:17, David Godfrey <info at sbts.com.au> wrote:

> Hi Kevin,
>
> It's also worth looking in ~/.*/.screen/*
>
> There is some software around (arandr comes to mind) that by default
> stores monitor/display setup scripts (using xrandr or similar) in that dir.
> It's then possible that your bashrc or .profile (check those in ~ as well
> as /etc and on occasion somewhere in /lib or /usr/lib) may actually call
> one of those screen scripts.
>
> btw: the ~/.*/ is listed above as depending on distro and version, it may
> be ~/.screen or ~/.local/config/screen or some other variation
> Oh, one other thing, what Video device is in use, and which drivers. Some
> of the drivers/cards may have specific tools for configuring them, eg
> official nvida drivers and tools.
>
> It may also be worth working out if your video driver and associated
> modules are being passed any extra arguments (including from the grub
> commandline)
>
> Beyond these and the other suggestions offered, it's going to be fun to
> track down :-/
>
>
> Regards
> David Godfrey
> SB Tech Services
> mb: +61 437 286 200 <+61437286200>
>
> chat: with *dcg_mx* at
> #sbts:matrix.org <http://riot.im/app/#/room/%23sbts:matrix.org> (Computer)
> #sbts:matrix.org <http://matrix.to/#/%23sbts:matrix.org> (mobile Device)
>
>
> On 08/09/17 14:27, Kevin Shackleton wrote:
>
> Thanks Nick, I'll try these suggestions out tonight.
>
> Cheers,
>
> Kevin.
>
> On 8 September 2017 at 14:00, Nick Bannon <nick at ucc.gu.uwa.edu.au> wrote:
>
>> On Thu, Sep 07, 2017 at 04:50:08PM +0800, Kevin Shackleton wrote:
>> [...]
>> > However, when I open a terminal, the screen switches to 1680 * 1050
>> > resolution, as though that's a setting in .bashrc or similar.
>>
>> I don't know how it would have gotten in there... but if something
>> indirectly runs xrandr(1) as part of your shell startup, that could do it?
>>
>> The startup files that bash could use are in:
>> man bash | less +/^INVOCATION
>>
>> You could confirm if /usr/bin/xrandr gets called with execsnoop(8)
>> (Debian/Ubuntu package perf-tools-unstable ; or as found from:
>> https://github.com/brendangregg/perf-tools
>> or:
>> http://www.brendangregg.com/ebpf.html
>> https://github.com/iovisor/bcc
>> )
>>
>> It's possible that the RandR code is being called from elsewhere,
>> e.g. via DBUS calls, which could be spotted with dbus-monitor ?
>>
>> Nick.
>>
>> --
>>    Nick Bannon   | "I made this letter longer than usual because
>> nick-sig at rcpt.to | I lack the time to make it shorter." - Pascal
>> _______________________________________________
>> PLUG discussion list: plug at plug.org.au
>> http://lists.plug.org.au/mailman/listinfo/plug
>> Committee e-mail: committee at plug.org.au
>> PLUG Membership: http://www.plug.org.au/membership
>>
>
>
>
> _______________________________________________
> PLUG discussion list: plug at plug.org.auhttp://lists.plug.org.au/mailman/listinfo/plug
> Committee e-mail: committee at plug.org.au
> PLUG Membership: http://www.plug.org.au/membership
>
>
>
> _______________________________________________
> PLUG discussion list: plug at plug.org.au
> http://lists.plug.org.au/mailman/listinfo/plug
> Committee e-mail: committee at plug.org.au
> PLUG Membership: http://www.plug.org.au/membership
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plug.org.au/pipermail/plug/attachments/20170908/a29e1c98/attachment.html>