Thanks for the information, I'll try that!

I just found something new, that's very odd:

* If I connect a second monitor via VGA, then fullscreen mode works on
both my laptop's monitor, as well as on the second monitor without any
problems

* If I connect a second monitor via HDMI, then fullscreen mode works
only on the second monitor

* If I don't connect a second monitor, fullscreen mode does not work
correctly

* Fullscreen terminals from dom0 work correctly, no matter the setup


I'm using the following commands to activate the second monitor for VGA:

xrandr --output DP2 --mode 1680x1050_60.00 --above eDP1


The following for HDMI:

xrandr --output HDMI1 --auto --above eDP1


To deactivate multiple desktops:

xrandr --output HDMI1 --off

xrandr --output DP2 --off


On 09/24/2017 12:24 PM, yuraei...@gmail.com wrote:
> On Sunday, September 24, 2017 at 8:52:32 AM UTC, Michael Strasser wrote:
>> Hi!
>>
>> I've been experiencing some strange issues recently, which I can't
>> really pin down on anything in particular.
>>
>> * I've been getting a frozen screen after random periods of time when
>> I've been using two different monitors. Usually the only solution is to
>> kill my machine.
>>
>> * Sometimes (again when using multiple screens) just mouse input and
>> keyboard input from my laptop stop working, although mouse input from my
>> USB mouse keeps working.
>>
>> * My laptop monitor has input "freezes" all the time (i.e. after about
>> 4-7 keypresses there is a delay of about 1 second until the input is
>> processed), but I do not experience the same on my second monitor and I
>> only experience them in AppVMs, not in dom0.
>>
>> * I can no longer put applications into fullscreen mode on my laptop
>> monitor - no input is recognized and the app "freezes" until I quit
>> fullscreen mode (at which point the input made in fullscreen mode is
>> delivered to/visible in the application) - fullscreen mode works fine on
>> my second monitor.
>>
>> I'm using Qubes 3.2 with i3, but I experienced the same problems with xfce.
>>
>> At first I thought this was a hardware issue, but I just tried booting
>> Ubuntu 16.04 from a USB stick and couldn't reproduce any of the issues.
>> I also just noticed that input "freezing" just happens in AppVMs, not in
>> dom0.
>>
>> I have no idea what is causing these issues, I've been using Qubes OS
>> since April and everything was fine, until about 1 1/2 months ago when
>> these problems started to arise. I also couldn't find any connection to
>> work load or anything performance related that would explain the issues.
>> I also tried changing the kernel version of one of the AppVMs from
>> 4.9.45-21 to 4.9.35-20 and 4.9.35-19 but nothing changed.
>>
>> Does anyone have any tips or has experienced something similar?
>>
>>
>> I'm using Qubes 3.2, kernel version 4.9.45-21 with i3 on a Lenovo X250.
>>
>>
>> Best regards
> To sum it up, I moved to the 4.9.45-21 kernel, and re-build some of my 
> AppVM's from scratch, which in combination, for now at least, solved the 
> speed/lag/freeze issues.
>

-- 
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/5e8ad01c-f6d2-467d-25db-263268e4bd34%40gmx.at.
For more options, visit https://groups.google.com/d/optout.

Reply via email to