On Sat, 2010-01-09 at 16:33 +, Martin Pitt wrote:
> Robert, nice catch! Indeed that makes absolute sense. I committed the
> waiting for D-Bus
>
> http://bazaar.launchpad.net/~ubuntu-desktop/gdm/ubuntu/revision/186
>
> and booted three times in a row, now it starts perfectly again.
>
That
Still a problem in -10.
--
gdm starts too early, X.org/VTs fail
https://bugs.launchpad.net/bugs/502838
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
desktop-bugs@lists.ubuntu.com
https://lis
This bug was fixed in the package gdm - 2.29.4-0ubuntu2
---
gdm (2.29.4-0ubuntu2) lucid; urgency=low
* debian/gdm.upstart: Wait for D-Bus to be ready, to avoid failure if gdm
starts too early. Thanks to Robert Hooker! (LP: #502838)
-- Martin PittSat, 09 Jan 2010 17:34:43 +0
Robert, nice catch! Indeed that makes absolute sense. I committed the
waiting for D-Bus
http://bazaar.launchpad.net/~ubuntu-desktop/gdm/ubuntu/revision/186
and booted three times in a row, now it starts perfectly again.
** Changed in: gdm (Ubuntu)
Status: Incomplete => In Progress
**
** Branch linked: lp:~ubuntu-desktop/gdm/ubuntu
--
gdm starts too early, X.org/VTs fail
https://bugs.launchpad.net/bugs/502838
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
desktop-bugs@list
Ahh sorry about the noise then, I assumed it worked because I didn't get
dropped to the login prompt for 6 boots after removing it and that was
pretty much unheard of. I should play the lottery today :) Thanks for
digging into it more though, seems like you have identified the problem.
Do you have
Robert, removing /lib/udev/rules.d/40-xserver-xorg-video-intel.rules
didn't fix it for me. Same thing as before, gdm-binary unable to connect
to the system bus and bailing out because of it.
--
gdm starts too early, X.org/VTs fail
https://bugs.launchpad.net/bugs/502838
You received this bug notif
Removing /lib/udev/rules.d/40-xserver-xorg-video-intel.rules seems to
have fixed the problem here.
Its contents:
# do not edit this file, it will be overwritten on update
# Jesse Barnes on ubuntu-de...@lists.ubuntu.com:
# You'll get three events, one when the error is detected, one before the
According to dbus.conf and gdm.conf they both start at roughly the same time if
no remote filesystems are to be mounted.
Sometimes dbus is fast enough and sets itself up before gdm, sometimes gdm is
faster. When gdm starts and dbus is not yet ready, it just bails out (see
gdm-2.29.4/daemon/main.
I redirected gdm's output to a logfile in /etc/init/gdm.conf (since it
wasn't logging anything anywhere when it failed), this is what I get
when it fails to start:
** (gdm-binary:1261): WARNING **: Couldn't connect to system bus: Failed
to connect to socket /var/run/dbus/system_bus_socket: No such
Argh, this is an utter pain to debug, but that's what I found out:
* When this happens, gdm only writes a "failsave.log" with a single
number in it. No other logs.
* Wrapping gdm-binary into strace in the upstart script introduces
enough slowdown to make gdm startup succeed. Yay heisenbug.
*
I seem to have the same issue.
But I have the VT for a longer time, some messages about readahead and /home
being clean, then gibberish.
But I even do net get readable output on my attached 2nd Monitor - only
gibberish on my netbooks monitor. The system is not unresponsive as the
contents chang
12 matches
Mail list logo
