Re: [gdm-list] gdm doesn't kill its own session clearly, causes two gnome-settings-daemon run on one DISPLAY
- From: Ray Strode <halfline gmail com>
- To: "fykcee1 gmail com" <fykcee1 gmail com>
- Cc: gdm-list gnome org, gnomecc-list gnome org
- Subject: Re: [gdm-list] gdm doesn't kill its own session clearly, causes two gnome-settings-daemon run on one DISPLAY
- Date: Thu, 17 Feb 2011 22:38:08 -0500
Hi,
> The output of the script follows:
> gdm 2232 47.1 4.6 53824 23424 ? Rsl 02:02 0:07
> /usr/lib/gnome-settings-daemon/gnome-settings-daemon
> --gconf-prefix=/apps/gdm/simple-greeter/settings-manager-plugins
> Starting gnome-settings-daemon...
> loongson 2337 0.0 0.2 6000 1424 ? S 02:02 0:00 grep
> gnome-settings-daemon
> ** (gnome-settings-daemon:2340): WARNING **: You can only run one xsettings
> manager at a time; exiting
> ** (gnome-settings-daemon:2340): WARNING **: Unable to start xsettings
> manager: Could not initialize xsettings manager.
> My gdm is 2.30.5 (based on 2.30.5-0ubuntu4), gnome-settings-daemon is 2.32.1
> (2.32.1-0ubuntu5), and gnome-session is 2.32.0 (2.32.0-0ubuntu1).
Sometime around 2.30 gdm was changed to only kill gnome-session and
none of the stuff gnome-session starts (This was to prevent ordering
problems on solaris). It now depends on gnome-session to clean up
after itself. My guess is either
1) gnome-settings-daemon isn't properly registering with the session
so isn't getting killed on exit
2) gnome-settings-daemon is ignoring SIGTERM (should be verifable by
trying to kill it after login)
3) gnome-session has some bug where it's not properly sending SIGTERM
to gnome-settings-daemon
--Ray
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]