<div dir="ltr"><div><div><div><div>My screen-resize problem was an "xrandr -s 1680x1050" in ~/.bashrc.  Actually where you would expect the command to be.<br><br></div>What threw me was that "grep 1680 ~/*" does not find it, so I didn't look for it there.  "grep 1680 ~/.* does find it.<br><br></div>Thanks for the assistance.<br><br></div>Cheers,<br><br></div>Kevin.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 8 September 2017 at 16:17, David Godfrey <span dir="ltr"><<a href="mailto:info@sbts.com.au" target="_blank">info@sbts.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div 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="m_1693488316789387097moz-signature">
       Regards<br>
      David Godfrey<br>
      SB Tech Services<br>
      <a class="m_1693488316789387097sig1" href="tel:+61437286200" target="_blank">mb: +61 437 286 200</a><br>
      <br>
      <div class="m_1693488316789387097sig"> <span class="m_1693488316789387097left"> <span class="m_1693488316789387097pulseit">chat:</span>
        </span> <span style="float:right"> with <em>dcg_mx</em> at<br>
          <a href="http://riot.im/app/#/room/%23sbts:matrix.org" target="_blank">#sbts:matrix.org</a>
          (Computer)<br>
          <a href="http://matrix.to/#/%23sbts:matrix.org" target="_blank">#sbts:matrix.org</a>
          (mobile Device) </span> </div>
      <br style="clear:both">
      <br>
    </div><div><div class="h5">
    <div class="m_1693488316789387097moz-cite-prefix">On 08/09/17 14:27, Kevin Shackleton
      wrote:<br>
    </div>
    <blockquote type="cite">
      <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">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>> 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">https://github.com/brendangreg<wbr>g/perf-tools</a><br>
            or:<br>
            <a href="http://www.brendangregg.com/ebpf.html" rel="noreferrer" target="_blank">http://www.brendangregg.com/eb<wbr>pf.html</a><br>
            <a href="https://github.com/iovisor/bcc" rel="noreferrer" target="_blank">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="m_1693488316789387097HOEnZb"><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" target="_blank">nick-sig@rcpt.to</a>
                | I lack the time to make it shorter." - Pascal<br>
              </font></span>
            <div class="m_1693488316789387097HOEnZb">
              <div class="m_1693488316789387097h5">______________________________<wbr>_________________<br>
                PLUG discussion list: <a href="mailto:plug@plug.org.au" target="_blank">plug@plug.org.au</a><br>
                <a href="http://lists.plug.org.au/mailman/listinfo/plug" rel="noreferrer" target="_blank">http://lists.plug.org.au/mailm<wbr>an/listinfo/plug</a><br>
                Committee e-mail: <a href="mailto:committee@plug.org.au" target="_blank">committee@plug.org.au</a><br>
                PLUG Membership: <a href="http://www.plug.org.au/membership" rel="noreferrer" target="_blank">http://www.plug.org.au/members<wbr>hip</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="m_1693488316789387097mimeAttachmentHeader"></fieldset>
      <br>
      <pre>______________________________<wbr>_________________
PLUG discussion list: <a class="m_1693488316789387097moz-txt-link-abbreviated" href="mailto:plug@plug.org.au" target="_blank">plug@plug.org.au</a>
<a class="m_1693488316789387097moz-txt-link-freetext" href="http://lists.plug.org.au/mailman/listinfo/plug" target="_blank">http://lists.plug.org.au/<wbr>mailman/listinfo/plug</a>
Committee e-mail: <a class="m_1693488316789387097moz-txt-link-abbreviated" href="mailto:committee@plug.org.au" target="_blank">committee@plug.org.au</a>
PLUG Membership: <a class="m_1693488316789387097moz-txt-link-freetext" href="http://www.plug.org.au/membership" target="_blank">http://www.plug.org.au/<wbr>membership</a></pre>
    </blockquote>
    <br>
  </div></div></div>

<br>______________________________<wbr>_________________<br>
PLUG discussion list: <a href="mailto:plug@plug.org.au">plug@plug.org.au</a><br>
<a href="http://lists.plug.org.au/mailman/listinfo/plug" rel="noreferrer" target="_blank">http://lists.plug.org.au/<wbr>mailman/listinfo/plug</a><br>
Committee e-mail: <a href="mailto:committee@plug.org.au">committee@plug.org.au</a><br>
PLUG Membership: <a href="http://www.plug.org.au/membership" rel="noreferrer" target="_blank">http://www.plug.org.au/<wbr>membership</a><br></blockquote></div><br></div>