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.
Thanks for the results from the script.
Agreed, usplash needs to be fixed to properly resolve this bug. It was
helpful for me to know if the script left things in a working state or
not, which is why I asked if it temporarily fixed the problem.
Looking at the results, I see that nine of the sixt
Don't worry, I'm not running out of patience. Any way, running your
script does NOT fix the problem, not even temporarily. See vbestates.tar
for the results.
I don't know who is responsible for maintaining the usplash utility, but
it would seem to me that fixing it, is only the proper way to deal
Thanks for the detailed response, and taking the time to make the tests.
It does make things more clear. Thanks also for the added info that the
reset command will fix the problem after loading the Uni1 font.
I do wish I had a Mobility Radeon X300 here to test with; it would make
things a lot eas
Additional note for #1 and #2: I don't have to disable the boot option
and both the GDM daemon for this bug to disappear.
--
Ubuntu boot screen causes virtual terminal display problems.
https://bugs.launchpad.net/bugs/392959
You received this bug notification because you are a member of Ubuntu
Bu
Some extra notes:
#3: The characters that become gibberish were already on the screen before
executing the setfont command. They would have been bright if it weren't for
this bug.
--
Ubuntu boot screen causes virtual terminal display problems.
https://bugs.launchpad.net/bugs/392959
You received
Okay, after a systematic test I concluded the following:
I tested the following situations:
1 The boot option "splash" is disabled.
2 The GDM daemon is disabled (using the rcconf utility.)
3 Executing "setfont Uni1-VGA16" in a virtual terminal.
4 Executing "setfont Lat15-VGA16" in a virtual termin
Peter, yes this is a weird one.
When you say that text "suddenly has the right colors after executing
the first command," I am assuming that you are refering to text already
on the screen. The unusual characters after the first command are
normal, since this changes from a 256-character font to a
Well, the result is even odder than trying those commands... Any text
that is supposed to be brightly colered (but isn't at first) suddenly
has the right colors after executing the first command but most of the
text has become unreadable (lots of unusual characters (with
accents/cyrilic.) The secon
Peter, thanks for the quick reply and attachment.
This may be related to another bug I've seen, but perhaps not. If it
is, loading a 512-character font, then immediately loading a
256-character font may help. This may sound odd, but humor me. If this
doesn't help I have no other ideas at the mo
No, changing the font doesn't help. See attachment for the contents of
/etc/default/console-setup
** Attachment added: "console-setup"
http://launchpadlibrarian.net/28506554/console-setup
--
Ubuntu boot screen causes virtual terminal display problems.
https://bugs.launchpad.net/bugs/392959
Yo
Peter, what font are you using? Does it make a difference if you run
setfont Lat15-Fixed16
The contents of your /etc/default/console-setup file could be helpful.
--
Ubuntu boot screen causes virtual terminal display problems.
https://bugs.launchpad.net/bugs/392959
You received this bug notific
12 matches
Mail list logo
