New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

external monitor enters screen saving mode even with all power saving settings disabled #2360

Open
adrelanos opened this Issue Oct 3, 2016 · 1 comment

Comments

Projects
None yet
4 participants
@adrelanos
Member

adrelanos commented Oct 3, 2016

Qubes OS version (e.g., R3.1):

R3.2 XFCE

Affected TemplateVMs (e.g., fedora-23, if applicable):

dom0


Expected behavior:

System should not turn off the screen.

Actual behavior:

System turns off screen.

Steps to reproduce the behavior:

  • turn off all xfce power saving settings
  • turn off xscreensaver
  • uninstall xscreensaver
  • connect hdmi screen
  • leave system unattended for 30 or 60 minutes
  • screen will be powered off
  • mice movement or keyboard press will not turn on the screen
  • switching to a virtual console and restarting lightdm helps to reactivate the screen (but it's not a great workaround, since all windows are now inside the same virtual desktop)

General notes:

Also xset did not help.

   xset s off
   xset -dpms

Uninstalled xscrensaver just to exclude it being the cause of this.

Did not happen with KDE previously.

Related issues:

#2287

@JeramyNS

This comment has been minimized.

Show comment
Hide comment
@JeramyNS

JeramyNS Oct 6, 2016

I have this issue also however I also get the following bug, after this issue occurs once.
Template is irrelevant for me as it also occurred while using whonix-ws.

It's a little random when it happens but the basics of it is:
Either:
A) Computer screen goes to screensaver
B) Screensaver is disabled and I leave unattended for a while

When I return, the computer will not wake from a Wireless Keyboard/Mouse (Logitech K350)
but it will wake up when using a basic Microsoft USB Keyboard. Then it will show the screensaver lock screen (I don't believe this happened when the screensaver was disabled).

After using the computer normally for a while, I will eventually switch workspaces.
Upon changing workspaces the screensaver lock screen will appear immediately but will vanish as you move your mouse around and click on windows.

For example, the black mask will appear over a window and the background.
Upon clicking on a window, the black mask vanishes from that screen area.
I then repeat this process by clicking on everything in the workspace until everything is visible.
Occasionally after doing this process the same black mask bug will immediately happen, without any apparent trigger.
Then if I leave that workplace and immediately return the same thing the bug will immediately occur.

This part of the bug will never affect more than one workspace at a time but can swap affect another workspace if it is left inactive for a period of time.

Haven't tried uninstalling it yet but will attempt that tomorrow.

JeramyNS commented Oct 6, 2016

I have this issue also however I also get the following bug, after this issue occurs once.
Template is irrelevant for me as it also occurred while using whonix-ws.

It's a little random when it happens but the basics of it is:
Either:
A) Computer screen goes to screensaver
B) Screensaver is disabled and I leave unattended for a while

When I return, the computer will not wake from a Wireless Keyboard/Mouse (Logitech K350)
but it will wake up when using a basic Microsoft USB Keyboard. Then it will show the screensaver lock screen (I don't believe this happened when the screensaver was disabled).

After using the computer normally for a while, I will eventually switch workspaces.
Upon changing workspaces the screensaver lock screen will appear immediately but will vanish as you move your mouse around and click on windows.

For example, the black mask will appear over a window and the background.
Upon clicking on a window, the black mask vanishes from that screen area.
I then repeat this process by clicking on everything in the workspace until everything is visible.
Occasionally after doing this process the same black mask bug will immediately happen, without any apparent trigger.
Then if I leave that workplace and immediately return the same thing the bug will immediately occur.

This part of the bug will never affect more than one workspace at a time but can swap affect another workspace if it is left inactive for a period of time.

Haven't tried uninstalling it yet but will attempt that tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment