[Bug 137311] Re: kcontrol-modules are broken

2007-12-08 Thread LimCore
** Changed in: kdebase (Ubuntu) Status: Confirmed => Invalid ** Changed in: kdebase (Ubuntu) Status: Invalid => Confirmed -- kcontrol-modules are broken https://bugs.launchpad.net/bugs/137311 You received this bug notification because you are a member of Kubuntu Team, which is a bu

[Bug 137311] Re: kcontrol-modules are broken

2007-12-08 Thread LimCore
Also exists in debian, btw ** Changed in: kdebase (Ubuntu) Status: New => Confirmed -- kcontrol-modules are broken https://bugs.launchpad.net/bugs/137311 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs maili

[Bug 137311] Re: kcontrol-modules are broken

2007-12-08 Thread LimCore
I seen simmilar bug in Debian. On Ubuntu I seen related (probably) bug, where some of the modules are missing (like, Monitors&Display, and if I start Display module by hand I get an empty window with no settings at all) -- kcontrol-modules are broken https://bugs.launchpad.net/bugs/137311 You re

[Bug 174738] Re: ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel

2007-12-07 Thread LimCore
Would it be nice to have losetup hint user about needed modules? ** Changed in: loop-aes-utils (Ubuntu) Assignee: (unassigned) => LimCore (limcore) Status: New => Invalid -- ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by

[Bug 174738] Re: ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel

2007-12-07 Thread LimCore
Ah, cryptoloop was not polled in automagically when modprobing aes... Hmm perhaps losetup could be a bit more verbose and hint user about lack of cryptoloop... Thanks -- ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel https://bugs.lau

[Bug 174738] Re: ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel

2007-12-07 Thread LimCore
** Tags added: aes amd64 kernel -- ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel https://bugs.launchpad.net/bugs/174738 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu.

[Bug 174738] Re: ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel

2007-12-07 Thread LimCore
The test is done after modprobing for aes. I am not sure, perhaps the bug should be for the kernel? Or am I doing something wrong, but the way above worked always (tested on other distro) -- ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by ke

[Bug 174738] ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel

2007-12-07 Thread LimCore
Public bug reported: ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel when setting up losetup -e aes-256 (or aes-128) Ubuntu 7.10 on amd64 with 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux - REPRODUCE

<    3   4   5   6   7   8