Skip to content

Screen doesn't blank after remote session. #5481

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

Closed
arnofkd opened this issue May 24, 2023 · 2 comments
Closed

Screen doesn't blank after remote session. #5481

arnofkd opened this issue May 24, 2023 · 2 comments

Comments

@arnofkd
Copy link

arnofkd commented May 24, 2023

Describe the bug

On Raspberry Pi 4, Raspberry OS (32bit as well as 64bit), after finishing a remote session, the screen will not blank after the designated time (default 600s).

This is under the condition that no local mouse or keyboard input is detected/made after the session disconnect.

Steps to reproduce the behaviour

  1. Raspberry Pi with Raspberry OS (32 or 64bit) installed.

  2. No mouse or keyboard connected to Raspberry

  3. Install AnyDesk

  4. Initiate remote session from a different device into Raspberry

  5. Disconnect the remote session

  6. Wait 10 minutes+

  7. Screen will not blank and continue staying on indefinitely

Device (s)

Raspberry Pi 400

System

Raspberry Pi reference 2023-05-03
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 47eee1f0ddcf8811559d51eea1c1bb48335e3e88, stage4

Mar 17 2023 10:50:39
Copyright (c) 2012 Broadcom
version 82f3750a65fadae9a38077e3c2e217ad158c8d54 (clean) (release) (start)

Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux

Logs

No response

Additional context

No response

@popcornmix
Copy link
Collaborator

I would say it's more likely this is an issue with the OS than the kernel (and so better reported here).

Assuming it only occurs when using AnyDesk, then it becomes much less likely it's kernel related.

To help identify where it is occurring, it may be possible to use dbus-monitor to check for messages related to DPMS.
It also may be possible to check if kernel is requested to blank using drm.debug cmdline option (but I suspect this is less likely).

@arnofkd
Copy link
Author

arnofkd commented May 25, 2023

Thank you for pointing me in the right direction!

@arnofkd arnofkd closed this as not planned Won't fix, can't repro, duplicate, stale May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants