Bug 123655
Summary: | Gnome leaves processes running at logout | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nils O. Selåsdal <nos> |
Component: | gnome-session | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | barryn, gharris, jval, mattdm, pza |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-05-11 21:33:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nils O. Selåsdal
2004-05-19 20:54:53 UTC
I'm having the same issue. Bonobo is ALWAYS running after someone logs out. In fact, a lot of times when I login it says gnome-panel is already running. I then try to kill the process using every SIGxxx under the sun to no avail, it just sits there as a defunct process. The only way to solve this problem is to reboot the computer. I certainly cannot deploy this on all of the machines in our computer lab until it is fixed. I can atleast kill bonobo-activation-server. Does it have a parent != 0 that you can kill ? (or a parent pid that actually does not exist, which I have a feeling is another bug in FC2). Btw, I see evolution-wombat also running after logging out. The processes are causing the machine to hang when the automount daemon tries to unmount the NFS user home directories. This is because the process is in that user name, (which keeps the user's home directory mounted). / isn't being unmounted either because it is busy. I think what is happening is one of the underlying gnome process (in this case probably bonobo) is causing the processes that use it to hang also. (like gnome-keyring and evolution-wombat) I did more research on this and this turns out to be a problem with libbonobo. The GNOME team says this is fixed in libbonobo >= 2.6.1. Any ideas when RPMS might be available for this package, and all its dependencies? (probably all of gnome >= 2.6.1). I consider this an urgent issue as if you are using autofs like I am, every fedora core 2 machine you are running is going to leave mounts open for every user that logs into the machines... think about lab machines, If you have 100 lab users, you're going to have 100 open bonobo processes left there, and 100 NFS mounts that won't go away because the processes are left there! Ray, Would you please post an RPM of libbonobo >= 2.6.1 to the updates tree so we can close this bug? Thanks. Hi Gregory, I'll be happy to push an updated version of libbonobo into updates. For reference, the relevent upstream bug is: http://bugzilla.gnome.org/show_bug.cgi?id=139500 Note that gnome-keyring-daemon doesn't use bonobo-activation-server, however, so pushing an updated libbonobo rpm probably won't be a complete solution to the problem. Before applying this update, I had never had any session problems (a few processes were often left behind, but they didn't cause problems). Since applying the update, I'm having all sorts of problems with users sessions leaving behind files, gconf not working, etc. All can be fixed with pkill -u USERNAME. I have rolled back to the version of libbonobo from the FC2 release, and all the problems have gone. Anyone else experiencing this? Fedora Core 2 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC3 updates or in the FC4 test release, reopen and change the version to match. Hi, This bug is being closed because it has been in the NEEDINFO state for a long time now. Feel free to reopen the bug report if the problem still happens for you and you can provide any information that was requested. These bugs are probably the same issue: bug #139999 and bug #281471 Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=534485 |