Description of problem: ssh -AXC server server $ firefox& (close firefox) server $ exit (ssh connection hangs) How reproducible: Not for all apps, but for most. firefox, thunderbird have the problem, xeyes does not. Actual results: ssh connection hangs after X program exits. Expected results: ssh connection does not hang. Additional info:
Created attachment 469105 [details] dump from sshd -d -d -d using firefox (just start and close the window) there are 3 opened channels 3, 4 and 5. The channel stay opened ... No data is send or received on that channel.
The sshd hangs, because there, after the firefox exit, stay dbus-launch processes which keep an open connection to the forwarded X socket.
OK, reassigning to dbus then for further investigation.
In this scenario currently, dbus currently doesn't terminate until the X server does. Now, short of mandating that the session bus be per (kernel, uid): http://lists.freedesktop.org/archives/dbus/2010-November/013683.html we could potentially patch the bus to optionally exit after it has no clients. Honestly though, we're no where near modern applications really working in this kind of scenario, if they access any non-display functionality like preferences, network status, etc.
https://bugs.freedesktop.org/show_bug.cgi?id=32509
Corresponding RHEL 6 bug: https://bugzilla.redhat.com/show_bug.cgi?id=638551
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is quite an important bug...
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
I'm still seeing this issue on Fedora 20. Are there any plans to still fix this?
I opened a support request to file this as a bug against RHEL7. Things like this might be okay for Fedora, but not for a commercial product. This was reported back in 2010! Yes, there are workarounds, but this behavior is broken. One workaround is to create a .logout with: eval `pkill -u $USER dbus-launch` > /dev/null
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
I can't reproduce this on Fedora 26. Clearing NEEDINFO, closing as NEXTRELEASE instead of EOL.