Public bug reported:
Binary package hint: gdm
lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04
apt-cache policy gdm
gdm:
Installed: 2.20.6-0ubuntu2
Candidate: 2.20.6-0ubuntu2
Version table:
*** 2.20.6-0ubuntu2 0
500 http://ca.archive.ubuntu.com hardy-updates/main Packages
100 /var/lib/dpkg/status
2.20.5-0ubuntu3 0
500 http://ca.archive.ubuntu.com hardy/main Packages
Persistence seems to be broken in /etc/gdm/gdm.conf-custom (and of
course /etc/gdm/gdm.comf). When adding a custom command to gdm, for
example, the option customcommand/CustomCommandIsPersistentN=true (where
N is the number from 0-9 of the command) SHOULD allow the custom command
to appear in both the greeter and the various logout choices:
QUERY_LOGOUT_ACTION, SET_LOGOUT_ACTION and SET_SAFE_LOGOUT_ACTION:
from /etc/gdm/gdm.conf-custom.
# Custom command persistence option. Setting it to true will allow this
# command to appear outside the login manager, e.g. on the desktop through
# Log Out/Shut Down dialogs. The default value is false.
Setting this value to true has no effect on the logout/shut down dialogs
inside the Ubuntu session, however. CUSTOM_CMDs show up on the action
list in the greeter, but not on the logoutout shut down queries inside
the session desktop. (This persistence also seems to be broken for
established commands as well: to check I tried changing the command for
suspend inside gdm.conf: when I rebooted suspend did not have the new
command).
I suppose the short way of saying this is that changes that affect the
greeter menu are not showing up in the logoff dialogue boxes even if
they are labelled persistent.
** Affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
custom_cmd persistence doesn't seem to work.
https://bugs.launchpad.net/bugs/248860
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
