Incoming RDP connections (to MATE desktop) fail with "Could not acquire name on session bus" if the same user was logged into the console (and vice versa trying to login on console with an RDP session running for the same user). This seems to be an inter-operability problem caused by one (or more) of: (a) DBUS defining DBUS_SESSION_BUS_ADDRESS too globally (b) Each desktop failing to properly re-acquire a distinct DBUS connection (c) Some single "middleware" (whatever "owns" /etc/sysconfig/desktop) not properly erasing DBUS_SESSION_BUS_ADDRESS on desktop startup How reproducible: Problem is easy to reproduce Steps to Reproduce: 1. Using MATE desktop 2 Start a console session for some user 3. Try to create another session for same user via RDP (via XRDP) 4. You will get "Could not acquire name on session bus" and the connection will not be usable. 5. NOTE: if you start the RDP session first, the console login will generally fail with the same DBUS error WORKAROUNDS: 1) Add "unset DBUS_SESSION_BUS_ADDRESS" to /etc/sysconfig/desktop. Apparently some desktops and some other packages do this, but MATE does not. Perhaps adding that to MATE is the proper solution. I'm not clear enough on the underlying architecture to understand what the "underlying problem" and "correct solution" is, just that I have a problem and that this manual workaround fixes the problem until the next clean install. BACKGROUND: I reported this issue 4 years ago (2017) against several components. They are finally noticing the issue and most are pointing to MATE as the proper party to fix the problem. I have not idea if that is correct, but am opening up a MATE-DESKTOP ticket in case it is. See also https://bugzilla.redhat.com/show_bug.cgi?id=1381034 https://bugzilla.redhat.com/show_bug.cgi?id=1452996
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.