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

note XRDP problems when disabling Screen Blanking #2173

Closed
wants to merge 1 commit into from
Closed

note XRDP problems when disabling Screen Blanking #2173

wants to merge 1 commit into from

Conversation

buhtz
Copy link

@buhtz buhtz commented Sep 28, 2021

I added information about a possible side problem with XRDP when disabling Screen Blanking.

Beside my own experience I also found some postings in the net about this. But the connection between Screen Blanking and XRDP-mouse-input is still unknown.

@lurch
Copy link
Contributor

lurch commented Sep 28, 2021

@XECDesign or @spl237 Any ideas about this? Is this an appropriate change to make to the documentation?

@spl237
Copy link
Contributor

spl237 commented Sep 28, 2021

No idea, but it seems unwise to change the documentation until the problem is understood - screen blanking really shouldn't affect XRDP sessions, so just documenting that it does is not the best solution...

@lurch lurch added the paused Waiting for other things to happen. label Sep 28, 2021
@aallan aallan marked this pull request as draft September 28, 2021 14:11
@MichaIng
Copy link
Contributor

If the Xorg session (xorgxrdp package) is used, then this is the reason: neutrinolabs/xorgxrdp#164

There are two different solutions provided in the issue, test the latter one used by the maintainer, which is present on Debian Bullseye as well: https://github.com/neutrinolabs/xorgxrdp/pull/181/files (apply to /etc/X11/xrdp/xorg.conf)

@ghost
Copy link

ghost commented Jan 21, 2022

It seems to me like this is not a documentation issue: rather it should be raised as a bug against the Raspberry Pi OS distro for the relevant package maintainer to take a look. It appears that the bug is in an upstream package so should probably be escalated upstream, but that's up to the relevant maintainer of Raspberry Pi OS to decide.

@aallan
Copy link
Contributor

aallan commented Feb 16, 2022

This doesn't seem like a docs issue. I'm closing, and I think the OP should raise an issue against the Raspberry Pi OS repo if they haven't already done so.

@aallan aallan closed this Feb 16, 2022
@aallan aallan added wontfix and removed requires technical check paused Waiting for other things to happen. needs discussion labels Feb 16, 2022
@MichaIng
Copy link
Contributor

As said, all fixed upstream, provided downstream with Bullseye already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants