Where is the fix that is released ?
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/504052
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
h
Not been able to boot (nor fix the problem) since I updated the system
the other day.
This is all I'm greeted by when booting:
Loading, please wait...
error: unexpectedly disconnected from boot status daemon
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/
mountall: Could not connect to Plymouth
Is the only message that I can see before the Plymounth Text Mode start.
When I Install the Beta Version in Lucid Plymounth start in graphic mode
correctlly, but now only display text-mode.
I have nVidia Private Dirvers Installed.
--
[lucid] No plymouth
madmed, please file a separate bug report instead of reopening one
without concrete evidence that it's the same error.
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Fix Released
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/504052
You recei
I have no plymouth in my two notebooks (intel graphics) since I upgraded
to lucid. But today after doing an update the mountall error appeared,
and it seems I am not the only one
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/505584/comments/19
** Changed in: plymouth (Ubuntu)
Stat
You're right - I kept reading the [ as a |. So no bug here, except in
my eyesight (or in my font). :)
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/504052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I'm not sure about it; it says * [ --rebuild-initrd ]*, which,
IMO, means " *and if you want also* --rebuild-initrd" (these are
square brackets, not a pipe)
But, again, that's how I read it and I may be mistaken (even because it is
not documented in the following help)
On Sun, Jan 24, 2010 at 03:00
On Sat, Jan 23, 2010 at 05:16:53PM -, Claudio Moretti wrote:
> Seems documented
> r...@jarvis:~# plymouth-set-default-theme --help
>* usage: plymouth-set-default-theme* { --list | --reset | * [
> --rebuild-initrd ]* | --help }
No, this documentation says that you can pass "--rebuild-init
Seems documented
r...@jarvis:~# plymouth-set-default-theme --help
* usage: plymouth-set-default-theme* { --list | --reset | * [
--rebuild-initrd ]* | --help }
--help show this help message
--list show available themes
--resetreset to default
Works perfectly on my system. Also tried the default ubuntu theme
(ubuntu-logo), which worked, too --- so on my computer the current status is:
- After the update from karmic plymouth didn't work on startup even after
reinstalling and reconfiguring it
- a "plymouth-set-default-theme solar; upda
On Fri, Jan 22, 2010 at 05:51:24PM -, Durand D'souza wrote:
> Same error here!
> On Fri, 22 Jan 2010 17:25:07 -, Claudio Moretti
> wrote:
> > The default theme is "ubuntu-logo"; that's what happens when I try to
> > switch
> > theme
> > r...@jarvis:~# plymouth-set-default-theme sola
This really is weird.
What I did after changing the theme the first time was
sudo update-grub
...Don't know if that can help you instead. The other times I changed
themes was before a big update that rebuilt the initrd, anyway. Seems
that at this point I am missing some vital information about c
Same error here!
On Fri, 22 Jan 2010 17:25:07 -, Claudio Moretti
wrote:
> The default theme is "ubuntu-logo"; that's what happens when I try to
> switch
> theme
>
> r...@jarvis:~# plymouth-set-default-theme solar
> r...@jarvis:~# plymouth-set-default-theme --rebuild-initrd
> /lib/plymout
The default theme is "ubuntu-logo"; that's what happens when I try to switch
theme
r...@jarvis:~# plymouth-set-default-theme solar
r...@jarvis:~# plymouth-set-default-theme --rebuild-initrd
/lib/plymouth/themes//.plymouth does not exist
r...@jarvis:~# plymouth-set-default-theme --reset
r...@jarvis
Only to make sure that nothing obvious is left out:
Have you ever tried to change the plymouth theme?
Background: I own 2 Ubuntu installations that I have upgraded from
karmic to lucid, one minimalistic installation that fits on the 8GB SDD
of my computer - and a second quite complete installation
Never mind, brain fart. Does anyone have a workaround for this? I have
idiotically uninstalled plymouth, trying to chroot into the system from
a Live CD and reinstall ...
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/504052
You received this bug notificati
I have noticed that the unexpected disconnect from boot status daemon
error is associated with the message "switching to color frame buffer
device." The latter seems to cause the problem whereby one cannot use
alt+ctl+Fx to drop into a shell. I am going to try to boot with the
"nofb" or the equival
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
> Stéphane, which version of cryptsetup do you have installed where it
> fails to prompt you for /home? I've just done a cryptsetup upload that
> fixes some bugs regarding plymouth prompting, but I don't know why this
> would mak
Claudio, since Stéphane reports the issue is fixed for him, please file
a separate bug report for the problem you're seeing.
Note that plymouth is known not to work currently on hardware that
doesn't support KMS (bug #506717), which would include nvidia.
Stéphane, which version of cryptsetup do y
Hi Steve, I can confirm that for me it's now fixed (sorry, only rebooted
my laptop today).
I now get the plymouth splash correctly with the only remaining issue
being that it gets stuck at the point where it should ask me for my
passphrase (to unlock my /home partition) but that's another bug repo
I run on ATI video and have 7 10.04 versions on my test drive. 6 of
them have plymouth working fine.
The one that is not working has no encryption running.
It has Lxde installed with Gnome.
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/504052
You receiv
This happens on my lucid too, with nvidia graphics.
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/504052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Still happens in my Lucid, last updated 10 minutes ago.
r...@jarvis:/var/log# apt-cache policy plymouth
plymouth:
Installato: 0.8.0~-7
Candidato: 0.8.0~-7
Tabella versione:
*** 0.8.0~-7 0
500 http://archive.ubuntu.com lucid/main Packages
100 /var/lib/dpkg/status
No sign o
Stéphane, I believe this was fixed just before alpha-2 - can you
confirm?
** Changed in: plymouth (Ubuntu)
Status: Confirmed => Incomplete
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/504052
You received this bug notification because you are a mem
This also affects me - I have no plymouth at boot time, even without any
encryption enabled. I am using 64bit CPU and R600 with KMS, the issue
can be reproduced with newest lucid kernels (2.6.32) and newest upstream
rc (from kernel-ppa, 2.6.33rc4). I am also using xorg-edgers ppa - could
it be an i
** Changed in: plymouth (Ubuntu)
Status: New => Confirmed
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/504052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
26 matches
Mail list logo
