This bug was fixed in the package ubiquity - 1.99.1
---
ubiquity (1.99.1) karmic; urgency=low
[ Colin Watson ]
* Use dh_lintian.
* Restore autologin-disabling code from oem-config, corrected to work with
new gdm (LP: #395861).
[ Evan Dandrea ]
* Add support for ubiquity
I fixed this in oem-config, but the autologin-disabling code was lost
when oem-config was merged into ubiquity recently. I've restored it and
re-merged my fix.
** Package changed: oem-config (Ubuntu) => ubiquity (Ubuntu)
--
gdm 2.26 custom configuration file: wrong filename
https://bugs.launchpa
** Branch linked: lp:ubiquity
--
gdm 2.26 custom configuration file: wrong filename
https://bugs.launchpad.net/bugs/395861
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://
This is a little off topic and perhaps fodder for another bug, but I had
serious gdm problems after this last batch of gdm and x updates because
my gdm custom file had an alternate server defined (by myself long ago).
I had the X path of /usr/X11R6/bin/X which no longer works (due to a
recent chang
This bug was fixed in the package casper - 1.180
---
casper (1.180) karmic; urgency=low
[ Colin Watson ]
* scripts/casper-bottom/15autologin: Minor consistency fixes.
[ Martin Pitt ]
* scripts/casper-bottom/15autologin: Update for new gdm custom configuration
file (/etc/g
This bug was fixed in the package gdm - 2.26.1-0ubuntu3
---
gdm (2.26.1-0ubuntu3) karmic; urgency=low
* Add 03_hide_system_users.patch: Do not show system users in the "frequent
users" list. (LP: #395281)
* debian/rules: Call dh_installinit with --no-scripts, to avoid restarti
Sebastien, I think we should use custom.conf, like upstream. I fixed
this in bzr.
--
gdm 2.26 custom configuration file: wrong filename
https://bugs.launchpad.net/bugs/395861
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
we used to use the gdm configure option to rename the file to gdm.conf-
custom, should we keep doing that now?
--
gdm 2.26 custom configuration file: wrong filename
https://bugs.launchpad.net/bugs/395861
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
This bug was fixed in the package user-setup - 1.27ubuntu4
---
user-setup (1.27ubuntu4) karmic; urgency=low
* Use /etc/gdm/custom.conf rather than /etc/gdm/gdm.conf-custom (LP:
#395861).
-- Colin WatsonMon, 06 Jul 2009 14:25:38 +0100
** Changed in: user-setup (Ubuntu)
** Changed in: user-setup (Ubuntu)
Importance: Undecided => Medium
** Changed in: user-setup (Ubuntu)
Status: New => Fix Committed
** Changed in: user-setup (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
** Changed in: oem-config (Ubuntu)
Status: Triaged => Fix
** Branch linked: lp:~ubuntu-core-dev/user-setup/ubuntu
--
gdm 2.26 custom configuration file: wrong filename
https://bugs.launchpad.net/bugs/395861
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Changed in: gdm (Ubuntu)
Status: In Progress => Fix Committed
--
gdm 2.26 custom configuration file: wrong filename
https://bugs.launchpad.net/bugs/395861
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Branch linked: lp:~ubuntu-desktop/gdm/ubuntu
--
gdm 2.26 custom configuration file: wrong filename
https://bugs.launchpad.net/bugs/395861
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.u
** Also affects: user-setup (Ubuntu)
Importance: Undecided
Status: New
--
gdm 2.26 custom configuration file: wrong filename
https://bugs.launchpad.net/bugs/395861
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This also needs to be adapted in casper and oem-config.
** Changed in: casper (Ubuntu)
Status: New => Triaged
** Changed in: casper (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: gdm (Ubuntu)
Importance: Low => Medium
** Also affects: oem-config (Ubuntu)
Indeed upstream uses /etc/gdm/custom.conf, and we have a patch which
changes the name to be loaded. We should remove that patch, move an
existing gdm.conf-custom to custom.conf during upgrade.
** Changed in: gdm (Ubuntu)
Status: Incomplete => In Progress
** Changed in: gdm (Ubuntu)
As
Issue #1: Upgrading from 2.20 to 2.26 leaves you with two configuration
files. Pretty confusing I'd say - especially because you have to
manually configure GDM since there is no graphical tool (yet?) to do it.
Issue #2: Fresh installations just install 'custom.conf', which isn't
used (yet?) by GDM
the configuration file has always been named gdm.conf-custom in ubuntu
is that an issue?
** Changed in: gdm (Ubuntu)
Importance: Undecided => Low
** Changed in: gdm (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs (
I can also confirm this.
An entry:
---
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=
---
in custom.conf does nothing.
But it works in gdm.conf-custom
--
gdm 2.26 custom configuration file: wrong filename
https://bugs.launchpad.net/bugs/395861
You received this bug notification because y
I can confirm that the contents of /etc/gdm/custom.conf are IGNORED and
the contents of /etc/gdm/gdm.conf-custom over-ride the settings in
/etc/gdm/gdm.schemas, contrary to the documentation.
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
gdm 2.26 custom configuration file: wrong
After reading the documentation
(http://library.gnome.org/admin/gdm/stable/configuration.html.en) it's
in fact custom.conf that should be used to config GDM. I suggest
renaming the bug to something like "gdm 2.26 wrong configuration file
used".
--
gdm 2.26 custom configuration file: wrong filenam
21 matches
Mail list logo
