[Bug 351251] Re: Jaunty Gimp running inside Xephyr causes a Segmentation fault

Exactly the same here with gimp and inkscape: Backtrace (8 deep): 0: Xephyr(KdBacktrace+0x35) [0x80c1595] 1: [0xb8041400] 2: Xephyr(ProcXGrabDevice+0x12a) [0x8195a0a] 3: Xephyr [0x81924e3] 4: Xephyr(Dispatch+0x33f) [0x80b356f] 5: Xephyr(main+0x3bd) [0x809869d] 6: /lib/tls/i686/cmov/libc.so.6(__lib

[Bug 119020] Re: kernel oops while using cryptsetup

Problem appears to be fixed in newer kernels, using 2.6.22-7-generic from gutsy I cannot trigger the bug anymore. -- kernel oops while using cryptsetup https://bugs.launchpad.net/bugs/119020 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for U

[Bug 70671] Re: cryptsetup luksAddKey fails on dapper

You need to specify a device node for the encrypted partition, not the path where the device it is mounted; For the key file, add the full path. You are confusing devices in /dev with "normal" files and folders. Furthermore, you most probably need root permissions to write to a device directly:

[Bug 81164] Re: [feisty] boot stalls on "starting kernel event manager"

2.6.20-16.29 fixed the problem - at least in my case. -- [feisty] boot stalls on "starting kernel event manager" https://bugs.launchpad.net/bugs/81164 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubu

[Bug 87477] Re: Unusual Boot Messages (hde: lost interrupt)

*** This bug is a duplicate of bug 81164 *** https://bugs.launchpad.net/bugs/81164 ** This bug has been marked a duplicate of bug 81164 [feisty] boot stalls on "starting kernel event manager" -- Unusual Boot Messages (hde: lost interrupt) https://bugs.launchpad.net/bugs/87477 You received

[Bug 81164] Re: [feisty] boot stalls on "starting kernel event manager"

I can confirm that 2.6.20-15 still works; 2.6.20-16 only is bootable with the irqpoll kernel parameter. -- [feisty] boot stalls on "starting kernel event manager" https://bugs.launchpad.net/bugs/81164 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug con

[Bug 119020] Re: kernel oops while using cryptsetup

** Attachment added: "lspci -vvnn output" http://launchpadlibrarian.net/8007888/lspci -- kernel oops while using cryptsetup https://bugs.launchpad.net/bugs/119020 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs

[Bug 119020] Re: kernel oops while using cryptsetup

nvidia module was intentionally not loaded while producing oops above. ** Attachment added: "dmesg output" http://launchpadlibrarian.net/8007882/dmesg -- kernel oops while using cryptsetup https://bugs.launchpad.net/bugs/119020 You received this bug notification because you are a member of Ub

[Bug 119020] kernel oops while using cryptsetup

Public bug reported: Binary package hint: linux-source-2.6.20 I get the following kernel oops while using cryptsetup (Luks) to add keys, remove them or just opening the device - almost every time. Sometimes the system just freezes without any further trace. The crucial point - I think - is that

[Bug 78288] Re: kernel 2.6.20-11,13 doesn't boot with sata-hd

>From remotely supporting an edgy->feisty upgrade, I conclude that this bug reappeared in 2.6.20-16; Using irqpoll to boot the system and then installing 2.6.20-15 resolved the issue. See also bug #81164 for similar reports. -- kernel 2.6.20-11,13 doesn't boot with sata-hd https://bugs.launchpad