Description of problem: Since Fedora-24 I've had a problem with incoming RDP connections (to MATE desktop) failing 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 I picked DBUS as the place to file this ticket, but I've seen various other tickets filed against "x2go" and "xrdp" (I filed that one but it was closed as "not an XDRP bug"). It would seem best to fix the inter-operation problem in ONE place rather than MANY if that is at all possible. Version-Release number of selected component (if applicable): dbus-1.11.12-1.fc25.x86_64 How reproducible: Highly reproducible Steps to Reproduce: 1. Ensure MATE is the default desktop 2 Start a console session for user XXX 3. Try to create another session for same user via RDP 4. You will get "Could not acquire name on session bus" and attempts to proceed are pretty ineffectual ALSO - you can reverse the order and start the RDP session first, then the console session will have the problems. Additional info: 1) There is a workaround, namely adding "unset DBUS_SESSION_BUS_ADDRESS" to /etc/sysconfig/desktop. Apparently some desktops and some other packages do this, but not all (for example not MATE). 2) I ran into this with XRDP, but really any other incoming remote desktop protocol should run into the same issue.
See also 1) https://bugzilla.redhat.com/show_bug.cgi?id=1350004 2) https://bugzilla.redhat.com/show_bug.cgi?id=1381034
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
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.
Still a bug in Fedora 33.
dbus-daemon exports its environment variables where it is started. Whether that is too broad is dependent on your session manager, not dbus.
David - thanks for the info. As I said 4 years ago I'm not sure what component "owns" the underlying problem that ends up resulting in "Could not acquire name on session bus" when a second user logs in via RDP/XRDP when there is a console user present. Can you provide any insight into what component owns the problem? I have only a cursory understanding of how DBUS, session managers, XRDP and desktops are all supposed to play nicely together. Could you help me get the problem presented to the "most appropriate" RedHat/Fedora "component", and perhaps with a better description of the underlying problem if that is needed? I HAVE found a workaround that I have kept applying for the last 4 years, namely: Add "unset DBUS_SESSION_BUS_ADDRESS" to /etc/sysconfig/desktop" but as noted above, not all environments provide that. It would seem desirable to get the problem to the proper folks to fix it properly for all users (without needing individual workarounds). Thanks! Charlie
Based on separate input from Bojan Smojver I just submitted https://bugzilla.redhat.com/show_bug.cgi?id=1928575 agains MATE-DESKTOP. Fingers crossed :-)