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 track down what process is the client
connection for this socket, we would certainly like to fix this end of
the problem as well.
> 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 ;-)
Oh, there are definitely quite a few cryptsetup users around, and I've
heard from many of them through the Lucid development cycle - and a lot
of effort has gone into fixing their bugs for 10.04 LTS (and my own
bugs, since I'm a cryptsetup user myself). This particular bug hasn't
come up before now.
** Changed in: plymouth (Ubuntu)
Importance: Undecided => Medium
** Changed in: plymouth (Ubuntu)
Status: Incomplete => Triaged
--
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 list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
