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 so
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 tt
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 bootchar
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
https://bugs.launchpad.
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
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!?!
>
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
https://bugs.launchpad.net/ubuntu/+sourc
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 becau
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
Y
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 db
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
https://
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"
GRUB
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"
https://bugs.launchpad.n
@John: Yes, I'm running apache. I don't see a way for me to test Dino's
bug 626723 on my Lucid machine. That bug appears to have a proposed fix
for Maverick. Also, the suggested workaround doesn't make sense on Lucid
--there is no "stty sane" line in my /etc/init.d/apache2.
--
X starts on wrong t
@dino99: These crashes definitely seem to correlate with the fastest
systems. Myself and a few others with the bug have SSD, 8 GB and fast
processors.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification becau
Okay, the crash from tty7 happened twice in a row, after reboots, for
me. I now see that I'd changed two different variables when I thought
the simple "plymouth:debug" was acting as a workaround. I'd also changed
these lines in /etc/default/grub, to allow me to catch grub and test
boot parameters (
New crash for me, possibly a fluke. I reverted my /etc/default/grub to
simply use the plymouth:debug on the boot line as a workaround, and also
reverted my /etc/init/gdm.conf (after trying Seth's workaround). My next
reboot looked normal, and X was on tty7, but I crashed very quickly, and
not when
Okay, I've tested Seth's patch to /etc/init/gdm.conf from
https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/532047/comments/91
I first changed my /etc/default/grub back to basics and ran update-grub
(so, a state that would normally cause this bug to occur after boot). I
did not notice a
@John, my /var/log/dmesg file...
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1563870/+files/dmesg
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received t
@John, my /var/log/udev file...
** Attachment added: "udev"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1563869/+files/udev
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this
@John,
Thanks again for keeping us moving. To the best of my
ability/understanding, your theories are sound to me, FWIW! Here's some
more info, as requested:
(a) My /var/run/gdm/firstserver.stamp does have a time matching my most
recent boot.
(b) I searched all of my /var/log/Xorg.* files for "n
@dino99: I installed updates this morning, which included the mountall
update for Lucid. I rebooted, but still ended up with X on tty2, and
crashed to the login screen after about 30 minutes of bouncing around in
Chrome browser tabs.
--
X starts on wrong tty: pressing enter after 5 minutes crashe
John, I've attached ps aux output while X is on tty2 (this is usually
what happens, but occasionally tty1--eventual crash in both cases).
Thanks.
** Attachment added: "ps.out"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1560408/+files/ps.out
--
X
@John,
Yes, the first plymouth-debug.log was generated the first time I added
"plymouth:debug" to the boot line, but I had a freeze on the splash screen and
powered off. When I booted again without plymouth:debug I found that log file
there, so it obviously generated that prior to the freeze and
@Carl,
Those grub resolution settings wreak havoc on me. I booted to vt2, so logged
out, logged in, on vt8. Then, for the first time ever, I had the X reset after
a logout/login cycle (some logs attached for this). Shortly thereafter, I had
yet another crash, and these did not seem to be related
@Seth: Oddly, I don't think my laptop has a scroll lock light, so I
can't confirm or deny that correlation. I honestly don't quite
understand your workaround in #91, sorry. And sorry if my comments got
verbose--I'll try to keep them succinct ;-) I'm a bit over my head, but
I'm doing my best to prov
More test results, log, and another workaround:
- booting with "plymouth:debug" added to boot line, but "quiet splash" removed,
results in booting to VT7 every time, and no crashes (sample plymouth debug log
attached).
- booting with "quiet plymouth:debug" (but no "splash"), same results--boots t
@Seth: Are you also watching bug #625239? This is where I've posted all
of my feedback, and there is active work going on there. It's difficult
for me to be certain of whether we're experiencing the very same bug or
not. I'm also on Lucid, nvidia-current, current updates and on a fast
machine, and
John:
Unfortunately, I don't seem to have an Xorg log for yesterday's crashes. I'll
try to be more diligent about grabbing those, but I had some quick unexpected X
crashes when experimenting with grub settings yesterday. I do have a bunch of
logs dated for yesterday under /var/log/gdm/, but I do
I tried editing the boot line from the grub menu and added
plymouth:debug to the end, but then the boot just froze at the splash
screen. I was unable to switch to another VT or find any way to get rid
of the splash screen, so had to do a hard power off. It did, however,
produce a debug log file, wh
** Attachment added: ":2-slave.log.1"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1557212/+files/%3A2-slave.log.1
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notif
** Attachment added: ":2.log.1"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1557211/+files/%3A2.log.1
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification beca
I reproduced the bug and will now attach these three files, which all had the
time stamp of the crash/reset to GDM login screen (and as usual, was on VT1
after boot, then VT8 after crash and second login):
/var/log/Xorg.2.log.old
/var/log/gdm/:2.log.1
/var/log/gdm/:2-slave.log.1
** Attachment ad
@Carl: I'm sorry to say that your suggested changes to /etc/default/grub
did not work for me. I noticed that 1920x1080 was not listed when I
tried the vbeinfo command from a GRUB command prompt, as suggested in
GRUB2 docs/help. I also tried a resolution that *is* listed as supported
for me, 1280x80
Okay, I've done some experimenting with my linux command options. If I
have vga=799 on there, I boot to tty7 every time. With or without the
"quite" and/or "splash" options, I see the same results. However, when I
tried vga=771, I end up on tty1 or tty2 again.
So, for whatever reason, this line in
Doh! Sorry for the confusion, I was just looking for /etc/grub/default
instead of /etc/default/grub. I'll have another cup of coffee and try
this again ;-)
On another note, in an effort to get that file back (the one that I'd a
mistaken path for, which was there all along), I installed
startupmana
Steve: I've always modified /etc/grub/default in the past, as suggested here:
https://wiki.ubuntu.com/Grub2#grub (/etc/default/grub)
...and in `cat /etc/grub.d/README`:
All executable files in this directory are processed in shell expansion order.
00_*: Reserved for 00_header.
10_*: Native boo
FYI: In an attempt to keep my environment as clean as possible, I've removed
the ppa:ubuntu-x-swat/x-updates repo, which I'd added earlier in an attempt to
fix this issue (http://ubuntuforums.org/showthread.php?t=1545846). Since this
did not work, I've removed it and reinstalled my nvidia-curren
Breaking news! John, I think you're definitely on to something with your
idea of this being a race condition. When I just rebooted, the periodic
disk check ran (at the splash screen, essentially), so I paid close
attention, remembering the race condition hunch. I noted that there was
no flicker bef
John, here's the version info you requested:
gdm 2.30.2.is.2.30.0-0ubuntu3
upstart 0.6.5-7
plymouth 0.8.2-2ubuntu2
nvidia-current 256.52-0ubuntu0sarvatt3~lucid
Next I'll reboot with plymouth debugging and post some logs...
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https:
Okay, this is really strange--I suddenly have no /etc/grub/ directory.
I've edited /etc/grub/default before, and I'm certain I had a couple
backup files in there too. Any thoughts???
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You rece
@John: Thanks very much for helping this along.
I watched very closely when I booted this morning, and I'm certain that I'm
seeing a flash of a text screen just after the Ubuntu splash, but before the
GDM login screen, and I'm certain that it is showing this message near the top:
"GLib-WARNING *
@John:
I do see a splash screen. Everything is relatively quick, as I have an SSD in
my new System76 laptop :D I see a blank screen with a blinking cursor, followed
by a quick flicker to the splash screen, followed by another
blank-screen/flicker, and then the login screen. I think there's a ver
Steve,
I have X running on VT1 or VT2 after every reboot, and I always
eventually have X crash on me when pressing Enter (but never the first
pressing of Enter).
--
Pressing Enter crashes both X and plymouth in graphical mode
https://bugs.launchpad.net/bugs/625239
You received this bug notificat
@John:
Synaptic shows plymouth 0.8.2-2ubuntu2.
--
Pressing Enter crashes both X and plymouth in graphical mode
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
FYI: I've posted a comment on bug #625239, as suggested by John on bug
#529230.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xor
After spending hours pouring over Google results and bug reports like
bug #529230 and bug #532047, I believe this is the bug I'm seeing on my
Lucid (Ubuntu 10.04 64-bit on a new System76 Serval Pro--serp6) laptop.
I have a decent amount of information to share, which corroborates this
bug, and I've
Sorry if this is not the right bug to comment on, but I spent hours yesterday
just trying to figure out where I should be commenting. I just commented on bug
#529230 (comments 21 and 22) because that seems the best fit, but it's listed
as a duplicate of this bug. This bug's description does not
48 matches
Mail list logo
