[Bug 1750273] Re: UI scaling broken after last update in Xenial
** Attachment added: "Screenshot of how Files looks like at 1.38 scaling" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1750273/+attachment/5057885/+files/1.38x.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750273 Title: UI scaling broken after last update in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1750273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750273] [NEW] UI scaling broken after last update in Xenial
Public bug reported: After an update that went live a few days ago, Unity's fractional scaling is misbehaving for some scaling values. It's something I had already noticed in Unity that shipped in Zesty some time ago. With this update, this now affects Xenial as well. For scaling values up to 1.38x it behaves as it should, but when the scaling hits the 1.5x mark, the UI elements resize as though I had selected a much higher scaling. Text resizes to 1.5x, but the UI itself scales to a much higher number. It wasn't like that until this last round of updates to Xenial. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.5+16.04.20171201.3 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Feb 18 15:08:20 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed bbswitch, 0.8, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0781] InstallationDate: Installed on 2017-07-28 (205 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7460 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.2 dmi.board.name: 0V736W dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.2:bd12/13/2017:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn0V736W:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7460 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750273 Title: UI scaling broken after last update in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1750273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750273] Re: UI scaling broken after last update in Xenial
Adding two screenshots highlighting the issue. ** Attachment added: "Screenshot of how Files looks like at 1.5 scaling" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1750273/+attachment/5057886/+files/1.5x.png ** Description changed: After an update that went live a few days ago, Unity's fractional scaling is misbehaving for some scaling values. It's something I had already noticed in Unity that shipped in Zesty some time ago. With this update, this now affects Xenial as well. For scaling values up to 1.38x it behaves as it should, but when the scaling hits the 1.5x mark, the UI elements resize as though I had - selected 2x scaling. Text resizes to 1.5x, but the UI itself scales to - 2x. + selected a much higher scaling. Text resizes to 1.5x, but the UI itself + scales to a much higher number. It wasn't like that until this last round of updates to Xenial. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.5+16.04.20171201.3 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Feb 18 15:08:20 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: - bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed - bbswitch, 0.8, 4.4.0-112-generic, x86_64: installed - nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed - nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed + bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed + bbswitch, 0.8, 4.4.0-112-generic, x86_64: installed + nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed + nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed GraphicsCard: - Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:0781] + Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:0781] InstallationDate: Installed on 2017-07-28 (205 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc. - Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller - Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc. + Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller + Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7460 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.2 dmi.board.name: 0V736W dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.2:bd12/13/2017:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn0V736W:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7460 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750273 Title: UI scaling broken after last update in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1750273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
** 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/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
** Tags added: verification-done-xenial ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
I've been testing version 1.157.16 from xenial-proposed for the last few hours. It successfully fixes the issue, and I can confirm that the correct firmware is loaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
@Seth You might have missed it (there's lots of text here, so it's more than ok :-) ) but I already had said in one comment here that it affects Artful as well (and Bionic, of course, but that is still in development). Pretty much it affects any distro using a kernel newer than or equal to 4.12. I've posted a report from Debian here and I've found mentions of this bug in Arch as well. The original question on askubuntu that led me to report the bug (although I had experienced it in Xenial) was from a user running Artful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
@Seth All good after a night long connected without interruptions and/or slowdowns. It's working great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
@Seth I just confirmed that it does fix the bug. I forced the re-installation of version 1.157.14 and rebooted. I checked that the old firmware was loaded and that the files in the /lib/firmware/ath10k/QCA6174/hw3.0/ folder were indeed the ones that came with the old package. Then I let the bug happen, which it did. Then I downloaded your package and installed it with dpkg. Rebooted, checked that the new firmware was loaded, checked the files and it's been 5 group rekeyings without any issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
AceLan, you can disconsider the last comment. I've found a way to use mIRC on the web browser and I've contacted the Kernel team there. They're already looking into this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
Hi there, AceLan, I've subscribed you to this bug because of 1) I've noticed you reported another bug, which had a fix submitted to xenial-proposed a few days ago, and I'm looking for some guidance here on how to have this bug fixed ASAP (even by me, if it means creating and submitting a new package myself or something like that, as per Ubuntu's documentation on fixing bugs) and 2) You're probably affected by it, if you own a QCA6174 and you're using a kernel later than 4.12. I'd consider this bug a high priority one because it directly affects users (and in a very significant way), it's been already fixed in upstream since October 2017 and porting the fix to Ubuntu would be trivial, I guess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
While this isn't fixed in Ubuntu, users can fix this issue with the following command: sudo wget https://github.com/kvalo/ath10k- firmware/raw/master/QCA6174/hw3.0/4.4.1/firmware-6.bin_WLAN.RM.4.4.1-00051-QCARMSWP-1 -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin ** Description changed: After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my WiFi would stop working after every 20 minutes or so. The problem initially seems related to some DNS services crashing because of what happend in browsers and other software that usually rely on DNS but I've noticed I couldn't ping my router and other local devices for which I knew the IP addresses. The connection is still presented as being connected, but it just doesn't work. After googling a lot, I came across this question on askubuntu.com https://askubuntu.com/questions/967355/wifi-unstable-after-17-10-update Which led me to this bug report on Debian's bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184 Which led me to this bug in upstream: http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html I've tested the proposed fixes myself and I can confirm they work. What causes the WiFi to stop working is a bug related to the group rekeying routines. It seems it only happens in >4.12 kernels, hence why I've only had problems after 4.13 was pushed as the current rolling HWE kernel for 16.04.3. kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1 of the firmware-6.bin file, which is the current one present in upstream. - Updating the firmware-6.bin and board-2.bin to any version equal or - later than that fixes the issue completely. + Updating the firmware-6.bin (and board-2.bin, optionally) to any version + equal or later than that fixes the issue completely. - SRU Justification: [Impact] - Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, silently stops working after the second group rekeying, which is usually few minutes after the user has connected to a WiFi network. The connection status remains unchanged but there's no connectivity at all. This effectively disconnects the user without notifying it of what's occurred. + Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, silently stops working after the second group rekeying, which is usually few minutes after the user has connected to a WiFi network. The connection status remains unchanged but there's no connectivity at all. This effectively disconnects the user without notifying it of what's occurred. Additionally, this happens for the only HWE kernel that's been patched against the recent Meltdown vulnerability, leaving the user without the option of using a recent kernel and a secure kernel at the same time. [Test Case] - After applying the required firmwares, check if the connectivity is unaffected after the second group rekeying, which can be checked with + After applying the required firmwares, check if the connectivity is unaffected after the second group rekeying, which can be checked with $ cat /var/log/syslog | grep wpa_.*rekeying + + [How to fix it] + + Update the firmware-6.bin file to version WLAN.RM.4.4.1-00051-QCARMSWP-1 + or later. [Regression Potential] The new firmware overwrites the old one, but since it's been in upstream since October 2017, it should be good. - Description: Ubuntu 16.04.3 LTS Release: 16.04 linux-firmware: Instalado: 1.157.14 Candidato: 1.157.14 Tabela de versão: *** 1.157.14 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 1.157 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
It's important to notice that this bugs affects any post-4.12 kernel, so it's present in both 16.04.3 HWE and 17.10 versions. ** Description changed: After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my WiFi would stop working after every 20 minutes or so. The problem initially seems related to some DNS services crashing because of what happend in browsers and other software that usually rely on DNS but I've noticed I couldn't ping my router and other local devices for which I knew the IP addresses. The connection is still presented as being connected, but it just doesn't work. After googling a lot, I came across this question on askubuntu.com https://askubuntu.com/questions/967355/wifi-unstable-after-17-10-update - While led me to this bug report on Debian's bug tracker: + Which led me to this bug report on Debian's bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184 Which led me to this bug in upstream: http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html I've tested the proposed fixes myself and I can confirm they work. What causes the WiFi to stop working is a bug related to the group - rekeying routines. Updating the board-2.bin and firmware-6.bin from - kvalo's git repository for version RM4.4.1 has worked for me and for - other users as well. + rekeying routines. - It seems it only happend in >4.12 kernels, hence why I've only had + It seems it only happens in >4.12 kernels, hence why I've only had problems after 4.13 was pushed as the current rolling HWE kernel for 16.04.3. - The files were fetched from https://github.com/kvalo/ath10k-firmware as - of this date, as of commit 35d8642f452827b955470de4ac997ffe906a6f17, - with the following sha256 sums: + kvalo made the fix available in version WLAN.RM.4.4.1-00051-QCARMSWP-1 + of the firmware-6.bin file, which is the current one present in + upstream. - 8fcc6b96c1895bc227c3caf0bd04b23d0292f8f919e819e4e025e29ef4b44d8e board-2.bin - 30fc3db3af9ba9f3b88e523fe39b715826a31738d48ca01a3fad0d14f7e46e20 firmware-6.bin_WLAN.RM.4.4.1-00065-QCARMSWP-1 + Updating the firmware-6.bin and board-2.bin to any version equal or + later than that fixes the issue completely. - It seems firmware-6.bin_WLAN.RM.4.4.1-00079-QCARMSWPZ-1 (sha256sum - 5554d6aa0de07394938a0094bae725ed24d4ceee3b38c849b4099a496ec50b48) works - as well. + - + + SRU Justification: + [Impact] + Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter, available in numerous laptops, including ones that ship with Ubuntu 16.04 pre-installed, silently stops working after the second group rekeying, which is usually few minutes after the user has connected to a WiFi network. The connection status remains unchanged but there's no connectivity at all. This effectively disconnects the user without notifying it of what's occurred. + + Additionally, this happens for the only HWE kernel that's been patched + against the recent Meltdown vulnerability, leaving the user without the + option of using a recent kernel and a secure kernel at the same time. + + [Test Case] + After applying the required firmwares, check if the connectivity is unaffected after the second group rekeying, which can be checked with + + $ cat /var/log/syslog | grep wpa_.*rekeying + + [Regression Potential] + The new firmware overwrites the old one, but since it's been in upstream since October 2017, it should be good. - Description: Ubuntu 16.04.3 LTS Release: 16.04 linux-firmware: - Instalado: 1.157.14 - Candidato: 1.157.14 - Tabela de versão: - *** 1.157.14 500 - 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages - 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 Packages - 100 /var/lib/dpkg/status - 1.157 500 - 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages + Instalado: 1.157.14 + Candidato: 1.157.14 + Tabela de versão: + *** 1.157.14 500 + 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages + 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 Packages + 100 /var/lib/dpkg/status + 1.157 500 + 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages -- You received this bug notification because you are a member of
[Bug 1743279] Re: QCA6174 stops working on newer kernels after second group rekeying
Reading https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/ath10k/QCA6174/hw3.0/firmware-6.bin?id=96a7402d4172f4786ee93dd9f7cb3f76e1a8025e it seems the fix for this particular issue was made available in version WLAN.RM.4.4.1-00051-QCARMSWP-1. Updating board-2.bin and firmware-6.bin as in what's available in the upstream for firmware-linux right now should fix 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/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743279] [NEW] QCA6174 stops working on newer kernels after second group rekeying
Public bug reported: After upgrading to the 4.13 kernel on Ubuntu 16.04.3, I've noticed my WiFi would stop working after every 20 minutes or so. The problem initially seems related to some DNS services crashing because of what happend in browsers and other software that usually rely on DNS but I've noticed I couldn't ping my router and other local devices for which I knew the IP addresses. The connection is still presented as being connected, but it just doesn't work. After googling a lot, I came across this question on askubuntu.com https://askubuntu.com/questions/967355/wifi-unstable-after-17-10-update While led me to this bug report on Debian's bug tracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879184 Which led me to this bug in upstream: http://lists.infradead.org/pipermail/ath10k/2017-September/010088.html I've tested the proposed fixes myself and I can confirm they work. What causes the WiFi to stop working is a bug related to the group rekeying routines. Updating the board-2.bin and firmware-6.bin from kvalo's git repository for version RM4.4.1 has worked for me and for other users as well. It seems it only happend in >4.12 kernels, hence why I've only had problems after 4.13 was pushed as the current rolling HWE kernel for 16.04.3. The files were fetched from https://github.com/kvalo/ath10k-firmware as of this date, as of commit 35d8642f452827b955470de4ac997ffe906a6f17, with the following sha256 sums: 8fcc6b96c1895bc227c3caf0bd04b23d0292f8f919e819e4e025e29ef4b44d8e board-2.bin 30fc3db3af9ba9f3b88e523fe39b715826a31738d48ca01a3fad0d14f7e46e20 firmware-6.bin_WLAN.RM.4.4.1-00065-QCARMSWP-1 It seems firmware-6.bin_WLAN.RM.4.4.1-00079-QCARMSWPZ-1 (sha256sum 5554d6aa0de07394938a0094bae725ed24d4ceee3b38c849b4099a496ec50b48) works as well. - Description:Ubuntu 16.04.3 LTS Release:16.04 linux-firmware: Instalado: 1.157.14 Candidato: 1.157.14 Tabela de versão: *** 1.157.14 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main i386 Packages 100 /var/lib/dpkg/status 1.157 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: ath10k qca6174 rekeying -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743279 Title: QCA6174 stops working on newer kernels after second group rekeying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1743279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
Disabling Powersave in NetworkManager did it for me. I was barely getting 300kB/s on certain workloads on my 2.4GHz network whereas I could get full speed on my 5GHz one. By disabling the power management in NetworkManager, I got full speed all the time and I haven't really noticed any decrease in power consumption. Running Ubuntu 16.04.2, Kernel 4.10 (HWE branch). Stock installation done just a few minutes ago. 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Doing the following will disable power saving in Network Manager by default: $ sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04
Hello Henryque, The scenario you describe (manually installing the NVIDIA drivers from their website) is not within the scope of this request/bug, as far as I know and having to install the 370 series is unrelated to this request/bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619306 Title: SRU request: Include the 367 driver in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533480] Re: banshee stops respondiing during media import
I can confirm that disabling the plugins solves the problem, but I don't know which one is causing the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533480 Title: banshee stops respondiing during media import To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1533480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625430] [NEW] When importing media, Rhythmbox fails to update track list and display text with artifacts
Public bug reported: When I was importing my media library to Rhythmbox, I noticed there were several repeated songs. After examining more closely, I observed the songs were being added correctly, but the track list wasn't being updated and it was displaying some weird characters. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rhythmbox 3.3-1ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 19 23:53:12 2016 InstallationDate: Installed on 2016-09-07 (13 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Screenshot showing the issue" https://bugs.launchpad.net/bugs/1625430/+attachment/4744028/+files/Captura%20de%20tela%20de%202016-09-19%2023-54-04.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625430 Title: When importing media, Rhythmbox fails to update track list and display text with artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1625430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624211] [NEW] Network-manager randomly won't recognize wireless card after resuming from sleep or hibernation or when disabling/reenabling the card
Public bug reported: When resuming from sleep or coming out of hibernation and sometimes when disabing and reenabling the wireless card (using Fn + the corresponding key), network-manager will stop recognizing that there's a wireless card in my laptop. The bluetooth applet and the card themselves still work. I can still connect to the same network it was connected before putting it to sleep/hibernate (because it's a known network and it does so automatically) but network-manager won't display anything regarding me having a wireless card, displaying the icon and information I would expect if I were connected using an ethernet cable. A workaround consists in restarting the network-manager service using systemctl sudo service network-manager restart or sudo systemctl restart network-manager.service The system is a Dell Vostro 5470 running a fresh installation of Ubuntu 16.04.1. If I recall correctly, this also happened with Ubuntu 14.04.4 too. BIOS version is A12 (the latest). I've seen several people with problems like this one that were solved by restarting network-manager (a quick Googling shows a handful of such cases). This can be a huge turn off for a newcomer. Some people also suggested creating a systemd service to restart the network-manager service when resuming, etc. but since this bug also occurs when disabling/reenabling the card, it might have another cause that's unrelated to resuming from sleep. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 16 01:26:01 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-10 (6 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp8s0 proto static metric 600 169.254.0.0/16 dev wlp8s0 scope link metric 1000 192.168.1.0/24 dev wlp8s0 proto kernel scope link src 192.168.1.248 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp8s0 wifi connected/org/freedesktop/NetworkManager/Devices/0 That's no moon! 1 2a59043a-02a4-4da0-ab5c-3c89c52bd15f /org/freedesktop/NetworkManager/ActiveConnection/1 enp7s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug network-manager wireless xenial ** Attachment added: "This is what happens." https://bugs.launchpad.net/bugs/1624211/+attachment/4741747/+files/Espa%C3%A7o%20de%20Trabalho%201_005.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624211 Title: Network-manager randomly won't recognize wireless card after resuming from sleep or hibernation or when disabling/reenabling the card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1624211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577942] Re: package ubuntu-drivers-common 1:0.4.17 failed to install/upgrade: pacote ubuntu-drivers-common não está pronto para configuração não posso configurar (estado atual 'half-installed')
You may try to run sudo apt-get -f install which sometimes corrects this kind of thing. May I ask you why you're using a 32-bit install? The 64-bit became the recommended one some time ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577942 Title: package ubuntu-drivers-common 1:0.4.17 failed to install/upgrade: pacote ubuntu-drivers-common não está pronto para configuração não posso configurar (estado atual 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1577942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622832] Re: package nvidia-367 367.44-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
This does not happen in Ubuntu 16.04.1 with the standard 4.4 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622832 Title: package nvidia-367 367.44-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1622832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04
** Attachment added: "X.org log after updating to ubuntu-drivers-common from xenial-proposed" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741696/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619306 Title: SRU request: Include the 367 driver in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04
I can confirm that indee, installing newer drivers will cause the dGPU to stay on. ** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741692/+files/gpu-manager.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619306 Title: SRU request: Include the 367 driver in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741693/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619306 Title: SRU request: Include the 367 driver in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04
** Attachment added: "GPU Manager log after installing the ubuntu-drivers-common from xenial-proposed" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741695/+files/gpu-manager.log ** Attachment removed: "X.org log after installing the ubuntu-drivers-common from xenial-proposed" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741695/+files/gpu-manager.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619306 Title: SRU request: Include the 367 driver in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619306] Re: SRU request: Include the 367 driver in Ubuntu 16.04
I installed this package from xenial-proposed and rebooted. The nVidia card was shut down correctly. ** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306/+attachment/4741694/+files/gpu-manager.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619306 Title: SRU request: Include the 367 driver in Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1619306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580241] [NEW] ubuntu-make android android-sdk does not set ANDROID_HOME
Public bug reported: Using $ umake android android-sdk to install the Android SDK sets the following variables in .profile: # Ubuntu make installation of Android SDK PATH=$ANDROID_HOME/tools:$ANDROID_HOME/platform-tools:$PATH But it does not set ANDROID_HOME anywhere. Therefore, the SDK does not work. I had to add ANDROID_HOME=$HOME/.local/share/umake/android/android-sdk to my .profile in order for it to work. Problem Type: Bug Distro Release: Ubuntu 16.04 Package: ubuntu-make 16.02.1 Architecture: amd64 ** Affects: ubuntu-make (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/1580241 Title: ubuntu-make android android-sdk does not set ANDROID_HOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-make/+bug/1580241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114025] Re: Problem with wine preloader: Warning: failed to reserve range 00000000-60000000
Have someone tried to disable apparmor? It started to happen in Feisty, isn't it? -- Problem with wine preloader: Warning: failed to reserve range -6000 https://bugs.launchpad.net/bugs/114025 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114025] Re: Problem with wine preloader: Warning: failed to reserve range 00000000-60000000
Forget abou that... I couldn't try because AppArmor in builtin in HArdy, but changing the value in /etc/sysctl.conf seems to be the only alternative -- Problem with wine preloader: Warning: failed to reserve range -6000 https://bugs.launchpad.net/bugs/114025 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
