Skip to content
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

Mumble client prevents display timeout sleep #5789

Open
cobrafast opened this issue Aug 11, 2022 · 7 comments
Open

Mumble client prevents display timeout sleep #5789

cobrafast opened this issue Aug 11, 2022 · 7 comments
Labels
bug A bug (error) in the software client GlobalShortcuts windows

Comments

@cobrafast
Copy link

Description

After doing the update from 1.3.X to 1.4.230 for Windows 10 (64b), my monitors no longer turn off for power saving while mumble is running. This is especially noticable on the lock screen which has a short display timeout (~1min).

Being connected to a server or not makes no difference.

I found #1394 which was solved by updating audio drivers, however I am on the latest audio drivers (which are dated December 2017) available for my mainboard (ASUS X299 Deluxe). Also, this was not a problem with mumble versions 1.3 or older.

powercfg -requests shows no difference between mumble running or not.

Steps to reproduce

  1. Verify energy/display timeout settings
  2. Start mumble
  3. (Optional) lock screen
  4. Wait and observe how the monitor(s) stay on

Mumble version

1.4.230

Mumble component

Client

OS

Windows

Reproducible?

Yes

Additional information

No response

Relevant log output

No response

Screenshots

No response

@cobrafast cobrafast added bug A bug (error) in the software triage This issue is waiting to be triaged by one of the project members labels Aug 11, 2022
@Krzmbrzl
Copy link
Member

Krzmbrzl commented Aug 11, 2022

@davidebeatrici could this somehow be related to the new shortcut implementation on Windows? E.g. it permanently generating some sort of input events making the display think it can't turn off?

@cobrafast is there an option under Settings > Global shortcuts to disable all shortcuts? If so, could you try doing that to see if the issue persists?

@cobrafast
Copy link
Author

@cobrafast is there an option under Settings > Global shortcuts to disable all shortcuts? If so, could you try doing that to see if the issue persists?

I can't find any such setting. Removing my one shortcut and unchecking 'Enable shortcuts in privileged applications' had no effect.

@Krzmbrzl
Copy link
Member

Ok then the system probably can't be disabled on Windows 👀

@cobrafast
Copy link
Author

cobrafast commented Aug 11, 2022

When checking the developer console, I saw that the shortcut system is hooking into my older Logitech joystick (Extreme 3D Pro model). Unplugging it fixed the problem.
Unchecking 'Enable XInput' does not help when the joystick is plugged in.

@Krzmbrzl
Copy link
Member

Good catch! So it somehow is related to the new shortcut implementation.

Iirc XInput is only relevant for Xbox-controllers used under Windows...

@Krzmbrzl Krzmbrzl added client GlobalShortcuts windows and removed triage This issue is waiting to be triaged by one of the project members labels Aug 11, 2022
@davidebeatrici
Copy link
Member

Iirc XInput is only relevant for Xbox-controllers used under Windows...

Correct.

I wonder if the joystick is sending "phantom" events that are registered by Windows (and in turn Mumble).

Here's some test applications: Joystick-Input-Examples_e2f196877de59134ac1499351d8e7391f4c6a3e0.zip

@Krzmbrzl
Copy link
Member

@cobrafast could you run the test application combined.exe and report its output?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug (error) in the software client GlobalShortcuts windows
Projects
None yet
Development

No branches or pull requests

3 participants