The problem is reproducable.
After latest updates my 10.04 Ubuntu Desktop (with cryptdisk) also hangs in
startup.
Ctrl-Alt-Del is working.
Switching to one of the tty's (Ctrl-Alt-Fx) doesn't.
The system seems to be up (server edition was reachable with SSH).
Maybe it has something to do with
OK, it doesnt seem to be related to my script.
In my script I set as root (after booting) CRYPTDISKS_ENABLE to Yes in
/etc/default/cryptdisks.
Then I restart the crypdisks service, enter the password, it tries to mount the
disk, and I put a No in /etc/default/cryptdisks for the next boot.
Works
sorry, ENABLE_AT_STARTUP should be CRYPTDISKS_ENABLE, of course.
--
no password prompt for cryptsetup in 10.04 64-bit server
https://bugs.launchpad.net/bugs/560105
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
If you have a hung plymouthd process again, please attach to it with gdb
('sudo gdb /sbin/plymouthd $pid') and paste the output of the 'bt'
command.
--
no password prompt for cryptsetup in 10.04 64-bit server
https://bugs.launchpad.net/bugs/560105
You received this bug notification because you
Hmmm, I'm puzzled again.
Just upgraded 10.04 server and desktop to kernel 2.6.32-20.
Desktop starts up fine (without asking for a password).
I'm able (from commandline) to start my encrypted disk with service cryptdisks
restart now.
On server I still have a hanging plymouth.
I'm getting kinda
Just close the call, I will work my way through this and wait it out
until the final release.
You are the only user reporting this issue. If you're not able to
provide the requested backtrace, it's unlikely that this will be
resolved for the final release.
--
no password prompt for
With all due respect, Steve, after all the instability problems with
cryptsetup in the last 2 years, I'm wondering if I'm indeed the only
user left ;-)
--
no password prompt for cryptsetup in 10.04 64-bit server
https://bugs.launchpad.net/bugs/560105
You received this bug notification because
.. and it's 10.04 BETA, so I'm not sure how many users there are.
But OK, I've attached the gdb backtrace output.
** Attachment added: gdb backtrace
http://launchpadlibrarian.net/43916814/gdb-bt.txt
--
no password prompt for cryptsetup in 10.04 64-bit server
with debugging symbols:
gdb /sbin/plymouthd 250
(gdb) bt
#0 0x7f99c2742500 in write () from /lib/libc.so.6
#1 0x7f99c2c0bd8b in ply_write (fd=7, buffer=0x40a7d0,
number_of_bytes=value optimized out) at ply-utils.c:306
#2 0x00404797 in ply_boot_connection_on_request
after all the instability problems with cryptsetup in the last 2 years
I have to correct myself on this, it's Ubuntu boot process that made it
instable
--
no password prompt for cryptsetup in 10.04 64-bit server
https://bugs.launchpad.net/bugs/560105
You received this bug notification because
Ok, it looks like what we have here is a blocking write from plymouthd
to some client that has stopped listening. There's not enough
information to tell us what client or why, but I think it's a bug that
the plymouth server doesn't have a sensible timeout for writes.
If you have time to also
Might that process be 'mountall', like I mentioned in #9?
message was:
mountall: Plymouth command failed
--
no password prompt for cryptsetup in 10.04 64-bit server
https://bugs.launchpad.net/bugs/560105
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes, it's very possible that mountall is the process in question. Is
mountall also still running after boot?
--
no password prompt for cryptsetup in 10.04 64-bit server
https://bugs.launchpad.net/bugs/560105
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 554737 ***
https://bugs.launchpad.net/bugs/554737
Looks like bug #554737 is the same issue; marking this as a duplicate.
** This bug has been marked a duplicate of bug 554737
Graphical bootstrap hangs on fsck
--
no password prompt for cryptsetup in
The device (as in /dev/sda6) is not mounted, of course. There aren't any
/dev/mapper devices either, only /dev/mapper/control.
On the /dev/sda disk there are 3 filesystems in use (root, swap and data).
--
no password prompt for cryptsetup in 10.04 64-bit server
Thanks for replying.
strace -o strace.txt -ff service cryptdisks restart
results in one tracefile per pid, from which I attached the two that did
not normally finish (I pressed Ctrl-C).
Regards
** Attachment added: strace.tar
http://launchpadlibrarian.net/43766585/strace.tar
--
no
** Attachment added: all strace files
http://launchpadlibrarian.net/43767306/strace.tar.gz
--
no password prompt for cryptsetup in 10.04 64-bit server
https://bugs.launchpad.net/bugs/560105
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
strace.txt.1165 shows that 'plymouth --ping' gets called, and instead of
immediately exiting because plymouthd isn't running, it manages to
connect to plymouthd and then hangs waiting for an answer!
Why is plymouthd running on your system? It's only supposed to be
running at startup or shutdown.
I don't know, actually.
The system has been upgraded since the alpha-1 stage.
So maybe it's some residue from earlier stages?
Would it been wise to reinstall (and update/upgrade) ?
Strange thing is that my Ubuntu 64-bit desktop installation doesnt seem
to have this problem.
--
no password
Could it be that plymouth quit is just not working ?
root 247 1 0 12:20 ?00:00:02 /sbin/plymouthd --mode=boot
--attach-to-session --pid-file=/dev/.initramfs/plymouth.pid
root 882 1 0 12:20 ?00:00:00 /bin/plymouth quit
root 1587 1105 0 15:40 pts/2
If I manually kill the plymouth commands:
mountall: Plymouth command failed
Seems it's going wrong in mountall ?
--
no password prompt for cryptsetup in 10.04 64-bit server
https://bugs.launchpad.net/bugs/560105
You received this bug notification because you are a member of Ubuntu
Bugs, which
After killing the plymouth stuff manually, I'm able to use cryptdisks.
For now I 've adapted my script to kill everything called plymouth ;-)
--
no password prompt for cryptsetup in 10.04 64-bit server
https://bugs.launchpad.net/bugs/560105
You received this bug notification because you are a
Well, since you've killed plymouth manually, we may never find out now
why it was hanging. Marking this bug as invalid; if you're able to
reproduce the problem again on a subsequent reboot and can provide more
debugging info (such as a backtrace of plymouthd with gdb), please
reopen.
** Changed
Some extra information:
1) splash hangs also
2) strace output is attached
** Attachment added: strace cryptsetup restart
http://launchpadlibrarian.net/43700517/strace.cryptsetup.txt
--
no password prompt for cryptsetup in 10.04 64-bit server
https://bugs.launchpad.net/bugs/560105
You
Thank you for taking the time to report this issue and help to improve
Ubuntu.
Is the device mounted at the time you try to restart it?
Please run strace with the '-ff' option; the attached strace tells us
nothing, since only the 'service' command is being traced and not the
underlying
25 matches
Mail list logo
