*** This bug is a duplicate of bug 615549 ***
https://bugs.launchpad.net/bugs/615549
@Jamie:
Looks like Martin is taking care of it in #615549. If I recall correctly, it
will be (has been?) uploaded to the proposed queue and, after testing, it will
be released to Lucid.
--
X starts on
*** This bug is a duplicate of bug 615549 ***
https://bugs.launchpad.net/bugs/615549
On 09/20/2010 03:39 PM, John S. Gruber wrote:
*** This bug is a duplicate of bug 615549 ***
https://bugs.launchpad.net/bugs/615549
@Jamie:
Looks like Martin is taking care of it in #615549. If I
*** This bug is a duplicate of bug 615549 ***
https://bugs.launchpad.net/bugs/615549
** This bug has been marked a duplicate of bug 615549
Dell Studio XPS 13 no video
* You can subscribe to bug 615549 by following this link:
Forgive me if I'm missing something, but based on comments from Martin
and Steve, and Seth's thorough testing reported in comment #159, my
understanding is that I should simply wait for the bug #615549 fix to be
back-ported to Lucid. Is this correct? Should I be updating bug #615549
for Lucid in
This sounds a lot like bug 615549 which was fixed yesterday. Is this
still an issue with gdm 2.30.5-0ubuntu4?
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
On Wed, Sep 15, 2010 at 06:55:49AM -, Martin Pitt wrote:
This sounds a lot like bug 615549 which was fixed yesterday.
Yep, sounds like exactly the same bug.
Is this still an issue with gdm 2.30.5-0ubuntu4?
So far the only test on maverick from someone who's confirmed to see this
bug on
On Tue, Sep 14, 2010 at 03:49:25PM -, Jamie Krug wrote:
The graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1 removal
tweak is not a guaranteed workaround after all. I just booted up again
and crashed within a minute of use. I was just waiting for a Chrome tab
to open--no keyboard
On 09/15/2010 07:23 AM, Steve Langasek wrote:
Can you include the gdm/X logs from these sessions, showing why it reset so
quickly - just to be absolutely certain of what we're seeing?
Good call. I've reviewed all leftover Xorg logs and there were no (EE)
messages, particularly note related
On 09/15/2010 03:02 AM, Steve Langasek wrote:
Actually, there might be an easier way. Could you boot with '--verbose'
added to the boot options, and attach the resulting /var/log/syslog?
Will do later tonight
--
X starts on wrong tty because gdm starts before nvidia driver is ready
Seth [2010-09-15 7:53 -]:
I will keep running with the modded upstart condition (which
incidentally matches the one from maverick, I believe?):
Correct.
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
You received this bug
On 09/15/2010 09:17 AM, Steve Langasek wrote:
So far the only test on maverick from someone who's confirmed to see this
bug on lucid has failed to reproduce the problem there, even /without/ the
new gdm package. Nevertheless, I think there's enough information here to
mark this as a duplicate
On 09/15/2010 03:02 AM, Steve Langasek wrote:
Actually, there might be an easier way. Could you boot with '--verbose'
added to the boot options
Would that go into grub config? I'm not used to seeing --flags on the
kernel param line?
--
X starts on wrong tty because gdm starts before nvidia
Steve Langasek wrote in #150:
Thanks. Could you now provide the same files when *not* booting with this
workaround?
Yes, the attached archive contains two sets of logs, both without
vga=799 or any other workaround in place. One has quiet splash
appended to the boot line, which landed X on tty2
for info, I have deleted ppa:bugs-sehe/gdm625239 because I don't think
it is relevant anymore. The patch is still available for reference in
comment #109
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
You received this bug
Confirming on Maverick, but before changing the status, is there any
other information you would like me to report?
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of
On Wed, Sep 15, 2010 at 06:32:41PM -, Mohamed Amine IL Idrissi wrote:
Confirming on Maverick, but before changing the status, is there any
other information you would like me to report?
Confirming with what version of gdm? The latest version of gdm in maverick,
2.30.5-0ubuntu4, is believed
has anyone reproduced this nvidia+gdm crash on maverick? Marking
incomplete for maverick pending confirmation.
** Description changed:
+ This bug has been repurposed based on the comments beginning at #15.
+ The original submitter's bug was a duplicate of bug #626723.
- After the system
BTW, the maverick problem that I reported was actually affecting the
apache2 package (bug #626723), which was setting incorrect stty flags
for the tty* which would make X crash on pressing the enter key.
I just wanted to tell you people to see if it helps in some way.
--
X starts on wrong tty
@Steve
Seth, Jamie, can one of you also show the output of 'grep fb
/var/log/kern.log' on a system showing this problem?
can try, but I'll have to downgrade from my own ppa version first so be
patient :) (tomorrow night perhaps)
--
X starts on wrong tty because gdm starts before nvidia driver
@Steve
PS. the description no longer reflects that people with ATI cards have
reported this issue (have I misread the comments or did you miss that?)
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
You received this bug
Steve,
Please show the contents of a plymouth:debug log, and /proc/fb, when
booting with vga=799 (and without grub_gfxmode set).
Attaching /var/log/udev, /var/log/plymouth-debug.log and /proc/fb after boot
with no GRUB_GFXMODE set and:
GRUB_CMDLINE_LINUX_DEFAULT=vga=799 plymouth:debug
Steve,
Seth, Jamie, can one of you also show the output of 'grep fb
/var/log/kern.log' on a system showing this problem?
Attached, after boot with standard configuration (no workarounds or
related custom config at all).
** Attachment added: kern.log-grep-fb.out
Steve,
I meant to confirm that the boot that produced the output file attached to
comment #127 did indeed land me with X on vt2, and I did crash, as expected,
after a few minutes, when pressing enter in Terminal.
--
X starts on wrong tty because gdm starts before nvidia driver is ready
Here is my complete kernel.log since last reboot, just after downgrading to the
regular gdm package for lucid (no workarounds).
You can do your own greps if you wish :)
---
Now if someone is ever interested in more
Steve,
You might also be able to confirm this is the problem by commenting out
the graphics-device-added fb0 part of the start condition.
Okay, testing with standard disto version of /etc/default/grub and the
following in my /etc/init/gdm.conf:
start on (filesystem
and started dbus
On 09/14/2010 05:09 PM, Jamie Krug wrote:
Steve,
You might also be able to confirm this is the problem by commenting out
the graphics-device-added fb0 part of the start condition.
Okay, testing with standard disto version of /etc/default/grub and the
following in my
Seth,
So let me get this straight, you just removed the graphics-device-added
fb0 PRIMARY_DEVICE_FOR_DISPLAY=1 disjunction?
Yes, that is exactly what I did, and nothing else.
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
You
Steve, Seth,
The graphics-device-added fb0 PRIMARY_DEVICE_FOR_DISPLAY=1 removal
tweak is not a guaranteed workaround after all. I just booted up again
and crashed within a minute of use. I was just waiting for a Chrome tab
to open--no keyboard activity this time.
--
X starts on wrong tty
On Tue, Sep 14, 2010 at 07:58, Steve Langasek
steve.langa...@canonical.comwrote:
has anyone reproduced this nvidia+gdm crash on maverick? Marking
incomplete for maverick pending confirmation.
On my system, this bug was fixed.
--
X starts on wrong tty because gdm starts before nvidia driver
On Tue, Sep 14, 2010 at 08:21:09AM -, Seth wrote:
PS. the description no longer reflects that people with ATI cards have
reported this issue (have I misread the comments or did you miss that?)
The only comments in this report from someone seeing issues on ATI are from
the original
On 09/14/2010 06:47 PM, Steve Langasek wrote:
On Tue, Sep 14, 2010 at 08:21:09AM -, Seth wrote:
PS. the description no longer reflects that people with ATI cards have
reported this issue (have I misread the comments or did you miss that?)
The only comments in this report from
On 09/14/2010 05:49 PM, Jamie Krug wrote:
no keyboard activity this time.
Erm... perhaps this is a different bug? Did you inspect the log(s) to
see what aborted X?
--
X starts on wrong tty because gdm starts before nvidia driver is ready
https://bugs.launchpad.net/bugs/625239
You received
I seem to have discovered a slightly new style of crashes, which I believe have
only occurred when I have a modified /etc/init/gdm.conf file. Yesterday and
today I've witnessed this new crash behavior with both:
* Seth's /etc/init/gdm.conf workaround from
On 09/14/2010 07:50 PM, Jamie Krug wrote:
I seem to have discovered a slightly new style of crashes, which I believe
have only occurred when I have a modified /etc/init/gdm.conf file.
May I suggest _not_ tweaking your gdm.conf in that particular way then?
change nothing else. I'm pretty
I just noticed there is a slightly cleaner approach to the source
manipulation fu:
sudo apt-add-repository ppa:bugs-sehe/gdm625239
and vice-versa:
sudo rm -fv /etc/apt/sources.list.d/bugs-sehe-gdm625239-lucid.list
--
X starts on wrong tty because gdm starts before nvidia driver is
Seth,
May I suggest _not_ tweaking your gdm.conf in that particular way
then?
Yes :) I did so only as a workaround, but obviously that was not stable.
I also just discovered that the same crashes can now occur even with a
untouched gdm.conf. Possibly a different bug, sure, but I hope not!?!
On 09/14/2010 05:19 PM, Seth wrote:
This could be brittle, because all this could do
is reduce the time window for the race condition to happen
I can confirm my suspicion to be right because after - granted: many-
some reboots I saw the log message again in successive reboots:
On 09/14/2010 09:28 PM, Jamie Krug wrote:
BTW, I just disabled my nVidia drivers, so I could at least post an
update without crashing, and I noticed that my boot was notably MUCH
faster. I'll be curious to see if I notice the same with your fix. Off
to apply your patch. Thanks!
If you are
Seth, thanks for the additional workaround. I've applied your patch from
ppa:bugs-sehe/gdm625239 and all has been well for about an hour. My boot
time seemed a little slow again, after re-enabling my nVidia drivers,
but I can live with that if I have a stable X session! I will report
back if I see
On 09/14/2010 10:16 PM, Jamie Krug wrote:
Seth, thanks for the additional workaround. I've applied your patch from
ppa:bugs-sehe/gdm625239 and all has been well for about an hour. My boot
time seemed a little slow again, after re-enabling my nVidia drivers,
but I can live with that if I have a
Seth,
I just installed bootchart, rebooted and had 2 quick crashes (with your
patch installed). I only see black screen when switching tty, so unable
to check out logs so far. I'll report back soon.
--
X starts on wrong tty because gdm starts before nvidia driver is ready
Seth,
With just a couple bootcharts, it appears I take 4 seconds longer to
boot with nVidia drivers enabled. Also, despite having an extremely fast
machine, your boots were about 400% faster than mine! I've attached the
two, in case they're of any interest.
Is there any reason installing
@Steve:
I've taken the trouble to install maverick beta (64bit). I installed on
the same iron, same disk configuration (2x SSD in raid0, lvm2 root).
After doing the server install I installed ubuntu-desktop and bootchart.
My few boots took max 5.71s in bootchart (woah) and all my X desktops
were
Hi Seth,
On Wed, Sep 15, 2010 at 12:25:13AM -, Seth wrote:
So that seems to imply that the problem does not manifest itself on
maverick (yet). However, since we have such good understanding of the
triggering events I decided to check with my force.sh (forced
reproduction script from
On Tue, Sep 14, 2010 at 02:23:31PM -, Jamie Krug wrote:
Attaching /var/log/udev, /var/log/plymouth-debug.log and /proc/fb after boot
with no GRUB_GFXMODE set and:
GRUB_CMDLINE_LINUX_DEFAULT=vga=799 plymouth:debug
GRUB_CMDLINE_LINUX=
Thanks. Could you now provide the same files when
On Tue, Sep 14, 2010 at 02:24:22PM -, Jamie Krug wrote:
Seth, Jamie, can one of you also show the output of 'grep fb
/var/log/kern.log' on a system showing this problem?
Attached, after boot with standard configuration (no workarounds or
related custom config at all).
** Attachment
On Tue, Sep 14, 2010 at 07:38:49PM -, Seth wrote:
This could be brittle, because all this could do
is reduce the time window for the race condition to happen
I can confirm my suspicion to be right because after - granted: many-
some reboots I saw the log message again in successive
47 matches
Mail list logo
