[Bug 1968790] Re: Webview for SAML does not allow Duo to use a Yubikey
I don't think this is an openconnect issue? Or are you handling network manager issues there too? I see the Ubuntu patch was merged upstream since this was opened? "External browser" would be nice, but IT says we can't turn it on, needs some upgrade, and CISCO says not to use it: The saml external-browser command is for migration purposes for those upgrading to AnyConnect 4.6 or later. Because of security limitations, use this solution only as part of a temporary migration while upgrading AnyConnect software. The command itself will be depreciated in the future. Since the latest Anyconnect client on Windows got the integrated browser upgraded to Edge and now supports all security key flows I'm not optimistic our deployment will ever enable it. So what we really want to see is something like network-manager- openconnect that can support webauthn, with CTAP2 support, but that seems alarmingly hard :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968790 Title: Webview for SAML does not allow Duo to use a Yubikey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1968790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968790] Re: Webview for SAML does not allow Duo to use a Yubikey
Upon more research it seems there is alot more wrong here than the misleading message from Duo. GTK Webkit completely lacks support for webauthn, so it is pointless to think about anything at the network-manager-openconnect level. This means this will not support security tokens for VPN login. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968790 Title: Webview for SAML does not allow Duo to use a Yubikey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1968790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1968467] Re: CSD scripts do not work on jammy
That does, work, note that the leading and trailing _ are garbage, file should be: root@c5c1367d7a8e:/# cat /tmp/openssl.conf openssl_conf = openssl_init [openssl_init] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] Options = UnsafeLegacyRenegotiation root@c5c1367d7a8e:/# OPENSSL_CONF=/tmp/openssl.conf curl -k -v https://xxx/CACHE/sdesktop/hostscan/linux_x64/manifest [..] < HTTP/1.1 200 OK < Content-Type: < Content-Length: 813 < Cache-Control: max-age=6000 Thanks, Jason On Fri, Apr 22, 2022 at 12:10 AM Dan Lenski <1968...@bugs.launchpad.net> wrote: > @jgunthorpe, what if you do something like this, where you create an > OPENSSL_CONF that explicitly (re)enables unsafe legacy negotiation? > Instead of using /dev/null. > > ``` > $ cat > /tmp/openssl.conf < _openssl_conf = openssl_init > [openssl_init] > ssl_conf = ssl_sect > [ssl_sect] > system_default = system_default_sect > [system_default_sect] > Options = UnsafeLegacyRenegotiation_ > EOF > > $ OPENSSL_CONF=/tmp/openssl.conf curl > ``` > > That comes from https://github.com/dlenski/gp-saml-gui/issues/42 > > ** Bug watch added: github.com/dlenski/gp-saml-gui/issues #42 >https://github.com/dlenski/gp-saml-gui/issues/42 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1968467 > > Title: > CSD scripts do not work on jammy > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968467 Title: CSD scripts do not work on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968790] [NEW] Webview for SAML does not allow Duo to use a Yubikey
Public bug reported: Thanks a lot for working on the new SAML support for openconnect, I just succeeded to make it work with our cisco anyconnect setup - it is going to make a lot of people happy here. Is there any thing I can do to help get the upstream parts merged - eg confirm it works etc? For this bug - one thing I hope is simple to resolve is that the webview that is spawned causes Duo MFA to complain it cannot use a Yubikey U2F token because popups are blocked - can popups be unblocked? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openconnect-gnome 1.2.6-4 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 20:44:56 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-openconnect UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-openconnect (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968790 Title: Webview for SAML does not allow Duo to use a Yubikey To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1968790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1968467] Re: CSD scripts do not work on jammy
On Mon, Apr 11, 2022 at 6:00 PM Dan Lenski <1968...@bugs.launchpad.net> wrote: > > My feeling is that curl should set the SSL option when -k is used. > openconnect itself sets this option already, it was fixed in commit > c8dcf10 > > If you replace the cURL invocation in the CSD/Trojan script with… > > ``` > OPENSSL_CONF=/dev/null curl > ``` > > … does this make it work? (For some hints about how/why it should work, > No, it didn't change, I tested with: # OPENSSL_CONF=/dev/null curl -k -v https://x.x.x.x/ * ALPN, offering h2 * ALPN, offering http/1.1 * TLSv1.0 (OUT), TLS header, Certificate Status (22): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (OUT), TLS header, Unknown (21): * TLSv1.2 (OUT), TLS alert, handshake failure (552): * error:0A000152:SSL routines::unsafe legacy renegotiation disabled * Closing connection 0 curl: (35) error:0A000152:SSL routines::unsafe legacy renegotiation disabled Inside ubuntu:22.04 as a docker container just to test curl. Thanks, Jason -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968467 Title: CSD scripts do not work on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968467] [NEW] CSD scripts do not work on jammy
Public bug reported: The CSD scripts all use curl to communicate to the ASA server and in Jammy curl has been linked with openssl 3. openssl 3 switched off SSL_OP_LEGACY_SERVER_CONNECT by default, and CISCO never implemented RFC5746 in ASA so the curl commands in the CSD script just fail to connect (and the scripts blindly ignore these errors making it hard to debug) When run manually curl reports back: * ALPN, offering h2 * ALPN, offering http/1.1 * TLSv1.0 (OUT), TLS header, Certificate Status (22): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS header, Certificate Status (22): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (OUT), TLS header, Unknown (21): * TLSv1.2 (OUT), TLS alert, handshake failure (552): * error:0A000152:SSL routines::unsafe legacy renegotiation disabled * Closing connection 0 curl: (35) error:0A000152:SSL routines::unsafe legacy renegotiation disabled My feeling is that curl should set the SSL option when -k is used. openconnect itself sets this option already, it was fixed in commit c8dcf10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openconnect 8.20-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 10 12:19:57 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openconnect UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openconnect (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968467 Title: CSD scripts do not work on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861028] Re: Fan control stops working on resume for Dell Precision
This still happens on a fresh Focal install using linux- image-5.4.0-26-generic version 5.4.0-26.30 ** Also affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags removed: bionic ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861028 Title: Fan control stops working on resume for Dell Precision To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861028] [NEW] Fan control stops working on resume for Dell Precision
Public bug reported: This system is a Dell Precision Tower 3420 with the latest BIOS 2.13.1, kernel version is 5.3.0-26-generic (HWE, bionic) Freshly booting the system and doing something CPU intensive, like compiling a kernel, cause the CPU fan to ramp up as expected and the CPU temperatures remain acceptable. After suspending (ie Alt-clicking the power button in Unity) and then resuming, the CPU fan runs at a permanent low frequency and does not ramp up. Doing something like a kernel build causes the CPU to overheat and logs messages to dmesg. Investigating I see that the dell_smm_hwmon driver has a 'temp2' input that reflects the CPU temperature. Upon power up the value works properly, after resume it returns -ENODATA. The other sensor for CPU temperature (thermal_zone3/temp, x86_pkg_temp) still works correctly. Blacklisting the dell_smm_hwmon driver has no impact Dell Precisions are listed as compatible with Ubuntu, and this system was purchased with Ubuntu pre-installed from Dell, so it is surpsing something so basic isn't working? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:48:39 2020 InstallationDate: Installed on 2018-08-04 (540 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861028 Title: Fan control stops working on resume for Dell Precision To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1861028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1603810] Re: Ubuntu turns monitor permanently off during boot
Were you still wanting to test this new kernel? On Mon, Jul 25, 2016 at 2:33 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > This does appear to be an Ubuntu specific kernel. I'll build an Ubuntu > kernel based on 4.0 and post a link to it for testing. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1603810 > > Title: > Ubuntu turns monitor permanently off during boot > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1603810/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603810 Title: Ubuntu turns monitor permanently off during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1603810] Re: Ubuntu turns monitor permanently off during boot
Wasn't testing with 3.16 and 3.19 ubuntu patched kernels enough to disprove the grub theory? Jason On Mon, Jul 25, 2016 at 1:44 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Can you see if the bug still happens when booting a Trusty kernel on the > Xenial system? This can be down by downloading the kernel from: > > https://launchpad.net/~canonical-kernel- > team/+archive/ubuntu/ppa/+build/10184623 > > You will need to install both the linux-image and linux-image-extra .deb > packages. > > If the bug still happens, it may indicate a bug in GRUB. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1603810 > > Title: > Ubuntu turns monitor permanently off during boot > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603810/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603810 Title: Ubuntu turns monitor permanently off during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1603810] Re: Ubuntu turns monitor permanently off during boot
As a clarification, the mainline boot behaviour is identical to the Ubuntu kernel with $vt_handoff removed. I double checked that the option is present in grub for all the tests. I guess this isn't surprising since that option isn't part of mainline. Jason On Wed, Jul 20, 2016 at 8:30 PM, Jason Gunthorpe <jguntho...@gmail.com> wrote: > 4.1.0-040100-generic works > 4.4.14-040414-generic works > > Didn't test others. > > The boot sequence is different with the main line kernels. There is a > black screen period with a couple of messages (1-2s), then the console font > load, then it briefly switches to the splash, black screen flash back to > the prior screen then the login prompt. There is no DPMS flash (the monitor > displays a dialog for 1s when it is DPMS powered off) > > Whereas when, say, 4.2-ubuntu rarely randomly works, or with 3.19-ubuntu, > it just stays at a black screen, briefly flashes a DPMS power off > notification, and then goes to the login screen without showing the couple > of messages. > > Sounds like an Ubuntu kernel bug? > > Obnoxiously all the console messages are not captured in the journal, that > seems like another bug.. > > > > On Tue, Jul 19, 2016 at 1:21 PM, Joseph Salisbury < > joseph.salisb...@canonical.com> wrote: > >> Would it be possible to test the upstream stable 4.0 and 4.1 kernels? >> They can be downloaded from: >> >> 4.0: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/ >> 4.1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-wily/ >> >> We can perform a kernel bisect once we identify the last good and first >> bad kernel versions. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1603810 >> >> Title: >> Ubuntu turns monitor permanently off during boot >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603810/+subscriptions >> > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603810 Title: Ubuntu turns monitor permanently off during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1603810] Re: Ubuntu turns monitor permanently off during boot
4.1.0-040100-generic works 4.4.14-040414-generic works Didn't test others. The boot sequence is different with the main line kernels. There is a black screen period with a couple of messages (1-2s), then the console font load, then it briefly switches to the splash, black screen flash back to the prior screen then the login prompt. There is no DPMS flash (the monitor displays a dialog for 1s when it is DPMS powered off) Whereas when, say, 4.2-ubuntu rarely randomly works, or with 3.19-ubuntu, it just stays at a black screen, briefly flashes a DPMS power off notification, and then goes to the login screen without showing the couple of messages. Sounds like an Ubuntu kernel bug? Obnoxiously all the console messages are not captured in the journal, that seems like another bug.. On Tue, Jul 19, 2016 at 1:21 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Would it be possible to test the upstream stable 4.0 and 4.1 kernels? > They can be downloaded from: > > 4.0: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/ > 4.1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-wily/ > > We can perform a kernel bisect once we identify the last good and first > bad kernel versions. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1603810 > > Title: > Ubuntu turns monitor permanently off during boot > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603810/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603810 Title: Ubuntu turns monitor permanently off during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1603810] Re: Ubuntu turns monitor permanently off during boot
On Mon, Jul 18, 2016 at 2:48 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Does booting back into the Trusty kernel on the Xenial installed system > make the bug go away? > Yes. I've done multiple reboot experiments now and have learned the bug only happens about 80% of the time, so I did all of these will multiple reboots each: 3.16.0-77 GOOD 3.19.0-65 GOOD 4.2.0-42 BAD 4.4.0-31 BAD All generic versions, 4.4 was using the .efi.signed variant. I've attached the dmesg for 3.19-65 BTW, none of the kernels manage a seamless graphical boot like Windows does. All successes sit at black screens for a long time then transition to the splash for maybe 0.5s then into the graphical login (after another black screen flash). Come to think of it, I don't think I've ever seen Ubuntu do this properly on any release on any hardware I've tried (at least with EFI boot). Even my HP's at work sit at a black screen for more time than the splash. So I don't understand why Canonical bothers with the vt_handoff stuff, when it seems *worse* on than off. At least without vt_handoff you get something that looks like a running computer instead of black screen.. That said, I think it works better with BIOS boot ?? Windows 7 & 10 both do this perfectly in EFI mode, the monitor is never black. Jason -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603810 Title: Ubuntu turns monitor permanently off during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603810] [NEW] Ubuntu turns monitor permanently off during boot
Public bug reported: This is a regression, at least trusty (and prior) worked fine on this hardware. Booting the Xenial installer image off USB also worked fine. The system boots fine, however the monitor is in DPMS power-off and does not ever turn back on. Switching VTs doesn't help, I have found no way to get it switch on. Removing '$vt_handoff' from grub resolves the problem and the system seems to work fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jgg2224 F pulseaudio /dev/snd/controlC0: jgg2224 F pulseaudio CurrentDesktop: Unity Date: Sun Jul 17 14:04:30 2016 HibernationDevice: RESUME=UUID=b254872c-e84b-427c-bebe-343c031cbdcd InstallationDate: Installed on 2016-04-22 (86 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=/dev/mapper/main2-xenial64 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd11/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603810 Title: Ubuntu turns monitor permanently off during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586570] [NEW] openvpn chroot does not have a valid resolv.conf
Public bug reported:
If you leave openvpn running for long enough it will eventually begin to
fail with output like:
May 27 19:16:54 wakko nm-openvpn[16480]: RESOLVE: Cannot resolve host
address: : Temporary failure in name resolution
Analysis shows this is because openvpn is sending DNS queries to
127.0.0.1:
socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 8
connect(8, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
poll([{fd=8, events=POLLOUT}], 1, 0)= 1 ([{fd=8, revents=POLLOUT}])
sendto(8, ..., 30, MSG_NOSIGNAL, NULL, 0) = 30
However, this is not correct, dnsmasq listens on 127.0.1.1.
It appears the a cause of this is the chroot, the chroot has no
resolv.conf in it and the glibc default is to use 127.0.0.1
openvpn does a DNS query before chroot'ing which used to be enough to
cache resolv.conf forever. I wonder if something has changed in glibc
recently to cause the resolv.conf to be reloaded (eg Debian apparently
has a patch that does this)
A work around would be to copy the system resolv.conf into
/var/lib/openvpn/chroot before starting openvpn
Seen on Xenial and a few prior versions.
** Affects: network-manager-openvpn (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586570
Title:
openvpn chroot does not have a valid resolv.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1586570/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304437] Re: After connecting to OpenVPN server the default DNS is no longer available
This still happens in Xenial. #7 has it right, if the IPv4 and IPv6 'use this connection only for resources on its network' are different then the default DNS server is dropped. It is very easy to make this mistake and very hard to figure out that is the problem! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304437 Title: After connecting to OpenVPN server the default DNS is no longer available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573778] [NEW] clang does not find libbacktrace any more (regression)
Public bug reported:
This small example does not compile in Xenial:
#include
#if !(BACKTRACE_SUPPORTED)
#error "Not supported"
#endif
#include
int main(int argc,const char *argv[])
{
struct backtrace_state *state =
backtrace_create_state(nullptr,false,nullptr,nullptr);
}
$ clang++-3.8 --std=c++14 t.cc -lbacktrace -v
#include <...> search starts here:
/usr/bin/../lib/gcc/x86_64-linux-gnu/5.3.1/../../../../include/c++/5.3.1
/usr/bin/../lib/gcc/x86_64-linux-gnu/5.3.1/../../../../include/x86_64-linux-gnu/c++/5.3.1
/usr/bin/../lib/gcc/x86_64-linux-gnu/5.3.1/../../../../include/c++/5.3.1/backward
/usr/local/include
/usr/lib/llvm-3.8/bin/../lib/clang/3.8.0/include
/usr/include/x86_64-linux-gnu
/usr/include
End of search list.
t.cc:1:10: fatal error: 'backtrace-supported.h' file not found
While using g++-5 works just fine.
The same example compiles fine on Vivid:
$ clang++-3.6 --std=c++14 t.cc -lbacktrace -v
#include <...> search starts here:
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/x86_64-linux-gnu/c++/4.9
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../../include/c++/4.9/backward
/usr/local/include
/usr/lib/llvm-3.6/bin/../lib/clang/3.6.0/include
/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/include
/usr/include/x86_64-linux-gnu
/usr/include
For some reason the clang install in Xenial does not search the libgcc
directory /usr/bin/../lib/gcc/x86_64-linux-gnu/5/include
** Affects: llvm-toolchain-3.8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573778
Title:
clang does not find libbacktrace any more (regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.8/+bug/1573778/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433557] Re: udev rules wrongly match on monitor hub, wrong invocation of systemd unit, changes config files in udev rules
I hit this problem as well, booting on my system hangs for three minutes waiting for udev to settle. I have a HP keyboard. Booting without the keyboard plugged in, or removing the hplip package solves the problem. hplip version 3.15.2-0ubuntu4.1 $ lsusb Bus 001 Device 002: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard $ sudo systemd-analyze blame 3min 40ms systemd-udev-settle.service $ journalctl | grep -i udev Jun 25 14:19:32 test-MSH87TN-00 systemd-udevd[265]: worker [283] /devices/pci:00/:00:14.0/usb1/1-1 is taking a long time Jun 25 14:19:32 test-MSH87TN-00 systemd-udevd[265]: worker [285] /devices/pci:00/:00:14.0/usb1/1-3 is taking a long time Jun 25 14:21:32 test-MSH87TN-00 systemd[1]: systemd-udev-settle.service start operation timed out. Terminating. Jun 25 14:21:32 test-MSH87TN-00 systemd[1]: Failed to start udev Wait for Complete Device Initialization. Jun 25 14:21:32 test-MSH87TN-00 systemd[1]: Unit systemd-udev-settle.service entered failed state. Jun 25 14:21:32 test-MSH87TN-00 systemd[1]: systemd-udev-settle.service failed. Jun 25 14:21:33 test-MSH87TN-00 systemd-udevd[283]: timeout '/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@001:002.service; else /usr/bin/nohup /usr/bin/hp-config_usb_printer 001:002 ; fi '' Jun 25 14:21:33 test-MSH87TN-00 systemd-udevd[283]: timeout '/bin/sh -c 'grep -q ^#hpaio /etc/sane.d/dll.conf;if [ $? -eq 0 ];then sed -i -e s/^#hpaio/hpaio/ /etc/sane.d/dll.conf;else grep -q ^hpaio /etc/sane.d/dll.conf;if [ $? -ne 0 ];then echo hpaio /etc/sane.d/dll.conf;fi;fi'' Jun 25 14:21:33 test-MSH87TN-00 systemd-udevd[283]: slow: '/bin/sh -c 'grep -q ^#hpaio /etc/sane.d/dll.conf;if [ $? -eq 0 ];then sed -i -e s/^#hpaio/hpaio/ /etc/sane.d/dll.conf;else grep -q ^hpaio /etc/sane.d/dll.conf;if [ $? -ne 0 ];then echo hpaio /etc/sane.d/dll.conf;fi;fi'' [1011] Jun 25 14:21:33 test-MSH87TN-00 systemd-udevd[285]: timeout '/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@001:003.service; else /usr/bin/nohup /usr/bin/hp-config_usb_printer 001:003 ; fi '' Jun 25 14:21:33 test-MSH87TN-00 systemd-udevd[285]: timeout '/bin/sh -c 'grep -q ^#hpaio /etc/sane.d/dll.conf;if [ $? -eq 0 ];then sed -i -e s/^#hpaio/hpaio/ /etc/sane.d/dll.conf;else grep -q ^hpaio /etc/sane.d/dll.conf;if [ $? -ne 0 ];then echo hpaio /etc/sane.d/dll.conf;fi;fi'' Jun 25 14:21:33 test-MSH87TN-00 systemd-udevd[285]: slow: '/bin/sh -c 'grep -q ^#hpaio /etc/sane.d/dll.conf;if [ $? -eq 0 ];then sed -i -e s/^#hpaio/hpaio/ /etc/sane.d/dll.conf;else grep -q ^hpaio /etc/sane.d/dll.conf;if [ $? -ne 0 ];then echo hpaio /etc/sane.d/dll.conf;fi;fi'' [1012] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433557 Title: udev rules wrongly match on monitor hub, wrong invocation of systemd unit, changes config files in udev rules To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1433557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458687] [NEW] rdesktop will not connect to Server 2008 when Kerberos is enabled
Public bug reported: This is a regression from Trusty, which worked OK $ rdesktop ads1.ads.orcorp.ca Connection established using CredSSP. $ echo $? 76 No GUI appears. It does go through kerberos steps: $ klist 05/25/15 15:39:52 05/26/15 01:39:48 TERMSRV/ads1.ads.orcorp.ca@ renew until 05/26/15 15:39:47 05/25/15 15:39:52 05/26/15 01:39:48 TERMSRV/ads1.ads.orcorp...@ads.orcorp.ca renew until 05/26/15 15:39:47 And it works as expected if KRB5CCNAME is blanked out (disabling kerberos): $ KRB5CCNAME= rdesktop ads1.ads.orcorp.ca ERROR: CredSSP: Initialize failed, do you have correct kerberos tgt initialized ? Connection established using SSL. This basically makes it unusable. The client is configured to use the Window AD server as a kerberos server, and the login user has a valid kerberos ticket from the sever. ** Affects: rdesktop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458687 Title: rdesktop will not connect to Server 2008 when Kerberos is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdesktop/+bug/1458687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1361842] Re: dmraid does not start on boot for single disk RAID0
Ignoring the raid label is the entire problem - that is what the broken dmraid script is already doing. Fundamentally, if /dev/sda has a valid RAID label then it *MUST* be setup and accessed through the dmraid device and *NEVER* via /dev/sda. Otherwise the installer will see a disc that is too big and it will destroy the RAID label at the end of the disc, then the system will not boot. The work around solution is to manually start dmraid before partitioning in the installer, then the system will remain bootable, the OS partition will not overlap the RAID label, etc. But once booted it still accesses through /dev/sda and there is a risk that a partitioning tool will again blindly destroy the RAID label. I can't see how it would ever be correct for boot scripts to ignore a RAID label, if there is a label, the drive is part of a RAID set and it must be activated through dmraid. A single disc RAID still has a label, and still needs to be accessed through device mapper. FWIW, RHEL gets this right and sets up dmraid on this disc. Jason On Tue, Oct 28, 2014 at 6:32 PM, Phillip Susi ps...@ubuntu.com wrote: That is one broken firmware if it does not present plain, non raid disks. You should be able to work around it by booting the installer with the nodmraid option. This will have Ubuntu ignore the raid signatures and just use the drive normally. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1361842 Title: dmraid does not start on boot for single disk RAID0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1361842/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361842 Title: dmraid does not start on boot for single disk RAID0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1361842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1361842] Re: dmraid does not start on boot for single disk RAID0
On Tue, Oct 28, 2014 at 9:06 PM, Phillip Susi ps...@ubuntu.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 10/28/2014 09:55 PM, Jason Gunthorpe wrote: Fundamentally, if /dev/sda has a valid RAID label then it *MUST* be setup and accessed through the dmraid device and *NEVER* via /dev/sda. Otherwise the installer will see a disc that is too big and it will destroy the RAID label at the end of the disc, then the system will not boot. For MBR partitioned disks this isn't really a problem because they never really use the last bit of the disk anyhow, but for GPT, yes... that would be a problem. Except never really use means don't fill up the filesystem. If the FS uses the last portion of the partition it will corrupt the RAID label and restoring the RAID label will corrupt the FS. Which is pretty bad, but not immediate. FWIW, RHEL gets this right and sets up dmraid on this disc. Interesting.. they must have a patch that hasn't been upstreamed. Looks like they have a dracut specific version, it seems much saner, no crazy parsing of dmraid output. info Scanning for dmraid devices $DM_RAIDS SETS=$(dmraid -c -s) if [ $SETS = no raid disks -o $SETS = no raid sets ]; then return fi [..] # scan and activate all DM RAIDS for s in $SETS; do info Activating $s dmraid -ay -i -p --rm_partitions $s 21 | vinfo [ -e /dev/mapper/$s ] kpartx -a -p p /dev/mapper/$s 21 | vinfo done Jason -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361842 Title: dmraid does not start on boot for single disk RAID0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1361842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1361842] Re: dmraid does not start on boot for single disk RAID0
The LSI option rom will not present a drive to the EFI BIOS without a raid label on the disc. If the array is deleted then EFI will not boot off the drive at all. As far as I can tell there is no fall back option rom that provides simple AHCI services to EFI. This is the problem, because the boot script is wrong the installer and so forth has a very high probability to destroy the RAID label when it writes a GPT partition label, which renders the system unbootable, and unless you actually know about this quirk the only symptom is that the boot menu from the BIOS has no option to boot from the hard drive. On Mon, Oct 27, 2014 at 9:18 AM, Phillip Susi ps...@ubuntu.com wrote: You can just delete the raid array in the bios utility, or use dmraid -E to erase it. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1361842 Title: dmraid does not start on boot for single disk RAID0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1361842/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361842 Title: dmraid does not start on boot for single disk RAID0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1361842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1361842] Re: dmraid does not start on boot for single disk RAID0
You'd think, but if this BIOS has an option to disable the LSI option ROM and still boot in EFI mode, then it is very well hidden.. On Tue, Oct 14, 2014 at 12:27 PM, Phillip Susi ps...@ubuntu.com wrote: The test in that script is wrong, but since you only have a single disk, you should be able to throw out the fake raid junk and just put the controller in AHCI mode. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1361842 Title: dmraid does not start on boot for single disk RAID0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1361842/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361842 Title: dmraid does not start on boot for single disk RAID0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1361842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361842] [NEW] dmraid does not start on boot for single disk RAID0
Public bug reported: I have a Lenovo server with a LSI controller that insists on having a RAID set to boot. So the BIOS is configured with a RAID0 stripe set, with a single disk: $ dmraid -i -si *** Group superset .ddf1_disks -- Subset name : ddf1_4c5349202020202080861d60471147111450 size : 974608384 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0 Notice that 'devs' is 1. This causes this bit of code in dm-activate to bail: case $Raid_Type in stripe) if [ $Raid_Nodevs -lt 2 ]; then if [ -n $Degraded ]; then log_error Cannot bring up a RAID0 array in degraded mode, not all devices present. fi return 2 fi ;; Of course, the above is totally bogus, a 1 disk RAID0 is perfectly valid. I wonder if this should be testing 'status' instead? This is a problem because of GPT partitioning. If you don't start the RAID downstream tools will attempt to partition sda. The RAID metadata at the end of the disk collides with the GPT partition backup and it ends up destroying the RAID set and making the server unbootable. The kernel hints at this condition: [4.202136] GPT:Primary header thinks Alt. header is not at the end of the disk. [4.202137] GPT:974608383 != 976773167 [4.202138] GPT:Alternate GPT header not at the end of the disk. [4.202138] GPT:974608383 != 976773167 Which is 100% true, the GPT was written to the RAID, not the raw disk, and 974608383 sectors is at the end of the raid volume. ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361842 Title: dmraid does not start on boot for single disk RAID0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/1361842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315565] Re: nss-winbind is returing -1 for supplemental groups
Turns out this is not just a cosmetic problem, having -1 in a supplementary group list completely breaks the NFS sever as well, in a very hard to find way. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1315565 Title: nss-winbind is returing -1 for supplemental groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1315565/+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 1315565] Re: nss-winbind is returing -1 for supplemental groups
Turns out this is not just a cosmetic problem, having -1 in a supplementary group list completely breaks the NFS sever as well, in a very hard to find way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315565 Title: nss-winbind is returing -1 for supplemental groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1315565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321869] [NEW] xmllint 2.9.1+dfsg1-3ubuntu4.1 does not load entities any more
Public bug reported: This is a regression, 2.9.1+dfsg1-3ubuntu4 and all prior for the last 5 years work fine. xmllint 2.9.1+dfsg1-3ubuntu4.1 doesn't load entities, for instance attempting to validate a docbook document: $ xmllint --load-trace --path build-hosted/doc/ --path doc/ --xinclude --nonet --postvalid --noout doc/oss-build.xml Loaded URL=doc/oss-build.xml ID=(null) Loaded URL=http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; ID=-//OASIS//DTD DocBook XML V4.5//EN doc/oss-build.xml:6: element article: validity error : No declaration for element article While prior versions work fine: Loaded URL=doc/oss-build.xml ID=(null) Loaded URL=http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; ID=-//OASIS//DTD DocBook XML V4.5//EN Loaded URL=file:///usr/share/xml/docbook/schema/dtd/4.5/dbnotnx.mod ID=-//OASIS//ENTITIES DocBook Notations V4.5//EN Loaded URL=file:///usr/share/xml/docbook/schema/dtd/4.5/dbcentx.mod ID=-//OASIS//ENTITIES DocBook Character Entities V4.5//EN Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOamsa.ent ID=ISO 8879:1986//ENTITIES Added Math Symbols: Arrow Relations//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOamsb.ent ID=ISO 8879:1986//ENTITIES Added Math Symbols: Binary Operators//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOamsc.ent ID=ISO 8879:1986//ENTITIES Added Math Symbols: Delimiters//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOamsn.ent ID=ISO 8879:1986//ENTITIES Added Math Symbols: Negated Relations//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOamso.ent ID=ISO 8879:1986//ENTITIES Added Math Symbols: Ordinary//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOamsr.ent ID=ISO 8879:1986//ENTITIES Added Math Symbols: Relations//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISObox.ent ID=ISO 8879:1986//ENTITIES Box and Line Drawing//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOcyr1.ent ID=ISO 8879:1986//ENTITIES Russian Cyrillic//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOcyr2.ent ID=ISO 8879:1986//ENTITIES Non-Russian Cyrillic//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOdia.ent ID=ISO 8879:1986//ENTITIES Diacritical Marks//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOgrk1.ent ID=ISO 8879:1986//ENTITIES Greek Letters//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOgrk2.ent ID=ISO 8879:1986//ENTITIES Monotoniko Greek//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOgrk3.ent ID=ISO 8879:1986//ENTITIES Greek Symbols//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOgrk4.ent ID=ISO 8879:1986//ENTITIES Alternative Greek Symbols//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOlat1.ent ID=ISO 8879:1986//ENTITIES Added Latin 1//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOlat2.ent ID=ISO 8879:1986//ENTITIES Added Latin 2//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOnum.ent ID=ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOpub.ent ID=ISO 8879:1986//ENTITIES Publishing//EN//XML Loaded URL=file:///usr/share/xml/entities/xml-iso-entities-8879.1986/ISOtech.ent ID=ISO 8879:1986//ENTITIES General Technical//EN//XML Loaded URL=file:///usr/share/xml/docbook/schema/dtd/4.5/dbpoolx.mod ID=-//OASIS//ELEMENTS DocBook Information Pool V4.5//EN Loaded URL=file:///usr/share/xml/docbook/schema/dtd/4.5/htmltblx.mod ID=-//OASIS//ELEMENTS DocBook XML HTML Tables V4.5//EN Loaded URL=file:///usr/share/xml/docbook/schema/dtd/4.5/calstblx.dtd ID=-//OASIS//DTD DocBook CALS Table Model V4.5//EN Loaded URL=file:///usr/share/xml/docbook/schema/dtd/4.5/dbhierx.mod ID=-//OASIS//ELEMENTS DocBook Document Hierarchy V4.5//EN Loaded URL=file:///usr/share/xml/docbook/schema/dtd/4.5/dbgenent.mod ID=-//OASIS//ENTITIES DocBook Additional General Entities V4.5//EN ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libxml2-utils 2.9.1+dfsg1-3ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 21 12:21:04 2014 InstallationDate: Installed on 2014-04-16 (35 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415) SourcePackage: libxml2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because
[Bug 1315562] [NEW] libnss-winbind should allow installation of the 32 bit libarary in trusty
Public bug reported: This is a regression. Prior versions of Ubuntu allowed the 32 bit and 64 bit libnss-winbind library to co-exist on the same system. $ apt-get install libnss-winbind:i386 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libnss-winbind:i386 : Depends: winbind:i386 (= 2:4.1.6+dfsg-1ubuntu2) but it is not going to be installed Depends: samba-libs:i386 (= 2:4.1.6+dfsg-1ubuntu2) but it is not going to be installed E: Unable to correct problems, you have held broken packages. This is important as 32 bit binaries running on a 64 bit system can still access NSS services and must still be able to load the nss-winbind plugin. The same comment applies to PAM as well, but I have no 32 bit apps using PAM so it isn't as interesting ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1315562 Title: libnss-winbind should allow installation of the 32 bit libarary in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1315562/+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 1315560] [NEW] winbind segfaults during pam login
Public bug reported: Attempting to login via PAM causes winbind to segfault and log this to syslog: May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540190, 0] ../lib/util/fault.c:72(fault_report) May 2 16:25:54 jggl winbindd[2416]: === May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540238, 0] ../lib/util/fault.c:73(fault_report) May 2 16:25:54 jggl winbindd[2416]: INTERNAL ERROR: Signal 11 in pid 2416 (4.1.6-Ubuntu) May 2 16:25:54 jggl winbindd[2416]: Please read the Trouble-Shooting section of the Samba HOWTO May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540263, 0] ../lib/util/fault.c:75(fault_report) May 2 16:25:54 jggl winbindd[2416]: === May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540295, 0] ../source3/lib/util.c:785(smb_panic_s3) May 2 16:25:54 jggl winbindd[2416]: PANIC (pid 2416): internal error May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.585897, 0] ../source3/lib/util.c:896(log_stack_trace) May 2 16:25:54 jggl winbindd[2416]: BACKTRACE: 27 stack frames: May 2 16:25:54 jggl winbindd[2416]:#0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) [0x7f6d3e2fff3a] May 2 16:25:54 jggl winbindd[2416]:#1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f6d3e300010] May 2 16:25:54 jggl winbindd[2416]:#2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f6d425d9c6f] May 2 16:25:54 jggl winbindd[2416]:#3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1ae86) [0x7f6d425d9e86] May 2 16:25:54 jggl winbindd[2416]:#4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f6d42a07340] May 2 16:25:54 jggl winbindd[2416]:#5 /usr/lib/x86_64-linux-gnu(krb5_storage_free+0x1) [0x7f6d3ce45441] May 2 16:25:54 jggl winbindd[2416]:#6 /usr/lib/x86_64-linux-gnu(+0x42465) [0x7f6d3ce2b465] May 2 16:25:54 jggl winbindd[2416]:#7 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0x86b1) [0x7f6d3ee756b1] May 2 16:25:54 jggl winbindd[2416]:#8 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(gse_krb5_get_server_keytab+0xfb) [0x7f6d3ee75beb] May 2 16:25:54 jggl winbindd[2416]:#9 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0xa7aa) [0x7f6d3ee777aa] May 2 16:25:54 jggl winbindd[2416]:#10 /usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech+0x71) [0x7f6d3f3012b1] May 2 16:25:54 jggl winbindd[2416]:#11 /usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech_by_oid+0x26) [0x7f6d3f301586] May 2 16:25:54 jggl winbindd[2416]:#12 /usr/sbin/winbindd(kerberos_return_pac+0x435) [0x7f6d42e66da5] May 2 16:25:54 jggl winbindd[2416]:#13 /usr/sbin/winbindd(winbindd_dual_pam_auth+0xec4) [0x7f6d42e78884] May 2 16:25:54 jggl winbindd[2416]:#14 /usr/sbin/winbindd(+0x5337c) [0x7f6d42e8d37c] May 2 16:25:54 jggl winbindd[2416]:#15 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x867b) [0x7f6d3c37167b] May 2 16:25:54 jggl winbindd[2416]:#16 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x6b27) [0x7f6d3c36fb27] May 2 16:25:54 jggl winbindd[2416]:#17 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7f6d3c36c5ed] May 2 16:25:54 jggl winbindd[2416]:#18 /usr/sbin/winbindd(+0x55702) [0x7f6d42e8f702] May 2 16:25:54 jggl winbindd[2416]:#19 /usr/sbin/winbindd(+0x55db5) [0x7f6d42e8fdb5] May 2 16:25:54 jggl winbindd[2416]:#20 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_immediate+0xd4) [0x7f6d3c36ce14] May 2 16:25:54 jggl winbindd[2416]:#21 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x8437) [0x7f6d3c371437] May 2 16:25:54 jggl winbindd[2416]:#22 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x6b27) [0x7f6d3c36fb27] May 2 16:25:54 jggl winbindd[2416]:#23 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7f6d3c36c5ed] May 2 16:25:54 jggl winbindd[2416]:#24 /usr/sbin/winbindd(main+0xad2) [0x7f6d42e5ee42] May 2 16:25:54 jggl winbindd[2416]:#25 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f6d3bfc4ec5] May 2 16:25:54 jggl winbindd[2416]:#26 /usr/sbin/winbindd(+0x25532) [0x7f6d42e5f532] May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.586279, 0] ../source3/lib/dumpcore.c:312(dump_core) May 2 16:25:54 jggl winbindd[2416]: unable to change to /var/log/samba/cores/winbindd May 2 16:25:54 jggl winbindd[2416]: refusing to dump core Attempting to validate passwords via wbinfo works fine, nss works fine, etc. The segfault prevents the login from succeeding, so pam winbind is basically unusable. This is a regression, this config has worked here on various Ubuntu's for at least 5 years. $ cat /etc/security/pam_winbind.conf [global] ;debug=yes ;debug_state=yes require_membership_of=ORCORP\orc krb5_auth=yes $ cat /etc/samba/smb.conf [global] workgroup = ORCORP realm = ADS.ORCORP.CA os level = 0 log
[Bug 1315565] [NEW] nss-winbind is returing -1 for supplemental groups
Public bug reported: This is a regression in trusty. Consider: $wbinfo -r jgg 1000 -1 10009 10011 10004 10003 -1 1002 -1 Results in: $ getent initgroups jgg jgg 4 24 27 30 46 108 124 1000 10009 10011 10004 10003 1002 $ id jgg uid=2009(jgg) gid=1000(orc) groups=1000(orc),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),108(lpadmin),124(sambashare),4294967295,10009(vpn_users),10011(xweb_users),10004(accounting),10003(domain_users),4294967295,1002(wsudoers),4294967295 Those 4294967295 values should not be in the group list. The underlying issue is that some of the AD groups the user is a part of are not UNIX groups, they are just general AD groups: $ ldapsearch uid=jgg memberOf dn: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=XWEB Users,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=VPN Users,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=accounting,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=wsudoers,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Boards website editors,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Parts website editors,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=adm,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Domain Users,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Print Operators,CN=Builtin,DC=ads,DC=orcorp,DC=ca For instance, 'Print Operators' is not a UNIX group, it doesn't have the RFC2307 schema elements. # Print Operators, Builtin, ads.orcorp.ca dn: CN=Print Operators,CN=Builtin,DC=ads,DC=orcorp,DC=ca objectClass: top objectClass: group cn: Print Operators description: Members can administer domain printers member: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca member: CN=Ian Crowe,CN=Users,DC=ads,DC=orcorp,DC=ca distinguishedName: CN=Print Operators,CN=Builtin,DC=ads,DC=orcorp,DC=ca instanceType: 4 whenCreated: 20080729165935.0Z whenChanged: 20080808163035.0Z uSNCreated: 8209 uSNChanged: 30817 name: Print Operators objectGUID:: SBkgyF4upEG4GO6bRhj17g== objectSid:: AQIAAAUgJgIAAA== adminCount: 1 sAMAccountName: Print Operators sAMAccountType: 536870912 systemFlags: -1946157056 groupType: -2147483643 objectCategory: CN=Group,CN=Schema,CN=Configuration,DC=ads,DC=orcorp,DC=ca isCriticalSystemObject: TRUE # wsudoers, Users, ads.orcorp.ca dn: CN=wsudoers,CN=Users,DC=ads,DC=orcorp,DC=ca objectClass: top objectClass: group cn: wsudoers description: Workstation Sudoers member: CN=Rolf Manderscheid,CN=Users,DC=ads,DC=orcorp,DC=ca member: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca member: CN=Ian Crowe,CN=Users,DC=ads,DC=orcorp,DC=ca distinguishedName: CN=wsudoers,CN=Users,DC=ads,DC=orcorp,DC=ca instanceType: 4 whenCreated: 20080808044201.0Z whenChanged: 2030193544.0Z uSNCreated: 30255 info: Members can use sudo on the workstations uSNChanged: 2007454 name: wsudoers objectGUID:: oYEd5AZTyESv6SHZoxBGeQ== objectSid:: AQUAAAUVmm48yDCxnAEu012CfgQAAA== sAMAccountName: wsudoers sAMAccountType: 536870912 managedBy: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca groupType: -2147483644 objectCategory: CN=Group,CN=Schema,CN=Configuration,DC=ads,DC=orcorp,DC=ca msSFU30Name: wsudoers msSFU30NisDomain: ads gidNumber: 1002 ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1315565 Title: nss-winbind is returing -1 for supplemental groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1315565/+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 1315551] [NEW] vc-git.el vc-git-grep does not work with git 1.9 in trusty
Public bug reported: For emacs to properly parse the result of git grep it must not be fed through a pager (like less) and it must not include colourization escape codes. If a pager is spawned, it might blow up with this: git grep -n -e ClkIB -- * WARNING: terminal is not fully functional - (press RETURN) If colourization is turned on then the output from git no longer matches the grep filename regex. For instance grepping for 'COPYRIGHT' gives colourized lines like this: Makefile.[36m:.[m2.[36m:.[m# .[1;31mCOPYRIGHT.[m (c) 2011-2012 O (where [ is the ESC). Git has colour'd the : characters as well as the matching string. The standard emacs grep regex is not prepared to handle the escape characters. Within vc-git.el/vc-git-grep, setting the environment PAGER= used to be enough: (when command (let ((default-directory dir) (compilation-environment '(PAGER=))) ;; Setting process-setup-function makes exit-message-function work ;; even when async processes aren't supported. (compilation-start command 'grep-mode)) But for whatever reason with git 1.9 this still spawns a pager. Updating to GIT_PAGER= does not spawn a pager, but still colourizes the output. The only fix I can find would be to replace: (grep-expand-template git grep -n -e R -- F regexp files)) with: (grep-expand-template git --no-pager grep --no-color -n -e R -- F regexp files)) This restores the behaviour older git's had with PAGER= and allows emacs to properly parse the result. However, I would expect that it won't be compatible with older gits. Since Ubuntu does not ship older gits it seems reasonable to patch vc- git.el and let upstream figure out how to make this generic. emacs23-el: Installed: 23.4+1-4.1ubuntu1 Candidate: 23.4+1-4.1ubuntu1 Version table: *** 23.4+1-4.1ubuntu1 0 ** Affects: emacs23 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315551 Title: vc-git.el vc-git-grep does not work with git 1.9 in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1315551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315562] [NEW] libnss-winbind should allow installation of the 32 bit libarary in trusty
Public bug reported: This is a regression. Prior versions of Ubuntu allowed the 32 bit and 64 bit libnss-winbind library to co-exist on the same system. $ apt-get install libnss-winbind:i386 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libnss-winbind:i386 : Depends: winbind:i386 (= 2:4.1.6+dfsg-1ubuntu2) but it is not going to be installed Depends: samba-libs:i386 (= 2:4.1.6+dfsg-1ubuntu2) but it is not going to be installed E: Unable to correct problems, you have held broken packages. This is important as 32 bit binaries running on a 64 bit system can still access NSS services and must still be able to load the nss-winbind plugin. The same comment applies to PAM as well, but I have no 32 bit apps using PAM so it isn't as interesting ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315562 Title: libnss-winbind should allow installation of the 32 bit libarary in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1315562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315560] [NEW] winbind segfaults during pam login
Public bug reported: Attempting to login via PAM causes winbind to segfault and log this to syslog: May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540190, 0] ../lib/util/fault.c:72(fault_report) May 2 16:25:54 jggl winbindd[2416]: === May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540238, 0] ../lib/util/fault.c:73(fault_report) May 2 16:25:54 jggl winbindd[2416]: INTERNAL ERROR: Signal 11 in pid 2416 (4.1.6-Ubuntu) May 2 16:25:54 jggl winbindd[2416]: Please read the Trouble-Shooting section of the Samba HOWTO May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540263, 0] ../lib/util/fault.c:75(fault_report) May 2 16:25:54 jggl winbindd[2416]: === May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.540295, 0] ../source3/lib/util.c:785(smb_panic_s3) May 2 16:25:54 jggl winbindd[2416]: PANIC (pid 2416): internal error May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.585897, 0] ../source3/lib/util.c:896(log_stack_trace) May 2 16:25:54 jggl winbindd[2416]: BACKTRACE: 27 stack frames: May 2 16:25:54 jggl winbindd[2416]:#0 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a) [0x7f6d3e2fff3a] May 2 16:25:54 jggl winbindd[2416]:#1 /usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f6d3e300010] May 2 16:25:54 jggl winbindd[2416]:#2 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f) [0x7f6d425d9c6f] May 2 16:25:54 jggl winbindd[2416]:#3 /usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1ae86) [0x7f6d425d9e86] May 2 16:25:54 jggl winbindd[2416]:#4 /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f6d42a07340] May 2 16:25:54 jggl winbindd[2416]:#5 /usr/lib/x86_64-linux-gnu(krb5_storage_free+0x1) [0x7f6d3ce45441] May 2 16:25:54 jggl winbindd[2416]:#6 /usr/lib/x86_64-linux-gnu(+0x42465) [0x7f6d3ce2b465] May 2 16:25:54 jggl winbindd[2416]:#7 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0x86b1) [0x7f6d3ee756b1] May 2 16:25:54 jggl winbindd[2416]:#8 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(gse_krb5_get_server_keytab+0xfb) [0x7f6d3ee75beb] May 2 16:25:54 jggl winbindd[2416]:#9 /usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0xa7aa) [0x7f6d3ee777aa] May 2 16:25:54 jggl winbindd[2416]:#10 /usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech+0x71) [0x7f6d3f3012b1] May 2 16:25:54 jggl winbindd[2416]:#11 /usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech_by_oid+0x26) [0x7f6d3f301586] May 2 16:25:54 jggl winbindd[2416]:#12 /usr/sbin/winbindd(kerberos_return_pac+0x435) [0x7f6d42e66da5] May 2 16:25:54 jggl winbindd[2416]:#13 /usr/sbin/winbindd(winbindd_dual_pam_auth+0xec4) [0x7f6d42e78884] May 2 16:25:54 jggl winbindd[2416]:#14 /usr/sbin/winbindd(+0x5337c) [0x7f6d42e8d37c] May 2 16:25:54 jggl winbindd[2416]:#15 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x867b) [0x7f6d3c37167b] May 2 16:25:54 jggl winbindd[2416]:#16 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x6b27) [0x7f6d3c36fb27] May 2 16:25:54 jggl winbindd[2416]:#17 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7f6d3c36c5ed] May 2 16:25:54 jggl winbindd[2416]:#18 /usr/sbin/winbindd(+0x55702) [0x7f6d42e8f702] May 2 16:25:54 jggl winbindd[2416]:#19 /usr/sbin/winbindd(+0x55db5) [0x7f6d42e8fdb5] May 2 16:25:54 jggl winbindd[2416]:#20 /usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_immediate+0xd4) [0x7f6d3c36ce14] May 2 16:25:54 jggl winbindd[2416]:#21 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x8437) [0x7f6d3c371437] May 2 16:25:54 jggl winbindd[2416]:#22 /usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x6b27) [0x7f6d3c36fb27] May 2 16:25:54 jggl winbindd[2416]:#23 /usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d) [0x7f6d3c36c5ed] May 2 16:25:54 jggl winbindd[2416]:#24 /usr/sbin/winbindd(main+0xad2) [0x7f6d42e5ee42] May 2 16:25:54 jggl winbindd[2416]:#25 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f6d3bfc4ec5] May 2 16:25:54 jggl winbindd[2416]:#26 /usr/sbin/winbindd(+0x25532) [0x7f6d42e5f532] May 2 16:25:54 jggl winbindd[2416]: [2014/05/02 16:25:54.586279, 0] ../source3/lib/dumpcore.c:312(dump_core) May 2 16:25:54 jggl winbindd[2416]: unable to change to /var/log/samba/cores/winbindd May 2 16:25:54 jggl winbindd[2416]: refusing to dump core Attempting to validate passwords via wbinfo works fine, nss works fine, etc. The segfault prevents the login from succeeding, so pam winbind is basically unusable. This is a regression, this config has worked here on various Ubuntu's for at least 5 years. $ cat /etc/security/pam_winbind.conf [global] ;debug=yes ;debug_state=yes require_membership_of=ORCORP\orc krb5_auth=yes $ cat /etc/samba/smb.conf [global] workgroup = ORCORP realm = ADS.ORCORP.CA os level = 0 log
[Bug 1315565] [NEW] nss-winbind is returing -1 for supplemental groups
Public bug reported: This is a regression in trusty. Consider: $wbinfo -r jgg 1000 -1 10009 10011 10004 10003 -1 1002 -1 Results in: $ getent initgroups jgg jgg 4 24 27 30 46 108 124 1000 10009 10011 10004 10003 1002 $ id jgg uid=2009(jgg) gid=1000(orc) groups=1000(orc),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),108(lpadmin),124(sambashare),4294967295,10009(vpn_users),10011(xweb_users),10004(accounting),10003(domain_users),4294967295,1002(wsudoers),4294967295 Those 4294967295 values should not be in the group list. The underlying issue is that some of the AD groups the user is a part of are not UNIX groups, they are just general AD groups: $ ldapsearch uid=jgg memberOf dn: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=XWEB Users,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=VPN Users,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=accounting,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=wsudoers,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Boards website editors,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Parts website editors,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=adm,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Domain Users,CN=Users,DC=ads,DC=orcorp,DC=ca memberOf: CN=Print Operators,CN=Builtin,DC=ads,DC=orcorp,DC=ca For instance, 'Print Operators' is not a UNIX group, it doesn't have the RFC2307 schema elements. # Print Operators, Builtin, ads.orcorp.ca dn: CN=Print Operators,CN=Builtin,DC=ads,DC=orcorp,DC=ca objectClass: top objectClass: group cn: Print Operators description: Members can administer domain printers member: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca member: CN=Ian Crowe,CN=Users,DC=ads,DC=orcorp,DC=ca distinguishedName: CN=Print Operators,CN=Builtin,DC=ads,DC=orcorp,DC=ca instanceType: 4 whenCreated: 20080729165935.0Z whenChanged: 20080808163035.0Z uSNCreated: 8209 uSNChanged: 30817 name: Print Operators objectGUID:: SBkgyF4upEG4GO6bRhj17g== objectSid:: AQIAAAUgJgIAAA== adminCount: 1 sAMAccountName: Print Operators sAMAccountType: 536870912 systemFlags: -1946157056 groupType: -2147483643 objectCategory: CN=Group,CN=Schema,CN=Configuration,DC=ads,DC=orcorp,DC=ca isCriticalSystemObject: TRUE # wsudoers, Users, ads.orcorp.ca dn: CN=wsudoers,CN=Users,DC=ads,DC=orcorp,DC=ca objectClass: top objectClass: group cn: wsudoers description: Workstation Sudoers member: CN=Rolf Manderscheid,CN=Users,DC=ads,DC=orcorp,DC=ca member: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca member: CN=Ian Crowe,CN=Users,DC=ads,DC=orcorp,DC=ca distinguishedName: CN=wsudoers,CN=Users,DC=ads,DC=orcorp,DC=ca instanceType: 4 whenCreated: 20080808044201.0Z whenChanged: 2030193544.0Z uSNCreated: 30255 info: Members can use sudo on the workstations uSNChanged: 2007454 name: wsudoers objectGUID:: oYEd5AZTyESv6SHZoxBGeQ== objectSid:: AQUAAAUVmm48yDCxnAEu012CfgQAAA== sAMAccountName: wsudoers sAMAccountType: 536870912 managedBy: CN=Jason Gunthorpe,CN=Users,DC=ads,DC=orcorp,DC=ca groupType: -2147483644 objectCategory: CN=Group,CN=Schema,CN=Configuration,DC=ads,DC=orcorp,DC=ca msSFU30Name: wsudoers msSFU30NisDomain: ads gidNumber: 1002 ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315565 Title: nss-winbind is returing -1 for supplemental groups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1315565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] Re: Using fscache with NFS causes random kernel oops
I'm not familiar with Ubuntu's process. This is clearly a bug in Raring, fixed in upstream and I would certainly like a backport to the Raring kernel package as we have no plans here to use Saucy, which isn't even in beta yet :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] Re: Using fscache with NFS causes random kernel oops
Well, if I understand https://wiki.ubuntu.com/KernelTeam/KernelUpdates properly, oops fixes for raring will not be accepted since it is not a LTS and it is past 4 months after release. So I guess that is the end of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1212818] Re: Using fscache with NFS causes random kernel oops
I don't have a recipe to quickly reproduce the oops, so a live environment doesn't help. I actually have to setup and use the install which takes a long time to do. Besides, this is a kernel oops, not a user space problem, changing out the user space isn't going to provide any more information when we already know that 3.11 solves the issue. Jason On Tue, Aug 27, 2013 at 4:07 AM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Jason Gunthorpe, testing the live environment would be just fine. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] Re: Using fscache with NFS causes random kernel oops
So, it has been 11 days and 3.11.0-031100rc5-generic hasn't crashed, I think that is enough to confirm it is fixed in this version. Per Joseph's instructions I've added the 'kernel-fixed-upstream' and marked the bug complete. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags removed: needs-upstream-testing ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1212818] Re: Using fscache with NFS causes random kernel oops
No, installing a whole new release from ISO is simply way too much work. I can test another kernel .deb if you send me a link, but if it is newer than 3.11 that seems wasteful. It would probably be more productive to test a build that includes the patches I linked to in my original report, since they actually seem to fix oops's with a similar back trace. On Mon, Aug 26, 2013 at 6:11 PM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Jason Gunthorpe, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p linux replace-with-bug-number ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] [NEW] Using fscache with NFS causes random kernel oops
Public bug reported: It is hard to get an oops because the entire FS system seems to hang and /var/log/kern.log won't capture it. I have managed to get a kdump capture. I think I told apport to submit the crash dump, but I'm not really sure if it worked, and I don't know where to look to see if it made it anyplace.. fscache was working fine in oneiric at least, so this is a regression. I'm thinking this is probably the fix that needs to be backported: http://www.redhat.com/archives/linux-cachefs/2013-May/msg8.html crash reports: [178619.012128] BUG: unable to handle kernel NULL pointer dereference at 000c [178619.012224] IP: [81044a99] __ticket_spin_lock+0x9/0x30 [178619.012303] PGD 0 [178619.012329] Oops: 0002 [#1] SMP [178619.012369] Modules linked in: nfsv4(F) cachefiles(F) rfcomm bnep bluetooth autofs4(F) nfsd(F) auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) nls_iso8859_1(F) snd_hda_codec_realtek snd_hda_codec_hdmi coretemp snd_hda_intel snd_hda_codec kvm_intel snd_hwdep(F) snd_pcm(F) kvm snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) snd_rawmidi(F) snd_seq(F) snd_seq_device(F) snd_timer(F) snd(F) soundcore(F) tpm_infineon ghash_clmulni_intel(F) aesni_intel(F) aes_x86_64(F) i915 xts(F) lrw(F) gf128mul(F) hp_wmi psmouse(F) drm_kms_helper drm ablk_helper(F) cryptd(F) microcode(F) i2c_algo_bit serio_raw(F) sparse_keymap mac_hid wmi tpm_tis lpc_ich ppdev(F) video(F) parport_pc(F) iTCO_wdt iTCO_vendor_support lp(F) parport(F) hid_generic usbhid hid ahci(F) libahci(F) e1000e(F) [178619.013231] CPU 4 [178619.013257] Pid: 21461, comm: kworker/u:0 Tainted: GF O 3.8.0-27-generic #40-Ubuntu Hewlett-Packard HP EliteDesk 800 G1 SFF/1998 [178619.013372] RIP: 0010:[81044a99] [81044a99] __ticket_spin_lock+0x9/0x30 [178619.013460] RSP: 0018:88034e9c9ce0 EFLAGS: 00010287 [178619.013512] RAX: 0001 RBX: 8803ef5c92c0 RCX: 81e4fc10 [178619.013579] RDX: 0001 RSI: 0005 RDI: 000c [178619.013669] RBP: 88034e9c9ce0 R08: R09: 81e4fb70 [178619.013749] R10: R11: R12: 0030 [178619.013816] R13: 000c R14: 81e4fb60 R15: 81e4fa00 [178619.013895] FS: () GS:88041eb0() knlGS: [178619.013997] CS: 0010 DS: ES: CR0: 80050033 [178619.014064] CR2: 000c CR3: 02c0d000 CR4: 001407e0 [178619.014132] DR0: DR1: DR2: [178619.014199] DR3: DR6: fffe0ff0 DR7: 0400 [178619.014267] Process kworker/u:0 (pid: 21461, threadinfo 88034e9c8000, task 8803b99cdd00) [178619.014364] Stack: [178619.014398] 88034e9c9cf0 816cc97e 88034e9c9da0 a02cc598 [178619.014483] 880406319c00 88034e9c9d20 8108f393 8803ef5c9340 [178619.014576] 88034e9c9d30 81074c74 88034e9c9d40 81074d14 [178619.014660] Call Trace: [178619.014698] [816cc97e] _raw_spin_lock+0xe/0x20 [178619.014762] [a02cc598] fscache_invalidate_writes+0x28/0xc0 [fscache] [178619.014839] [8108f393] ? wake_up_process+0x23/0x40 [178619.014927] [81074c74] ? wake_up_worker+0x24/0x30 [178619.014985] [81074d14] ? insert_work+0x94/0xb0 [178619.015043] [8107725a] ? __queue_work+0xea/0x370 [178619.015111] [a02c8f6f] fscache_object_state_machine+0x6f/0xa30 [fscache] [178619.015192] [a02c995b] fscache_object_work_func+0x2b/0x60 [fscache] [178619.015263] [8107682c] process_one_work+0x15c/0x4d0 [178619.015325] [8107808e] worker_thread+0x16e/0x480 [178619.015418] [81077f20] ? manage_workers+0x2a0/0x2a0 [178619.015491] [8107d420] kthread+0xc0/0xd0 [178619.015558] [8107d360] ? kthread_create_on_node+0x120/0x120 [178619.015662] [816d516c] ret_from_fork+0x7c/0xb0 [178619.015728] [8107d360] ? kthread_create_on_node+0x120/0x120 [178619.015790] Code: 00 00 48 c7 c1 a1 48 04 81 48 c7 c2 9e 48 04 81 e9 dd fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 b8 00 00 01 00 48 89 e5 f0 0f c1 07 89 c1 c1 e9 10 66 39 c1 89 ca 74 11 0f 1f 80 00 00 [178619.016207] RIP [81044a99] __ticket_spin_lock+0x9/0x30 [178619.016302] RSP 88034e9c9ce0 [178619.016338] CR2: 000c ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1212818] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774137/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774130/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] Re: Using fscache with NFS causes random kernel oops
apport information ** Tags added: apport-collected ** Description changed: It is hard to get an oops because the entire FS system seems to hang and /var/log/kern.log won't capture it. I have managed to get a kdump capture. I think I told apport to submit the crash dump, but I'm not really sure if it worked, and I don't know where to look to see if it made it anyplace.. fscache was working fine in oneiric at least, so this is a regression. I'm thinking this is probably the fix that needs to be backported: http://www.redhat.com/archives/linux-cachefs/2013-May/msg8.html crash reports: [178619.012128] BUG: unable to handle kernel NULL pointer dereference at 000c [178619.012224] IP: [81044a99] __ticket_spin_lock+0x9/0x30 [178619.012303] PGD 0 [178619.012329] Oops: 0002 [#1] SMP [178619.012369] Modules linked in: nfsv4(F) cachefiles(F) rfcomm bnep bluetooth autofs4(F) nfsd(F) auth_rpcgss(F) nfs_acl(F) nfs(F) lockd(F) sunrpc(F) fscache(F) nls_iso8859_1(F) snd_hda_codec_realtek snd_hda_codec_hdmi coretemp snd_hda_intel snd_hda_codec kvm_intel snd_hwdep(F) snd_pcm(F) kvm snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) snd_rawmidi(F) snd_seq(F) snd_seq_device(F) snd_timer(F) snd(F) soundcore(F) tpm_infineon ghash_clmulni_intel(F) aesni_intel(F) aes_x86_64(F) i915 xts(F) lrw(F) gf128mul(F) hp_wmi psmouse(F) drm_kms_helper drm ablk_helper(F) cryptd(F) microcode(F) i2c_algo_bit serio_raw(F) sparse_keymap mac_hid wmi tpm_tis lpc_ich ppdev(F) video(F) parport_pc(F) iTCO_wdt iTCO_vendor_support lp(F) parport(F) hid_generic usbhid hid ahci(F) libahci(F) e1000e(F) [178619.013231] CPU 4 [178619.013257] Pid: 21461, comm: kworker/u:0 Tainted: GF O 3.8.0-27-generic #40-Ubuntu Hewlett-Packard HP EliteDesk 800 G1 SFF/1998 [178619.013372] RIP: 0010:[81044a99] [81044a99] __ticket_spin_lock+0x9/0x30 [178619.013460] RSP: 0018:88034e9c9ce0 EFLAGS: 00010287 [178619.013512] RAX: 0001 RBX: 8803ef5c92c0 RCX: 81e4fc10 [178619.013579] RDX: 0001 RSI: 0005 RDI: 000c [178619.013669] RBP: 88034e9c9ce0 R08: R09: 81e4fb70 [178619.013749] R10: R11: R12: 0030 [178619.013816] R13: 000c R14: 81e4fb60 R15: 81e4fa00 [178619.013895] FS: () GS:88041eb0() knlGS: [178619.013997] CS: 0010 DS: ES: CR0: 80050033 [178619.014064] CR2: 000c CR3: 02c0d000 CR4: 001407e0 [178619.014132] DR0: DR1: DR2: [178619.014199] DR3: DR6: fffe0ff0 DR7: 0400 [178619.014267] Process kworker/u:0 (pid: 21461, threadinfo 88034e9c8000, task 8803b99cdd00) [178619.014364] Stack: [178619.014398] 88034e9c9cf0 816cc97e 88034e9c9da0 a02cc598 [178619.014483] 880406319c00 88034e9c9d20 8108f393 8803ef5c9340 [178619.014576] 88034e9c9d30 81074c74 88034e9c9d40 81074d14 [178619.014660] Call Trace: [178619.014698] [816cc97e] _raw_spin_lock+0xe/0x20 [178619.014762] [a02cc598] fscache_invalidate_writes+0x28/0xc0 [fscache] [178619.014839] [8108f393] ? wake_up_process+0x23/0x40 [178619.014927] [81074c74] ? wake_up_worker+0x24/0x30 [178619.014985] [81074d14] ? insert_work+0x94/0xb0 [178619.015043] [8107725a] ? __queue_work+0xea/0x370 [178619.015111] [a02c8f6f] fscache_object_state_machine+0x6f/0xa30 [fscache] [178619.015192] [a02c995b] fscache_object_work_func+0x2b/0x60 [fscache] [178619.015263] [8107682c] process_one_work+0x15c/0x4d0 [178619.015325] [8107808e] worker_thread+0x16e/0x480 [178619.015418] [81077f20] ? manage_workers+0x2a0/0x2a0 [178619.015491] [8107d420] kthread+0xc0/0xd0 [178619.015558] [8107d360] ? kthread_create_on_node+0x120/0x120 [178619.015662] [816d516c] ret_from_fork+0x7c/0xb0 [178619.015728] [8107d360] ? kthread_create_on_node+0x120/0x120 [178619.015790] Code: 00 00 48 c7 c1 a1 48 04 81 48 c7 c2 9e 48 04 81 e9 dd fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 b8 00 00 01 00 48 89 e5 f0 0f c1 07 89 c1 c1 e9 10 66 39 c1 89 ca 74 11 0f 1f 80 00 00 [178619.016207] RIP [81044a99] __ticket_spin_lock+0x9/0x30 [178619.016302] RSP 88034e9c9ce0 [178619.016338] CR2: 000c + --- + ApportVersion: 2.9.2-0ubuntu8.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: jgg 17760 F pulseaudio + /dev/snd/pcmC1D0p: jgg 17760 F...m pulseaudio + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. +
[Bug 1212818] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774133/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774129/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774138/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774127/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774126/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] HookError_cloud_archive.txt
apport information ** Attachment added: HookError_cloud_archive.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774128/+files/HookError_cloud_archive.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774134/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774132/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774136/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774135/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1212818/+attachment/3774131/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212818] Re: Using fscache with NFS causes random kernel oops
Joseph: I have successfully booted: Linux jggl 3.11.0-031100rc5-generic #201308112135 SMP Mon Aug 12 01:35:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Since I don't know how to reproduce the crash, I will update this bug either when 3.11 crashes or in about a weeks time. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212818 Title: Using fscache with NFS causes random kernel oops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996151] Re: disable apt http pipelining in quantal
Wow, I'm really surprised you guys have decided to turn pipe-lining off. That is crazy. Pipelining has been in APT since day one (ie since 1997, wow!), and I personally worked with a number of web server developers to make sure their severs worked properly, according to the RFC. Squid has *always* had varying levels of breakage when working with pipelining, but I also extensively tested APT's HTTP method with squid and ensured it worked for many years. It looks to me like someone must have tried to 'improve' things in squid (probably tried to support HTTP/1.1 keep-alive) and broke it even more.. The thought that pipe lining is inherently broken is ridiculous. The behaviour of requesters, proxies and completer's is very well defined, and if you follow the damn spec you don't create any problems, security, correctness, or otherwise. And yes, it makes an huge, obvious, night and day difference: $ time sudo apt-get update -o Acquire::http::Pipeline-Depth=10 real0m9.090s $ time sudo apt-get update -o Acquire::http::Pipeline-Depth=0 real0m19.700s A much better suggestion would be to detect a proxy during install (most proxies add headers to their reply) and drop a pipeline depth config into /etc/apt/apt.conf.d/ ... Or perhaps not pipeline the first request and look for a proxy in the reply, then turn it on. It is completely mind blowing that squid has been broken since 1997, even to the extent that the breakage created a whole new class of proxy vulnerabilities (request smuggling) and nobody has fixed it, or even really cared to notice.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/996151 Title: disable apt http pipelining in quantal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/996151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 784473] Re: Treats partial InRelease signature as verifying the entire file
You really need to use --output to process inline signatures, trying to exactly match what gnupg validated externally is not a robust way to run such important crypto. It would be better to require full gpg until gpgv can be fixed - (not having --output in gpgv only encourages incorrect use of the program!). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784473 Title: Treats partial InRelease signature as verifying the entire file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/784473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 702707] Re: grub-install fails to run due to missing grub_mkdevicemap
True enough - EFI should use the EFI console interface which hopefully works reliably. But grub prints a warning message at boot that it cannot locate hwmatch.lua, so maybe the grub.conf construction scripts should be updated to not include that fragment if the lua script is not available. On Thu, Jan 20, 2011 at 1:33 PM, Colin Watson cjwat...@canonical.comwrote: Jason: I think we're probably OK leaving out hwmatch.lua for now. The whole deal with graphical boot images is likely to be completely different on UEFI vs. BIOS anyhow ... -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/702707 Title: grub-install fails to run due to missing grub_mkdevicemap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/702707 Title: grub-install fails to run due to missing grub_mkdevicemap -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 702707] Re: grub-install fails to run due to missing grub_mkdevicemap
Thanks Colin,
I also noticed that the missing lua file is from this:
grub.cfg: if lua ${prefix}/hwmatch.lua; then
when grub.cfg is built by the default scripts. Looks like the EFI packages
should also include this file, or something..
On Mon, Jan 17, 2011 at 1:49 PM, Colin Watson
cjwat...@canonical.comwrote:
Thanks! Fixed for my next upload.
** Changed in: grub2 (Ubuntu)
Importance: Undecided = High
** Changed in: grub2 (Ubuntu)
Status: New = Fix Committed
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/702707
Title:
grub-install fails to run due to missing grub_mkdevicemap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702707
Title:
grub-install fails to run due to missing grub_mkdevicemap
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 702707] [NEW] grub-install fails to run due to missing grub_mkdevicemap
Public bug reported:
Binary package hint: grub2
This is a bug in the grub-install included in grub-efi-amd64
Running it gives:
$ grub-install
/usr/sbin/grub-install: 391: : Permission denied
/usr/sbin/grub-install: 391: : Permission denied
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: ,0001,0002,0003
Boot* Windows Boot Manager
Boot0001* Hard Drive
Boot0002* Network Card
Boot0003* UEFI: 0.00
/usr/sbin/grub-install: 636: --device-map=/dev/stdout: not found
Could not open disk : No such file or directory
Installation finished. No error reported.
Notice there is no 'ubuntu' entry in the listing from efibootmgr. Oops.
Easy fix:
--- grub-install2011-01-13 19:37:55.125032970 -0700
+++ /usr/sbin/grub-install 2011-01-11 16:58:32.0 -0700
@@ -38,7 +38,6 @@
grub_setup=${sbindir}/`echo grub-setup | sed ${transform}`
grub_mkimage=${bindir}/`echo grub-mkimage | sed ${transform}`
+grub_mkdevicemap=${sbindir}/`echo grub-mkdevicemap | sed ${transform}`
grub_probe=${sbindir}/`echo grub-probe | sed ${transform}`
grub_editenv=${bindir}/`echo grub-editenv | sed ${transform}`
grub_mkrelpath=${bindir}/`echo grub-mkrelpath | sed ${transform}`
Works fine after:
$ grub-install
BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0004,,0001,0002,0003
Boot* Windows Boot Manager
Boot0001* Hard Drive
Boot0002* Network Card
Boot0003* UEFI: 0.00
Boot0004* ubuntu
Installation finished. No error reported.
Also, this bit fails:
for file in ${grubdir}/*.mod ${grubdir}/*.lua ${grubdir}/*.lst
${grubdir}/*.img ${grubdir}/efiemu??.o; do
(and others with *.lua) because there is no *.lua files in the grubdir, or
included with the package. Probably should use
for file in `find ${grbudir} -name *.mod -or -name *.lua -or -name *.lst
-or -name *.img [...]`
or so.
I'm running the natty version on maverick because the maverick version
corrupts the initrd with my BIOS ...
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: grub-efi-amd64 1.99~20110111-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Thu Jan 13 19:48:11 2011
ProcEnviron:
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
SourcePackage: grub2
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug maverick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702707
Title:
grub-install fails to run due to missing grub_mkdevicemap
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 702707] Re: grub-install fails to run due to missing grub_mkdevicemap
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/702707 Title: grub-install fails to run due to missing grub_mkdevicemap -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 648721] Re: page allocation failure on machines under heavy network load
I see this too. This is not similar to kernel bug 12135, this is a failing order 5 allocation, not a failing order 0 allocation. The net stack should not be making high order allocations, something to do with Xen causes them to happen and of course they fail as memory is fragmented. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/648721 Title: page allocation failure on machines under heavy network load -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 681598] Re: passwd doesn't work with pam_winbind
*** This bug is a duplicate of bug 570944 *** https://bugs.launchpad.net/bugs/570944 Unless someone has a plan to actually go and fix pam_unix, I'd suggest a better idea is to update pam_winbind's /usr/share/pam-configs/winbind to get rid of use_authtok. The objection that this disables strength checking modules is fair, but in practice nobody will care - the AD server already does strength checking. That 'passwd' doesn't work AT ALL, is rather more serious and everyone using winbind will ultimately care about that. Jason On Thu, Dec 2, 2010 at 11:24 AM, Serge Hallyn 681...@bugs.launchpad.netwrote: *** This bug is a duplicate of bug 570944 *** https://bugs.launchpad.net/bugs/570944 ** This bug has been marked a duplicate of bug 570944 passwd : gives Authentication token manipulation error * You can subscribe to bug 570944 by following this link: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/570944/+subscribe -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/681598 Title: passwd doesn't work with pam_winbind -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. https://bugs.launchpad.net/bugs/681598 Title: passwd doesn't work with pam_winbind -- 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
Re: [Bug 681598] Re: passwd doesn't work with pam_winbind
*** This bug is a duplicate of bug 570944 *** https://bugs.launchpad.net/bugs/570944 Unless someone has a plan to actually go and fix pam_unix, I'd suggest a better idea is to update pam_winbind's /usr/share/pam-configs/winbind to get rid of use_authtok. The objection that this disables strength checking modules is fair, but in practice nobody will care - the AD server already does strength checking. That 'passwd' doesn't work AT ALL, is rather more serious and everyone using winbind will ultimately care about that. Jason On Thu, Dec 2, 2010 at 11:24 AM, Serge Hallyn 681...@bugs.launchpad.netwrote: *** This bug is a duplicate of bug 570944 *** https://bugs.launchpad.net/bugs/570944 ** This bug has been marked a duplicate of bug 570944 passwd : gives Authentication token manipulation error * You can subscribe to bug 570944 by following this link: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/570944/+subscribe -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/681598 Title: passwd doesn't work with pam_winbind -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/681598 Title: passwd doesn't work with pam_winbind -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 681598] Re: passwd doesn't work with pam_winbind
** Visibility changed to: Public -- passwd doesn't work with pam_winbind https://bugs.launchpad.net/bugs/681598 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 141569] Re: should distribute a 32 bit version of nss_winbind.so
Another use case: 64 bit base OS install running 32 bit proprietary applications using winbind for NSS. The apps tend to freak out when they try to do NSS lookups (ie getpwname). Sigh. -- should distribute a 32 bit version of nss_winbind.so https://bugs.launchpad.net/bugs/141569 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 114620] Re: GDM has no change password option
Just had this happen here too, using pam_winbind - gdm displayed the password has expired message and then it locked up :( On maverick -- GDM has no change password option https://bugs.launchpad.net/bugs/114620 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 681598] Re: passwd doesn't work with pam_winbind
** Visibility changed to: Public -- passwd doesn't work with pam_winbind https://bugs.launchpad.net/bugs/681598 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 141569] Re: should distribute a 32 bit version of nss_winbind.so
Another use case: 64 bit base OS install running 32 bit proprietary applications using winbind for NSS. The apps tend to freak out when they try to do NSS lookups (ie getpwname). Sigh. -- should distribute a 32 bit version of nss_winbind.so https://bugs.launchpad.net/bugs/141569 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 673708] [NEW] getaddrinfo and AI_PASSIVE is broken for net.ipv6.bindv6only=0
Public bug reported:
When calling getaddrinfo and specifying AF_UNSPEC and AI_PASSIVE it
returns both IPv4 and IPv6 addresses when the sysctl net.ipv6.bindv6only
= 0. Proper app behavior for AI_PASSIVE should be to bind and listen to
all returned addresses, but the kernel does not allow binding to a V4
and V6 address with the same port. In this case getaddrinfo should
return only a IPv4 or only a IPv6 address.
Illustrated with python because I'm lazy:
resx =
socket.getaddrinfo(None,'1234',0,socket.SOCK_STREAM,0,socket.AI_PASSIVE)
print resx
[(2, 1, 6, '', ('0.0.0.0', 1234)), (10, 1, 6, '', ('::', 1234, 0, 0))]
res = resx[0]
fd = socket.socket(res[0],res[1],res[2])
fd.bind(res[4]);
res = resx[1]
fd2 = socket.socket(res[0],res[1],res[2])
fd2.bind(res[4]);
Traceback (most recent call last):
File stdin, line 1, in module
File string, line 1, in bind
socket.error: [Errno 98] Address already in use
At least in earlier Ubuntu releases this case returned the IPv6 address
first, so most apps which don't properly use all addresses 'worked' but
it was still wrong to return both addresses. The new behavior breaks
IPv6 in various cases, with no possible app work-around!
Apps should not be expected to 'sense' if the system is bindv6only.
getaddrinfo AF_UNSPEC/AI_PASSIVE should return v6 only for an IPv6
enabled bindv6only = 0 host and both IPv6 and IPv4 (in any order) for an
IPv6 enabled bindv6only= host.
At a minimum the old sorting behavior of putting v6 first should be
restored! Real apps depend on this!
I've noted various other bugs in this same theme:
http://sources.redhat.com/bugzilla/show_bug.cgi?id=9981
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573456
So here is one for Ubuntu with a bit more clarity on the exact problem.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libc6 2.12.1-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Wed Nov 10 12:52:08 2010
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
ProcEnviron:
PATH=(custom, no user)
LANG=C
SHELL=/bin/bash
SourcePackage: eglibc
** Affects: eglibc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug maverick
--
getaddrinfo and AI_PASSIVE is broken for net.ipv6.bindv6only=0
https://bugs.launchpad.net/bugs/673708
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 673708] Re: getaddrinfo and AI_PASSIVE is broken for net.ipv6.bindv6only=0
-- getaddrinfo and AI_PASSIVE is broken for net.ipv6.bindv6only=0 https://bugs.launchpad.net/bugs/673708 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 344843] Re: After OpenVPN NM installed its not work, but when I restarted it will works fine
Just saw this on 10.10 too. /etc/init.d/network-manager restart got things going again. -- After OpenVPN NM installed its not work, but when I restarted it will works fine https://bugs.launchpad.net/bugs/344843 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 384017] Re: Loading /etc/bash_completion is slow
There is more going on here than just loading a lot of completion.
Something is weird inside bash, look at the strace of completion loading
and you see it is doing a wack of busy work crap like this. The fiddling
with FDs looks like it is probably some kind of errant debug feature?
This is from maverick with bash 4.1-2ubuntu4. It is annoying that
16:58:30 access(/etc/bash_completion.d/mutt, R_OK) = 0
16:58:30 open(/etc/bash_completion.d/mutt, O_RDONLY) = 3
16:58:30 fstat(3, {st_mode=S_IFREG|0644, st_size=4527, ...}) = 0
16:58:30 read(3, # mutt completion\n#\n# Mutt doesn..., 4527) = 4527
16:58:30 close(3) = 0
16:58:30 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
16:58:30 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
16:58:30 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
16:58:30 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
16:58:30 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
16:58:30 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
16:58:30 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
16:58:30 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
16:58:30 open(/dev/null, O_WRONLY|O_CREAT|O_TRUNC, 0666) = 3
16:58:30 fcntl(1, F_GETFD) = 0
16:58:30 fcntl(1, F_DUPFD, 10) = 10
16:58:30 fcntl(1, F_GETFD) = 0
16:58:30 fcntl(10, F_SETFD, FD_CLOEXEC) = 0
16:58:30 dup2(3, 1) = 1
16:58:30 close(3) = 0
16:58:30 fcntl(2, F_DUPFD, 10) = 11
16:58:30 fcntl(2, F_GETFD) = 0
16:58:30 fcntl(11, F_SETFD, FD_CLOEXEC) = 0
16:58:30 dup2(1, 2) = 2
16:58:30 stat(., {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
16:58:30 stat(/usr/sbin/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file or dir
16:58:30 stat(/usr/bin/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file or dire
16:58:30 stat(/sbin/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file or directo
16:58:30 stat(/bin/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file or director
16:58:30 stat(/usr/bin/X11/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file or
16:58:30 stat(/usr/bin/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file or dire
16:58:30 stat(/usr/local/bin/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file o
16:58:30 stat(/usr/games/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file or di
16:58:30 stat(/home/jgg/bin/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file or
16:58:30 stat(/sbin/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file or directo
16:58:30 stat(/usr/sbin/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file or dir
16:58:30 stat(/usr/local/sbin/mutt, 0x7fff6d9e1230) = -1 ENOENT (No such file
16:58:30 write(2, bash: type: mutt: not found\n, 28) = 28
16:58:30 dup2(11, 2)= 2
16:58:30 fcntl(11, F_GETFD) = 0x1 (flags FD_CLOEXEC)
16:58:30 close(11) = 0
16:58:30 dup2(10, 1)= 1
16:58:30 fcntl(10, F_GETFD) = 0x1 (flags FD_CLOEXEC)
16:58:30 close(10) = 0
16:58:30 rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
--
Loading /etc/bash_completion is slow
https://bugs.launchpad.net/bugs/384017
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 642551] [NEW] [ATIIXP - ATI IXP] SPDIF output does not work with pulseaudio (reason included)
Public bug reported: Binary package hint: pulseaudio SPDIF works fine if pulseaudio is disabled via aplay The problem is that this ALSA environment has this mixer control: Simple mixer control 'IEC958 Playback AC97-SPSA',0 Capabilities: volume volume-joined penum Playback channels: Mono Capture channels: Mono Limits: 0 - 3 Mono: 3 [100%] Which pulseaudio *forces* to be '3' and keeps it there. Unfortunately *this is not a volume control* - inside the kernel this setting controls the SPSA channel assignment (see the A97 2.2 spec page 58). For output to work on my system this must be set to 0 - S/PDIF source data assigned to AC-link slots 34 I'm not sure who is at fault here. Some possibilities: 1) The kernel should export this as an ENUM type setting, not a volume slider 2) pulseaudio should treat it in some special way and at least let me set it to 0 3) Something else?? What is this even used for? The 'right' setting might naturally fall out depending on the channel count, or hardware config and this shouldn't even leave the kernel at all? Clearly, at least the current situation is completely useless. The value needs to be set properly, pulse has no way to set it, thus I get no sound. There have been other bugs related to this.. bug #198523, for instance. It is really obscure that something that looks like a volume slider has nothing to do with volume and is *critical* to proper sound output!! Jason ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: IXP [ATI IXP], device 0: ATI IXP AC97 [ATI IXP AC97] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jgg1933 F pulseaudio /dev/snd/pcmC0D0p: jgg1933 F...m pulseaudio Card0.Amixer.info: Card hw:0 'IXP'/'ATI IXP rev 2 with ALC658D at 0xfe02a000, irq 17' Mixer name : 'Realtek ALC658D' Components : 'AC97a:414c4781' Controls : 38 Simple ctrls : 24 Date: Sat Sep 18 23:00:05 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta i386 (20100901.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en PATH=(custom, no user) LANG=C SHELL=/bin/bash SelectedCard: 0 IXP ATIIXP - ATI IXP SourcePackage: alsa-driver Symptom: audio Title: [ATIIXP - ATI IXP] ALSA test tone not correctly played back dmi.bios.date: 09/30/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 3.35 dmi.board.name: AMETHYST-M dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.35:bd09/30/2005:svnCompaqPresario061:pnED865AA-ABASR1610NXNA540:pvr0n41411RE101AMETH00:rvnMSI:rnAMETHYST-M:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: ED865AA-ABA SR1610NX NA540 dmi.product.version: 0n41411RE101AMETH00 dmi.sys.vendor: Compaq Presario 061 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- [ATIIXP - ATI IXP] SPDIF output does not work with pulseaudio (reason included) https://bugs.launchpad.net/bugs/642551 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 642551] Re: [ATIIXP - ATI IXP] SPDIF output does not work with pulseaudio (reason included)
** Attachment added: AlsaDevices.txt https://bugs.launchpad.net/bugs/642551/+attachment/1606393/+files/AlsaDevices.txt ** Attachment added: AplayDevices.txt https://bugs.launchpad.net/bugs/642551/+attachment/1606394/+files/AplayDevices.txt ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/642551/+attachment/1606395/+files/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/642551/+attachment/1606396/+files/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt https://bugs.launchpad.net/bugs/642551/+attachment/1606397/+files/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt https://bugs.launchpad.net/bugs/642551/+attachment/1606398/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/642551/+attachment/1606399/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/642551/+attachment/1606400/+files/Dependencies.txt ** Attachment added: PciMultimedia.txt https://bugs.launchpad.net/bugs/642551/+attachment/1606401/+files/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/642551/+attachment/1606402/+files/ProcCpuinfo.txt -- [ATIIXP - ATI IXP] SPDIF output does not work with pulseaudio (reason included) https://bugs.launchpad.net/bugs/642551 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 259914] [NEW] prefs in ubufox extension override system prefs
Public bug reported: Binary package hint: ubufox This is quite annoying, we cannot customize system wide settings via the prefs in /etc/firefox/pref/firefox.js if they are overridden by /usr/lib/firefox-3.0.1/extensions/[EMAIL PROTECTED]/defaults/preferences /ubuntu-mods.js Since the extensions are loaded after the system preferences. The most significant of these for us would be the pref(network.negotiate-auth.trusted-uris, https://;); Setting. I want that to be our domain not https:// and it is impossible to change via the system wide configuration due to the override in ubufox. Please move all the pref overrides out of an extension and put them in proper pref files loaded before the system pref files. *** 0.5-0ubuntu1 0 ** Affects: ubufox (Ubuntu) Importance: Undecided Status: New -- prefs in ubufox extension override system prefs https://bugs.launchpad.net/bugs/259914 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 159432] python-mode does not autoload on emacs21
Public bug reported: Binary package hint: python-mode python mode no longer auto loads on emacs21 with gutsy. Looks like the /etc/emacs/site-start.d/50python-mode.el isn't quite right, I suspect it got broke while fixing 155681. By my eye, the entire file should be executed when emacs21 is used, but the form of the if statement only executes the first line. The rest of the file is executed on emacs22/emacs20 which does not seem to be the intent. I fixed it by wrapping the bulk of the file in a progn block. (if (not (or (eq (symbol-name debian-emacs-flavor) emacs20) (eq (symbol-name debian-emacs-flavor) emacs22))) (progn (autoload 'python-mode python-mode Python editing mode. t) [..] The execution of the bulk of this file as an else block is probbably related to 155681, but the fix from there is needed too, the eq should be string=. ** Affects: python-mode (Ubuntu) Importance: Undecided Status: New -- python-mode does not autoload on emacs21 https://bugs.launchpad.net/bugs/159432 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
