<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Kevin,</p>
<p>It's also worth looking in ~/.*/.screen/*</p>
<p>There is some software around (arandr comes to mind) that by
default stores monitor/display setup scripts (using xrandr or
similar) in that dir.<br>
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.</p>
<p>btw: the ~/.*/ is listed above as depending on distro and
version, it may be ~/.screen or ~/.local/config/screen or some
other variation</p>
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.
<p>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)<br>
</p>
<p>Beyond these and the other suggestions offered, it's going to be
fun to track down :-/</p>
<p><br>
</p>
<div class="moz-signature">
<style>
div.sig {
border: 1px solid black;
height: auto;
float: left;
padding: 1em;
padding-top: 0.5em;
padding-bottom: 0.5em;
}
a.sig1 {
padding-bottom:1em;
margin-bottom:1em;
}
span.left {
width: 4em;
float: left;
}
span.pulseit {
-webkit-animation: mymove 1s infinite; /* Chrome, Safari, Opera */
animation: pulse 2s infinite;
}
@keyframes pulse { 50% {font-size: 0.9em;} }
</style> Regards<br>
David Godfrey<br>
SB Tech Services<br>
<a class="sig1" href="tel:+61437286200">mb: +61 437 286 200</a><br>
<br>
<div class="sig"> <span class="left"> <span class="pulseit">chat:</span>
</span> <span style="float: right;"> with <em>dcg_mx</em> at<br>
<a href="http://riot.im/app/#/room/#sbts:matrix.org">#sbts:matrix.org</a>
(Computer)<br>
<a href="http://matrix.to/#/#sbts:matrix.org">#sbts:matrix.org</a>
(mobile Device) </span> </div>
<br style="clear:both">
<br>
</div>
<div class="moz-cite-prefix">On 08/09/17 14:27, Kevin Shackleton
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADr1vmSvX2_FUF1evAR2dhdsnxX=-6+F_it29-ARX9ueJnQx0w@mail.gmail.com">
<div dir="ltr">
<div>
<div>Thanks Nick, I'll try these suggestions out tonight.<br>
<br>
</div>
Cheers,<br>
<br>
</div>
Kevin.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 8 September 2017 at 14:00, Nick
Bannon <span dir="ltr"><<a
href="mailto:nick@ucc.gu.uwa.edu.au" target="_blank"
moz-do-not-send="true">nick@ucc.gu.uwa.edu.au</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu,
Sep 07, 2017 at 04:50:08PM +0800, Kevin Shackleton wrote:<br>
[...]<br>
<span class="">> However, when I open a terminal, the
screen switches to 1680 * 1050<br>
> resolution, as though that's a setting in .bashrc or
similar.<br>
<br>
</span>I don't know how it would have gotten in there... but
if something<br>
indirectly runs xrandr(1) as part of your shell startup,
that could do it?<br>
<br>
The startup files that bash could use are in:<br>
man bash | less +/^INVOCATION<br>
<br>
You could confirm if /usr/bin/xrandr gets called with
execsnoop(8)<br>
(Debian/Ubuntu package perf-tools-unstable ; or as found
from:<br>
<a href="https://github.com/brendangregg/perf-tools"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/<wbr>brendangregg/perf-tools</a><br>
or:<br>
<a href="http://www.brendangregg.com/ebpf.html"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://www.brendangregg.com/<wbr>ebpf.html</a><br>
<a href="https://github.com/iovisor/bcc" rel="noreferrer"
target="_blank" moz-do-not-send="true">https://github.com/iovisor/bcc</a><br>
)<br>
<br>
It's possible that the RandR code is being called from
elsewhere,<br>
e.g. via DBUS calls, which could be spotted with
dbus-monitor ?<br>
<span class="HOEnZb"><font color="#888888"><br>
Nick.<br>
<br>
--<br>
Nick Bannon | "I made this letter longer than usual
because<br>
<a href="mailto:nick-sig@rcpt.to" moz-do-not-send="true">nick-sig@rcpt.to</a>
| I lack the time to make it shorter." - Pascal<br>
</font></span>
<div class="HOEnZb">
<div class="h5">______________________________<wbr>_________________<br>
PLUG discussion list: <a href="mailto:plug@plug.org.au"
moz-do-not-send="true">plug@plug.org.au</a><br>
<a href="http://lists.plug.org.au/mailman/listinfo/plug"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://lists.plug.org.au/<wbr>mailman/listinfo/plug</a><br>
Committee e-mail: <a
href="mailto:committee@plug.org.au"
moz-do-not-send="true">committee@plug.org.au</a><br>
PLUG Membership: <a
href="http://www.plug.org.au/membership"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://www.plug.org.au/<wbr>membership</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
PLUG discussion list: <a class="moz-txt-link-abbreviated" href="mailto:plug@plug.org.au">plug@plug.org.au</a>
<a class="moz-txt-link-freetext" href="http://lists.plug.org.au/mailman/listinfo/plug">http://lists.plug.org.au/mailman/listinfo/plug</a>
Committee e-mail: <a class="moz-txt-link-abbreviated" href="mailto:committee@plug.org.au">committee@plug.org.au</a>
PLUG Membership: <a class="moz-txt-link-freetext" href="http://www.plug.org.au/membership">http://www.plug.org.au/membership</a></pre>
</blockquote>
<br>
</body>
</html>