[Bug 1968588] Re: Cannot create or add VPN in connection editor
Workaround available here https://askubuntu.com/questions/1403896/cant-add-cisco-compatible-vpn-vpnc-on-network-manager-ubuntu-22-04/1404609#1404609 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968588 Title: Cannot create or add VPN in connection editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1968588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968588] Re: Cannot create or add VPN in connection editor
** Tags added: indeed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968588 Title: Cannot create or add VPN in connection editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1968588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855762] Re: Freeipa 4.7 released long ago, but we still on beta version
I'm moving this to won't fix in 18.04 as it doesn't follow the Ubuntu ethos of bug/security-fix only after release. Also it looks like 4.9.8-1 is being worked on for jammy. ** Changed in: freeipa (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855762 Title: Freeipa 4.7 released long ago, but we still on beta version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1855762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855762] Re: Freeipa 4.7 released long ago, but we still on beta version
Unfortunately Ubuntu is not a rolling release. If there are specific issues that you'd like patched please link to the specific patches so they can be discussed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855762 Title: Freeipa 4.7 released long ago, but we still on beta version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1855762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824280] Re: freeipa server dns -- problem with certificates section of webui
It looks like the linked ticket has been closed as fixed released. I'm closing this ticket as a result. If there is still an issue please re- open. ** Changed in: freeipa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824280 Title: freeipa server dns -- problem with certificates section of webui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1824280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922298] [NEW] Activities panel on wrong display
Public bug reported: The activities panel is showing up on the wrong display. Selecting the "primary display" as 3 in the display settings puts the top bar on display 3 , but the activities bar on screen 2. Screenshot attached Similarly, selecting primary display = 2 then activities bar ends up on 1 primary display = 1 then activities bar ends up on 3 I'm hoping this is just an off by one error somewhere. I think gnome-shell is the correct package. Feel free to move to the correct package ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 17:16:30 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (293 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2021-04-01 17-05-08.png" https://bugs.launchpad.net/bugs/1922298/+attachment/5483269/+files/Screenshot%20from%202021-04-01%2017-05-08.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922298 Title: Activities panel on wrong display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890613] [NEW] Gnome unresponsive JS ERROR: TypeError: windowActor is null
Public bug reported: gnome-shell becomes unresponsive after about 1 day. I'm able to interact with the window that had focus when the problem appears (in this case it was Chrome), but I'm unable to select or otherwise interact with other windows, the shell, dock, or indicators. The logs are spammed with gnome-shell[2916]: JS ERROR: TypeError: windowActor is null#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 This looks similar to but different enough from https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774 I was using the i915 driver when this happened if that makes any difference ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 09:08:32 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (54 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890613 Title: Gnome unresponsive JS ERROR: TypeError: windowActor is null To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851749] Re: Frequently getting thermal warnings and cpu throttling messages in syslog
This is seems to be wider than simply Lenovo machines as my Dell Precision 5540 is hitting this as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876157] Re: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020
Get memtest into debian, and it will get pulled in to Ubuntu ... eventually. The reason it hasn't been updated is that Ubuntu does not wish to fork memtest from Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876157 Title: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
** Also affects: linux-5.4 (Ubuntu Focal) Importance: Medium Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
** Package changed: linux-signed-5.4 (Ubuntu) => linux-5.4 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
Also I should have mentioned that 5.3.0-24-generic as a workaround also fixed it for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
I also am hitting this. This looks to be a gen 9 graphics problem, as sforshee with gen 10 graphics appears unaffected. I'm on a Dell Inspiron 5540 with an i9-9880H $ glxinfo | grep Device Device: Mesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) (0x3e9b) @tyhicks reported on #ubuntu-kernel his affected box was Device: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2) (0x5917) It appears that this might be limited to kaby and coffee lake generations of gpu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861521] Re: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled
** Summary changed: - [FOCAL][REGRESSION] HP EliteBook 840 G5 screen brightness cannot be controlled + [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861521 Title: [FOCAL][REGRESSION] Intel Gen 9 brightness cannot be controlled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1861521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev
Targeting for bionic, but I haven't checked the other releases. I will say it's odd that there's a libssl-dev and libssl-doc but not a libssl only a libssl1.0 and a libssl1.1. I'm sure there's reasons, and I'm not privy to them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861304 Title: libmysqlclient-dev will not install with libssl1.0-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1861304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861304] Re: libmysqlclient-dev will not install with libssl1.0-dev
** Changed in: mysql-5.7 (Ubuntu) Importance: Undecided => High ** Also affects: mysql-5.7 (Ubuntu Bionic) Importance: Undecided Status: New ** Tags added: regression-release ** Changed in: mysql-5.7 (Ubuntu Bionic) Milestone: None => bionic-updates ** Changed in: mysql-5.7 (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861304 Title: libmysqlclient-dev will not install with libssl1.0-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1861304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847786] Re: Update linux-firmware in bionic for 19.04 and 19.10 hwe kernels
** Tags added: indeed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847786 Title: Update linux-firmware in bionic for 19.04 and 19.10 hwe kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847786] [NEW] Update linux-firmware in bionic for 19.04 and 19.10 hwe kernels
Public bug reported: It looks like the hwe kernels need the linux-firmware revved again. update-initramfs: Generating /boot/initrd.img-5.3.0-12-generic W: Possible missing firmware /lib/firmware/i915/icl_guc_32.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_32.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_32.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_32.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_32.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_huc_ver8_4_3238.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_huc_ver03_01_2893.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_8_2893.bin for module i915 I have a feeling those with broadcom cards will also need a revved firmware in order to acquire bnx2x/bnx2x-e2-7.13.11.0.fw as they will not be able to be used with the 5.3 kernel without it. ** Affects: linux-firmware (Ubuntu) Importance: High 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/1847786 Title: Update linux-firmware in bionic for 19.04 and 19.10 hwe kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844805] Re: virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from 19.04 to 19.10
This is similar to https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1844805 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844805 Title: virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from 19.04 to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1844805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521734] Re: virtualbox-dkms: virtualbox kernel module failed to build [gcc: error: unrecognized command line option ‘-fstack-protector-strong’]
** Changed in: virtualbox (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521734 Title: virtualbox-dkms: virtualbox kernel module failed to build [gcc: error: unrecognized command line option ‘-fstack-protector-strong’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1521734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371494] Re: VirtualBox crashed with SIGSEGV
** Changed in: virtualbox (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371494 Title: VirtualBox crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1371494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847662] [NEW] virtualbox-dkms fails to build with 18.04-hwe-edge kernel 5.3.0-12
Public bug reported: With 5.3.0-12-generic on bionic virtualbox-dkms fails to build the kernel driver. Excerpt of build failure below. Full text attached. This is the second time I've been bitten by this dkms failing to build on kernel upgrades. It really feels like the -dkms packages successfully building should be a gating factor in releasing hwe- kernels. Perhaps such a test can be added to autopkgtests? CC [M] /var/lib/dkms/virtualbox/5.2.32/build/vboxdrv/r0drv/linux/semmutex-r0drv-linux.o /var/lib/dkms/virtualbox/5.2.32/build/vboxdrv/r0drv/linux/mp-r0drv-linux.c: In function ‘VBoxHost_RTMpOnAll’: /var/lib/dkms/virtualbox/5.2.32/build/vboxdrv/r0drv/linux/mp-r0drv-linux.c:287:18: error: void value not ignored as it ought to be int rc = smp_call_function(rtmpLinuxAllWrapper, , 0 /* wait */); ^ /var/lib/dkms/virtualbox/5.2.32/build/vboxdrv/r0drv/linux/mp-r0drv-linux.c: In function ‘VBoxHost_RTMpOnOthers’: /var/lib/dkms/virtualbox/5.2.32/build/vboxdrv/r0drv/linux/mp-r0drv-linux.c:341:8: error: void value not ignored as it ought to be rc = smp_call_function(rtmpLinuxWrapper, , 1 /* wait */); ^ scripts/Makefile.build:288: recipe for target '/var/lib/dkms/virtualbox/5.2.32/build/vboxdrv/r0drv/linux/mp-r0drv-linux.o' failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virtualbox-dkms 5.2.32-dfsg-0~ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.3.0-12.13~18.04.2-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 10 14:49:53 2019 InstallationDate: Installed on 2018-03-28 (561 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: High Status: Confirmed ** Affects: virtualbox (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Virtualbox-dkms failure output." https://bugs.launchpad.net/bugs/1847662/+attachment/5296320/+files/virtualbox-dkms.0.crash ** Summary changed: - virtualbox-dkms fails to build with 18.04-hwe-edge kernel + virtualbox-dkms fails to build with 18.04-hwe-edge kernel 5.3.0-12 ** Also affects: virtualbox (Ubuntu Bionic) 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/1847662 Title: virtualbox-dkms fails to build with 18.04-hwe-edge kernel 5.3.0-12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1847662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
@oddbjornk @cristofaro Launchpad is not a forum. Each bug is meant to solve one problem. One of you need to create a new bug for the new problem. You are welcome to reference or link this issue in that new bug though so whoever triages it has a reference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838555] Re: nvme-cli 1.5 in Bionic does not support Micron NVME drives
I got my act together and sponsored this bug today. Now you just need SRU approval. @mruffell, welcome to the party. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838555 Title: nvme-cli 1.5 in Bionic does not support Micron NVME drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1838555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838555] Re: nvme-cli 1.5 in Bionic does not support Micron NVME drives
@slashd , Reading through the patch, it's exactly as @mruffell says it is. It's sequestered into a code path that only exists for micron drives. A code path which previously did not exist. This satisfies the intro, and the first three bullet points of Other_safe_cases. This patch is upstream and AFAICT from git log and comparing of the enablement patch and the file on master of the public project micron-nvme.c has not changed in any consequential way. IMHO. there should be no issue with pushing this in as an SRU into bionic, and does significantly improve the user experience for those with Micron drives. This simultaneously has little to no impact on other users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838555 Title: nvme-cli 1.5 in Bionic does not support Micron NVME drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1838555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841654] Re: Consider replacing mawk with gawk in main
We (Indeed) were recently hit by mawk posix non-compliance as well. For all the reasons stated above, I would also like to see mawk replaced with gawk in main. I'd also like to see the mawk dependencies in the ubuntu-meta packages replaced with gawk. For that reason I'm opening a separate target for this bug in ubuntu-meta. ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags added: indeed ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841654 Title: Consider replacing mawk with gawk in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mawk/+bug/1841654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839589] Re: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]
Hey thanks for the fix, I've been on vacation, and didn't have a chance to look at this further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839589 Title: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839589] Re: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test]
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Dave Chiluk (chiluk) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839589 Title: pulseaudio FTBFS on eoan 12.2-2ubuntu4 [FAIL: cpu-volume-test] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839589] [NEW] pulseaudio FTBFS on eoan 12.2-2ubuntu4
Public bug reported: pulseaudio fails to build from source on Eoan I was attempting to put together a patchset for LP#1839580, but it appears as if the packages are currently failing to build from source. Not sure how they built the first time around. Here's my ppa's buildlog, for a source package with my patch commented out of the series file. https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz ** Affects: pulseaudio (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/1839589 Title: pulseaudio FTBFS on eoan 12.2-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839580] Re: LucidSound LS31 only outputs mono sound
Upstream merge request. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/143 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839580 Title: LucidSound LS31 only outputs mono sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839580] [NEW] LucidSound LS31 only outputs mono sound
Public bug reported: LucidSound LS31 only outputs mono sound. The usb vendor:prod = 2f12:0109. The fix is incoming. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Assignee: Dave Chiluk (chiluk) Status: In Progress ** Changed in: pulseaudio (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839580 Title: LucidSound LS31 only outputs mono sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
Enabling this plugin is the easiest way to work around this issue in bionic. https://extensions.gnome.org/extension/1328/disable-workspace-switch-animation/ That being said what is the status of a real fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1812527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
** Tags added: indeed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702961] Re: Intel wifi instability with 4.10 and Intel Device 24fd
I'm going to close out this bug, as I have not experienced this since moving to 18.04. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702961 Title: Intel wifi instability with 4.10 and Intel Device 24fd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
You will want to contact Dell support on that one as it appears you are running a non- Ubuntu kernel version (it's probably Dell provided). You might simply need to upgrade. On Thu, Mar 28, 2019, 3:40 PM Maxwell Ballenger wrote: > Thanks for the work you all have done tracking this down. I am > experiencing an issue with identical symptoms. I understand the problem > should be fixed with 4.15+, so I may be experiencing a different bug. If > anyone could help me determine that conclusively or point me in a > direction that might help me fix this one, I'd really appreciate it! > > Below I have reproduced the issue in the same way as above, with the > same workaround. > > Dell Precision 5530 > TB16 Dock > Ubuntu 18.04 > Kernel: 4.15.0-1034-oem > > $ sudo ethtool --offload enx3c2c30b2d39a rx on > $ for i in 1 2 3 4 5 6 7 8 9; do curl -s > http://old-releases.ubuntu.com/releases/17.04/ubuntu-17.04-server-amd64.img > -o $i.iso; md5sum $i.iso; done > 4672ce371fb3c1170a9e71bc4b2810b9 1.iso > 5cfcb270becce9962c0dc305dac943b9 2.iso > 4672ce371fb3c1170a9e71bc4b2810b9 3.iso > ba8ec5ef56501dbab731dcd0e627a334 4.iso > 7d5d892efa5899a99129d90167508434 5.iso > c0402e3a6a1179d77c3132e15af2b81f 6.iso > 4672ce371fb3c1170a9e71bc4b2810b9 7.iso > 4672ce371fb3c1170a9e71bc4b2810b9 8.iso > 4672ce371fb3c1170a9e71bc4b2810b9 9.iso > $ sudo ethtool --offload enx3c2c30b2d39a rx off > $ for i in 1 2 3 4 5 6 7 8 9; do curl -s > http://old-releases.ubuntu.com/releases/17.04/ubuntu-17.04-server-amd64.img > -o $i.iso; md5sum $i.iso; done > 4672ce371fb3c1170a9e71bc4b2810b9 1.iso > 4672ce371fb3c1170a9e71bc4b2810b9 2.iso > 4672ce371fb3c1170a9e71bc4b2810b9 3.iso > 4672ce371fb3c1170a9e71bc4b2810b9 4.iso > 4672ce371fb3c1170a9e71bc4b2810b9 5.iso > 4672ce371fb3c1170a9e71bc4b2810b9 6.iso > 4672ce371fb3c1170a9e71bc4b2810b9 7.iso > 4672ce371fb3c1170a9e71bc4b2810b9 8.iso > 4672ce371fb3c1170a9e71bc4b2810b9 9.iso > $ uname -r > 4.15.0-1034-oem > $ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1729674 > > Title: > TB16 dock ethernet corrupts data with hw checksum silently failing > > Status in Dell Sputnik: > Triaged > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Xenial: > Fix Released > Status in linux source package in Artful: > Fix Released > Status in linux source package in Bionic: > Fix Released > Status in linux package in Fedora: > Confirmed > > Bug description: > It looks like TCP rx and tx checksum offloading is broken on the TB16 > dock's ethernet adapter. For example downloading a large file such as the > Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. > This is because > rx-checksumming: on > tx-checksumming: on > and both set to on by default. > > Running sudo ethtool -K tx off rx off, allows the > download to complete correctly. This is very bad since this can cause > very bad untrustworthy behavior. > > This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- > generic-hwe-16.04-edge. > > Thank you > > To manage notifications about this bug go to: > https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: product=dell-sputnik; status=Triaged; importance=High; > assignee=None; > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > milestone=ubuntu-18.04; status=Fix Released; importance=High; assignee= > kai.heng.f...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=xenial; > sourcepackage=linux; component=main; status=Fix Released; > importance=Undecided; assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=artful; > sourcepackage=linux; component=main; status=Fix Released; importance=High; > assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=linux; component=main; milestone=ubuntu-18.04; status=Fix > Released; importance=High; assignee=kai.heng.f...@canonical.com; > Launchpad-Bug: distribution=fedora; sourcepackage=linux; component=None; > status=Confirmed; importance=Undecided; assignee=None; > Launchpad-Bug-Tags: indeed verification-done-artful > verification-done-xenial > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: ballengerm benjamin-redhat-bugs chiluk > christian-redhat-bugs gerben-redhat-bugs janitor jarod-redhat-bugs > jeremy-redhat-bugs jiri-redhat-bugs kai-heng-redhat-bugs kaihengfeng katamo > luciano marianne-z mario-redhat-bugs martin
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
I have tested bionic and cosmic myself, but I'd like to hear from a user or two. I have experienced the low-volume issue, but that appears to be correctable by launching alsamixer. All in all it's a better experience than before imho. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
I uploaded these changes for bionic and cosmic. Just waiting on sru approval now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
I uploaded the changes to disco this morning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
** Description changed: + [Impact] + + * User is only able to get mono audio from steelseries headsets because + they provide both a stereo and mono output. PA selects the mono output + by default. + + * This should be backported to stable releases because this fix is +isolated to code that only applies to the affected headsets. +Additionally other gaming headsets may be more easily enabled by adding + ATTRS{idVendor}=="", ATTRS{idProduct}=="", ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf" +to /lib/udev/rules.d/90-pulseaudio.rules now. Such as the Lucidsound +LS31 which I own. + + * The upload fixes the bug by conditionally setting a pulseaudio + profile for the headset based on specific usb vendor and product ids in + the udev rules. + + [Test Case] + + 1. Acquire headset. + 2. Open sound settings, and click test speakers. + 3. Only option available will be mono sound + + [Regression Potential] + + * Risk of regressions should be mitigated to those who own the headset. + In which case it is likely that their headset is already not working. + + [Other Info] + + * All patches originate from upstream pulseaudio, and are documented as +such including the shas. + + * I will be pursuing enabling other similar headsets in the coming weeks. + * I plan to work with upstream pulseaudio to enable my own headset and to +also make the headset templates backported here more generic. + + + Original Description - + There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio - /dev/snd/controlC1: kaj1755 F pulseaudio - /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio - /dev/snd/controlC0: kaj1755 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio + /dev/snd/controlC1: kaj1755 F pulseaudio + /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio + /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
I uploaded test packages for cosmic and disco to my ppa today. If someone with the headset could test either of those as well that would be awesome. I should be getting a headset here soon to test with. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
** Changed in: pulseaudio (Ubuntu Cosmic) Status: Confirmed => In Progress ** Changed in: pulseaudio (Ubuntu Disco) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
I'm pretty sure you need to adjust the "chat mix" knob on your headset as the audio will now be playing through a separate audio device on the headset. Basically previously it was using the mono "chat"/mono output on the headphones. Now with the ppa it's primarily using the "game"/stereo output. AFAIU the knob adjusts the mix between the two outputs on the headphones themselves. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
@Kaj Printz Madsen I know you opened this a long time ago, but is there any chance you could test the ppa for me? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813663] Re: External monitors does not work anymore 4.15.0-44
Yah @jparedes you should probably open a different bug. You are running into something different. I've also verified that this is now fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813663 Title: External monitors does not work anymore 4.15.0-44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
Looking at pulseaudio upstream, it looks like 12.2 has 15386a710c1500f70085a6312fb4d84be4d254c9 and c7fe78c9f73ded2c3428666722ec9c1af4b82812 but not 83675b3745c64bd738400eae44eb4daa195ed88a fe6a9a8f59932f29cc77eac2a7e2c6bd07c8c7d0 3454c19f3c277d5d0099f17e7ebf5d2005afa4b0 Bionic will needs all of the above sha's. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
Can someone on this bug please test the packages from https://launchpad.net/~chiluk/+archive/ubuntu/lp1758736 on Bionic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
Basically what I did was backport all the required Arctis stuff that seemed to be required in order to get my lucid sound headphones working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Dave Chiluk (chiluk) ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Also affects: pulseaudio (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Disco) Importance: Low Assignee: Dave Chiluk (chiluk) Status: Confirmed ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu Cosmic) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Cosmic) Assignee: (unassigned) => Dave Chiluk (chiluk) ** Changed in: pulseaudio (Ubuntu Bionic) Assignee: (unassigned) => Dave Chiluk (chiluk) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
** Tags added: indeed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680438] Re: gnome-calculator comes up with totally wrong answer
gnome has moved to gitlab. Corresponding bug is now https://gitlab.gnome.org/GNOME/gnome-calculator/issues/59 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680438 Title: gnome-calculator comes up with totally wrong answer To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1680438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
@katamo 4.14.xx is not a supported Ubuntu kernel. I'm not sure where you pulled that kernel from, but it is not supportable. At this point all Supported Ubuntu kernels and mainline 4.15+ have this fix. @EVERYONE ELSE If you think you are hitting this issue and are running the latest supported kernels, you are likely hitting a different issue, and should be opening a new bug. Please stop resurrecting this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
Ran same tests against 4.13.0-38 on artful. Just curious, this only seems to be applied to hwe and hwe-edge kernels for xenial. Is that a change in policy? Even though I haven't attempted it, it appears as if this should be pretty straightforward apply on the 4.4 kernel stream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727285] Re: xfs_quota always exit with 0
I'm marking this won't fix pending a response from @Kaoet and a behavior change from upstream xfs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727285 Title: xfs_quota always exit with 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/1727285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727285] Re: xfs_quota always exit with 0
xfs_quota appears to be working as expected, but it seems you would like to change it's behavior. Ubuntu would prefer not diverge from the upstream xfsprogs project. Please bring up this issue with xfs project directly at http://xfs.org/index.php/Main_Page If they agree to change the behavior please point us at the change and we will get it backported. ** Changed in: xfsprogs (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727285 Title: xfs_quota always exit with 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/1727285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290563] Re: tar restore or cp to disk produces corrupt data
Closing Won't fix as this version has end of lifed and has likely been resolved. Please reopen if this is still an issue. ** Changed in: xfsprogs (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290563 Title: tar restore or cp to disk produces corrupt data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/1290563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 910067] Re: xfs_freeze, xfs_io "command not found"
Closing Won't fix as this version has end of lifed and has likely been resolved. Please reopen if this is still an issue. ** Changed in: xfsprogs (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/910067 Title: xfs_freeze, xfs_io "command not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/910067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 103159] Re: [apport] xfs_db crashed with SIGSEGV in pthread_mutex_lock()
Closing Won't fix as this version has end of lifed and has likely been resolved. Please reopen if this is still an issue. ** Changed in: xfsprogs (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/103159 Title: [apport] xfs_db crashed with SIGSEGV in pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/103159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 119224] Re: xfs_admin gives "fatal error" when trying to label mounted device
Closing Won't fix as this version has end of lifed and has likely been resolved. ** Changed in: xfsprogs (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/119224 Title: xfs_admin gives "fatal error" when trying to label mounted device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/119224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 808470] Re: mount fails, xfs_repair does not run
Closing Won't fix as this version has end of lifed and has likely been resolved. Please reopen if this is still an issue. ** Changed in: xfsprogs (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/808470 Title: mount fails, xfs_repair does not run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/808470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 236847] Re: xfs_db: fatal error in gparted
Closing Won't fix as this version has end of lifed and has likely been resolved. Please reopen if this is still an issue. ** Changed in: xfsprogs (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/236847 Title: xfs_db: fatal error in gparted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/236847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 519336] Re: mkfs.xfs partially broken in hardy heron
Closing Won't fix as this version has end of lifed and has likely been resolved. Please reopen if this is still an issue. ** Changed in: xfsprogs (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/519336 Title: mkfs.xfs partially broken in hardy heron To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/519336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 344761] Re: XFS corrupts data when filesystem full (on sw-raid5)
Closing Won't fix as this version has end of lifed. ** Changed in: xfsprogs (Ubuntu) Status: New => Incomplete ** Changed in: xfsprogs (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/344761 Title: XFS corrupts data when filesystem full (on sw-raid5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/344761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772235] Re: xfs_check eats up memory
Closing Won't fix as this version has end of lifed and has likely been resolved. Please reopen if this is still an issue. ** Changed in: xfsprogs (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/772235 Title: xfs_check eats up memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/772235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 307625] Re: xfs_fsr should run automatically if on xfs volumes if it is installed
Closing Won't fix as this version has end of lifed and has likely been resolved. Please reopen if this is still an issue. ** Changed in: xfsprogs (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/307625 Title: xfs_fsr should run automatically if on xfs volumes if it is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsprogs/+bug/307625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723390] Re: lxd containers have become degraded
Same thing in bionic # journalctl -u systemd-hostnamed -- Logs begin at Wed 2018-02-28 16:43:47 UTC, end at Wed 2018-02-28 16:44:28 UTC. -- Feb 28 16:44:03 bionic systemd[1]: systemd-hostnamed.service: Failed to reset devices.list: Operation not permitted Feb 28 16:44:03 bionic systemd[1]: systemd-hostnamed.service: Failed to set invocation ID on control group /system.slice/systemd-hostnamed.service, ignoring: Ope Feb 28 16:44:03 bionic systemd[1]: Starting Hostname Service... Feb 28 16:44:03 bionic systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK Feb 28 16:44:03 bionic systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'. Feb 28 16:44:03 bionic systemd[1]: Failed to start Hostname Service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723390 Title: lxd containers have become degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723390] Re: lxd containers have become degraded
Verified kind of still exists with ubuntu 17.10 amd64 (daily) (20180227) # journalctl -u systemd-hostnamed.service -- Logs begin at Wed 2018-02-28 16:38:35 UTC, end at Wed 2018-02-28 16:39:16 UTC. -- Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Failed to reset devices.list: Operation not permitted Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Failed to set invocation ID on control group /system.slice/systemd-hostnamed.service, ig Feb 28 16:38:51 pants systemd[1]: Starting Hostname Service... Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK Feb 28 16:38:51 pants systemd[1]: Failed to start Hostname Service. Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Unit entered failed state. Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'. However I'm not sure where @xnox saw the "degraded" status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723390 Title: lxd containers have become degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
Looks like this has been released with 4.15.0-9.10 which is available in bionic. ** Also affects: linux (Ubuntu Bionic) Importance: High Assignee: Kai-Heng Feng (kaihengfeng) Status: In Progress ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Bionic) Milestone: None => ubuntu-18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
@kmously I see that you marked this fix as Fix Committed in Artful, but I do not see it in the master-next branch of artful. I'm moving this back to In progress in artful as this does not appear to have been pushed to master-next for artful yet. Feel free to push it back to Fix Committed when you accept or merge the patch into master-next. ** Changed in: linux (Ubuntu Artful) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
** Tags added: indeed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
@pandasauce ... Fix committed means it's in the git archive, but has completed testing nor been integrated into the archives yet. Also please refrain from repeating things we already know in the thread or otherwise +1'ing or me-tooing. It just wastes developers time that could be spent actually fixing the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
Hasn't completed testing or been integrated into the archives. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
That patch note makes it sound like there will be a hardware/firmware fix that will hopefully resolve this. If so it is very unlikely that upstream will accept your patch, as the proper fix will really be to upgrade your firmware. A more preferable patch will be to log a big bad warning if you have TB16 with the bad firmware revision. The kernel people don't tend to like to BUG hardware issues that are resolvable through firmware updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
I should also mention that this should probably be pushed to linux- stable as well as mainline as this is a silent data corruption bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
Those changes test as good. @Kai-Heng Feng. In the future you should consider setting LOCALVERSION or using a PPA and setting a +lp1729674 to version string in the changelog. With what you did it's hard to distinguish between your test package and an official package. See https://wiki.ubuntu.com/Kernel/Dev/KernelBugFixing#Publish_a_Package_for_Testing for more info. Thanks for the work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742364] Re: Updated microcode for Spectre fix
** Also affects: intel-microcode (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Bionic) Importance: Critical Status: Triaged ** Also affects: intel-microcode (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Zesty) 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/1742364 Title: Updated microcode for Spectre fix To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1742364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
I'm sorry I've been unable to test this from my end. Have you been able to make any progress on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670959] Re: systemd-resolved using 100% CPU
** Tags added: indeed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670959 Title: systemd-resolved using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1670959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
I reviewed your patch, and it appears as if it only turns off receive checksumming. The internets are saying that transmit needs to be turned off as well. Have you checked to see if transmit is affected as well? I will try to do some transmit tests. I'll also "test" your kernel when I get a chance, but by the looks of the patch there shouldn't be too much to test as it simply turns off RX checksuming which is already a known good solution. On Mon, Nov 20, 2017 at 2:06 AM, Kai-Heng Fengwrote: > Dave, > > Please try this kernel, > http://people.canonical.com/~khfeng/lp1729674/ > > The temporary workaround is what we can get before chip vendors solve > the issue. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1729674 > > Title: > TB16 dock ethernet corrupts data with hw checksum silently failing > > Status in Dell Sputnik: > Triaged > Status in linux package in Ubuntu: > In Progress > Status in linux package in Fedora: > Confirmed > > Bug description: > It looks like TCP rx and tx checksum offloading is broken on the TB16 > dock's ethernet adapter. For example downloading a large file such as the > Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. > This is because > rx-checksumming: on > tx-checksumming: on > and both set to on by default. > > Running sudo ethtool -K tx off rx off, allows the > download to complete correctly. This is very bad since this can cause > very bad untrustworthy behavior. > > This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- > generic-hwe-16.04-edge. > > Thank you > > To manage notifications about this bug go to: > https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
udevadm info -e as requested. ** Attachment added: "udevadminfo" https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+attachment/5010640/+files/udevadminfo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
I also just went through the process of reproducing this while watching the kern.log. Absolutely 0 messages came out. If you find some verbose debugging you want me to turn on let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing
I am not using ipv6. On Tue, Nov 14, 2017 at 9:10 AM, Mario Limonciellowrote: > @Dave: > > I was glancing at r8152 driver and notice that it has some special > handling for ipv6. Is this issue reproducing only in ipv6 for you? > https://github.com/torvalds/linux/commit/6128d1bb30748d0ff56a63898d14f3 > 12126e404c > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1729674 > > Title: > TB16 dock ethernet corrupts data with hw checksum silently failing > > Status in Dell Sputnik: > Triaged > Status in linux package in Ubuntu: > In Progress > > Bug description: > It looks like TCP rx and tx checksum offloading is broken on the TB16 > dock's ethernet adapter. For example downloading a large file such as the > Ubuntu ISO, and then running an md5sum on it yields the incorrect md5sum. > This is because > rx-checksumming: on > tx-checksumming: on > and both set to on by default. > > Running sudo ethtool -K tx off rx off, allows the > download to complete correctly. This is very bad since this can cause > very bad untrustworthy behavior. > > This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux- > generic-hwe-16.04-edge. > > Thank you > > To manage notifications about this bug go to: > https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729674 Title: TB16 dock ethernet corrupts data with hw checksum silently failing To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1729674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724650] Re: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)
There is no way to tell if you even have the intel-microcode package installed which should have the newest microcode. Please apt install intel-microcode and update this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724650 Title: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1724650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719047] [NEW] Unable to resize window after snapped to half screen.
Public bug reported: Unable to resize window after snapped to half screen. You can see the arrow, tempting you to just try and resize the window at the edge, but it's just toying with you. More info https://bugzilla.gnome.org/show_bug.cgi?id=645153 This used to work in z+Unity ;(. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 19:15:17 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['google-chrome-beta.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop', 'keepassx.desktop', 'chrome-knipolnnllmklapflnccelgolnpehhpl-Default.desktop', 'terminator.desktop', 'org.gnome.Calculator.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.2' b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2016-04-25 (515 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-09 (13 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful regression-release wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719047 Title: Unable to resize window after snapped to half screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1719047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712925] Re: FFE: HAproxy dropping connections (RST) during config reload / support seamless reload
** Changed in: haproxy (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712925 Title: FFE: HAproxy dropping connections (RST) during config reload / support seamless reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1712925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712925] Re: FFE: HAproxy dropping connections (RST) during config reload / support seamless reload
Added configuration and testing results to top page. Upload commencing shortly. ** Description changed: Reloading haproxy causes TCP resets for active connections. This can be a serious issue for clouds that rely on haproxy for load balancing, and as a result are restarting it frequently. Full related blog post is here. https://www.haproxy.com/blog/truly-seamless-reloads-with-haproxy-no-more-hacks/ FFE Justification - - Description- The patchset fixes the issue by adding the -x option to haproxy. This option is used for passing the unix stats socket from the old haproxy to the new one. The old haproxy then passes connections to the new haproxy using this socket *(simplified explanation). The changes are largely isolated to new functions that implement this functionality. + - Description- The patchset fixes the issue by adding the -x option to haproxy. This option is used for passing the unix stats socket from the old haproxy to the new one. The old haproxy then passes connections to the new haproxy using this socket *(simplified explanation). The changes are largely isolated to new functions that implement this functionality. - Rationale - The change is largely isolated to the new option, but for those running clouds this could be potentially very important. Clouds that are "doing it right", and treating instances as cattle are constantly tearing down and rebuilding instances. This has the side effect of constantly reloading haproxy. For example at Indeed on a few of our clouds haproxy gets restarted roughly every second. My tests show that this causes a connection reset rate of about 18 resets for 50k connections. The haproxy teams are showing 11 tcp resets for 2k connections. Either way it's greater than 0 and it's dependent on how many connections you receive and how fast you are restarting haproxy. I've chosen not to enable this by default in the systemd unit files, as enabling that the stats socket in the haproxy config match the one passed with the -x command. However for those that are seeing this problem only having to make the config and unit file changes should be a better user experience than hand building packages. + + Configuration + 1. Add the following lines to your haproxy.cfg + "# turn on stats unix socket + stats socket /var/lib/haproxy/stats expose-fd listeners + stats bind-process 1 + " + 2. Add "HAPROXY_STATS_SOCKET=/var/lib/haproxy/stats" to the Environment variable in /lib/systemd/system/haproxy.service + 3. $ sudo systemctl daemon-reload + 4. $ systemctl reload haproxy. + It's important to use reload as it is accomplished using the haproxy-systemd-wrapper. + + Testing. + 1. Configure as above. + 2. put haproxy in a reload loop + $ while true ; do sudo systemctl reload haproxy ; sleep 3 ; done + 3. run apache bench against it. + $ ab -r -c 20 -n 10 http://192.168.1.226:8070/ + + Results: + With these patches: + Complete requests: 10 + Failed requests:0 + + Without these patches: + Complete requests: 10 + Failed requests:81 +(Connect: 0, Receive: 27, Length: 27, Exceptions: 27) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712925 Title: FFE: HAproxy dropping connections (RST) during config reload / support seamless reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1712925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712925] Re: FFE: HAproxy dropping connections (RST) during config reload / support seamless reload
** Description changed: - haproxy is releasing a feature that provides for seamless reloads for - 1.8. + Reloading haproxy causes TCP resets for active connections. This can be + a serious issue for clouds that rely on haproxy for load balancing, and + as a result are restarting it frequently. Full related blog post is here. https://www.haproxy.com/blog/truly-seamless-reloads-with-haproxy-no-more-hacks/ - I have attempted a backport of the feature, and attached it. The patch - needs to be cleaned up, needs dep-3 tags, and needs to be tested. At - this point I'm mostly just sure that it builds. + FFE Justification + - Description- The patchset fixes the issue by adding the -x option to haproxy. This option is used for passing the unix stats socket from the old haproxy to the new one. The old haproxy then passes connections to the new haproxy using this socket *(simplified explanation). The changes are largely isolated to new functions that implement this functionality. + + - Rationale - The change is largely isolated to the new option, but for + those running clouds this could be potentially very important. Clouds + that are "doing it right", and treating instances as cattle are + constantly tearing down and rebuilding instances. This has the side + effect of constantly reloading haproxy. For example at Indeed on a few + of our clouds haproxy gets restarted roughly every second. My tests + show that this causes a connection reset rate of about 18 resets for 50k + connections. The haproxy teams are showing 11 tcp resets for 2k + connections. Either way it's greater than 0 and it's dependent on how + many connections you receive and how fast you are restarting haproxy. + I've chosen not to enable this by default in the systemd unit files, as + enabling that the stats socket in the haproxy config match the one + passed with the -x command. However for those that are seeing this + problem only having to make the config and unit file changes should be a + better user experience than hand building packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712925 Title: FFE: HAproxy dropping connections (RST) during config reload / support seamless reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1712925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713532] Re: Intel-8260 not init'd by intel-microcode=3.20170707.1~ubuntu16.04.0
@yarko, Please start by gathering the information @hmh requested. Those include: 1. output of /proc/cpuinfo 2. /var/log/kern.log Please provide both of these with both the working and newest microcode. Also please reverify bluetooth in both cases, as we need to make sure that the issue wasn't simply resolved with a reboot. Thank you, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713532 Title: Intel-8260 not init'd by intel-microcode=3.20170707.1~ubuntu16.04.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1713532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713532] Re: Intel-8260 not init'd by intel-microcode=3.20170707.1~ubuntu16.04.0
According to the bios changelog https://downloadmirror.intel.com/26841/eng/SY_0061_ReleaseNotes.pdf 0061 of your bios should already include the microcode that is also available in the intel-microcode package. As such, on boot I'd expect a no-op when checking for newer microcode version. We definitely need to know microcode version your machine is reporting with both packages installed. Is there any chance that linux-firmware got updated as well? I suspect linux-firmware to be the culprit over intel-microcode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713532 Title: Intel-8260 not init'd by intel-microcode=3.20170707.1~ubuntu16.04.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1713532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712925] Re: FFE: HAproxy dropping connections (RST) during config reload / support seamless reload
Another thing just occurred to me. We probably want the kinks in this worked out in the 17.10 development and release cycle, as 18.04 will hopefully get haproxy 1.8 which will include these changes officially. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712925 Title: FFE: HAproxy dropping connections (RST) during config reload / support seamless reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1712925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712925] Re: HAproxy dropping connections (RST) during config reload / support seamless reload
The original intention was to get it into 17.10, but I didn't have enough time yesterday to get it tested and cleaned up. I really think we should consider this for FFE, as it is a bug fix. That being said it also is an interface change, and will probably require changes to the systemd unit files as well *(still have to work that bit out). ** Summary changed: - HAproxy dropping connections (RST) during config reload / support seamless reload + FFE: HAproxy dropping connections (RST) during config reload / support seamless reload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712925 Title: FFE: HAproxy dropping connections (RST) during config reload / support seamless reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1712925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712925] Re: HAproxy dropping connections (RST) during config reload / support seamless reload
** Description changed: haproxy is releasing a feature that provides for seamless reloads for 1.8. Full related blog post is here. https://www.haproxy.com/blog/truly-seamless-reloads-with-haproxy-no-more-hacks/ I have attempted a backport of the feature, and attached it. The patch - needs to be cleaned up, needs dep-3 tags, and needs to be tested. + needs to be cleaned up, needs dep-3 tags, and needs to be tested. At + this point I'm mostly just sure that it builds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712925 Title: HAproxy dropping connections (RST) during config reload / support seamless reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1712925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712925] Re: HAproxy dropping connections (RST) during config reload / support seamless reload
I have created a ppa with this current patch to assist with testing. https://launchpad.net/~chiluk/+archive/ubuntu/lp1712925 This patchset is still in the early stages, so use/test this with extreme caution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712925 Title: HAproxy dropping connections (RST) during config reload / support seamless reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1712925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712925] [NEW] HAproxy dropping connections (RST) during config reload / support seamless reload
Public bug reported: haproxy is releasing a feature that provides for seamless reloads for 1.8. Full related blog post is here. https://www.haproxy.com/blog/truly-seamless-reloads-with-haproxy-no-more-hacks/ I have attempted a backport of the feature, and attached it. The patch needs to be cleaned up, needs dep-3 tags, and needs to be tested. ** Affects: haproxy (Ubuntu) Importance: Undecided Assignee: Dave Chiluk (chiluk) Status: New ** Attachment added: "artful.patch" https://bugs.launchpad.net/bugs/1712925/+attachment/4938252/+files/artful.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712925 Title: HAproxy dropping connections (RST) during config reload / support seamless reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1712925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README
Sponsored artful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674680 Title: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README
** Also affects: bluez (Ubuntu Artful) Importance: Low Status: New ** Tags removed: sts-sponsor-chiluk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674680 Title: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1674680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1702961] Re: Intel wifi instability with 4.10 and Intel Device 24fd
I'm now on the 4.11.0-10-generic kernel, and have not seen this failure again. However, I'll leave it up to the kernel team to see if they want to pursue this further. You can install this kernel on Xenial by installing linux-generic-hwe-16.04-edge. More information is available https://wiki.ubuntu.com/Kernel/LTSEnablementStack If you have enough time to do a git bisect so we can pull the commit back into official kernels that would be really helpful. Thanks, Dave On Fri, Aug 4, 2017 at 1:04 AM, Alfred <1702...@bugs.launchpad.net> wrote: > Today, I replace my old 7260 dual band(engineer sample) with a new 7260 > dual band. > > 04:00.0 Network controller [0280]: Intel Corporation Wireless 7260 > [8086:08b2] (rev 83) > > The network is becoming more instable. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1702961 > > Title: > Intel wifi instability with 4.10 and Intel Device 24fd > > Status in linux-hwe package in Ubuntu: > Confirmed > > Bug description: > Wifi drops and has to reconnect regularly. > > This is on a Dell Precision 5520. > > Kernel warnings in log include. > > [ cut here ] > WARNING: CPU: 4 PID: 1042 at /build/linux-hwe-dbNd9L/linux- > hwe-4.10.0/drivers/net/wireless/intel/iwlwifi/mvm/sta.c:1523 > iwl_mvm_rm_sta+0x3ea/0x460 [iwlmvm] > Modules linked in: ccm rfcomm bbswitch(OE) bnep snd_hda_codec_hdmi > dell_led snd_hda_codec_realtek snd_hda_codec_generic hid_multitouch joydev > i2c_designware_platform i2c_designware_core dell_wmi mxm_wmi nls_iso8859_1 > dell_rbtn dell_laptop dell_smbios dcdbas dell_smm_hwmon intel_rapl > x86_pkg_temp_thermal intel_powerclamp coretemp arc4 kvm_intel kvm irqbypass > crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc iwlmvm aesni_intel > mac80211 aes_x86_64 crypto_simd glue_helper cryptd iwlwifi cfg80211 > rtsx_pci_ms memstick snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep > snd_pcm input_leds snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi > snd_seq snd_seq_device snd_timer snd soundcore uvcvideo videobuf2_vmalloc > videobuf2_memops idma64 videobuf2_v4l2 virt_dma videobuf2_core videodev > media >btusb btrtl mei_me shpchp mei processor_thermal_device intel_lpss_pci > intel_soc_dts_iosf intel_pch_thermal hci_uart btbcm btqca btintel bluetooth > dell_smo8800 wmi intel_hid intel_lpss_acpi nvidia_uvm(POE) sparse_keymap > mac_hid intel_lpss tpm_crb int3400_thermal int3403_thermal acpi_als > int340x_thermal_zone acpi_thermal_rel kfifo_buf acpi_pad industrialio > parport_pc ppdev lp parport autofs4 i915 rtsx_pci_sdmmc nvidia_drm(POE) > nvidia_modeset(POE) nvidia(POE) i2c_algo_bit drm_kms_helper syscopyarea > sysfillrect sysimgblt fb_sys_fops psmouse drm nvme ahci rtsx_pci nvme_core > libahci i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes > CPU: 4 PID: 1042 Comm: wpa_supplicant Tainted: P OE > 4.10.0-27-generic #30~16.04.2-Ubuntu > Hardware name: Dell Inc. Precision 5520/0R6JFH, BIOS 1.3.4 06/08/2017 > Call Trace: >dump_stack+0x63/0x90 >__warn+0xcb/0xf0 >warn_slowpath_null+0x1d/0x20 >iwl_mvm_rm_sta+0x3ea/0x460 [iwlmvm] >iwl_mvm_mac_sta_state+0x40a/0x600 [iwlmvm] >drv_sta_state+0x8a/0x460 [mac80211] >__sta_info_destroy_part2+0x17a/0x1b0 [mac80211] >__sta_info_flush+0x103/0x1b0 [mac80211] >ieee80211_set_disassoc+0xba/0x3f0 [mac80211] >ieee80211_mgd_auth+0x26c/0x3c0 [mac80211] >? cfg80211_get_bss+0x1c5/0x2d0 [cfg80211] >ieee80211_auth+0x18/0x20 [mac80211] >cfg80211_mlme_auth+0x101/0x210 [cfg80211] >nl80211_authenticate+0x30b/0x370 [cfg80211] >genl_family_rcv_msg+0x1db/0x3b0 >genl_rcv_msg+0x59/0xa0 >? genl_notify+0x80/0x80 >netlink_rcv_skb+0xa4/0xc0 >genl_rcv+0x28/0x40 >netlink_unicast+0x18c/0x240 >netlink_sendmsg+0x2fb/0x3a0 >? aa_sock_msg_perm+0x61/0x150 >sock_sendmsg+0x38/0x50 >___sys_sendmsg+0x2c2/0x2d0 >? destroy_inode+0x3b/0x60 >? evict+0x136/0x1a0 >? iput+0x1bb/0x240 >? __dentry_kill+0x110/0x160 >? dput+0x214/0x250 >? mntput+0x24/0x40 >? __fput+0x190/0x220 >__sys_sendmsg+0x54/0x90 >SyS_sendmsg+0x12/0x20 >entry_SYSCALL_64_fastpath+0x1e/0xad > RIP: 0033:0x7f6d6dd04450 > RSP: 002b:7ffcd1f168b8 EFLAGS: 0246 ORIG_RAX: 002e > RAX: ffda RBX: 0004 RCX: 7f6d6dd04450 > RDX: RSI: 7ffcd1f16940 RDI: 0007 > RBP: 562488dd1adc R08: R09: 00df > R10: 1000 R11: 0246 R12: 562488dd1adc > R13: 562488dd4550 R14: R15: > ---[ end trace 24fe098f56796fbc ]--- > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.10.0-27-generic 4.10.0-27.30~16.04.2 [modified: > boot/vmlinuz-4.10.0-27-generic] > ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 >
[Bug 1700373] Re: intel-microcode is out of date, version 20170707 fixes errata on 6th and 7th generation platforms
I just verified skylake + 20170707 on zesty. I did not rerun the testcase, but I did do boot testing. Marking verification-done. ** Tags removed: verification-needed verification-needed-zesty ** Tags added: verification-done verification-done-zesty ** Changed in: intel-microcode (Ubuntu Yakkety) Assignee: Dave Chiluk (chiluk) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: intel-microcode is out of date, version 20170707 fixes errata on 6th and 7th generation platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs