The usplash package has been superseded by plymouth and has been removed
from the Ubuntu archive. Closing all related bugs.
** Changed in: usplash (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ricardisimo: Updating to grub2 was a one-time fix for me when I tried it a
couple months ago. After a second try, ubuntu once again was failing to boot.
However, with the Lucid release this issue seems to had some more attention
from other people new to ubuntu installing it, and coincidentally I
I have discovered that I still had grub - and not grub2 - installed on
my system for some reason (shouldn't this have updated automatically?)
after following the instructions in the grub2 wiki:
https://wiki.ubuntu.com/Grub2
... all is goodness and light. I hope this can help you as well,
jetsetle
Well, as expected, that lasted exactly two bootings. The problem is
back, and no one here is responding. As far as I am concerned this is a
dead thread. feel free to close. I'm going to file a new bug under the
kernel, rather than usplash. Clearly nobody here knows or cares what's
going on here. Ta
There was a linux-firmware update today that seemed like it might be
pertinent to this issue. After updating, I switched my menu.list to "0"
for the default kernel, which is to say the newest one instead of
2.6.31.14. Then I rebooted - twice. So far so good. I have my doubts
about how permanent thi
So, two weeks have gone by, and not only has the problem not corrected
itself, but also, amazingly, not one other person on the entire planet
can even post a simple "hello" within this thread. I have to say, it's
getting to be pretty puzzling.
I see a list of over fifty names in the right sidebar,
Very little to report, but here it is:
Just before the latest kernel upgrade, I was able to get 2.6.31.17 to
load normally. Then, 2.6.31-19-generic came along and was also working
perfectly... for less than a week. I have no idea what change allowed
the newer kernels to start up, nor what subseque
Hello? Once again, I'd like to know if anyone is ever going to respond
to this. If not, that's fine, but I'd just like to know.
Also, at some point, if I can't upgrade past kernel 2.6.31.14, then I am
slowly and steadily getting handicapped. Should I also start looking at
reloading Windows, like t
So, there was a new kernel update today - version 2.6.31-17.54 - with
exactly the same results: frozen at Ubuntu splash screen immediately
after selecting kernel to load.
Could someone (other than the OP) please just copy and paste the
following message into this thread: "We're busy right now... w
I realize I'm not supposed to clog up the bug reports with idle chatter
or repetitive posts, but we're going on two months without even a
dismissive comment from anyone other than the OP and myself. Not one
single comment or request from anyone... it seems a tad neglectful.
How about a simple ques
Something - and I don't know what - changed the the "default num" in my
menu.lst. I had set it to 4, so that 2.6.31.14 would always load, and it
was changed back to 0 at some point, by one or another update, I have to
assume. As I described, the newer kernels will not load. Don't know if
it's perti
It would be nice if you could check to see if linux-image 2.6.31.14
works properly for you as well, no? Hopefully that would kind of narrow
some possibilities. Being neither a programmer nor hacker, I have no
clue myself. Thanks for replying... at least I know this thread is
actually working. :)
-
I migrated back to Windows as my primary OS, as I couldn't deal with the
problem. I still have Ubuntu installed so I could test any recommended
fixes but it's not really usable as an everyday OS in the state it's in
between this and the intel driver issues.
--
Ubuntu fails to load after white log
Kernel upgrade today... no change. Still only 2.6.31.14 will load
properly.
Is anyone there? How about the OP? Has your issue been resolved?
--
Ubuntu fails to load after white logo splash screen.
https://bugs.launchpad.net/bugs/483451
You received this bug notification because you are a member
Latest update:
2.6.31-16 provided some relief for a few days here on this same machine,
but no longer. I have no idea what caused a renewal of this same
problem, but it started with major, MAJOR problems trying to print OOo
Writer documents (screen flashing wildly, then the entire system seizing
u
So, I've tried it a few more times, and so far 2.6.31-14 is loading
properly every time, and 2.6.31-15 fails almost every time. I say
"almost" because it loaded at least a few times since this kernel was
installed, but not at all over the past few days. Thanks again for your
attention to this.
--
My machine is freezing during boot as well, during the mentioned splash
with the white Ubuntu logo on black screen. I'm on 9.10, and having
better luck booting selecting 2.6.31-14 (no freezing as of yet) than I
am with 2.6.31-15. Some basic info below. Please let me know what else I
can provide.
~
** Attachment added: "uname-a.txt"
http://launchpadlibrarian.net/35741955/uname-a.txt
** Description changed:
Binary package hint: usplash
- New install of Ubuntu 9.10 Karmic. About 9/10 of the time I attempt to boot
Ubuntu, it freezes on a black screen right after showing the white Ubu
** Attachment added: "usplash.conf"
http://launchpadlibrarian.net/35741947/usplash.conf
--
Ubuntu fails to load after white logo splash screen.
https://bugs.launchpad.net/bugs/483451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "lspci-vnvn.log"
http://launchpadlibrarian.net/35741916/lspci-vnvn.log
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/35741917/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/35741919/CurrentDmesg.txt
** Attac
20 matches
Mail list logo
