On Monday, February 12, 2018 at 9:21:13 AM UTC+1, Laszlo Zrubecz wrote:
> Hash: SHA256
> On 02/11/2018 05:38 PM, Devin T. Theriot-Orr wrote:
> > I've been using Qubes3.2 for about 6 months as my primary machine.
> > Some time recently, perhaps in the last month, I've started to
> > experience a rather deadly usability problem where the mouse will
> > no longer select anything. Everything else works, I can move the
> > mouse, I can change windows using the keyboard, type, etc. But
> > clicking with the mouse does not work. Only solution I've figured
> > out is to reboot the whole machine.
> > 
> > I don't know if there's any solution other than reinstalling, but
> > if anyone has ideas, I'd love to hear it.
> Is this issue can be related to multiple monitor setup changes (for
> example attaching/detaching external monitors) by any chance?
> - -- 
> Zrubi
> N2TJ3BAAm2ERFkyq+EuqLeDnZrh85gctYu70B0+rK+MnAKsOMzvL2Y7H2y/QBwQC
> FW87SqQsYs0lgc9nKzxFpoKsEUtfDxPXbAQJw27GNZyNpxgfQ/bixjUzjCmydkD/
> nNAcUjeTdJnx+uLjGUI6zkPAtdZh1mYgyciCh6avlFg6PevxkVp2kFxT7CW2gDN1
> vrFNFH+QtplMFQB/uwSUR2EwILZCDSkcWvPesRMRrKkcdouJs8mwFqroIavjK+KQ
> G2Xhut2/+hA/F4xDKyYep4WzPRrwMa8WzgqAht2mIXchECp5cnqd1dt745FNSRB+
> jVGLW9uM3ZMhGXTPCdwxEzHdmWCwErfQ2V8mqBsBjZ92vXaydLbeve05ntK6aK1U
> 2hPDIoHriu63jvVLO8PowDApmNALpuZXb9/LcIaFy2TFwxxMqnhhSAIVygWPZ9o4
> J1wBLQFdE8Xh0xrncELRD4o5D5CZFTGKVKmc9Cc9ZcVxfYGSw4CecCzGRVz8NkO1
> PzJo9wrccGxRjErWe1x9xGmLvjplgnIYulQ7N1SH44zU4S59TCOa+9ZuJ5dOUqcX
> u1va8IfAETaDIb41hswfq2bLVjtPV7TvVZts3lcmCbLVJF9urCszx7B8uTuyp3K1
> o1cjcBqqhx+gEMoaERtzy9IrNf2O5mvf9/X81o+deZb3MO/Ud58=
> =Tpo0

I switch/add/remove extra monitors daily, sometimes even multiple of times 
daily, at least for my part, I've never encountered this issue, not even once. 
For the record, I use Qubes 4 as well, since RC-2. 

I do however encounter this issue on Windows 7, both on Qubes 3.2. and Qubes 
4.0, but it's relatively easy to fix by clicking the middle-mouse button, which 
immediately returns the usage of mouse-1 and mouse-2 buttons. Could it be 
something similar, perhaps? In Win7, this only happens to me when I navigate 
the GUI Windows in non-seamless mode. It sounds very, very similar to your 
description too. It's possible it's a similar issue, and if so, maybe it can be 
used to track down the core issue.

Extra questions that may help troubleshot the issue:

- For those experiencing something similar as OP, are you using Qubes 4 or 
Qubes 3.2.?

- How frequent do you experience this issue? Daily? Weekly?

- Is the frequency between when it happens somewhat evenly distributed, or is 
it more random like in the frequency pattern?

- When did it start to happen? Did you update dom0 or templates at the time? 

- Is it only an issue in certain VM's, or is it universal for all windows in 

- If only happening inside certain VM's, then which ones? Are other VM's 
behaving differently?

- Do you sync updates between dom0 and template updates?

- If you use current-testing updates, do you run current-testing in both dom0 
and templates?

- and other possible scenarios like the above, try track it down bit by bit in 
a detective kind of fashion, to be a bit cliché and cite: "When you have 
eliminated the impossible, whatever remains, must be the truth". Essentially, 
limit and narrow down the issue, until there is few or nothing left to pick 
from. You can start with the list above, but try go beyond it.

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 
For more options, visit https://groups.google.com/d/optout.

Reply via email to