[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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/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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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) Status: Fix Released = 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
I'm not sure about it; it says *theme-name [ --rebuild-initrd ]*, which,
IMO, means theme name *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, Steve Langasek
steve.langa...@canonical.comwrote:
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 |
*theme-name [
--rebuild-initrd ]* | --help }
No, this documentation says that you can pass --rebuild-initrd *or*
theme-name. The implementation requires that --rebuild-initrd only be
passed when you *also* pass theme-name.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/504052
You received this bug notification because you are a direct subscriber
of the bug.
Status in “plymouth” package in Ubuntu: Fix Released
Bug description:
Binary package hint: plymouth
When trying to reproduce a /home encryption issue I have (not being
prompted for the key at boot time), I noticed that I currently don't get
plymouth to start at all !
In order to test in a clean environment, I did a VM install using the
mini.iso (amd64 install) with the same partitioning as my laptop and
installed a command line Ubuntu + the plymouth package (to keep the image
small so I can upload it if needed).
At boot time I get:
-
mountall: Could not connect to Plymouth
fsck from util-linux-ng 2.16
/dev/sda1: clean, 43560/122160 files, 193804/487966 blocks
* Starting init crypto disks... * sda2_crypt (starting)..
Unlocking the disk /dev/disk/by-uuid/91c20a8a-ea4d-4352-aa89-21470dad5a5d
(sda2_crypt)
* sda2_crypt (starting)..
Skipping /home at user request
init: plymouth-log main process (941) terminated with status 111
-
I don't get prompted for the key to unlock /dev/sda2 and it even gets
discarded by mountall after that.
Also, when trying to login, vt1 seems broken as after typing two
characters, the terminal freeze and I have to switch to vt2 to get a working
console.
I'm not sure if that's a Plymouth issue triggering a mountall one or the
other way around, so I may very well be reporting it against the wrong
package, feel free to reassign.
As I said, I have the same issue on my laptop as in the VM (no Plymouth,
broken VT and no cryptsetup prompt) and I'm keeping the VM around in case
you would like a copy of it.
To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/504052/+subscribe
--
[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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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; update-grub did solve this problem, - and since then everything works as expected. -- [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
Seems documented
r...@jarvis:~# plymouth-set-default-theme --help
* usage: plymouth-set-default-theme* { --list | --reset | *theme-name [
--rebuild-initrd ]* | --help }
--help show this help message
--list show available themes
--resetreset to default theme
--rebuild-initrd rebuild initrd (necessary after changing theme)
theme-name name of new theme to use (see --list for available
themes)
But it worked:
r...@jarvis:~# plymouth-set-default-theme --rebuild-initrd solar
update-initramfs: Generating /boot/initrd.img-2.6.32-11-generic
No way to make it work for all initrd images?
But plymouth *doesn't* work yet.
On Fri, Jan 22, 2010 at 20:06, Steve Langasek
steve.langa...@canonical.comwrote:
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
flyingsta...@gmail.com 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/plymouth/themes//.plymouth does not exist
You need to run this as 'plymouth-set-default-theme --rebuild-initrd
solar'.
I don't know if this is a documentation or implementation bug.
--
[lucid] No plymouth at boot time and mountall error
https://bugs.launchpad.net/bugs/504052
You received this bug notification because you are a direct subscriber
of the bug.
Status in “plymouth” package in Ubuntu: Fix Released
Bug description:
Binary package hint: plymouth
When trying to reproduce a /home encryption issue I have (not being
prompted for the key at boot time), I noticed that I currently don't get
plymouth to start at all !
In order to test in a clean environment, I did a VM install using the
mini.iso (amd64 install) with the same partitioning as my laptop and
installed a command line Ubuntu + the plymouth package (to keep the image
small so I can upload it if needed).
At boot time I get:
-
mountall: Could not connect to Plymouth
fsck from util-linux-ng 2.16
/dev/sda1: clean, 43560/122160 files, 193804/487966 blocks
* Starting init crypto disks... * sda2_crypt (starting)..
Unlocking the disk /dev/disk/by-uuid/91c20a8a-ea4d-4352-aa89-21470dad5a5d
(sda2_crypt)
* sda2_crypt (starting)..
Skipping /home at user request
init: plymouth-log main process (941) terminated with status 111
-
I don't get prompted for the key to unlock /dev/sda2 and it even gets
discarded by mountall after that.
Also, when trying to login, vt1 seems broken as after typing two
characters, the terminal freeze and I have to switch to vt2 to get a working
console.
I'm not sure if that's a Plymouth issue triggering a mountall one or the
other way around, so I may very well be reporting it against the wrong
package, feel free to reassign.
As I said, I have the same issue on my laptop as in the VM (no Plymouth,
broken VT and no cryptsetup prompt) and I'm keeping the VM around in case
you would like a copy of it.
To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/504052/+subscribe
--
[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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 | *theme-name [
--rebuild-initrd ]* | --help }
No, this documentation says that you can pass --rebuild-initrd *or*
theme-name. The implementation requires that --rebuild-initrd only be
passed when you *also* pass theme-name.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
--
[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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 on an external USB HDD. My system is an Acer Aspire One and uses Intel's 945GME graphics chipset. On both installs plymouth didn't work no matter what I was doing. The error message was the same as stated above (unexpectedly disconnected from boot status daeome) - until I switched plymouth's theme with plymouth-set-default-theme. Since then I have not found a theme that doesn't work for me. But if you tell me which one is installed by default I will give it a try. What I haven't tried, too, is, if plymouth does still work if I remove the splash parameter from the kernal command line. But I think you would know the result in advance, anyway. Another thing I noticed is that currently on my system the fact if plymouth is working on powerdown, too, depends on the graphics mode my grub2 uses. 640x400 is bad, 1280x600 works fine. -- [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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:~# plymouth-set-default-theme --rebuild-initrd /lib/plymouth/themes//.plymouth does not exist That's weird... On Fri, Jan 22, 2010 at 17:44, PeterPall gun...@peterpall.de wrote: 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 on an external USB HDD. My system is an Acer Aspire One and uses Intel's 945GME graphics chipset. On both installs plymouth didn't work no matter what I was doing. The error message was the same as stated above (unexpectedly disconnected from boot status daeome) - until I switched plymouth's theme with plymouth-set-default-theme. Since then I have not found a theme that doesn't work for me. But if you tell me which one is installed by default I will give it a try. What I haven't tried, too, is, if plymouth does still work if I remove the splash parameter from the kernal command line. But I think you would know the result in advance, anyway. Another thing I noticed is that currently on my system the fact if plymouth is working on powerdown, too, depends on the graphics mode my grub2 uses. 640x400 is bad, 1280x600 works fine. -- [lucid] No plymouth at boot time and mountall error https://bugs.launchpad.net/bugs/504052 You received this bug notification because you are a direct subscriber of the bug. Status in “plymouth” package in Ubuntu: Fix Released Bug description: Binary package hint: plymouth When trying to reproduce a /home encryption issue I have (not being prompted for the key at boot time), I noticed that I currently don't get plymouth to start at all ! In order to test in a clean environment, I did a VM install using the mini.iso (amd64 install) with the same partitioning as my laptop and installed a command line Ubuntu + the plymouth package (to keep the image small so I can upload it if needed). At boot time I get: - mountall: Could not connect to Plymouth fsck from util-linux-ng 2.16 /dev/sda1: clean, 43560/122160 files, 193804/487966 blocks * Starting init crypto disks... * sda2_crypt (starting).. Unlocking the disk /dev/disk/by-uuid/91c20a8a-ea4d-4352-aa89-21470dad5a5d (sda2_crypt) * sda2_crypt (starting).. Skipping /home at user request init: plymouth-log main process (941) terminated with status 111 - I don't get prompted for the key to unlock /dev/sda2 and it even gets discarded by mountall after that. Also, when trying to login, vt1 seems broken as after typing two characters, the terminal freeze and I have to switch to vt2 to get a working console. I'm not sure if that's a Plymouth issue triggering a mountall one or the other way around, so I may very well be reporting it against the wrong package, feel free to reassign. As I said, I have the same issue on my laptop as in the VM (no Plymouth, broken VT and no cryptsetup prompt) and I'm keeping the VM around in case you would like a copy of it. To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/504052/+subscribe -- [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
Same error here! On Fri, 22 Jan 2010 17:25:07 -, Claudio Moretti flyingsta...@gmail.com 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/plymouth/themes//.plymouth does not exist r...@jarvis:~# plymouth-set-default-theme --reset r...@jarvis:~# plymouth-set-default-theme --rebuild-initrd /lib/plymouth/themes//.plymouth does not exist That's weird... On Fri, Jan 22, 2010 at 17:44, PeterPall gun...@peterpall.de wrote: 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 on an external USB HDD. My system is an Acer Aspire One and uses Intel's 945GME graphics chipset. On both installs plymouth didn't work no matter what I was doing. The error message was the same as stated above (unexpectedly disconnected from boot status daeome) - until I switched plymouth's theme with plymouth-set-default-theme. Since then I have not found a theme that doesn't work for me. But if you tell me which one is installed by default I will give it a try. What I haven't tried, too, is, if plymouth does still work if I remove the splash parameter from the kernal command line. But I think you would know the result in advance, anyway. Another thing I noticed is that currently on my system the fact if plymouth is working on powerdown, too, depends on the graphics mode my grub2 uses. 640x400 is bad, 1280x600 works fine. -- [lucid] No plymouth at boot time and mountall error https://bugs.launchpad.net/bugs/504052 You received this bug notification because you are a direct subscriber of the bug. Status in “plymouth” package in Ubuntu: Fix Released Bug description: Binary package hint: plymouth When trying to reproduce a /home encryption issue I have (not being prompted for the key at boot time), I noticed that I currently don't get plymouth to start at all ! In order to test in a clean environment, I did a VM install using the mini.iso (amd64 install) with the same partitioning as my laptop and installed a command line Ubuntu + the plymouth package (to keep the image small so I can upload it if needed). At boot time I get: - mountall: Could not connect to Plymouth fsck from util-linux-ng 2.16 /dev/sda1: clean, 43560/122160 files, 193804/487966 blocks * Starting init crypto disks... * sda2_crypt (starting).. Unlocking the disk /dev/disk/by-uuid/91c20a8a-ea4d-4352-aa89-21470dad5a5d (sda2_crypt) * sda2_crypt (starting).. Skipping /home at user request init: plymouth-log main process (941) terminated with status 111 - I don't get prompted for the key to unlock /dev/sda2 and it even gets discarded by mountall after that. Also, when trying to login, vt1 seems broken as after typing two characters, the terminal freeze and I have to switch to vt2 to get a working console. I'm not sure if that's a Plymouth issue triggering a mountall one or the other way around, so I may very well be reporting it against the wrong package, feel free to reassign. As I said, I have the same issue on my laptop as in the VM (no Plymouth, broken VT and no cryptsetup prompt) and I'm keeping the VM around in case you would like a copy of it. To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/504052/+subscribe -- [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 canging themes, though. -- [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 flyingsta...@gmail.com 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/plymouth/themes//.plymouth does not exist You need to run this as 'plymouth-set-default-theme --rebuild-initrd solar'. I don't know if this is a documentation or implementation bug. -- [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 equivalent vga=normal paramenter This is fuzzy logic, I know, but let us run it up the flagpole ... -- [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 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 make a difference for you - essentially, the prompt is always going to be blank until bug #496765 is fixed, but the input dialog seems to work reliably for me. ** Changed in: plymouth (Ubuntu) Status: Confirmed = Fix 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
-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 make a difference for you - essentially, the prompt is always going to be blank until bug #496765 is fixed, but the input dialog seems to work reliably for me. I opened #509487 about this issue, I'll attach the package details to that bug report instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktVtfEACgkQjxyfqkjBhuwzsgCfcfV+xTaj+4BiW4+rAPyyRMDG qU8An1pp/LKZefdIjWygm4Ux5g9gRELq =T3Xp -END PGP SIGNATURE- -- [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 report. For now I simply boot without my /home and mount it afterwards. -- [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 of plymouth errors in /var/log (did a grep plymouth *, returned entries only from dpkg logs) ** Changed in: plymouth (Ubuntu) Status: Incomplete = 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
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 issue with libdrm, which AFAIK plymouth uses? After booting with `debug' kernel argument instead of `quiet', the following could be noticed in /dev/.initramfs/initramfs.debug: + /scripts/init-top/plymouth error: unexpectedly disconnected from boot status daemon And nothing else. Note that VT is not broken in my case, but often I have to log in with KDM twice (after first log-in X restarts - note that KDE session is using composition). Additionally KDM doesn't start automatically now - I had to write 'start kdm' into /etc/rc.local. It can be totally other issue, though. But without this change and after manually starting kdm (by logging onto root in vt1) double-log-in doesn't occur. It may be some time issue. -- [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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 504052] Re: [lucid] No plymouth at boot time and mountall error
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
