I've seen something similar to this but not freezing on Intel x4500
(Lenovo ThinkPad X200). When I booted up tonight to do bootchart timing
the system would just stay at a black X screen with the cursor being all
that was displayed. I heard the login music play but nothing else. I
changed vt's and
Since daily-live of Feb23, I have had no more issues with Plymouth.
Thanks Steve for all your help!
--
Plymouth AND Automatic Login enabled system freezes
https://bugs.launchpad.net/bugs/521175
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It no longer freezes and Plymouth works perfectly.
** Changed in: plymouth (Ubuntu)
Status: Incomplete = Fix Released
--
Plymouth AND Automatic Login enabled system freezes
https://bugs.launchpad.net/bugs/521175
You received this bug notification because you are a member of Ubuntu
Bugs,
Steve Langasek This is a log from right after a hung boot?
Yes, it is.
Steve Langasek If you press Alt+SysRq+K at the hung screen, does X
restart and are you then able to use the system without a reboot?
No. All keyboard input is frozen. I tried that input along with all the
others from REISUB.
Nothing telling in the kernel log that would suggest a cause of a
freeze.
This is a log from right after a hung boot?
If you press Alt+SysRq+K at the hung screen, does X restart and are you
then able to use the system without a reboot?
--
Plymouth AND Automatic Login enabled system freezes
Is the behavior *identical* when booting with/without splash, or are
there differences in how or when the freeze happens? You may be
encountering two different bugs, one with splash and one without.
Identical. VT are also identical.
..you can attach /var/log/kern.log to this bug...
Attached:
ok, please post the output of 'cat /proc/cmdline'. If I can figure out
how to reproduce the problem here then I should be able to debug it
locally, but so far I've been unable to reproduce it.
--
Plymouth AND Automatic Login enabled system freezes
https://bugs.launchpad.net/bugs/521175
You
cat /proc/cmdline:
BOOT_IMAGE=/vmlinuz root=UUID=54cb8887-31e8-4da4-91e5-ca71a0c70388 ro #splash
--
Plymouth AND Automatic Login enabled system freezes
https://bugs.launchpad.net/bugs/521175
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 518352 ***
https://bugs.launchpad.net/bugs/518352
Thanks - if you're booting with 'splash' disabled, then I think this is
the same as bug #518352. Marking as a duplicate.
(Why do you have the 'splash' option commented out, btw?)
** This bug has been
*** This bug is a duplicate of bug 518352 ***
https://bugs.launchpad.net/bugs/518352
Wow, I'm nobody to teach anyone lessons but... ok, let's analyze this
closure you just did:
- You didn't wait for the user that reported the issue to confirm whether
adding 'splash' solves the problem.
-
*** This bug is a duplicate of bug 518352 ***
https://bugs.launchpad.net/bugs/518352
I have splash commented out so I can see the text output and know where the
last message fails.
I only removed splash AFTER I started having the issue at hand.
--
Plymouth AND Automatic Login enabled
*** This bug is a duplicate of bug 518352 ***
https://bugs.launchpad.net/bugs/518352
Ok quiet is the one that silences the boot up messages. I put
splash back but it made no difference.
BTW- Even with splash removed my VT is still VT7 as usual, and not VT1 l.
The duplicate bug you referred
*** This bug is a duplicate of bug 518352 ***
https://bugs.launchpad.net/bugs/518352
Agreed, X is running on VT7 for me as well and not VT1.
Also, removing the nvidia driver and using the nv driver seemed to
solve my problem (before removing plymouth) in gdm, but would then
freeze after
*** This bug is a duplicate of bug 518352 ***
https://bugs.launchpad.net/bugs/518352
Termina,
I'm using Intel i865 integrated video. I noticed on bug #518352 that it was
suggested if using splash and the problem reoccurs then to open another bug
report. If you do then let me know I will add
On Mon, Feb 15, 2010 at 07:52:20PM -, hexion wrote:
Wow, I'm nobody to teach anyone lessons but... ok, let's analyze this
closure you just did:
Marking a bug as a duplicate is not closing it.
- You didn't wait for the user that reported the issue to confirm whether
adding 'splash'
** This bug is no longer a duplicate of bug 518352
[lucid] if booting without 'splash', gdm starts X on wrong vt
--
Plymouth AND Automatic Login enabled system freezes
https://bugs.launchpad.net/bugs/521175
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So the issue now is, with splash on or off, it still freezes. Remove
Plymouth and I NEVER have a boot up issue.
Ok, unmarking this as a duplicate then.
Is the behavior *identical* when booting with/without splash, or are
there differences in how or when the freeze happens? You may be
I am seeing this on a daily live usb. If I go into terminal and press
enter it is a hard lock. At that point in time it is like the keyboard
and mouse are of no use. If I remove Plymouth my daily live usb is
useful again. As the live usb uses autologin that seems to not like
Plymouth for some
I'm affected by this bug too. After I uninstalled plymouth I could log into the
system in graphic mode.
Changing status to 'New' since the data requested has been provided.
** Changed in: plymouth (Ubuntu)
Status: Incomplete = New
--
Plymouth AND Automatic Login enabled system freezes
Changing status to 'New' since the data requested has been provided.
No, it hasn't. I still need the output of the ps command when the
system is in this state.
** Changed in: plymouth (Ubuntu)
Status: New = Incomplete
--
Plymouth AND Automatic Login enabled system freezes
Tried SSH. Could not login. Nothing.
So now what?
We are in a stale mate. A catch-22.
You need output of the ps command, but I can't get it because the
system is frozen solid!
Is there any way to get the command 'ps aw | grep X.*vt' any other way.
Say in the boot process? Is there a script
I just found another wrinkle regarding this problem.
When I boot Lucid and it freezes, if I then power-cycle(no other
choice), when it boots again it may boot up completely. Sometimes it
takes 5 times doing this, but eventually it will go through to a
complete boot.
What do you make of that?
vmc:
As far as scripts go, try:
ps aw | grep X.*vt/home/awxvt.log
The path to awxvt.log might need modification, but that method works on a
running system.
(see post 11 in your forum thread).
--
Plymouth AND Automatic Login enabled system freezes
https://bugs.launchpad.net/bugs/521175
You
On Sat, Feb 13, 2010 at 02:51:46AM -, vmc wrote:
I just realize you want the information during a freeze. Question. How
am I suppose to do that. When it freezes I have no way to open up a
terminal to type anything. Its frozen.
Does switching to console with Ctrl+Alt+F2 not work?
When it
Like I stated above, nothing works. It tried all that stuff ---
Alt+F2, or Ctrl+Alt+F2 does nothing. I get no response.
I thought about using ssh, but I have never used it before or its been
such a long time I forget how. I will research it and get back here.In
the meantime someone else with
I do not use auto login as a general rule. I read this and decided to
set my most reliable install to auto login (I have 7 installs total).
It will freeze right when the login page would normally come up now that
it is set to auto login.
--
Plymouth AND Automatic Login enabled system freezes
The freeze may not happen immediately. But it will happen. It took me 3
re-boots AFTER I re-installed Plymouth.
After that, it took a power-cycle to restart my computer. Then it
froze from then on.
--
Plymouth AND Automatic Login enabled system freezes
https://bugs.launchpad.net/bugs/521175
vmc,
please provide answers to the following questions when plymouth is installed on
your system.
- did you see an Ubuntu logo at boot?
- if so did it disappear before the spinning X cursor appeared?
- if you don't see an Ubuntu logo, do you see a blue and white bar at the
bottom of your
Please note that I need the answers to some of these questions during a
session that freezes. So if the freeze doesn't happen consistently,
please record the information for each attempt and send me the
information corresponding to a reproduced freeze.
** Changed in: plymouth (Ubuntu)
Q- did you see an Ubuntu logo at boot?
A - Yes.
Q if so did it disappear before the spinning X cursor appeared?
A- No.
Q- if you don't see an Ubuntu logo, do you see a blue and white bar at the
bottom of your screen?
A- Nothing at the bottom just the logo.
- show the output of 'cat /proc/fb':
I just realize you want the information during a freeze. Question. How
am I suppose to do that. When it freezes I have no way to open up a
terminal to type anything. Its frozen.
The above info came from same machine that previously freezes.
When it freezes I have to turn off the power. No input
Here's another problem. Once it freezes, it will always freeze.
I have grub.cfg setup to display test messages only:
linux /vmlinuz root=UUID=d08c04f8-f062-43b0-a56a-1dc36ee4e81d ro
the very last text messages I get are:
/script/init/bottom
fsck /dev/sda7...
Then the screen goes blank as a
Wow, mine is not that bad. I can alt+SysRq+b out and actually boot to
the desktop through recovery and the text login.
The answers to your questions, given by vmc, are, except for the
severity of the freeze, accurate for me too. The only difference would
be my Radeon HD2400 Pro using the
33 matches
Mail list logo
