Jamie,
> 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.
Please show the conte
** Description changed:
- Binary package hint: xorg
- After the system boots and the plymouth screen disappears and X starts
- up, if I press the enter key (occurs only with the enter key) X shuts
- down and starts again in around 2 seconds. In the session of X that
- comes up after this, the p
** Tags added: patch
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
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
http
Oh PS. all, because I'm starting to feel this workaround is looking
pretty good[1] in my own (humble) opinion - functionally - I wish to
point out that this is probably best integrated directly into an altered
05_initial_server_on_vt7.patch instead of adding another patch.
My patch (40_initial_ser
The timestamps from those logfiles (#118) were
r...@lucid:/tmp# ls -ltr --full-time var/log/
total 32
-rw-r--r-- 1 root root 6399 2010-09-11 00:14:15.0 +0200 Xorg.1.log
-rw-r--r-- 1 root root 6399 2010-09-11 00:14:15.0 +0200 Xorg.0.log
-rw-r--r-- 1 root root 13404 2010-09-11 00:1
** Attachment added: ""synthetic" retest of gdm X respawn on nvidia not ready"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1568079/+files/retest_logs.tgz
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net
Thanks for the hint. Very timely.
I just learned that some things are best not kept on tmpfs, especially
when doing frequent reboots
I sort of forced the issue just to prove that the mechanism works as
advertised by doing
chvt 1
stop gdm; sleep 1; rm -fv /var/log/Xorg.*
# emulate a fresh boot.
In syslog you might find messages like:
gdm_binary[2542]WARNING: GdmDisplay: display lasted 0.945450 seconds
Those are the ones Jamie has coming out quickly. I only get one when I start.
It may be easier to look for those than to look at the log files.
--
X starts on wrong tty: pressing enter af
> Sounds like you are close to the limit
Yeah in retrospect I can't be to sure I haven't been counting logs from across
reboots there; I had been rebooting like hell before it dawned on me that I
would need to look at the logfiles to find out whether the 'early X failure due
to nvidia not ready'
@Seth:
I just saw that I missed several of your messages above. In particular 98 and
99. I'm sorry. Before I say it you coded it and had it building on launchpad.
Great.
I see no problem with your code. I built your change here and am running
it successfully. Since I didn't see the bug I can't s
@Jamie: Rats.
We don't need the plymouth:debug anymore. Would deleting it help? Can
you simply go back to where you were last night when you were getting
logs (albeit with the tty1 bug). If you can, maybe you can try Seth's
new gdm fix.
modeset and nomodeset are other possible things to try (I ca
@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
Dammit! Launchpad ate my comment with #109... Ok, typing it up again
I think I have a fix that I like. I added a debian patch
(40_initial_server_on_vt7-improve-timing.patch see #109)
What happens is that I moved the creation of the signal file
(/var/run/gdm/firstserver.stamp) to the emit_ready_i
@Gruber: duh... our posts crossed. Consider my patch a response :)
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Patch added: "proposed test patch"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1567308/+files/40_initial_server_on_vt7-improve-timing.patch
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/62523
@Bilal:
Congratulations.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
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
@Jamie: One of the earlier X logs you posted had an error that ended
like that--without giving any backtrace.
I see you are running apache. Does Dino's have your fix?
Sounds like our fraternal twin bug may have been fixed since Bilal
confirmed it is gone. Great catch, Dino. It also sounds like vt
@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
might be fixed due to bug 626723 solution (apache)
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
hello guys,
i'm reading your posts with interest, as my system boot and log as it
might now, here is grub settings:
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
what i see when booting and logging is that hdd activity have not ended
when i validate my password login, so i
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
@Jamie:
Great! That's confirmation that gdm is starting too early relative to the
tty's. and helps confirm similarity of your situation with Seth's.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification becaus
@Seth:
I don't believe initctl passes a VT parameter. gdm is either starting X with a
VT parameter, or not. It determines whether plymouth is running and if it is,
and if it has its screen before the user, gdm tries to determine what VT that
is and specifies that to X in a VT parameter. If that
ne'er mind I found it in gdm-server.c (05_initial_server_on_vt7.patch)
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Wouldn't it simply appear that /var/run/gdm/firstserver.stamp is simply
created prematurely...?
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Gruber
No I don't think my xorg.conf is involved.
Now on the ps -aux output: I can confirm that when X startup is 'sane'
(works first time around) then the vt7 param is indeed passed. If X ends
up on vt2, it is not:
/root$ ps -ef | grep X | tee -a vts.log
root 1274 1252 0 16:57 tty2
@Brian
This bug was split at about comment 30. We have been working on the case where
the X crash happens some time after login because it has been started on tty1.
Bilal's case start on tty7 is now being discussed in bug #626723. I feel a
little bad that we aren't discussing his situation but t
Hi all. I'm glad my findings helped.
For me, I learned from your comments: I wasn't even aware of the fact
that initctl supplies a VTx parameter to gdm on first launch. That
certainly explains how things go haywire _after_ on quick relaunch(es).
I will post later with more information about the ac
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
I'd like to point out that this isn't just an nvidia bug. It was
originally filed for an ati card, and I'm seeing the problem with intel
graphics. It's most likely a kernel/VT bug.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You receiv
hello dear bug fighters,
dont want to make you sad, but all is fine on my end.
@Seth,
i'm very surprised to see such xorg.conf on your system: ok you use a crt and
need to add refresh rates (maybe, not sure by the way as i'm also using a crt
and nvidia-current detect it without additional setti
I don't see any errors in the dmesg log and it looks like the nvidia
kernel module is ready rather late in that log. Looking at the udev log
I would guess that the module isn't loaded any sooner than about .31
seconds before the last entry in the udev log (if I'm reading it
correctly).
@Seth:
*IF*
@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
@Jamie,
It's my pleasure to work with you all.
Would you mind posting your /var/log/udev file and /var/log/dmesg file?
It probably doesn't matter when they are collected relative to when the
bug occurs.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.ne
@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
So here is a theory for Seth and Jamie's case:
gdm starts its race with the tty's before the nvidia software is really
ready for X.
Plymouth is running and gdm starts up, hand shakes with plymouth. Starts
X.
Gdm in the handshake tells plymouth to quit and it does.
X crashes because it is too ea
Seth:
That is simply wonderful.
One of Jamie's logs from comment 62 says:
(**) Sep 07 22:16:47 NVIDIA(0): Enabling RENDER acceleration
(II) Sep 07 22:16:47 NVIDIA(0): Support for GLX with the Damage and Composite X
extensions is
(II) Sep 07 22:16:47 NVIDIA(0): enabled.
NVIDIA: could not open
For completeness, my xorg.conf so you can see details on loaded modules,
devices and monitor setup. Just in case you wonder whether I
misconfigured my keyboard (which is PS/2) as a Power Button (LOL)
** Attachment added: "xorg.conf"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
Ok two more things:
(a) strike the comments about garbling: this just happens when I switch to a
text console too quickly after gdm starts (so the video is probably still
initializing?). It also happens when X is nicely on vt7 and it doesn't happen
with X on vt2, but with enough delay before sw
Must. Remember. Attach. File.
** Attachment added: "Xorg logs from the described session"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1563400/+files/Xorg_logs.tgz
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.laun
Heya, that turned quite some interesting information.
I think (and hope) you may find these Xorg logs very interesting, as they
certainly surprised me, which is why I attach all the four described log files.
(Rest assured, 3 are tiny).
Here is what happened:
first of I had a number of reboots
Ok, joining here by Gruber's request from #532047. I have temporarily
removed my workaround from my comment #91 there, so I'm testing against
a 'standard' lucid install on a very fast booting system with i386
generic-pae, 8Gb RAM, Q9550 and nvidia-current.
(a) adding plymouth:debug affects timing
Hi Dino
Thanks for the information. That's good about firstserver.stamp.
>From the ps.out I assume that the bug is still gone on your system since
X started on tty7. If it ever fails again (starting on tty1-tty6) that
time stamp, the output of ps before X crashes, and, if possible, the
output in /
hello John,
some readings for you !!
o...@dub:~$ sudo ls -l /var/run/gdm/firstserver.stamp
[sudo] password for oem:
-rw-r--r-- 1 root root 0 2010-09-09 16:03 /var/run/gdm/firstserver.stamp
--> time is ok with my last logging
** Attachment added: "ps.out"
https://bugs.launchpad.net/ubunt
It would be great if anyone else having the problem could post the
output from the ps command on their system while they are running X on
tty1 through tty6.
@Dino:
That's great news!
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You rec
@Dino
Could you attach the output from ps as Jamie did? If it starts happening again
perhaps you can do the same again during a session you expect to crash?
@Jamie and Dino
Could you look again at that file creation time?
sudo ls -l /var/run/gdm/firstserver.stamp
It should exist and be empty, i
hi Jamie,
good news on my end: since #72 and its tweaks, my issues are gone, now
gdm logging is ok, tested several reboots along this day and no problem.
So i might conclude that old (udev) conf was breaking this gdm/X stuff,
dont know exactly where to find the good explanations as i've
purged/r
@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
maybe some good news:
http://www.ubuntuupdates.org/packages/show/216647
in the past few hours we have had some fixing about apt too, so there is
some hope about better conf.
i've made some more tweaks: purging/reinstalling gdm plymouth jockey
apt-xapian and updating packages ( my issues are only
It's a shame about the crash getting in our way, but oh well. I don't
see anything in the log either, sad to say. the acpid messages at
10:00:17 are from an unrelated daemon that tells interested processes on
your computer about closing the lid, etc., if I'm not mistaken.
Could you recreate the si
@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
@Jamie,
Do you remember how you got the first log?
Could the log you posted be from some time it hung? If it's complete it
does look like plymouth crashed. For the crash situation does anything
get recorded in the plymouth-debugging log?
Maybe we should look in your /var/log/syslog from the time
@Carl,
Dino99 has the problem with Maverick.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
@Jamie,
I tested a Serval with a full 1080p HD LCD (1920x1080). Interestingly,
1600x900x32 provides a clean splash screen and starts on VT7.
GRUB_GFXMODE=1600x900x32
GRUB_GFXPAYLOAD_LINUX=1600x900x32
Also, it appears this bug is fixed in Maverick. However, the splash
screen when using nVidia's p
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
Thanks for sticking with this even though you guys have found
circumventions. If someone can fix this without adding boot parameters,
etc. -- if it just works-- it will be better for many Ubuntu users.
@Jamie:
It looks like :2.log.1 is what I would expect for the bug we have been
hunting. It was
have a backtrace on gdm fallback
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/maverick/+source/plymouth/+bug/625239/+attachment/1557756/+files/Xorg.0.log.old
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
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
** 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
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
Jamie and Dino:
If I understand, you each reported a problem with an X crash when X had
already crashed. As Dino pointed out, that's very different. Would you
please post the failing Xorg log? You can probably figure out which one
by the time on the file.
--
X starts on wrong tty: pressing enter
** Also affects: plymouth (Ubuntu Maverick)
Importance: High
Status: Confirmed
** Also affects: xserver-xorg-video-ati (Ubuntu Maverick)
Importance: Medium
Status: Invalid
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/62523
new test: booting without "vga=xxx quiet splash"
it give the same issues:
- first login fail and reset numlock
- second login usually works, except this time (few minutes ago) it crashed
(fall back to gdm) while writing a previous comment, but without resetting
numlock
so, what i think is:
- a
@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
Cool, Jamie. I'm glad you found a work-around, and I appreciate your
kind offer to post the logs later. I'd like to see how they match up
with dino's, both with regard to the messages dino saw in his plymouth
log post, and with regard to the little dance gdm and plymouth do to
keep on the same VT7
Hi Jamie,
Great find! With vga=799 my Serval boots on vt7 every time. As you noted
vga=799 is depreciated and replaced by gfxpayload. You can have the
correct boot image and start on VT7 by adding the following lines to
/etc/default/grub and then "sudo update-grub".
I have tested this on the
hi John,
have you seen errors logged into # 36 ? seem interesting to digg around
the libs issues
to Jamie: please stay tuned to this report subject only, launchpad isn't
a forum or chat.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
Yo
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
Our comments crossed. Sorry.
Please take your time and only do things you are ok with.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I don't have /etc/grub/default either. I do have /etc/default/grub. The
file names are confusing.
I see no reference to the former in update-grub or grub-mkconfig, but
grub-mkconfig includes the contents of /etc/default/grub. Are you
missing /etc/default/grub?
I sometimes get nervous about grub,
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
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
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
On Tue, Sep 07, 2010 at 05:59:47PM -, Jamie Krug wrote:
> 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???
This is /boot/grub, not /etc/grub.
--
Steve Lan
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
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, 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:
On Tue, Sep 7, 2010 at 10:53 AM, dino99 <625...@bugs.launchpad.net> wrote:
> hi Jamie,
> have done it by editing the boot line (E) into grub menu ( added at end of
> quiet splash ) then boot (ctrl+x)
Yep. That's what I do, too. As soon as the grub menu appears I move the
arrow to the item I want
hi Jamie,
have done it by editing the boot line (E) into grub menu ( added at end of
quiet splash ) then boot (ctrl+x)
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
B
@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 *
merci, Dino
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
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://lists
r...@dub:/var/run/gdm# ls
auth-for-gdm-tIW1mo auth-for-oem-Z9n9W2 firstserver.stamp
firstserver.stamp is an empty file
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
some errors seen into debug.log
** Attachment added: "plymouth-debug2.log"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/625239/+attachment/1552650/+files/plymouth-debug2.log
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
Y
** Attachment added: ":0-greeter.log"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/625239/+attachment/1552621/+files/%3A0-greeter.log
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification becaus
hi John,
here are your #33 requests:
my system:
home made desktop: p5wdh+q9550+8500gt+4go ddr2+2pata+1sata
os: maverick i386 with latest main server updates (35-20-generic-pae)
packages: plymouth 0.2.8.2-2ubuntu3, gdm 2.30.5-0ubuntu2, upstart 0.6.6-3,
nvidia-current 256.53-0ubuntu2
note: compi
@Jamie:
Since I'm only another member of the community it's completely possible
that I won't be able to see this through to a fix. A glance from a
plymouth or gdm developer may mean more progress than I could make in
days. If it's ok with you, though, maybe we can move this towards a
successful tr
@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
** Changed in: plymouth (Ubuntu)
Importance: Medium => High
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Okay, I agree with what Chris is saying, it is correct that whenever I
switched back to tty7 after the crash, I saw ^C or \▉ over there.
--
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a m
So, I think there may be two separate issues here:
1) X started on the wrong tty, resulting in getty eventually timing out and
resetting the tty input, manifests as “X crashes when pressing enter after 5
minutes or so”.
2) X started on the correct tty, but with incorrect input settings, manifests
96 matches
Mail list logo
