How exactly did you go about deleting plymouth and does that allow you
to boot consistently?
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Summary changed:
- [Lucid] No longer boots with new 2.6.32-12 generic kernel
+ [Lucid] No longer boots with new 2.6.32-16 generic kernel
Oh, no, it doesn't. Again I had the same problems and deleted this
plymouth crap.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
[Lucid] No longer boots with new 2.6.32-12 generic kernel
https://bugs.launchpad.net/bugs/518452
You received this bug notification because you are
It's ok now, thanks!
--
[Lucid] No longer boots with new 2.6.32-12 generic kernel
https://bugs.launchpad.net/bugs/518452
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://li
Oh, I hope I'll be able to recover if something goes wrong... I'll try
to tomorrow.
--
[Lucid] No longer boots with new 2.6.32-12 generic kernel
https://bugs.launchpad.net/bugs/518452
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
@Дмитрий "Divius" Танцур:
There have been two major updates that may solve your issue. First, the
2.6.32-16 and later kernels have updated graphics drivers. Second, the
plymouth package was just updated today to version 0.8.0~-13. Please
upgrade to these versions of the packages and retest.
Thank
I don't think there's enough evidence here to conclude that this is a
plymouth bug, or that it's the same as bug #510524. Plymouth doesn't do
anything extraordinary that should break VT switching; if the system is
hanging to the point where Ctrl+Alt+F1, Ctrl+Alt+F2, etc. have no
effect, this is mo
*** This bug is a duplicate of bug 510524 ***
https://bugs.launchpad.net/bugs/510524
@Дмитрий "Divius" Танцур
I'm marking this as a duplicate bug of 510524 since removing plymouth
fixed things for you.
** This bug has been marked a duplicate of bug 510524
Multiple freeze during boot
** C
setting Triaged and Medium importance. Will inquire as to direction this
should go today.
-JFo
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
[Lucid] No longer boots with new 2.6.32-12 generic kernel
https://bugs.
Well, deleting Plymouth fixed the issue.
--
[Lucid] No longer boots with new 2.6.32-12 generic kernel
https://bugs.launchpad.net/bugs/518452
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.u
I'm not sure:
>During the boot I have a first freeze on ubuntu logo. To pass it I switch to
>Ctrl+Alt+F1 and come back to Alt-F7
>I access gdm, enter login+ pass and got a new freeze. Make another switch to
>Ctrl+Alt+F1 and come back to Alt-F7 and freeze disapear and gnome is ready.
Ctrl+Alt+F1
This is perhaps a dublicate to the bug 510524:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/510524
Try removing the package plymouth completely.
But note that the package libplymouth2 must remain untouched.
You may be able to boot into recovery mode.
Then drop into shell and run command
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/38862026/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/38862027/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38862028/BootDmesg.txt
** Att
12 matches
Mail list logo
