** Changed in: plymouth (Ubuntu)
Status: Invalid = New
** Changed in: plymouth (Ubuntu)
Status: New = Incomplete
** Changed in: plymouth (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
According to Steve in #16: If you don't want the graphical
splash, you can remove the plymouth-theme-ubuntu-logo package. Or you can
boot without the 'splash' option to get a text-only view, which is in fact
the default on new installs of Ubuntu 10.04 LTS Server; though this causes
some problems
So no, this bug is not invalid.
Yes, it is. The other issue I referred to is a separate bug, bug
#563916, which has been resolved.
** Changed in: plymouth (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My apologies Steve, I didn't see bug 563916 referenced here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/531331
Title:
Remove plymouth destroying system
--
ubuntu-bugs mailing list
For Lucid Server edition we disabled Plymouth by removing the
/etc/init/plymouth*.conf scripts. That and some other changes resulted
in a nicer console for servers: http://staff.adams.edu/~cdmiller/posts
/Ubuntu-Lucid-server-disable-plymouth/ In the post is our list of
packages that apt reports
Plymouth is not working for me either. I have to run Nvidia proprietary
driver (nouvaeu does not work at all for Quadro FX380m), and plymouth
can't handle that. I dont see why user is *forced* to have plymouth,
especially on servers. I now have to rebuild whole bunch of software to
get rid of
On Wed, May 26, 2010 at 06:46:33AM -, UnstableGhost wrote:
Plymouth is not working for me either. I have to run Nvidia proprietary
driver (nouvaeu does not work at all for Quadro FX380m), and plymouth
can't handle that.
Please file a separate bug report, detailing how plymouth doesn't
Please file a separate bug report, detailing how plymouth doesn't handle
nvidia drivers for you. For the vast majority of users, it's working as
intended.
As far as I know KMS is not available for NVIDIA\ATI proprietary
drivers, and plymouth without KMS is 16 color ugliness (ignoring that
fact
On Wed, May 26, 2010 at 09:53:38PM -, UnstableGhost wrote:
Please file a separate bug report, detailing how plymouth doesn't handle
nvidia drivers for you. For the vast majority of users, it's working as
intended.
As far as I know KMS is not available for NVIDIA\ATI proprietary
Plymouth is not working properly on my ubuntu box, so i would like to
remove it. When I was running the 9.10 release, I uninstalled usplash
and xsplash, 'cause I like verbose/text boot. Unfortunately this is not
possible with plymouth, or is it?
--
Remove plymouth destroying system
Confirmed on an x86 Lucid installed two days before. The reason I wanted to
remove plymouth was its incompatibility with fglrx (proprietary Radeon driver
that I need).
Trying to remove plymouth results in about a half of the system nominated for
deletion, including Xorg, alsa, etc.
--
Remove
This isn't a direct solution to this problem, but I suspect that a few
of you who are affected by this problem would be satisfied if the splash
screen displayed at the proper resolution while booting with a
proprietary graphics driver enabled. Here are instructions for just such
a solution.
I can't understand how you can't remove:
libdrm-intel1
libdrm-nouveau1
libdrm-radeon1
libdrm2
libplymouth2
plymouth
on a Ubuntu sever, that I run in a virtual machine. Doesn't make any sense.
--
Remove plymouth destroying system
https://bugs.launchpad.net/bugs/531331
You received this bug
There should be a very easy way during installation to switch on or off
grub2 and Plymouth. Lets get rid of this useless splashscreens and boot
up with a nice resolution on the framebuffer screen.
--
Remove plymouth destroying system
https://bugs.launchpad.net/bugs/531331
You received this bug
mountall has a hard dependency on Plymouth, as of version 2.10.
( https://edge.launchpad.net/ubuntu/+source/mountall/2.10 )
* Add hard dependency on Plymouth; without it running, mountall will
ignore any filesystem which doesn't show up within a few seconds or that
fails to fsck or
On Wed, 2010-03-03 at 16:52 +, Steve Langasek wrote:
Well, don't do that.
You can't say that on bug reports ;-) Reddit get upset.
Scott
--
Scott James Remnant
sc...@ubuntu.com
--
Remove plymouth destroying system
https://bugs.launchpad.net/bugs/531331
You received this bug
Surely a splash screen that is displayed for approx 5 seconds can't be a
core package that has nearly 2 gig of dependencies.
--
Remove plymouth destroying system
https://bugs.launchpad.net/bugs/531331
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Wish I could edit the above. I meant to say it's more than splash screen
but a few weeks back you could remove it no problem.
--
Remove plymouth destroying system
https://bugs.launchpad.net/bugs/531331
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Did you remove the package plymouth or libplymouth2? I cannot confirm
problems with removing the former.
plymouth:
Installed: 0.8.0~-10ubuntu1
Candidate: 0.8.0~-10ubuntu1
Version table:
*** 0.8.0~-10ubuntu1 0
500 http://archive.ubuntu.com lucid/main Packages
100
I did remove libplymouth2. Try it in Synaptic, then going to remove
important packages like acpid, cups, dbus, dkms, gdm, xserver* and
others.
--
Remove plymouth destroying system
https://bugs.launchpad.net/bugs/531331
You received this bug notification because you are a member of Ubuntu
Bugs,
Well, don't do that.
Obviously when you remove core packages that other important packages
depend on, it makes a mess of the system.
** Changed in: plymouth (Ubuntu)
Status: New = Invalid
--
Remove plymouth destroying system
https://bugs.launchpad.net/bugs/531331
You received this bug
21 matches
Mail list logo
