This bug was fixed in the package plymouth - 0.8.0~-13
---
plymouth (0.8.0~-13) lucid; urgency=low
[ Steve Langasek ]
* Don't attach /proc/cmdline to apport reports, this is already in the
standard info that gets collected...
[ Alberto Milone ]
* ubuntu_logo theme:
-
On Thu, Feb 25, 2010 at 05:13:46PM -, Claudio Moretti wrote:
> sudo ls -la /dev/.initramfs returns the following:
> r...@jarvis:/dev/.initramfs# ls -la
> totale 0
> drwxr-xr-x 2 root root 40 2010-02-25 13:14 .
> drwxr-xr-x 16 root root 3880 2010-02-25 15:50 ..
That's actually inconclusive,
Update:
As I've noted in my comments to bug 499399, I found a link between this
behaviour and the kernel version that I'm running.
Karmic kernel is fine; various versions of 2.6.32 don't work.
Therefore, it may be a different bug.
--
System does not booth with last plymouth. SAK needed to unlo
I am wondering if the problems I'm experiencing in bug 499399 are
related to this bug. I get similar symptoms: scripts init-bottom are
run, then the whole thing hangs.
Output of lshw and a syslog are attached to that bug. (comments 18 and
19)
I also noticed in daemon.log:
Mar 5 22:07:48 localho
I don't know how to verify it, but I can exclude tha last 2 entries as sudo
ls -la /dev/.initramfs returns the following:
r...@jarvis:/dev/.initramfs# ls -la
totale 0
drwxr-xr-x 2 root root 40 2010-02-25 13:14 .
drwxr-xr-x 16 root root 3880 2010-02-25 15:50 ..
I have also found this:
r...@jar
Yes, plymouth should fall back to the text plugin when not given
'splash', but you may have found a problem that's specific to the text
plugin so I think we want to verify whether it happens when using
splash.
Also, if plymouth is running in the initramfs like it should be, it
doesn't matter what
Looking at the attachments in this bug report, I noticed that
"plymouth.diff" was flagged as a patch. A patch contains changes to an
Ubuntu package that will resolve a bug, since this was not one I've
unchecked the patch flag for it. In the future keep in mind the
definition of a patch. You can
** Tags added: patch
--
System does not booth with last plymouth. SAK needed to unlock it.
https://bugs.launchpad.net/bugs/526321
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
I'm using cryptsetup 2:1.1.0~rc2-1ubuntu12 to unlock the root filesystem
(sda6_crypt) and the home filesystem (sda7_crypt) that is unlocked with a
keyfile located into the root fs.
Here's my /etc/crypttab
sda5_crypt /dev/sda5 /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,swap
sda6_crypt /dev
The apport information in your report shows a root device of
/dev/mapper/sda6_crypt. Are you using cryptsetup to decrypt this at
boot time? What version of cryptsetup do you have installed?
It also shows that you're booting without the 'splash' option - why is
this?
If you're using cryptsetup,
** Patch added: "plymouth.diff"
http://launchpadlibrarian.net/39600534/plymouth.diff
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/39600535/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/39600536/CurrentDmesg.txt
** Attachment a
11 matches
Mail list logo
