We have been ignoring the fall releases for our desktop machines. It works in Jaunty.
I guess it is not critical, but it was a nice feature that we had gotten used to. I think the workaround is just to not restart gdm when the package gets updated or the configuration gets changed. I believe that it will bet restarted when someone logs in and out. This is really only a problem if there are security updates for gdm. We'll be able to deploy the new gdm, but we won't be able to restart it automatically because someone may be logged in. On Friday, June 04, 2010 01:33:23 pm you wrote: > I can confirm the output of the command on Lucid is "Not supported". > What is the release used in your last deployment where gdm-safe-restart > was supported? > > Take a look at this recent commit which shows the commands are removed in > current development GNOME: > http://git.gnome.org/browse/gdm/commit/?id=9aace1fa58d1a4219fdddc4df01e073 > 5f78dd306 > > - gdm-stop \ > - gdm-restart \ > - gdm-safe-restart \ -- gdm-safe-restart not supported https://bugs.launchpad.net/bugs/589320 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
