[Bug 1805088] Re: iwlwifi fails to work on 16 or more logical CPUs machines
There isn't yet a new kernel in *bionic* -proposed to solve this issue, so I can't test it. I have verified that building the 4.15.0-42.45 kernel with the patch (https://patchwork.kernel.org/patch/10382693/) applied fixes wifi for 16+ threaded systems 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/1805088 Title: iwlwifi fails to work on 16 or more logical CPUs machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805088] Re: iwlwifi fails to work on 16 or more logical CPUs machines
I encountered this iwlwifi failure while testing the Intel 9260 with the AMD Ryzen 7 2700x (8 core, 16 thread). By bisecting the kernel, I was able to narrow it down to the same commit. I can also verify that setting maxcpus=15, fixes wifi (at the cost of performance). This is a really important fix for certain System76 products. We'd really like to see it backported so Ubuntu works without compromises on our machines. I'm happy to test any testing or proposed kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805088 Title: iwlwifi fails to work on 16 or more logical CPUs machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766555] Re: openscad package missing from 18.04
Can we still try to get openscad released in Ubuntu for bionic? If it's going to take time to fix the arm failure, perhaps at least release it for the architectures that do build, especially amd64, which is what most openscad users will have. As a stopgap for our users, I've had to put builds in our ppas, but it would look much better to have openscad back in Ubuntu proper. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766555 Title: openscad package missing from 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openscad/+bug/1766555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
I can reproduce the issue with ethernet failing on the r8169 on resume from suspend with the current kernel. This is a regression since a previous kernel on 18.04 since the symptoms occur after installing updates. I can also confirm that Kai's kernel seems to fix ethernet after suspend on at least one of our products. Will do more testing, but this would be very good to get into the next bionic kernel update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738579] [NEW] package openjdk-10-jre-headless (not installed) failed to install/upgrade: trying to overwrite '/usr/share/apport/package-hooks/source_openjdk-9.py', which is also in package openj
Public bug reported: During install of openjdk-9-* and openjdk-10-* failure occured ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openjdk-10-jre-headless (not installed) ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu4 Architecture: amd64 Date: Fri Dec 15 20:51:10 2017 DuplicateSignature: package:openjdk-10-jre-headless:(not installed) Unpacking openjdk-10-jre-headless:amd64 (10~32-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-BYL08R/001-openjdk-10-jre-headless_10~32-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/apport/package-hooks/source_openjdk-9.py', which is also in package openjdk-9-jre-headless:amd64 9.0.1+11-1 ErrorMessage: trying to overwrite '/usr/share/apport/package-hooks/source_openjdk-9.py', which is also in package openjdk-9-jre-headless:amd64 9.0.1+11-1 InstallationDate: Installed on 2017-12-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215) Python3Details: /usr/bin/python3.6, Python 3.6.4rc1, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: openjdk-10 Title: package openjdk-10-jre-headless (not installed) failed to install/upgrade: trying to overwrite '/usr/share/apport/package-hooks/source_openjdk-9.py', which is also in package openjdk-9-jre-headless:amd64 9.0.1+11-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openjdk-10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738579 Title: package openjdk-10-jre-headless (not installed) failed to install/upgrade: trying to overwrite '/usr/share/apport/package- hooks/source_openjdk-9.py', which is also in package openjdk-9-jre- headless:amd64 9.0.1+11-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-10/+bug/1738579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724024] Re: can't set usable scale for hidpi internal display if when using external display less than 1600x1200
Mutter 3.26.2-0ubuntu0.1 fixes this bug. The fullscreen unredirection change is also notably present, which is probably good except for the regression with fullscreen video in Firefox (eg youtube). This could probably be fixed via a future patch in Mutter or Gnome Shell to exclude fullscreen windows of problematic applications from being unredirected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724024 Title: can't set usable scale for hidpi internal display if when using external display less than 1600x1200 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725821] Re: mutter 3.26 doesn't properly unredirect windows
This fix breaks video playback in at least Firefox. After installing the test package, playing fullscreen video in Firefox results in lots of tearing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725821 Title: mutter 3.26 doesn't properly unredirect windows To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724024] Re: can't set usable scale for hidpi internal display if when using external display less than 1600x1200
** Patch added: "updated patch to apply cleanly to mutter in artful" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1724024/+attachment/4973082/+files/monitor-managerxrandr-Use-a-single-supported-scale.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724024 Title: can't set usable scale for hidpi internal display if when using external display less than 1600x1200 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724024] [NEW] can't set usable scale for hidpi internal display if when using external display less than 1600x1200
Public bug reported: [Impact] Users on X11 are unable to set sane configurations for mixed hidpi/lowdpi multi-monitor setups. A limitation in Mutter prevents gnome-control-center (and any other users of the dbus api or monitors.xml) from changing even unrelated display settings unless 1x scaling factor is chosen. There is no user-facing reason why, the settings just won't apply. This applies to X11 and not Wayland. All NVIDIA users and some others who require X for the time being are affected when using mixed-dpi setups. This especially affects System76 customers, since the patch is required for the automatic multi-monitor setup to work. [Description] When plugging in an external 1920 x 1080 monitor to a laptop with a hipdi screen (e.g. 13" 3200x1800), mutter automatically configures the two displays next to each other and keeps the 2x scale factor. If the user sets the scale factor (using the control center, the dbus api, or the monitors.xml file), they will be stuck at 1x and everything will be tiny on the internal display. It's not possible to set the scale factor back to 2x, and any attempts to do so will result in mutter complaining that "Logical monitor scales must be identical" or "Scale 2 not valid for resolution 1920x1080". The user can't even move the external display from the right of the internal to the left without selecting 1x scaling. The configuration simply won't apply. Mutter prevents applying a scale to a logical display if it would result in a logical resolution less than 800x600. On X11, all displays must have the same scaling factor. The primary reason to prevent setting a too-high a scale factor is that a user may get stuck in an unusable state. The proposed patch, enables Mutter to apply a given scale factor if at least one display supports it. [Test Case] 1) Install Ubuntu 17.10 on a laptop with a hidpi display. By default, Gnome should be correctly scaled at 2x. If you have previously configured this setup, you will have to delete the monitors.xml file and reboot. 2) Plug in a 1920x1080 monitor. At this point, both monitors should be scaled at 2x because Mutter has not received a request to change the display configuration. 3) Now open gnome-control center and attempt to change a display setting like moving the external 1920x1080 display from the right to the left side of the internal display. This should be a valid thing to do. However, there will be no apply button. 4) Now, set the scale factor from 2x to 1x. The apply button will now show. Clicking apply will make the external display the right scale, but everything will be very tiny on the internal display. With the patch, you should be able to make changes without switching from 2x to 1x. [Regression Potential] Potential regressions are likely to manifest in the checking of display scale factors. It's possible that corner cases exist where a user might be able to apply a scale factor that's too big/small for their use. However, the current situation is already a regression from Ubuntu 17.04 that prevents proper monitor configuration. [Upstream Bug] https://bugzilla.gnome.org/show_bug.cgi?id=788901 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: hidpi multi-monitor mutter system76 ** Patch added: "monitor-managerxrandr-Use-a-single-supported-scale.patch" https://bugs.launchpad.net/bugs/1724024/+attachment/4972934/+files/monitor-managerxrandr-Use-a-single-supported-scale.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724024 Title: can't set usable scale for hidpi internal display if when using external display less than 1600x1200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1724024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: intel-microcode is out of date, version 20170511 fixes errata on 6th and 7th generation platforms
The 20170707 version would be ideal to SRU for Xenial (and Zesty) since it fixes the hyperthreading defect on Skylake, Skylake-X, and Kabylake. The Kabylake fix is especially important. There is a lot of demand from users for a fix, and bios updates really aren't an ideal way to deliver it. -- 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 20170511 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
[Bug 1686815] Re: Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04
I tested the package on a new system that hadn't gotten the new firmware installed yet. Bluetooth works after installing the test package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686815 Title: Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1686815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687901] Re: i915 driver makes linux crash
@Joseph Salisbury, Nope, haven't found the commit yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687901 Title: i915 driver makes linux crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687901] Re: i915 driver makes linux crash
The underlying problem appears to be the same (identical errors reported), but the symptoms can be different. The hardware I'm testing doesn't crash completely. Instead X creates a non-existent DisplayPort monitor with 1024x768 resolution and 0x0 physical size (on hardware without any DisplayPort ports). While less catastrophic than alex-garel's symptoms, it's still really confusing for the user to lose their mouse and windows to the ether of an impossible screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687901 Title: i915 driver makes linux crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687901] Re: i915 driver makes linux crash
I can confirm this bug on both Ubuntu 16.04 and 17.04 on Intel Kabylake i7-7500U with Sunrise Point chipset. The 4.11 kernel you suggested fixes the problem, so it is fixed upstream. We should try and backport the fix into at least 16.04 and 17.04. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-fixed-upstream xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687901 Title: i915 driver makes linux crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686815] [NEW] Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04
Public bug reported: Bluetooth doesn't work in Ubuntu 16.04 on systems with Intel 8265 wireless modules that haven't yet had firmware loaded onto them. dmesg reports the following: Bluetooth: hci0: Direct firmware load for intel/ibt-12-16.sfi failed with error -2 This could be difficult for many people to reproduce, since installing a later version of Ubuntu once will load the necessary firmware, which will persist through reinstalling the operating system. So installing Ubuntu 17.04 just once, will leave Bluetooth in a working state forever. I was able to consistently produce the issue on a *brand new* Kabylake Meerkat 3. With Ubuntu 16.04.2, bluetooth didn't work. I copied the ibt-12-16.sfi and ibt-12-16.ddc into /lib/firmware/intel and rebooted. After this point, Bluetooth worked (and continued to work after reinstalling Ubuntu 16.04.2 and *not* copying the firmware files again). ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686815 Title: Missing Bluetooth firmware for intel 8265 on Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1686815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22
Verified the 1.164.1 package in proposed. It fixes this bug. ** Tags removed: wifi ** Tags added: verification-donewifi ** Tags removed: verification-donewifi ** Tags added: verification-done wifi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647826 Title: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631191] Re: Display backlight won't turn on after screen timeout
Robert and Troy: I believe you are experiencing a different issue. Do you both have an Oryx with a GTX 1060? If so, this is a known issue, which we issued a workaround for a few days ago. Try updating to the latest system76-driver-nvidia. That should at least prevent the need for a restart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631191 Title: Display backlight won't turn on after screen timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1631191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622686] Re: double header in 16.10
Did some quick testing with the 0.6.10.1 package in -proposed, and can verify that it fixes 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/1622686 Title: double header in 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
Did some quick testing with the 0.6.10.1 package in -proposed, and can verify that it fixes 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/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
Did some quick testing with the 0.6.11.1 package in -proposed, and can verify that it fixes 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/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622686] Re: double header in 16.10
Did some quick testing with the 0.6.11.1 package in -proposed, and can verify that it fixes this bug. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622686 Title: double header in 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646574] Re: Mouse cursor invisible or does not move
Initial testing shows that the test kernel resolves the issue as well. I will continue to test to check for regressions, but I think we have a solution here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646574 Title: Mouse cursor invisible or does not move To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646574] Re: Mouse cursor invisible or does not move
This bug affects a number of different systems with Nvidia 10 Series (Pascal) GPUs. When using Nouveau, the cursor is drawn in the top left corner of the screen and appears to be stuck there despite the user being able to move around and click anywhere. While it's possible to work around this bug by installing the proprietary Nvidia driver, this bug is a huge hassle when installing from the standard iso. (Also when the proprietary driver breaks or is removed for some reason) The Nouveau developers report that this is fixed in Kernel 4.10 and pointed to this commit as solving the issue: https://github.com/skeggsb/nouveau/commit/b94985176af536ab752a63baecdee263ffcce63f With the two preceding commits being needed as well: https://github.com/skeggsb/nouveau/commit/0d874f550816a6d7038658c3ec78c992e40c132f https://github.com/skeggsb/nouveau/commit/88a1b714678ad1f5bda441052383e70a9d52f100 Still need to test these commits, but they look promising. With 16.04.2 bringing in the 4.8 kernel, which is affected by this bug, it would be nice to have these cherry picked to make sure the ISO works with modern NVIDIA GPUs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646574 Title: Mouse cursor invisible or does not move To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1646574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622686] Re: double header in 16.10
** Description changed: - STEPS: - 1. grab the latest iso - 2. Note the header during install + [Impact] - EXPECTED: - Icon on one header + During install and oem-firstboot, the header bar at the top of the + screen in Ubiquity is twice as tall as it should be on hidpi screens + (looking like two normal sized header bars stacked on top of each + other), and the blue a11y icon is double sized. - ACTUAL: - I believe the a11y icon is double sized and forces a double header. see photo + This looks obviously incorrect and ugly and makes a bad first impression + on users installing Ubuntu on a hidpi laptop or customers of Ubuntu OEMs + booting new machines for the first time. Arstechnica commented + negatively on this in their review of Dell's XPS 13: + http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still- + delivers-linux-now-embraces-svelte-hardware/ - /!\ Seem to be a hidpi only issue I see it on xps13 but not on other - installs + Users of the Dell XPS 13 are affected as well as users of other brands + of laptops with hidpi screens. System76 is temporarily carrying a + patched version of Humanity to work around this bug. + + The a11y icon is double-sized because the version of Humanity shipping + in Ubuntu doesn't support @2 hidpi scaling, which results in the header + bar doubling its height. Because the header bar is drawn with + CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars + stacked one on top of the other. The fix to the Humanity icon theme + adds @2 hidpi support, which shrinks the icon and restores the header + bar to its normal height. + + + [Test Case] + ISO install: + 1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer with a hidpi screen. + 2. Note the double-sized header and icon during install. + - Using an iso with a fixed version of Humanity, the header and icon should look normal. + + OEM-Firstboot: + 1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi screen. + 2. After installing, click the launcher icon to "Prepare for shipping to the end user" and reboot. + 3. During oem-firstboot, note the double-sized header and icon during install. + - To test the fix, install a fixed version of humanity before preparing the system for the end user. + + + [Regression Potential] + + This patch affects the look of anything using the Humanity icon set. + The look of Nautilus, and many other GTK apps will be affected. This is + not a regression but fixes another bug and resolves a discrepancy + between rendering of icons on hidpi screens vs lowdpi screens. + + The biggest risk for regression comes from the off chance that there is + an error or omission in the index.theme files. Comparing icons on a + broad range of applications and systems should catch this class of + issues. If any issues with icons are found, check there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622686 Title: double header in 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
** Description changed: - Because Humanity doesn't have support for @2x icons, some icons are - displayed too big. This is a general issue, but is easily noticed in a - few examples below. + [Impact] - In Nautilus, the icons are much too big on hidpi screends in 16.04, - while in 16.10 the icons are the same size but use different icons with - much thinner strokes. The difference is also visible in icons on the - Desktop. + Humanity icons are sometimes displayed too big on hidpi screens in + 16.04. On both 16.04 and 16.10, different icons are used on hidpi + screens than non-hidpi screens. Sometimes the icons look similar but + with much thinner strokes, while other times an icon with a different + metaphor is used. Users on hidpi screens will notice that icons in + applications like Nautilus, Transmission, etc. look different (not just + clearer) on hidpi screens. - In Transmission, the "Open" button in the toolbar uses an icon with a - different metaphor on hidpi screens (an up arrow emerging from a folder) - than on lowdpi screens (a sheet of paper emerging from a folder). + The fix here is to add support for @2 icons to the Humanity theme by + adding symbolic links for @2 icons and updating the index.theme files + accordingly. - After adding symbolic links for @2x icons and updating the index.theme - files accordingly fixes these issues. + We should backport the fix to 16.04 and 16.10, so Humanity icons look + the same on hidpi screens as non-hidpi screens. + + + [Test Case] + + Here are a few test cases: + 1) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi screen are much larger. (This applies to icons on the desktop as well.) + -The fix should result in icons being the same size on both hidpi and lowdpi. + + 2) Using a computer with a hidpi screen and one with a lowdpi screen running Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). + - The fix should result in the "sheet of paper emerging from a folder" icon being used here on both hidpi and lowdpi screens. + + 3) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons look sutbly different. The strokes in icons on the hidpi screen will be visibly thinner on the hidpi screen because icons for bigger scale are used (say 48 on hidpi instead of 24) rather than rendering the original size icon at a larger resolution. + - The fix should result in icons that have the same stroke width on hidpi and lowdpi screens. The icons will still be sharper on the hidpi screen, but the lines won't be thinner. + + + [Regression Potential] + + The patch is designed for compatibility where @2 support is not + available by listing the @2 directories under "ScaledDirectories=" + rather than "Directories=". However it's possible there could be other + kinds of issues not found in testing. If there are any omissions or + errors in the index.theme, this could cause rendering issues for some + categories of icons. Comparing icons on a broad range of applications + and systems should catch this class of issues. + + Hidpi users may find that their machine looks different after the update + than it did before. This is not a regression, but a fix to a bug that's + been present all along. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622686] Re: double header in 16.10
** Branch linked: lp:~dmj726/humanity/hidpi-2x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622686 Title: double header in 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
** Branch linked: lp:~dmj726/humanity/hidpi-2x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
Left side: humanity without @2x support Right side: humanity with @2x support (looks just like lowdpi but crisper) ** Description changed: Because Humanity doesn't have support for @2x icons, some icons are displayed too big. This is a general issue, but is easily noticed in a few examples below. - In nautilus, the default window size only fits 4 columns of icons on a - hidpi screen, compared with 7 on a non-hidpi screen. + In Nautilus, the icons are much too big on hidpi screends in 16.04, + while in 16.10 the icons are the same size but use different icons with + much thinner strokes. The difference is also visible in icons on the + Desktop. In Transmission, the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). After adding symbolic links for @2x icons and updating the index.theme files accordingly fixes these issues. ** Attachment added: "humanity hidpi xenial.png" https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+attachment/4806440/+files/humanity%20hidpi%20xenial.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657863] [NEW] Icons are too big or the wrong icon is shown on hidpi screens
Public bug reported: Because Humanity doesn't have support for @2x icons, some icons are displayed too big. This is a general issue, but is easily noticed in a few examples below. In nautilus, the default window size only fits 4 columns of icons on a hidpi screen, compared with 7 on a non-hidpi screen. In Transmission, the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). After adding symbolic links for @2x icons and updating the index.theme files accordingly fixes these issues. ** Affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: hidpi humanity icons nautilus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622686] Re: double header in 16.10
So, I've been working on adding hidpi support in the Humanity icon theme today, and noticed that the blue accessibility icon looks like one of the icons in Humanity. After installing my updated Humanity icon (with @2x support added) the blue accessibility icon is the correct size, and the panel is no longer double height. The icon was simply too big and the panel was resizing to match, so updating humanity to support @2x icons should fix the incorrect panel height. However, Matheiu's code does improve the appearance of the bottom pixels of the panel. Previously, there was a small band at the bottom of the panel that repeated the much lighter shade of the top of the panel. With the patch, that band uses the darker color immediately above. You can see the difference in the attached image (with the @2x humanity theme in both cases). ** Attachment added: "ubiquity panel cairo extend mode patch.jpg" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622686/+attachment/4805542/+files/ubiquity%20panel%20cairo%20extend%20mode%20patch.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622686 Title: double header in 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622686] Re: double header in 16.10
Her is what the above changes do on a hidpi screen. ** Attachment added: "ubiquity panel cairo extend mode patch double height.jpg" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622686/+attachment/4805541/+files/ubiquity%20panel%20cairo%20extend%20mode%20patch%20double%20height.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622686 Title: double header in 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622686] Re: double header in 16.10
I tested Mathieu's patch (relavant portion attached here), and it definitely provides an improvement, but doesn't fully fix the bug. Instead of repeating, the bottom half of the panel is dark and flat. ** Patch added: "cairo_extend_pad-snippet.patch" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622686/+attachment/4805540/+files/cairo_extend_pad-snippet.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622686 Title: double header in 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1622686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631191] Re: Display backlight won't turn on after screen timeout
Thanks for confirming the fix! Just to clarify, the nvidia 375.26 driver is not in the Ubuntu repositories yet. We packaged it in the System76 ppa so our customers get the fixes in a timely manner. Since Tuesday, running updates should fix this issue for all affected System76 customers. For people wanting to use the 375.26 driver for non-System76 machines, I recommend using the Graphics Drivers Team ppa. Thank you all for adding your comments. This really helped in getting it fixed in the nvidia driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631191 Title: Display backlight won't turn on after screen timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1631191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649736] Re: unity picks poor hidpi scale factor defaults
Yes, I had a momentary brain glitch. 1.5x is a better place to put the sudden jump in size than 2x, so yes, your patch is a good improvement, and with both patches I think we'll have a good solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649736 Title: unity picks poor hidpi scale factor defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1649736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649736] Re: unity picks poor hidpi scale factor defaults
I just tried the merge proposal, and it works much less great for me. The merge proposal changes don't improve the default scaling, which is the focus of this bug, but it does make it very difficult for users to choose an in-between scale if they want or need it for accessibility reasons. Kai-Heng Feng, What's the physical size of your 4K monitor, and what scaling size does this pick for you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649736 Title: unity picks poor hidpi scale factor defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1649736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634478] Re: module "QtQuick.Controls" is not installed
Kdenlive crashes if I just install the kdenlive package with the above error messages. After installing the qml-module-qtquick-controls package, Kdenlive starts successfully. Can we get a revised package with the needed module added to the dependencies? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634478 Title: module "QtQuick.Controls" is not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1634478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649736] Re: unity picks poor hidpi scale factor defaults
This patch should scale to the nearest integer scaling factor. ** Patch added: "hidpi-integer-scaling.patch" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1649736/+attachment/4792495/+files/hidpi-integer-scaling.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649736 Title: unity picks poor hidpi scale factor defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1649736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649736] Re: unity picks poor hidpi scale factor defaults
The "broken widget rendering" is a manifestation of how GTK3 handles HiDPI. GTK3 doesn't natively scale at 1/8 increments, so Unity's scaling is working around that by messing with the size of text and widgets. To give you an idea, I'm attaching a screenshot of the same window as rendered at 1x (as on a 140dpi screen) and 1.5x (as on a 210dpi screen). You can see how the text nearly overflows the switches and drop downs. Plus the window doesn't resize correctly (same width in pixels but physically smaller). To actually get non-integer scaling to look right would be quite a big effort. We'd need to either patch the major toolkits to support non- integer scaling or modify Ubuntu's window manager/compositor to render individual windows at the next integer scale up (2x) and then rescale the window down to the correct size (1.5x), plus add proper input redirection support in X. That's why I'm suggesting we minimize the number of people we give non- integer scaling. ** Attachment added: "gtk-non-integer-scaling.jpg" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1649736/+attachment/4792063/+files/gtk-non-integer-scaling.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649736 Title: unity picks poor hidpi scale factor defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1649736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649736] Re: unity picks poor hidpi scale factor defaults
After thinking through the various cases, I think the cases where integer scaling can't provide an ideal widget size are also the cases where user's preferences are going to be split. There is also at least one usable integer scale for any given dpi. I did a fair bit of testing to simulate the apparent scale of widgets. Everything from 140 dpi up to 210 dpi is usable at 1x. Everything between 210 dpi and 280 dpi is usable at 2x (if sometimes a bit big). Exactly 210 dpi is usable either way, and I could see different users choosing 1x, 2x, or 1.5x depending on their preference between a) lots of screen real estate, b) big, readable text, or c) average size at the expense of broken widget rendering. I think we can provide a usable default experience actually with just integer scaling. 140 dpi is good as the optimal target, but instead of rounding to eighths, just round to a whole integer (Scale factor or 8 or 16). The usability problems for 1x scaling begin just above 210 dpi, so above that 2x is appropriate. That way we deliver correct widget rendering out of the box. The fractional scaling will still be there in the settings for people who prefer to optimize size and screen real estate at the cost of ugly GTK rendering. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649736 Title: unity picks poor hidpi scale factor defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1649736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649736] [NEW] unity picks poor hidpi scale factor defaults
Public bug reported: The recently set-hidpi-scale-factor branch provides extremely valuable support for hidpi displays, but it does introduce a few easily fixed regressions because of the way it anchors scaling too rigidly to simulate 140 DPI. This works well on a 15" Full HD or 4K screen, but sets a non-integer scale factor on 14" and 17" Full HD or 4K screens. Most toolkits don't support non-integer scaling factors very well, and even if they did, it would still result in a loss of sharpness. The displays mentioned above are perfectly usable at the nearest integer scaling factor, and windows render much more cleanly when set to 1x or 2x than 1.125x or 1.875x. The +-1/8 scale difference in size compared to 1x or 2x isn't worth breaking pixel perfect widget rendering. It would be a good idea to try to default to integer scaling factors whenever reasonable. Otherwise most people will have mangled widgets unless they spend the time to set the scale factor themselves. Here's the relevant merge: https://code.launchpad.net/~kaihengfeng/unity /set-hidpi-scale-factor/+merge/299380 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: hidpi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649736 Title: unity picks poor hidpi scale factor defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1649736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
Just tested 1.161.1 in yakkety-proposed and can confirm it fixes the issue. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647826 Title: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
The test package works here! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647826 Title: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647826] [NEW] intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22
Public bug reported: The -22 microcode for the intel 8260 wifi adapter has compatibility issues with Linux Kernel 4.8 under certain hardware configurations. The iwlwifi module crashes resulting in wifi failing with "device not ready" and kernel errors reported in dmesg. [ 10.691115] iwlwifi :6e:00.0: Microcode SW error detected. Restarting 0x200. Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to fallback to the -21 ucode resolves the issue and wifi begins working normally again. This is an issue with Linux kernel 4.8 on both yakkety and xenial, so the bug doesn't currently affect users on xenial, but will begin to after the 16.04.2 HWE release. Kernel 4.4 is unaffected because it doesn't attempt to use the -22 ucode The failure doesn't necessarily affect all machines of a given model with the 8260, but I can reproduce it on multiple laptops when 64GB of RAM are installed (4x16GB). The RAM itself does not appear to be an issue. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug linux-firmware wifi yakkety ** Attachment added: "oryp2_64gb_iwlwifi_dmesg" https://bugs.launchpad.net/bugs/1647826/+attachment/4788267/+files/oryp2_64gb_iwlwifi_dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647826 Title: intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645911] Re: linux-firmware 1.157.5 causes sound issues after initramfs update
Verified linux-firmware 1.157.6 from xenial-proposed. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645911 Title: linux-firmware 1.157.5 causes sound issues after initramfs update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645911] Re: linux-firmware 1.157.5 causes sound issues after initramfs update
Just tested on the affected hardware, and can confirm the new package fixes this bug. After enabling -proposed, running updates, and doing a full shutdown, sound begins working correctly again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645911 Title: linux-firmware 1.157.5 causes sound issues after initramfs update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645911] Re: linux-firmware package causes sound issues with after initramfs update
The test package fixes the issue (after running 'sudo update-initramfs -u' and doing a shutdown and cold boot. Perhaps we could have the linux-firmware package update the initramfs as part of the post install process. In my testing simply installing a new linux-firmware package didn't immediately manifest different behavior, which made tracking this issue down more difficult. This would make it so the updated package automatically heals the affected systems on the next cold boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645911 Title: linux-firmware package causes sound issues with after initramfs update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645911] [NEW] linux-firmware package causes sound issues with after initramfs update
Public bug reported: On laptops with Kaby Lake processors and Sunrise point chipsets (System76 Lemu7), updating to the current (1.157.5) version of the linux-firmware package and then updating initramfs causes sound issues. This can manifest in two ways: 1: Volume hotkeys and controls appear to work, but actual playback volume remains the same. Three HDMI devices appear in the sound-settings gui, despite no HDMI device connected (and only 1 HDMI port) 2: 'Dummy Output' is the only device in the sound-settings gui, and there is no sound output at all. In both cases dmesg shows error output relating to snd_hda_codec_hdmi. This bug only affects Xenial, not Yakkety. Xenial still exhibits the above symptoms after installing the current Yakkety linux-firmware package. I believe the issue is related to the Kaby Lake firmware. In testing, I was able to remove '/lib/firmware/i915/kbl_dmc_ver1_01.bin', run 'sudo update-initramfs -u', and reboot to get sound working correctly again. Perhaps this firmware is needed for the upcoming Union Point chipsets, but causes problems with the for Kaby Lake processor laptops running the 4.4.0 kernel and Sunrise Point chipsets. There is either a bug in the new Kaby Lake firmware or it is being erroneously applied to inappropriate hardware. I have received a number of reports of users running into this bug, presumably anyone who updated to the latest kernel and linux-firmware packages at the same time. Based on testing, next kernel update could trigger the bug for many more users. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: kabylake linux-firmware sound update-initramfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645911 Title: linux-firmware package causes sound issues with after initramfs update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1645911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608622] Re: 14.04.5 drops to initramfs prompt during boot with nvme drive
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu) ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608622 Title: 14.04.5 drops to initramfs prompt during boot with nvme drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1608622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608622] [NEW] 14.04.5 drops to initramfs prompt during boot with nvme drive
Public bug reported: So, installing 14.04.4 works fine, but systems with nvme drives don't boot after installing 14.04.5. Steps to reproduce: 1) Install Ubuntu 14.04.5 on a system with an nvme drive 2) reboot 3) instead of booting to a graphical environment, there is an initramfs prompt. Notes: This also prevents reaching any of the recovery mode tools. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608622 Title: 14.04.5 drops to initramfs prompt during boot with nvme drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600308] Re: ubiquity targets invalid device name with nvme disks, fails to install grub
I just tested the new code, and your updated regex still breaks the installation in exactly the same way as before. The portion of the regex that reads '/dev/[a-z]+' truncates the target to '/dev/nvme' before it gets to the bit you added. You should be able to use the following: target = re.sub(r'(/dev/(cciss|ida)/c[0-9]d[0-9]|/dev/nvme[0-9]+n[0-9]+\ |/dev/[a-z]+).*', r'\1', target) ** Changed in: ubiquity (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600308 Title: ubiquity targets invalid device name with nvme disks, fails to install grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1600308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602340] Re: nouveau: boot hangs at blank screen with unsupported graphics cards
Tested the proposed kernel with: * GTX 970M * GTX 970 * GTX 1080 All three systems boot into unity as expected with the proposed kernel. Only the GTX 1080 is in low graphics mode (expected because nouveau doesn't yet support it) This should be good to go. It's already a confirmed improvement for first boot, and I'll test again to confirm that the new kernel enables the graphical installer once it hits the daily iso. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602340 Title: nouveau: boot hangs at blank screen with unsupported graphics cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602340] Re: nouveau: boot hangs at blank screen with unsupported graphics cards
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602340 Title: nouveau: boot hangs at blank screen with unsupported graphics cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602340] Re: nouveau: boot hangs at blank screen with unsupported graphics cards
Success with the patched test build! The nouveau patch allows our systems to boot into Unity with Pascal series cards without requiring nvidia-367. Tested and successfully booted with: *GTX 1070 *GTX 1080 *GTX 970 *GTX 950 *GTX 730 No regressions found so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602340 Title: nouveau: boot hangs at blank screen with unsupported graphics cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602340] Re: nouveau: boot hangs at blank screen with unsupported graphics cards
** Description changed: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. + + + Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 ** Description changed: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. - Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 + Adds a check to nouveau that the gfx chipset is supported before booting fbdev off the hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602340 Title: nouveau: boot hangs at blank screen with unsupported graphics cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602340] [NEW] nouveau: boot hangs at blank screen with unsupported graphics cards
Public bug reported: This issue prevents installing Ubuntu and booting with certain GPUs until the Nvidia-367 graphics drivers have been installed. Nouveau in 16.04 doesn't include support for the current series of Nvidia GPUs (Pascal architecture, GTX 1070 and 1080), but still tries to load, resulting in boot hanging at a blank screen. The current behavior will cause Ubuntu 16.04 to be difficult for most users to install on computers with NVidia hardware newer than the previous generation. To reproduce: Create an Ubuntu live image and attempt to install Ubuntu on a computer with an NVidia Pascal GPU. Expected Results: Ubuntu graphical installer appears. Actual Results: Boot hangs at blank screen. Possible fix: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470 Adds a check to nouveau that the gfx chipset is supported before booting fbdev off the hardware. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-bug nouveau -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602340 Title: nouveau: boot hangs at blank screen with unsupported graphics cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600308] Re: ubiquity targets invalid device name with nvme disks, fails to install grub
** Summary changed: - ubiquity targets wrong drive, fails to install grub with nvme disks + ubiquity targets invalid device name with nvme disks, fails to install grub ** Description changed: On Ubuntu 16.04, when installing Ubuntu to an nvme drive, Ubiquity fails to install grub. In ubiquity/misc.py the function default_grub targets /dev/nvme0 instead of /dev/nvme0n1, which is the real name of the device. For single drive scenarios, this can be fixed by filtering out nvme devices from the regex line: old: target = re.sub(r'(/dev/(cciss|ida)/c[0-9]d[0-9]|/dev/[a-z]+).*', - r'\1', target) + r'\1', target) fixed: target = re.sub(r'(/dev/(cciss|ida)/c[0-9]d[0-9]|/dev/(?!nvme)[a-z]+).*', - r'\1', target) - - For multi-drive scenarios, Ubiquity behaves inconsistently between bios - and uefi modes. In UEFI mode, default_grub behaves like the single - drive scenario and only sees the usb media (which it ignores) and the - nvme drive. - - In BIOS mode, there is a device listed at /dev/sda before the nvme - drive. Ubiquity then tries to put grub on /dev/sda regardless that - we're installing to the nvme drive. Grub then fails to install on - /dev/sda. - - This makes Ubuntu a pain to reinstall for our customers if they have an - nvme drive. + r'\1', target) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1600308 Title: ubiquity targets invalid device name with nvme disks, fails to install grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1600308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600308] [NEW] ubiquity targets wrong drive, fails to install grub with nvme disks
Public bug reported: On Ubuntu 16.04, when installing Ubuntu to an nvme drive, Ubiquity fails to install grub. In ubiquity/misc.py the function default_grub targets /dev/nvme0 instead of /dev/nvme0n1, which is the real name of the device. For single drive scenarios, this can be fixed by filtering out nvme devices from the regex line: old: target = re.sub(r'(/dev/(cciss|ida)/c[0-9]d[0-9]|/dev/[a-z]+).*', r'\1', target) fixed: target = re.sub(r'(/dev/(cciss|ida)/c[0-9]d[0-9]|/dev/(?!nvme)[a-z]+).*', r'\1', target) For multi-drive scenarios, Ubiquity behaves inconsistently between bios and uefi modes. In UEFI mode, default_grub behaves like the single drive scenario and only sees the usb media (which it ignores) and the nvme drive. In BIOS mode, there is a device listed at /dev/sda before the nvme drive. Ubiquity then tries to put grub on /dev/sda regardless that we're installing to the nvme drive. Grub then fails to install on /dev/sda. This makes Ubuntu a pain to reinstall for our customers if they have an nvme drive. ** Affects: ubiquity (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/1600308 Title: ubiquity targets wrong drive, fails to install grub with nvme disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1600308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
