There is no bug in gdm, but only a confusing option
(CustomCommandNo_Restart_ which _exits_ gdm when false) that should be
renamed or at least documented in the config file properly (it is
documented right now, but somewhat confusing). Maybe this is an upstream
bug.

** Summary changed:

- gdm crashes on execution of Custom Command
+ gdm CustomCommandNoRestart documentation confusing

** Description changed:

  Binary package hint: gdm
  
  Hi,
  
  found a problem that arouse recently with both Gutsy and Intrepid (worked 
some day last year in gutsy):
  When configuring a custom command in /etc/gdm/gdm.conf-custom in the 
[customcommand] section via CustomCommand[0-9]=/some/command (tested with own 
shell script, and with /usr/bin/yes) gdm crashes when the command is picked 
from the actions-menu. It shows the ubuntu splash screen, but nothing happens. 
Attached the syslog with debugging enabled for gdm.
  However, the command is executed (/usr/bin/yes used one full CPU).
  
  There is an easy workaround: If you enable the CustomCommandNoRestart option 
via adding
  CustomCommandNoRestart[0-9]=true (default is false)
  to gdm.conf-custom, gdm does not crash anymore.
  
  If you need more information, a backtrace, tests on vanilla Ubuntu
  installations or whatever, don't hesitate to ask
  
  Thanks,
  
  Mika
+ 
+ == Update ==
+ Without CustomCommandNoRestart gdm exits upon execution of the custom 
command. I guess the idea is, that all custom commands deal somehow with 
Restarting the machine or similar where it is a good idea to exit gdm.
+ However, in Intrepid and Gutsy there is no hint that gdm has exited - this 
hint can be seen in Jaunty (it says something along the lines of "The system is 
being shut down").
+ Thus I propose to clarify the documentation, see my comment below.

-- 
gdm CustomCommandNoRestart documentation confusing
https://bugs.launchpad.net/bugs/315484
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to