[Bug 550905] Re: jockey fails to install linux-headers-generic metapackage (was: dkms does not run when upgrade downloads new kernel version)
When I look in the source packageof jockey I saw this line in data/handlers/nvidia.py: def enable(self): # Ensure that the necessary kernel headers need to be installed kernel_headers = 'linux-headers-' + os.uname()[2] ... Why does jockey not use kernel_headers = 'linux-headers-generic here? apt-get would automatically install the correct headers and using it would be safe between kernel-upgrades: $ dpkg -s linux-headers-generic | grep Depends Depends: linux-headers-2.6.32-26-generic -- jockey fails to install linux-headers-generic metapackage (was: dkms does not run when upgrade downloads new kernel version) https://bugs.launchpad.net/bugs/550905 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 657302] Re: ssh X11 forwarding does not work
Instead of edititing /etc/init/ssh.conf (exec /usr/sbin/sshd -4) you can add AddressFamily inet to /etc/ssh/sshd_config which lets sshd only listen to IPv4. -- ssh X11 forwarding does not work https://bugs.launchpad.net/bugs/657302 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 657302] Re: ssh X11 forwarding does not work
Instead of edititing /etc/init/ssh.conf (exec /usr/sbin/sshd -4) you can add AddressFamily inet to /etc/ssh/sshd_config which lets sshd only listen to IPv4. -- ssh X11 forwarding does not work https://bugs.launchpad.net/bugs/657302 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 645318] Re: pam-auth-update does not obey debconf preseeding
Ok, if the 'seen'-flag is essential then it was my mistake. - You may close this bug report Your question: We are not using a p-a-u profile as we are also deploying native debian clients which to not have p-a-u. We want do keep the configuration differences between Debian- and Ubuntu-Clients as small as possible. -- pam-auth-update does not obey debconf preseeding https://bugs.launchpad.net/bugs/645318 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 645318] [NEW] pam-auth-update does not obey debconf preseeding
Public bug reported: We deploy Linux clients with modified /etc/pam.d/common-* When a user (with root privileges) installs/upgrade a package which calls pam-auth-update --package in a postinst script, the user is asked the question Override local changes to /etc/pam.d/common-*? It looks like some of our user choose Yes because the common-* files on their systems were reverted to ubuntu defaults and our common-* files were moved away to .pam-old We preseeded debconf with this line to hide this question but the user is still asked one time: libpam-runtimelibpam-runtime/override boolean false The solution was to set also the seen-flag in debconf right after installing the computer: echo libpam-runtime libpam-runtime/override seen true | debconf- set-selections Is this behavior intended? ** Affects: pam (Ubuntu) Importance: Undecided Status: New -- pam-auth-update does not obey debconf preseeding https://bugs.launchpad.net/bugs/645318 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 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
off-topic: Did the upstart maintainer say how configuration is done in upstart? When I look to /etc/init, there are also other scripts using /etc/default $ grep -rl /etc/default/ /etc/init /etc/init/apport.conf /etc/init/gssd.conf /etc/init/idmapd.conf /etc/init/rpc_pipefs.conf /etc/init/hwclock.conf /etc/init/mountall.conf /etc/init/portmap.conf /etc/init/statd.conf /etc/init/hwclock-save.conf /etc/init/gdm.conf $ -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
off-topic: Did the upstart maintainer say how configuration is done in upstart? When I look to /etc/init, there are also other scripts using /etc/default $ grep -rl /etc/default/ /etc/init /etc/init/apport.conf /etc/init/gssd.conf /etc/init/idmapd.conf /etc/init/rpc_pipefs.conf /etc/init/hwclock.conf /etc/init/mountall.conf /etc/init/portmap.conf /etc/init/statd.conf /etc/init/hwclock-save.conf /etc/init/gdm.conf $ -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 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 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
Attached patch allows /etc/init/ssh.conf to use also the SSHD_OPTS from /etc/default/ssh. So it doesn't matter how sshd is started (but it should be clarified for the future!) ** Patch added: ssh_conf.diff http://launchpadlibrarian.net/51173516/ssh_conf.diff -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 531912] Re: [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used.
Attached patch allows /etc/init/ssh.conf to use also the SSHD_OPTS from /etc/default/ssh. So it doesn't matter how sshd is started (but it should be clarified for the future!) ** Patch added: ssh_conf.diff http://launchpadlibrarian.net/51173516/ssh_conf.diff -- [LUCID] /etc/init.d/ssh seems to work, but actually upstart is used. https://bugs.launchpad.net/bugs/531912 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 445487] Re: Network-Manager fails WPA2 Enterprise configuration
There is a further easy workaround which works also with nm-connection- editor on karmic. Just concatenate your privatekey together with your cert like cat key.pem cert.pem mynewkey.pem # key.pem needs to be encryted with a password! Then use mynewkey.pem as new private key and the Apply button should appear (thx to https://bugzilla.gnome.org/show_bug.cgi?id=585570#c6) But it looks like the bug is already fixed in upstream - I have no idea if this patch is already included in Lucid or not (?): git log NetworkManager/libnm-util/nm-setting-8021x.c commit 4274edf47dfc1341704311d9587dc6951db480e9 Author: Dan Williams d...@redhat.com Date: Tue Dec 8 16:52:24 2009 -0800 libnm-util: client certificate should not be required to set private key (bgo #585570) Not sure what I was thinking originally; there's no way this was correct in the first place. ** Bug watch added: GNOME Bug Tracker #585570 https://bugzilla.gnome.org/show_bug.cgi?id=585570 -- Network-Manager fails WPA2 Enterprise configuration https://bugs.launchpad.net/bugs/445487 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 445487] Re: Network-Manager fails WPA2 Enterprise configuration
With nm-connection-editor I still have problems. As workaround I avoided using it and used a system-connection file instead. See the attached example file. It works for Karmic and Lucid. HTH, Patrick ** Attachment added: A network-manager system-connection file to avoid nm-connection-editor http://launchpadlibrarian.net/50319228/MY_CONNECTION_NAME.txt -- Network-Manager fails WPA2 Enterprise configuration https://bugs.launchpad.net/bugs/445487 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 445487] Re: Network-Manager fails WPA2 Enterprise configuration
Attached a patch, which lets you use a .pem as private-key-file in nm- connection-editor. The button Apply should then work. I tested it in the nm-connection-editor in Karmic, but couldn't test it with wlan neither with lucid. You have to use your .pem file together with a password, otherwise network-manager refuses to use it. ** Attachment added: crypto.c.diff.txt http://launchpadlibrarian.net/50338402/crypto.c.diff.txt -- Network-Manager fails WPA2 Enterprise configuration https://bugs.launchpad.net/bugs/445487 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 447145] Re: Connect-button greyed out trying to connect to wireless network
*** This bug is a duplicate of bug 445487 *** https://bugs.launchpad.net/bugs/445487 ** This bug has been marked a duplicate of bug 445487 Network-Manager fails WPA2 Enterprise configuration -- Connect-button greyed out trying to connect to wireless network https://bugs.launchpad.net/bugs/447145 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 445487] Re: Network-Manager fails WPA2 Enterprise configuration
** Bug watch added: GNOME Bug Tracker #590644 https://bugzilla.gnome.org/show_bug.cgi?id=590644 ** Also affects: network-manager-applet via https://bugzilla.gnome.org/show_bug.cgi?id=590644 Importance: Unknown Status: Unknown -- Network-Manager fails WPA2 Enterprise configuration https://bugs.launchpad.net/bugs/445487 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 392227] Re: Network Manager: EAP/TLS configuration dialog broken
*** This bug is a duplicate of bug 445487 *** https://bugs.launchpad.net/bugs/445487 ** This bug has been marked a duplicate of bug 445487 Network-Manager fails WPA2 Enterprise configuration -- Network Manager: EAP/TLS configuration dialog broken https://bugs.launchpad.net/bugs/392227 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 445487] Re: Network-Manager fails WPA2 Enterprise configuration
** Changed in: network-manager-applet (Ubuntu) Status: Fix Released = Confirmed -- Network-Manager fails WPA2 Enterprise configuration https://bugs.launchpad.net/bugs/445487 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 445487] Re: Network-Manager fails WPA2 Enterprise configuration
I can confirm note #23: Bug still exists and Workaround #15 works. In my case I had .pem files and had to convert them to .p12 -- Network-Manager fails WPA2 Enterprise configuration https://bugs.launchpad.net/bugs/445487 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
