[Bug 1173457] Re: Ubuntu Installer uses wrong bootloader location for USB UEFI installs
I managed to clean up the damage I used efibootmgr to delete the EFI boot entries on the Windows drive I then booted an Ubuntu USB stick, followed Gentoo's guide for mounting and chrooting into the Ubuntu environment I needed to fix https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base I then did grub-install --target=x86_64-efi --efi-directory=/boot/efi, where /boot/efi had my external drive's EFI partition mounted up https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Bootloader I checked the drive with efibootmgr to make sure Grub installed right, it did. This is a really critical bug for any desktop user... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173457 Title: Ubuntu Installer uses wrong bootloader location for USB UEFI installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1173457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173457] Re: Ubuntu Installer uses wrong bootloader location for USB UEFI installs
How do I clean this up if I was affected? My EFI partition on my external drive is empty, internal one has grub. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173457 Title: Ubuntu Installer uses wrong bootloader location for USB UEFI installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1173457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173457] Re: Ubuntu Installer uses wrong bootloader location for USB UEFI installs
https://answers.launchpad.net/ubuntu/+question/662540 Is this what is happening to me here? This is pretty critical - Ubuntu is touching drives it is told not to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173457 Title: Ubuntu Installer uses wrong bootloader location for USB UEFI installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1173457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360342] Re: Add Multi-arch support in libxi-dev
Ditto. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360342 Title: Add Multi-arch support in libxi-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/1360342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 407875] Re: Kindle 2 HAL support
Hi, This needs a quirk in unusual_devs.h to force max sectors to 64 https://lists.one-eyed-alien.net/pipermail/usb-storage/2009-August/004789.html It does work with that option, otherwise it will corrupt data or work erratically. I never got around to submitting a patch upstream...but it was working fine. I had it working in udev 145 on gentoo, but I'm on ubuntu now.. I am not sure if the device is being correctly detected with udev 147/the kerne in ubuntu server 9.10. It may be being detected with the wrong protocol, again. I need to install kernel sources and mess with it...unless someone who is better with udev and kernel hacking wants to step in... :sigh: -- Kindle 2 HAL support https://bugs.launchpad.net/bugs/407875 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 398549] Re: Slapd, unless started manually, will not work with saslauthd
Ok, figured it out /etc/init.d/saslauthd start a folder is created, /var/run/saslauthd with the socket and pid drwx--x--- owner root group sasl openldap user does not have access to this folder added openldap to sasl group and it works Is this normal behavior? -- Slapd, unless started manually, will not work with saslauthd https://bugs.launchpad.net/bugs/398549 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 398549] Re: Slapd, unless started manually, will not work with saslauthd
I'm not sure..but /usr/lib/sasl2 you need to have a file called slapd.conf there, pwcheck_method:saslauthd for this to work under any account, root or not It's chmodded a+r right now, it's not working still under the openldap account And I take it back, slapd -g openldap -u openldap, sasl still isn't working, but -u root works fine... -- Slapd, unless started manually, will not work with saslauthd https://bugs.launchpad.net/bugs/398549 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 398549] [NEW] Slapd, unless started manually, will not work with saslauthd
Public bug reported:
Ubuntu Server 9.04 32 bit
package version slapd 2.4.15-1ubuntu3
Problem: does not work with saslauthd unless running as root
To reproduce:
install slapd, saslauthd, krb kdc server
you can run saslauthd -d -a kerberos5 & or check logs in var to see if
slapd is communicating with saslauthd
start up slapd and the kdc
in ldap, set a userPassword to {sasl}u...@yourealm
Try to auth as that user, will fail, saslauthd doesn't output anything
in the logs, slapd doesnt appear to be communicating with it
if you edit /etc/default/slapd.conf and comment out SLAPD_USER and
SLAPD_GROUP or set them to root, and use the init script to launch, sasl
auth works fine, you can see ldap connect in saslauthd's logs and debug
output
also, starting slapd manually by going slapd -u openldap -g openldap
will work
It doesn't make sense, I don't see any chrooting, so it should be able
to hit saslauthd's socket file fine...
** Affects: openldap2.3 (Ubuntu)
Importance: Undecided
Status: New
--
Slapd, unless started manually, will not work with saslauthd
https://bugs.launchpad.net/bugs/398549
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
