** Changed in: gconf
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/269541
Title:
gconfd-2 becomes orphane when parent process crashes
To manage notifications
** Package changed: gconf2 (Ubuntu) = gconf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/269541
Title:
gconfd-2 becomes orphane when parent process crashes
To manage notifications
** Changed in: gconf
Importance: Unknown = Critical
--
gconfd-2 becomes orphane when parent process crashes
https://bugs.launchpad.net/bugs/269541
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Changed in: gconf
Status: Unknown = New
--
gconfd-2 becomes orphane when parent process crashes
https://bugs.launchpad.net/bugs/269541
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Also affects: gconf via
http://bugzilla.gnome.org/show_bug.cgi?id=534485
Importance: Unknown
Status: Unknown
** Changed in: gconf2 (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Triaged
--
gconfd-2
This bug causes LTSP users grief without a stale process 'cleanup'
program such as gnome-watchdog. It will cause unexpected behavior when
logged out (thus the gconfd-2 process stays alive) and logging back in,
as there is conflicting processes, causing crashes and other unexpected
GNOME behavior.
The same kind of bug on the Gnome bugzilla:
http://bugzilla.gnome.org/show_bug.cgi?id=534485
If anyone has the same bug, please confirm it there also.
--
gconfd-2 becomes orphane when parent process crashes
https://bugs.launchpad.net/bugs/269541
You received this bug notification because you
** Description changed:
Binary package hint: gconf2
When using a thin client kind of way (Nomachine NX or LTSP), it stays
running when the connection crashes for some reason or when terminating
the session on the serverside. gnome-session gets killed correctly, but
gconfd stays
Please also see http://logicalnetworking.net/other/watchdog.txt and
search for all instances of 'gconfd-2' . Seems that it is pretty common
for it to hang around upon normal exit of an LTSP TC session, which
package gnome-watchdog sees and forcefully kills to keep stale
processes to a minimum.
--
