[14:48] <hjd> Any opinions on whether to reopen bug 965272 or if I should simply file a new bug?
[15:22] <da3m0n22> hello, anybody could review this bug please? https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261
[15:23] <da3m0n22> after being confirmed, we fell into this issue too, and i'm unable to fix that, if anybody knows workaround, it isn't posted there
[15:23] <da3m0n22> and i haven't found it either
[15:24] <penguin42> da3m0n22: Does it dump you at an initramfs prompt?
[15:25] <da3m0n22> penguin42: nope, it dumps core
[15:26] <penguin42> da3m0n22: What do you actually mean by dumps core?
[15:27] <da3m0n22> kernel panic, with core dumped error message
[15:27] <penguin42> da3m0n22: Can you get a capture of that - photo ?
[15:28] <penguin42> da3m0n22: I'm wondering what dumped; it sounds like init perhaps
[15:29] <da3m0n22> penguin42: yes, it's init dumped, showing lines of "plymouth-upstart-bridge--started terminated with status 6", "error.c:219 Assertion failed in _nih_error_raise_system: errno > 0"
[15:29] <da3m0n22> and "Error whie reading from descriptor: Bad file descriptor"
[15:30] <da3m0n22> penguin42: see images, https://plus.google.com/photos/115401880503838928078/albums/6066739816541481313?banner=pwa
[15:31] <da3m0n22> first is core dump, it's scrolled too far down, if i append "recovery" into boot params, it won't scroll so far
[15:31] <da3m0n22> second appears to be the same issue as in linked bug
[15:32] <da3m0n22> azur is volume group, root is partition
[15:32] <da3m0n22> penguin42: ^
[15:33] <da3m0n22> it's root filesystem, encrypted, which is game stopper for now
[15:33] <penguin42> da3m0n22: I've marked that bug 'high' - are you sure it's the same bug though
[15:33] <da3m0n22> it appears from second image
[15:33] <penguin42> da3m0n22: Their initial report doesn't mention the cores
[15:34] <da3m0n22> penguin42: honestly, it may be another issue than which we are facing
[15:35] <penguin42> da3m0n22: Can you post yours as a new bug, and file it against plymouth
[15:36] <penguin42> da3m0n22: Mention that other bug in the message, and tell us the bug number and I'll also mark it high
[15:37] <da3m0n22> penguin42: i'll do, thanks
[15:37] <penguin42> da3m0n22: The thing is anything that causes the decryption/lvm setup to fail will probably get you a similar error about not finding the /dev entry - but those abort's are better diagnosis for a particular cause
[15:37] <da3m0n22> penguin42: from what you see, do you think there is something which could be done now?
[15:37] <da3m0n22> i've been into rescue, volume mounts correctly, tried update-initramfs which didn't helped
[15:38] <penguin42> da3m0n22: It's hard; most of the time when these thing screw up they drop you to an initramfs and you can manually recover, but it looks like that's crashing
[15:38] <penguin42> da3m0n22: I'd try disabling the graphical boot
[15:38] <da3m0n22> yup, i've tried to add sh/ash into scripts/cryptsetup but that only screwes up the booting screen
[15:38] <penguin42> da3m0n22: See if you can remove plymouth?
[15:39] <da3m0n22> penguin42: i could probably, will test in a minute
[15:43] <da3m0n22> penguin42: oh, actually this lead me to this, https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284
[15:43] <da3m0n22> we also have 14.04 box
[15:45] <da3m0n22> is it possible for AppArmor to interfere in initrd creation ?
[15:45] <penguin42> A screwed up AppArmor could break anything - but I've not seen it break initrd
[15:46] <penguin42> da3m0n22: Just checking, your /boot isn't full is it?
[15:47]  * penguin42 gets confused between High: 'For example if the system fails to boot' and  Critical: 'Renders the system temporarily or permanently unusable'
[15:47] <penguin42> but I tend to leave critical to bugs that actually corrupt data or emit smoke
[15:48] <da3m0n22> penguin42: /boot is 68% full, leaving 146M free
[15:49] <penguin42> da3m0n22: OK, probably not that; I often see /boot get full during updates and cause complete chaos creating the initramfs
[15:49] <da3m0n22> also, aptitude from recovery reports segfault
[15:50] <penguin42> that's also not good; I'm wondering if you've got any other problems
[15:51] <da3m0n22> penguin42: me too, colleague who suffers from this issue is trying to remove the plymouth/apparmor
[15:51] <penguin42> da3m0n22: I'd advise against removing any of the apparmor stuff
[15:52] <da3m0n22> penguin42: even with backups?
[15:53] <penguin42> da3m0n22: It just sounds like it'll create more pain
[15:56] <da3m0n22> penguin42: plymouth is not easy to be removed, some conflicts appear with xorg, nvidia and udev
[15:56] <penguin42> hmm ok