[Bug 408612] [NEW] seahorse does not display the password tab

2009-08-03 Thread Shiv V
Public bug reported: Binary package hint: seahorse seahorse (2.27.5-0ubuntu1) does not display the Passwords tab. Downgrading to 2.26.1-0ubuntu1 from jaunty fixes the issue and allows the user to see/modify all the keyring secrets. Release: Ubuntu karmic (with all updates) Arch: i386 What I

[Bug 316607] Re: Encrypted SWAP partition not created/mounted

2009-02-13 Thread Shiv V
The sed part isn't necessary. I only put it in for the sake of robustness against future updates/regressions to vol_id. In the past, 'vol_id -t /dev/null' used to report /dev/null: unknown volume type. Now it does not mention the device that was probed, just the result unknown or non-unique

[Bug 316607] Re: Encrypted SWAP partition not created/mounted

2009-02-13 Thread Shiv V
Also, when I checked the vol_id source, error code 4 was not restricted to the unknown device type case. I can't remember of the top of my head what the other cases were that also returned error 4, but as of a month ago, there were some. -- Encrypted SWAP partition not created/mounted

[Bug 327481] [NEW] seahorse does not display passwords from login.keyring

2009-02-09 Thread Shiv V
Public bug reported: Binary package hint: seahorse I just noticed that /usr/bin/seahorse (2.25.4-0ubuntu1) does not display passwords in my .gnome2/keyrings/login.keyring. The password tab is empty. Trying to create a new keyring does not work: choosing File New Password Keyring does

[Bug 317442] [NEW] initrd does not contain conf/conf.d/cryptroot file for encrypted root

2009-01-15 Thread Shiv V
Public bug reported: Binary package hint: cryptsetup Ubuntu Jaunty amd64, cryptsetup 2:1.0.6-7ubuntu1, initramfs-tools 0.92bubuntu18, udev 136-4 I have an encrypted root so the initrd has to decrypt it during boot. Previously, initrds generated with initramfs-tools had a conf/conf.d/cryptroot

[Bug 317442] Re: initrd does not contain conf/conf.d/cryptroot file for encrypted root

2009-01-15 Thread Shiv V
Despite there being a NAME=mapper/$env{DM_NAME} rule in /lib/udev/rules.d/65-dmsetup.rules, udevadm test /devices/virtual/block/dm-5 either does not get to it or does not apply it. Instead I get: [ ... snip ... ] udev_event_execute_rules: no node name set, will use kernel name 'dm-5' [ ... snip

[Bug 317442] Re: initrd does not contain conf/conf.d/cryptroot file for encrypted root

2009-01-15 Thread Shiv V
I took a look at all the rules in /lib/udev/rules.d and noticed that every 'NAME=' assignment is preceeded by a conditional (e.g. KERNEL== or SUBSYSTEM==). Adding a conditional seems to make the rule apply. Here's what I did: --- a/lib/udev/rules.d/65-dmsetup.rules 2009-01-09 06:02:58.0

[Bug 317442] Re: initrd does not contain conf/conf.d/cryptroot file for encrypted root

2009-01-15 Thread Shiv V
** Tags added: dmsetup udev -- initrd does not contain conf/conf.d/cryptroot file for encrypted root https://bugs.launchpad.net/bugs/317442 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 316607] Re: Encrypted SWAP partition not created/mounted

2009-01-14 Thread Shiv V
It seems this is due to a change in vol_id (udev package). vol_id (udev: 124-12) used to say /dev/mapper/swap: unknown volume type when it failed to find a known filesystem on /dev/mapper/swap. After my latest update, vol_id (udev: 136-4) says unknown or non-unique volume type (--probe-all lists

[Bug 304315] [NEW] no support for blowfish passwords

2008-12-02 Thread Shiv V
Public bug reported: Binary package hint: libpam-unix2 See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487487 for upstream bug. Changing password fails with no blowfish support compiled in message in syslog. Need a backport from jaunty libpam-unix2 (1:2.4.1-2). Ubuntu: 8.10 i386