[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing

2010-09-15 Thread Bug Watch Updater
** Changed in: gdm
   Status: Invalid = Expired

** Changed in: gdm
   Importance: Unknown = Low

-- 
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


[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing

2010-06-07 Thread Sebastien Bacher
the CustomCommandNoRestart command has been deprecated in the new gdm,
closing the bug

** Changed in: gdm (Ubuntu)
   Status: Triaged = Invalid

-- 
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


[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing

2010-06-04 Thread Bug Watch Updater
** Changed in: gdm
   Status: New = Invalid

-- 
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


[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing

2009-07-24 Thread Mika Pflüger
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


[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing

2009-07-24 Thread Sebastien Bacher
The issue is an upstream one and it would be nice if somebody having it
could send the bug the to the people writting the software
(https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

** Changed in: gdm (Ubuntu)
   Importance: Medium = Low

** Changed in: gdm (Ubuntu)
   Status: Incomplete = New

** Also affects: gdm
   Importance: Undecided
   Status: New

-- 
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


[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing

2009-07-24 Thread Mika Pflüger
Hm, I am actually not sure anymore if GNOME is the right place to report
it. I couldn't find the gdm.conf-custom file in the GNOME gdm sources
(maybe I just don't find it, but maybe it is not there). Could it be,
that gdm.conf-custom and especially the documentation therein is instead
added by Debian?

-- 
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


[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing

2009-07-24 Thread Sebastien Bacher
the upstream naming is custom.conf which is the karmic naming too now

-- 
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


[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing

2009-07-24 Thread Mika Pflüger
Reported upstream.

** Bug watch added: GNOME Bug Tracker #589614
   http://bugzilla.gnome.org/show_bug.cgi?id=589614

** Changed in: gdm
   Importance: Undecided = Unknown

** Changed in: gdm
   Status: New = Unknown

** Changed in: gdm
 Remote watch: None = GNOME Bug Tracker #589614

-- 
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


[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing

2009-07-24 Thread Bug Watch Updater
** Changed in: gdm
   Status: Unknown = New

-- 
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


[Bug 315484] Re: gdm CustomCommandNoRestart documentation confusing

2009-07-24 Thread Sebastien Bacher
** Changed in: gdm (Ubuntu)
   Status: New = Triaged

-- 
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