[Bug 1033443] [NEW] udev-175-0ubuntu9.1 broken when custom udev rules are present
Public bug reported: On a 12.04 system I've been in the process of creating some custom udev rules for removable USB devices. In fact I'm writing a udev rule that calls cryptsetup luksOpen --key-file=/media/uuid/of/my/keyfile/on/usb. The rule actually unlocks an internal spinning disk, and then mounts the disk. I was just about finished creating the udev rule, as it was correctly unlocking the encrypted container and mounting the real ext4 partition as well. The only thing left I had to do was add to the rule options for when the USB device is removed, run umount and luksClose. In between this came udev-175-0ubuntu9.1. I did not think that this would break my work, but it has. My basis for this is that when I call cryptsetup luksOpen from the command line when the latest update to udev is installed the commands work succesully. However, the same commands ran from my udev rule do not work correctly with 75-0ubuntu9.1. In my syslog I see errors about timeouts, and dozens of temporary-crypt-00253 type entries in /dev/mapper, when there should only be the one entry the udev rule contains. (/dev/mapper/cryptstorage1) Additionally, The machine starts to lockup, and becomes unresponsive. It's an Intel Corei5 with 16GB ram, doing absolutely so heavy lifting, so there is no valid reason for the machine to be unresponsive. Since 175-0ubuntu9.1, I've seen errors about semaphores, and check if the kernel has support for the aes-xts-plain64 cipher. This is especially infuriating because the root partition is encrypted with the same exact cipher, and the rest of the system works fine until my udev rule is brought into play. I am using kmod aesni_intel, for what it's worth. To test my thoery, I have manually rolled back to the previous version of udev and libudev0, and then once again my udev rule works correctly again. ** Affects: udev (Ubuntu) Importance: Undecided Status: New ** Tags: custom rules udev -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033443 Title: udev-175-0ubuntu9.1 broken when custom udev rules are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1033443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1033443] Re: udev-175-0ubuntu9.1 broken when custom udev rules are present
** Attachment added: custom rule that breaks with udev-175-0ubuntu9.1 https://bugs.launchpad.net/bugs/1033443/+attachment/3249834/+files/45-usb-crypto.rules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1033443 Title: udev-175-0ubuntu9.1 broken when custom udev rules are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1033443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911689] Re: [precise] [oneiric-alpha1] bootup hangs after ~ 4 secs due to nouveaufb - EFI VGA conflict
I have been testing pure EFI booting with precise on a MacBook Pro (4,1 or 3,1) using grub-efi-amd64. When I have quiet and splash removed from the boot options I am seeing the same error message: fb: conflicting fb hw usage nouveaufb vs EFI VGA - removing generic driver background info: To get started I booted from precise Live CD in BIOS emulation mode. (note, this works great!) I bootstrapped the install of precise using rsync and a chroot so I could get precise onto the hard disk and then replace grub-pc with grub-efi-amd64 while in the chroot. The only way I can boot precise successfully is by running these steps 1. setting the text option for GRUB_CMDLINE_LINUX_DEFAULT in the file /etc/default/grub, and then running update-grub2 when booted from the precise Live CD again. (chroot) 2. creating a file named blacklist-nouveau.conf in /etc/modprobe.d (file contents blacklist nouveau 3. running update-initramfs If I remove the nouveau blacklist and remove text from grub2, I'm back to the error message above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911689 Title: [precise] [oneiric-alpha1] bootup hangs after ~ 4 secs due to nouveaufb - EFI VGA conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/911689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911689] Re: [precise] [oneiric-alpha1] bootup hangs after ~ 4 secs due to nouveaufb - EFI VGA conflict
** Changed in: linux (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911689 Title: [precise] [oneiric-alpha1] bootup hangs after ~ 4 secs due to nouveaufb - EFI VGA conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/911689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 834487] Re: Add keyboard layout indicator to unity-greeter
I have to add my comments to this one too. Being able to change the keyboard layout at the login screen is something that GNOME has supported for years. It is required functionality when more than one layout is configured on the system. For example, here we use English Dvorak and English US (qwerty) layouts on the same machines and keyboards. Being able to switch layouts at the login screen is essential to be able to properly type in user names and passwords. One of Ubuntu's primary goals is usability, and not having an option to select a layout at the login screen is damaging to usability. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/834487 Title: Add keyboard layout indicator to unity-greeter To manage notifications about this bug go to: https://bugs.launchpad.net/unity-greeter/+bug/834487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 844039] Re: Unity Greeter - By default the 'Other' login option should not be displayed
On Linux Mint 12, using the following options in the file, /etc/lightdm/lightdm.conf greeter-hide-users=true allow-guest=false unity-greeter displays Other... at the top, when it should say Login because the user list is disabled. Other... has no meaning or purpose here, and to be completely honest it looks very strange. in unity-greeter.c I see Other... mentioned in at least three places. (Lines 598,684,1299) I'm guessing these could be changed to say Login to accomplish what would make some sort of sense. This particular machine is not using NIS login or card readers, all logins are local but we don't want the list of local user names displayed. Here is a link to a forum user looking for the same thing, changing Other... to Login when the user list is disabled. http://ubuntuforums.org/showthread.php?t=1858962 quoteAlso is there a way to change 'Other...' to 'Login' when the user listing is disabled?/quote Also, if you switch to high-contrast mode, Other... is displayed in its normal location, but also, two more times below where you enter a user name,for a total of three Others... Please accept my apologies in advance if all of this is something that is now fixed, but not merged into downstream Mint 12. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/844039 Title: Unity Greeter - By default the 'Other' login option should not be displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/844039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 745245] Re: Seahorse cannot set up SSH keys for login servers
I have the same issue on a clean install of Natty beta 2. ** Attachment added: seahorse-natty-ssh-issue_screenshot https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/745245/+attachment/2046500/+files/seahorse-ssh-issue.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745245 Title: Seahorse cannot set up SSH keys for login servers -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 564436] [NEW] network places does not inform users to use brackets for IPv6 address
Public bug reported: Binary package hint: gnome-panel On Lucid development branch, network places gives generic error message when trying to connect to a server over IPv6, rather than suggesting the user place the address in square brackets. [ ] Further more, placing the address address in brackets is not an intuitive method for users to connect to remote machines. If brackets are indefinitely needed place a reminder in the connect to server window after it's open. To clarify when connecting to (for example) an openssh server that listens on IPv6: this won't work: 2001:470:1f06:a25:a00:24ff:fe77:2bb but this will work:[2001:470:1f06:a25:a00:24ff:fe77:2bb] ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: connect ipv6 network places -- network places does not inform users to use brackets for IPv6 address https://bugs.launchpad.net/bugs/564436 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
[Bug 564440] [NEW] connect to server address box to small for user to properly see IPv6 address
Public bug reported: Binary package hint: gnome-panel On Lucid development branch (and earlier), connect to server address input box is too small to fully display a IPv6 address. Needs to be made large enough for a user to see a full IPv6 address without scrolling. Notice how the address gets cut off in attached screen shot. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: connect ipv6 network places server -- connect to server address box to small for user to properly see IPv6 address https://bugs.launchpad.net/bugs/564440 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
[Bug 564440] Re: connect to server address box to small for user to properly see IPv6 address
** Attachment added: address input too small to dispaly full ipv6 http://launchpadlibrarian.net/44398478/connect-ipv6-short-sm.png -- connect to server address box to small for user to properly see IPv6 address https://bugs.launchpad.net/bugs/564440 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
[Bug 375088] Re: IPv6 addresses are hidden
I have IPv6 running on Lucid, and this is still a valid bug in Lucid. No IPv6 address or info is displayed in Network Manager's connection information dialog box. Network Manager should display connection info for both IP types on dual-stacked installations of Ubuntu. -- IPv6 addresses are hidden https://bugs.launchpad.net/bugs/375088 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
