Description of problem: The default Xorg (via Xorg.wrap) setting of "allowed_users=console" seems overly restrictive. Requiring the user to be CURRENTLY logged into the console seems odd (and counter productive). Surely this must affect any software that wants to create a virtual framebuffer using Xorg software. In particular, to make XRDP work (with Xorg) requires the user to know enough to manually change to "allowed_users = anybody". Is there a really compelling reason for the default? If so, is the reason sufficiently compelling that XRDP users should avoid Xorg sessions and use Xvnc sessions instead (which do work by default)? Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.19.3-1.fc25.x86_64
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Just installed F28 Mate Spin - problem still there.
Still a problem in Fedora-29
Knock knock. Anybody there? I'm puzzled that there is no comment of any sort from the maintainers since the ticket was filed in Spring of 2017. Is this bug report filed for the wrong group? Some feedback would be helpful.
OOPS, never mind. My bad. This problem WAS fixed a while ago. I was updating 3 OTHER XRDP related bugs that are still outstanding in F29 and I mistakenly made the same edit to this ticket. My apologies. Thanks for the good work./etc/X11/Xwrapper.config
OOPS. My previous comment 6 was in error. Sadly, the default behaviour has NOT been changed. What I though was an xorg provided /etc/X11/Xwrapper.config was merely a file I had created as a workaround long ago. ISSUE RESTATED The current default used by Xorg.wrap prevents XRDP from creating a VIRTUAL framebuffer UNLESS the SAME user is ALSO currently logged into the physical console (which is quite unlikely). So to make XRDP work (and perhaps other similar technologies based on X/Xorg) the user must know how to create a subtle config file, instead of things "just working". CANDIDATE FIXES (any would seem to fix the RDP problem) 1) Don't perform this check when creating a VIRTUAL framebuffer 2) Change the default behavior to allowed_users=anybody 3) Change the default behavior to check for whether the user is ALLOWED to login to the console (rather than requiring them to BE logged in). 4) Have the various RDP groups each deliver an /etc/X11/Xwrapper.config that changes the behavior (sadly for both VIRTUAL and PHYSICAL framebuffers). Anyway, some feedback would be appreciated. Perhaps I'm overlooking something totally obvious.
As an aside, the "Xvnc" session type supported by XRDP does not have this limitation. It seems to be purely the "Xorg" session type.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Updated version from 29 to 33, same default/problem as F29
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.