This was in response to your (!) comment #106: > The right fix is to eliminate all uses of "console owner" (which is > clearly wrong) and get rid of it.
usplash clearly has nothing to do with this bug, cryptsetup is responsible for taking away the console from X, and the place where you would get rid of "console owner" is upstart, right? Now if someone familiar with the cryptsetup package could explain why it needs console ownership, we could actually get anywhere. Scott James Remnant wrote: > On Tue, 2009-10-13 at 15:46 +0000, Tom Jaeger wrote: > >> ** Also affects: cryptsetup (Ubuntu) >> Importance: Undecided >> Status: New >> >> ** Changed in: cryptsetup (Ubuntu Karmic) >> Status: New => Confirmed >> >> ** Changed in: usplash (Ubuntu Karmic) >> Status: Confirmed => Invalid >> >> ** Changed in: upstart (Ubuntu Karmic) >> Status: Invalid => Confirmed >> > Why have you made these changes? > > Please provide an explanation - do you have a proposed fix for the bug > that fits these status changes - or do you have detailed debugging that > proves that they are correct. > > If not, please don't randomly reassign packages. > > Scott -- [karmic] Xorg 100% CPU utilization -- only after first login https://bugs.launchpad.net/bugs/439138 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
