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
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
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
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
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:
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
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.
** 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
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
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.
--
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
@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:
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
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:
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
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
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.
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
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
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
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.
** 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
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.
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
** 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
** 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
** 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:
** 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
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
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
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
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
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"
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
** 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:
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:
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:
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
** 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
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
** 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
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,
** 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
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
58 matches
Mail list logo
