[Bug 505278] Re: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added?
Confirmed in 14.04.4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/505278 Title: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added? To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/505278/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 584048] Re: kvm images losing connectivity w/bridged network
I have the same 4-second bridge freeze when using LXC containers and
lxc-start or lxc-stop. (I am using a custom script to create my LXC
containers.) I saw the reference to this above:
https://www.redhat.com/archives/libvir-list/2010-July/msg00450.html
I changed my custom script from this:
MACADDR=00:16:3e:`head /dev/urandom | md5sum | sed -r
's/^(.{6}).*$/\1/; s/([0-9a-f]{2})/\1:/g; s/:$//;'`
...to this:
MACADDR=fe:16:3e:`head /dev/urandom | md5sum | sed -r
's/^(.{6}).*$/\1/; s/([0-9a-f]{2})/\1:/g; s/:$//;'`
...and now the freezing is gone.
Since this is my own custom script, I'm not sure what package it would
belong to. Just be aware that this is a fundamental bridge issue and
not limited to libvirt, KVM. It shows up with LXC and probably any
other system where you add a new MAC.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/584048
Title:
kvm images losing connectivity w/bridged network
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 673705] Re: running guests freeze when a guest is powered down
This bug is probably a duplicate issue as this: https://bugs.launchpad.net/ubuntu/maverick/+source/qemu-kvm/+bug/584048 The problem is with Linux bridging. When adding or removing a MAC address (like for KVM, VirtualBox, or even LXC) then if the bridge changes its MAC, this symptom happens. See comment #60 at the URL above, and also see this: https://www.redhat.com/archives/libvir-list/2010-July/msg00450.html The workaround is to use a MAC address that starts with fe (or any high really high number) for your guests. This causes the kernel to default to the hardware MAC for the bridge. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/673705 Title: running guests freeze when a guest is powered down -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 578930] Re: qemu-kvm: ksmd should have a less CPU-hogging default config
I'm getting burned by this too, and I disagree with Mr. Kirkland's assertion that Ubuntu should just use the upstream default. There are many, many Ubuntu packages which alter the upstream default to make Ubuntu a more user-friendly experience. One could even argue that Ubuntu's best feature is that it changes the upstream defaults of the world to be something that actually works for human beings. Please, set this to a reasonable value (200ms?). As has been pointed out, the upsteam default is not even considered a reasonable value by the upstream maintainers. Ethically speaking, this bug is causing more CPU power consumption (and thus, global warming) for absolutely no reason whatsoever. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/578930 Title: qemu-kvm: ksmd should have a less CPU-hogging default config -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 563805] Re: mount.cifs won't mount shares; set uid bit not set
I disagree with Dietmar's comment #5, which says that 9.10 didn't have the setuid bit. Here is my Ubuntu 9.10: r...@cst6:~# ls -la /bin/mount /sbin/mount.cifs -rwsr-xr-x 1 root root 78096 2009-10-22 21:28 /bin/mount -rwsr-xr-x 1 root root 36296 2010-03-22 15:27 /sbin/mount.cifs Here is my Ubuntu 10.4: r...@cst5:/etc/samba# ls -la /bin/mount /sbin/mount.cifs -rwsr-xr-x 1 root root 82256 2010-03-22 10:57 /bin/mount -rwxr-xr-x 1 root root 35648 2010-04-09 10:38 /sbin/mount.cifs As an aside, I see that /sbin/mount.nfs are still set to be setuid (in Ubuntu 10.4): r...@cst5:/etc/samba# ls -la /sbin/mount.nfs -rwsr-xr-x 1 root root 94544 2010-03-23 23:18 /sbin/mount.nfs -- mount.cifs won't mount shares; set uid bit not set https://bugs.launchpad.net/bugs/563805 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 551655] Re: open-whois.org is cybersquatted and its rules should be removed from Spamassassin
If I understood Mathias' comment, he just wants somebody to do steps one and two of the update procedure to justify backporting this bug. So, here goes: Step 1: The bug is fixed in the latest branch, and it is flagged fixed released (as per above). Done. Step 2: I am updating the bug description with the required information below. Step 2.1: The impact is that users of 8.04 are getting false positives from SpamAssassin. I'm seeing it on an eBox system (eBox is an email system based on Ubuntu that includes SpamAssassin). Step 2.2: The bug was addressed as per this bug report. (See above.) Step 2.3: Patch: I don't have one, sorry. The patch is just to remove all the open-whois.org from /usr/share/spamassassin/72_active.cf ; the patch used above should suffice. Step 2.4: To repro the bug: let SpamAssassin filter a mail and flag it (as per defaults). You'll see a header like: X-Spam-Status: No, score=2.431 required=5 tests=[DNS_FROM_OPENWHOIS=2.431] Once the fix is in place the DNS_FROM_OPENWHOIS rule (and all other open-whois.org rules) should be gone. Step 2.5: I don't see how a regression could inadvertently be affected. The open-whois.org service is dead, the domain has been taken by a squatter, and 100% of all SpamAssassin installs should have these rules removed. I hope the lack of a patch won't prevent this from getting backported. I'm as excited about 10.4 as anyone, but I won't be upgrading my email systems for several weeks or months. (The OpenLDAP upgrade is broken, due to cn=config and bugs like #364531, so moving from 8.04 to 10.4 for my email systems will be a huge investment of time.) Thank You, Derek Simkowiak -- open-whois.org is cybersquatted and its rules should be removed from Spamassassin https://bugs.launchpad.net/bugs/551655 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 442498] Re: openldap install bare bones need default DIT separate package
In my opionion, the new (useless) slapd package should not have shipped until the accompanying slapd-dit was ready. It basically broke LDAP for everyone but experts, and now Mathias doesn't have time to fix it. Mathias, can you make slapd-dit a priority? It's been several months since a usable slapd has been available for Ubuntu. ** Changed in: openldap (Ubuntu) Status: Triaged = Confirmed -- openldap install bare bones need default DIT separate package https://bugs.launchpad.net/bugs/442498 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 253937] Re: Local login fails without LDAP server
Same thing here on Ubuntu 9.10. Here is a (possibly) relevant nss_ldap thread: http://old.nabble.com/No-timeout-for-nss_ldap--td14576190.html Unfortunately, that thread ends with I am looking at fixing this now and providing some time outs on the soft path as well. Will keep you informed. That was back in 2008. In my opinion this is an important bug. One of the major reasons for using LDAP+nss is for high availability in corporate networks... and this bug breaks that completely. -- Local login fails without LDAP server https://bugs.launchpad.net/bugs/253937 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 253937] Re: Local login fails without LDAP server
Here is another relevant thread (from April 2009): http://old.nabble.com/nss-ldap-timeouts--when-used-with-nscd-and-gnutls- td23145909.html -- Local login fails without LDAP server https://bugs.launchpad.net/bugs/253937 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 442498] Re: karmic openldap cut-to-bone-and-beyond install, why ????
*** This bug is a duplicate of bug 463684 *** https://bugs.launchpad.net/bugs/463684 Please, provide a working default configuration with the common schemas (inetOrgUser, sambaUser, maybe virtual mail domains). Do we really need to argue the benefits an easy-to-install network LDAP server? As of 9.04 the client installation was very straight-forward... but right now the fastest way to get a usable Ubuntu LDAP server is to install eBox, which comes with hundreds of megs of stuff that we really don't need. Even though I know how to configure a slapd server by hand, doesn't mean I want to waste my time doing it. -- karmic openldap cut-to-bone-and-beyond install, why https://bugs.launchpad.net/bugs/442498 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 319656] Re: nmap script engine error
The latest 9.04 package 4.76-0ubuntu4 is still broken. Can we get a backport? I'm not moving to 9.10 because of all the new bugs it introduced... (I can't use 8.04 LTS because I need some of the newer 9.04 packages.) -- nmap script engine error https://bugs.launchpad.net/bugs/319656 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nmap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
