Unless your dropouts were happening exactly after the second group
rekeying, it is a different bug that would need its own bug report.
I haven't had any problems with 18.04 or any distro that uses newer
kernels and firmwares (say Arch).
--
You received this bug notification because you are a
Oops. Sorry if it appeared as if I was requesting it to be implemented
soon. I know this will need extensive testing, which is partly why I
wanted to put this on the radar as soon as possible.
Thanks for getting back to me so quickly.
--
You received this bug notification because you are a
Hey, Alberto. I have a few questions:
1. Are these changes intended to be deployed to Bionic, eventually? (I
assume yes, by the names/versions you're working on, but I wanted to
confirm this)
2. Would it make it not necessary to switch to nouveau at all? (I assume
this is why prime-select
Public bug reported:
[Impact]
* Touchpad using libinput behaves badly. It's imprecise for small
movements, the cursor jumps from one point to another, movements seem to
take a while to register, etc., specially if compared to the Synaptics
driver that was used in Xenial. Since users will
Actually, I confused trackpoints with trackpads. Indeed, there's no fix
for trackpoints yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773276
Title:
Cursor jumps at the end of trackpoint
Actually, I confused trackpoints with trackpads. Indeed, there's no fix
for trackpoints yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769322
Title:
Trackpoint reacts jumpy and isn't precise
This is probably (I'm 99% certain) fixed in libinput 1.11 for good. It's
now on par with Windows/macOS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769322
Title:
Trackpoint reacts jumpy and
Upgrading to 1.11 would fix those + touchpad movement in general
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767559
Title:
Provide libinput 1.10.6 in bionic-updates to fix specific touchpad and
This would be fixed by upgrading to libinpu 1.11. Peter Hutteter put in some
great effort into analyzing touchpad data from Windows and MacOS, as well as
the old Synaptics driver, and I must say, after upgrading from 1
10.5 to 1.11 in Fedora, it's just on par with MacOS and Windows now.
--
You
** 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.
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
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,
** 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
** 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
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.
@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.
@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
@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
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.
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
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:
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
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
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
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
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
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
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:
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
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
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
** 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,
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
** 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.
** 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
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
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
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
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
39 matches
Mail list logo
