In Jaunty gdm just exits and says something like "System is restarting" or similar. I guess in hardy and intrepid it is exiting also, but not displaying any message. I'm perfectly cool with this behaviour (that gdm just exits and displays some message unless you set CustomCommandNoRestartN=True), but maybe we could enhance the documentation in /etc/gdm/gdm.conf. At the moment it reads: > # Custom command gdm/system restart option. Setting it to true will not > # restart gdm after command execution. The default commands (reboot, shut > # down) all reboot the system by default which is why the default setting > # is true. But gdm does not /restart/, but exits. So my idea would be: > # Custom command gdm stop option. Setting it to true will not > # stop gdm after command execution. The default commands (reboot, shut > # down) all reboot the system by default which is why the default setting > # is false. (additionally the "the default setting is true" is somewhat misleading, as the default setting of CustomCommandNoRestartN is false. Maybe we should even say: "...which is why the default behaviour is to stop gdm.")
Greets, Mika -- gdm crashes on execution of Custom Command https://bugs.launchpad.net/bugs/315484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
