Issue fixed. In my fedora28 template I
changed /etc/X11/xorg-qubes.conf.template to have a hardcoded amount of RAM
for "Videocard0". So from:
VideoRam %MEM%
to
VideoRam 49576
49576 is just the amount of RAM which was calculated by the
`qubes-set-monitor-layout` script for a VM started after my external
monitors were plugged in. VMs started before extra monitors were plugged
in had about half that amount.
There appears to be a bug on github which may very well be the same thing,
and I'll try to circle back to that github issue and report what worked for
me when I get a moment tomorrow.
- Ralph
On Mon, Sep 10, 2018 at 2:01 PM, qubes-users-list - <
qubes-users-l...@ralphdouglass.com> wrote:
> I've been running into an issue where mouse events inside of a qube (i.e.
> clicking around inside of a window) aren't being recognized if I started a
> qube before plugging in additional monitors and the area I'm trying to
> click in is off-screen from the standpoint of the monitor layout I had when
> the qube was started.
>
> Moving windows 'off-screen' works just fine, not surprisingly, since I
> assume that's Dom0's job and it's not confused about my screens.
>
> xrandr in the problematic qube and dom0 match in terms of screen sizes,
> but it looks like all screens in the problematic qube are positioned at 0x0.
>
> Here's the output from xrandr in a problematic qube started before I
> plugged in more monitors, and a non-problematic qube I started afterwards
> plugging in more monitors. I left off the disconnected devices
> (DUMMY{3..15}).
>
> Started before I plugged in extra monitors:
> ----
> Screen 0: minimum 64 x 64, current 2560 x 1440, maximum 32767 x 32767
> DUMMY0 connected primary 2560x1440+0+0 325mm x 182mm
> QB2560x1440 34.61*+
> DUMMY1 connected 1920x1200+0+0 0mm x 0mm
> QB2560x1440 34.61 +
> QB1920x1200 59.88*
> DUMMY2 connected 1920x1200+0+0 0mm x 0mm
> QB2560x1440 34.61 +
> QB1920x1200 59.88*
> QB1200x1920 59.95
>
> Started after I plugged in extra monitors:
> ----
> Screen 0: minimum 64 x 64, current 3160 x 3360, maximum 32767 x 32767
> DUMMY0 connected primary 2560x1440+600+1920 0mm x 0mm
> QB3160x3360 14.85 +
> QB2560x1440 59.96*
> DUMMY1 connected 1920x1200+1200+300 0mm x 0mm
> QB3160x3360 14.85 +
> QB1920x1200 59.88*
> DUMMY2 connected 1200x1920+0+0 0mm x 0mm
> QB3160x3360 14.85 +
> QB1200x1920 59.95*
>
> I can move the problematic DUMMY0 screen around, but not all the way to
> 600x1920 as I want to match the actual layout of my monitors.
> Specifically, I can move DUMMY0 to the position 599x383 but no further on
> either the x or y dimension. If I do more, I get the following error:
>
> $ xrandr --output DUMMY0 --auto --pos 600x383
> X Error of failed request: BadMatch (invalid parameter attributes)
> Major opcode of failed request: 139 (RANDR)
> Minor opcode of failed request: 7 (RRSetScreenSize)
> Serial number of failed request: 100
> Current serial number in output stream: 101
>
> (Same is true for 599x384).
>
> 600x384 is obviously not a random number, but I haven't figured out where
> to take this further.
>
> Any thoughts on what to try next?
>
> Thanks in advance,
>
> Ralph
>
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/CAMVV%3Dfz8DgX5eVkguO-rimMQCwyf4fQDBeNW%3DbMfQF6wr3W4Lw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
