** Changed in: gdm (Ubuntu Lucid)
Status: Triaged = Won't Fix
** Changed in: gdm (Ubuntu Natty)
Status: Triaged = Won't Fix
** Changed in: gdm (Ubuntu Natty)
Milestone: natty-updates = None
** Changed in: gdm (Ubuntu Natty)
Assignee: James Hunt (jamesodhunt) =
This bug was fixed in the package kdebase-workspace - 4:4.6.5-0ubuntu1
---
kdebase-workspace (4:4.6.5-0ubuntu1) natty-proposed; urgency=low
* Upload to natty-proposed for SRU testing (LP: #859562)
-- Scott Kitterman sc...@kitterman.com Mon, 26 Sep 2011 07:37:25 -0400
** Changed
** Tags added: runlevel1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't start
on post-boot runlevel
** Branch linked: lp:ubuntu/kdebase-workspace
** Branch linked: lp:ubuntu/natty-proposed/kdebase-workspace
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart
I permission to you to use package in your team
** Changed in: gdm (Ubuntu Natty)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
** Changed in: gdm (Ubuntu Natty)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single
I permission to you in package
** Changed in: gdm (Ubuntu Natty)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job
Heru, don't randomly change states on bugs please.
** Changed in: gdm (Ubuntu Natty)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
I permission to fix released
** Changed in: gdm (Ubuntu Natty)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job
I want to permission with natty to Robbie Williamson
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't
gdm is not fixed in Natty, setting the task back to Triaged.
** Changed in: gdm (Ubuntu Natty)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
setting back to 'triaged' for gdm, since the SRU has been superseded as
Jamie mentioned. James, can you merge the gdm security fix and prepare
another SRU upload?
** Changed in: gdm (Ubuntu Natty)
Status: Fix Committed = Triaged
--
You received this bug notification because you are a
gdm 2.32.1-0ubuntu3.1 has been superseded by the 2.32.1-0ubuntu3.2
security update in natty.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks
** Branch linked: lp:~kubuntu-packagers/kdebase-workspace/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single user
This bug was fixed in the package kdebase-workspace - 4:4.6.3-1ubuntu1
---
kdebase-workspace (4:4.6.3-1ubuntu1) oneiric; urgency=low
[ Jonathan Thomas ]
* Merge with Debian Unstable, remaining changes:
- Add kdebase-workspace-wallpapers.{links, install}
- Add
kdm doesn't come up when selecting resume normal boot in the single user mode.
I've tested it on two machines.
I'll leave the verification-needed tag since I haven't tested gdm.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in
Accepted kdebase-workspace into natty-proposed, the package will build
now and be available in a few hours. Please test and give feedback here.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you in advance!
** Changed in:
The kdebase-workspace upload has a cp problem in the changelog:
+kdebase-workspace (4:4.6.2a-0ubuntu5.2) natty-proposed; urgency=low
+
+ [ James Hunt ]
+ * Updated gdm.conf to fix gdm in single user mode (LP: #436936)
+
+ -- Stéphane Graber stgra...@ubuntu.com Mon, 02 May 2011 14:00:03 -0400
Accepted gdm into natty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: gdm (Ubuntu Natty)
** Branch linked: lp:ubuntu/natty-proposed/gdm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't start
on
SRU testing should make sure that both of these start gdm as usual:
- Regular boot to gdm
- Boot in single user mode, then resuming boot
This should ideally be tested with most existing drivers, especially:
- Intel (seems to be fine)
- Nvidia (both with nouveau and with proprietary)
- ATI
** Changed in: kdebase-workspace (Ubuntu Karmic)
Status: Triaged = Won't Fix
** Changed in: kdebase-workspace (Ubuntu Karmic)
Milestone: karmic-updates = None
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
Attached is the debdiff for gdm.
I updated James' gdm.conf to keep the tab/spaces as they were in natty to limit
the delta.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
** Patch added: Debdiff for gdm in natty-proposed
https://bugs.launchpad.net/ubuntu/karmic/+source/kdebase-workspace/+bug/436936/+attachment/2106684/+files/bug436936-gdm.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
** Patch added: Debdiff for kdebase-workspace in natty-proposed
https://bugs.launchpad.net/ubuntu/karmic/+source/kdebase-workspace/+bug/436936/+attachment/2106688/+files/bug436936-kdebase-workspace.debdiff
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
The kdebase-workspace change has been commited to lp:~kubuntu-packagers
/kdebase-workspace/ubuntu/ and so will be part of the next Oneiric
upload.
I'm currently trying to figure out if we want a gdm upload in Oneiric
with just that change or should do the same as with kdebase-workspace.
I'd
This bug was fixed in the package gdm - 2.32.1-0ubuntu4
---
gdm (2.32.1-0ubuntu4) oneiric; urgency=low
[ Martin Pitt ]
* Add 44_xsession-errors_symlink.patch: Don't rename .xsession-errors to
.xsession-errors.old if the file is a symlink. The later code will
truncate the
** Branch linked: lp:ubuntu/gdm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't start
on post-boot
The version number in the gdm debdiff is wrong, it's going to be
ubuntu3.1 instead.
SRU for gdm in natty has been uploaded.
SRU for kdebase-workspace will have to wait until the kdebase-workspace
currently in -proposed is moved to -updates.
** Changed in: kdebase-workspace (Ubuntu)
Above fix would have to be tested on various hardware, including intel,
nvidia and ati graphic cards to make sure we don't get any regular boot
regression.
I'll do a quick test later today and prepare a similar .conf for
kdebase-workspace.
Then the two can go to -proposed for more testing before
Fix has now had to change due to an update to gdm.conf for udev-
fallback-graphics.
An updated gdm.conf is attached.
** Attachment added: gdm.conf
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/436936/+attachment/2059024/+files/gdm.conf
--
You received this bug notification because you
** Changed in: kdebase-workspace (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-2 = ubuntu-11.04
** Changed in: gdm (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-2 = ubuntu-11.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm
** Changed in: kdebase-workspace (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-1 = ubuntu-11.04-beta-2
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job
** Changed in: gdm (Ubuntu Natty)
Milestone: ubuntu-11.04-beta-1 = ubuntu-11.04-beta-2
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks
Ah, disregard that last comment. I ended up here due to James Hunt's
request for testing at bug 735805 and I'd not taken time to read the
history of this bug.
Regarding Natty only, using the 'gdm.conf' provided by James Hunt in
post #20 telinit 2 from a recovery shell does start gdm. Using the
That gdm.conf works like the current config file. Normal and recovery
boot do what they should.
I found one bug: Do a recovery boot and select resume. tty1 will come
up, but not GDM.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Do a recovery boot and select resume. tty1 will come up, but not GDM.
Should one of us start a new bug report regarding friendly-recovery?
I think it's been that way for quite a while.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Regarding the friendly recovery I checked to be sure and that problem
existed even in Maverick. I tried booting my stable Maverick recovery
mode using both a Natty grub and it's own grub and got the tty rather
than GDM.
Give me 24 to 48 hours so I can test Lucid with and w/o proposed
updates, and
Please could those who experienced the problems on bug 735805 provide
feedback on using the attached gdm.conf. If possible, could you confirm
that:
1) When you boot normally, gdm starts as expected.
2) When you boot to a recovery console that gdm does *NOT* start.
(hold down SHIFT and select
OK I replaced /etc/init/gdm.conf and normal boot worked fine but booting
in recovery mode stalled with the following lines at the bottom:
Begin: Running /scripts/local-bottom ... done.
[ 9.718090] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing
gen
I was not able to start a
Just comparing diff and noticed this:
+start on ((filesystem
+and (runlevel [!06]
+and (started dbus
+and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
+or stopped udevtrigger or runlevel PREVLEVEL=S)
-start on (filesystem
-
I tested the new gdm.conf, and confirm that
a) GDM doesn't start in recovery mode
b) GDM does start if I telinit 2 from a recovery mode shell
However, (b) is not particularly helpful, because it still doesn't work
if I choose the Resume option from the Recovery Menu.
All the Resume option does
On my system gdm failed to start with version 2.32.0-0ubuntu10.
With the gdm.conf from comment 15 I confirm that 1), 2) and 3) work fine
now. I rebooted four times, with gdm properly starting every time.
Thanks James!
--
You received this bug notification because you are a member of Ubuntu
@Jonathan - thanks for testing! Good news. Yes, I think you are right re
friendly-recovery.
@Erick and others - I attach an updated gdm.conf which might help.
Looking at the old gdm.conf, I think it was missing a condition which
this new gdm.conf adds. Please let me know your findings. Thanks for
Works perfectly for me :^)
I repeated both normal boots and recovery boots twice. All three tests
work as expected.
I do agree that friendly-recovery would be better but that's a
different issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
ok, that breaked system and needs to be debugged so the fix has been
reverted for now, see bug #735805 for details
** Changed in: gdm (Ubuntu Natty)
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
This bug was fixed in the package gdm - 2.32.0-0ubuntu10
---
gdm (2.32.0-0ubuntu10) natty; urgency=low
* debian/patches/01git_xdmcp_ipv6.patch:
- git commit to fix xdmcp issue when ipv6 is used
[ Martin Pitt ]
* Add 00git_passwordless_login_crash.patch: Disable the login
** Branch linked: lp:ubuntu/gdm
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't start
on post-boot
Fix now also tested on lucid.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't start
on post-boot
thanks James, the patch is in trunk now
** Changed in: gdm (Ubuntu Natty)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm
We should also backport this fix to Lucid, if at all possible. Not
worth the effort on Maverick and Karmic.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart
** Branch linked: lp:~jamesodhunt/ubuntu/natty/gdm/single-user-to-multi-
user-mode-fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks
Fix tested on natty only at this stage.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't start
on
** Changed in: kdebase-workspace (Ubuntu Natty)
Milestone: karmic-updates = ubuntu-11.04-beta-1
** Tags added: kubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
** Changed in: gdm (Ubuntu Natty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single
** Branch linked: lp:~jamesodhunt/gdm/ubuntu-desktop-single-user-mode-
fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single
** Changed in: gdm (Ubuntu Maverick)
Assignee: (unassigned) = James Page (james-page)
** Also affects: gdm (Ubuntu Natty)
Importance: Medium
Status: Triaged
** Also affects: kdebase-workspace (Ubuntu Natty)
Importance: Medium
Status: Triaged
** Changed in: gdm (Ubuntu
** Also affects: gdm (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: kdebase-workspace (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: gdm (Ubuntu Maverick)
Importance: Undecided
Status: New
** Also affects: kdebase-workspace
This bug is still present in Lucid.
It is exacerbated by the fact that recovery mode offers a resume
option which is supposed to return the machine to its normal state.
However, since recovery mode is single user mode, gdm never starts.
It would be great if this was finally fixed in Natty,
So based on some digging, I don't think the issue here is actually the
one described, at least not immediately.
Booting with single in /proc/cmdline causes the system to emit the
runlevel S event (read switch to runlevel S if you don't feel like
thinking Upstart-y). When the user exits out of the
Of course, once something does actually trigger the gdm job to run (with
the exception of doing start gdm directly), that will still trigger
command-line inhibition code originally described in this bug, so we
would still need to do something about that.
--
You received this bug notification
** Summary changed:
- gdm upstart job checks /proc/cmdline for single user mode, won't dtrt on
post-boot runlevel change
+ gdm upstart job checks /proc/cmdline for single user mode, won't start on
post-boot runlevel change
--
gdm upstart job checks /proc/cmdline for single user mode, won't
62 matches
Mail list logo
