** Tags removed: bios-outdated-1.36 kernel-bug-exists-upstream-v4.17-rc6
** Tags added: bios-outdated-1.38 kernel-bug-exists-upstream-v4.19-rc4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It was still happening on 4.19-rc1. I'll test on later 4.19 rcs over the
weekend.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1782934
Title:
XPS 13 9350 black screen with kernel
** Tags added: latest-bios-1.28
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1768139
Title:
Kernel crash when booting laptop with hdmi monitor connected
Status in linux package in
Gioele Barabucci, thank you for reporting this and helping make Ubuntu
better.
1a) Regarding regression potential, did you personally test with your
Samsung NP900X3D-A03IT (not someone else, somewhere else) a prior Ubuntu
release or prior kernel version and this was working?
1b) If so, which one
** Changed in: linux (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1644981
Title:
ExFAT Formatted SD Cards not mounted
Status in linux package in
** No longer affects: linux (Ubuntu)
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu)
Status: In Progress => New
** Changed in: linux (Ubuntu)
Remote watch: Linux Kernel Bug Tracker #43081 => None
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776887
Title:
Critical upstream bugfix missing in Ubuntu 18.04 -
Donk:
>"The bug is solved in Cosmic but it's not solved in Xenial"
The Status Fix Released took this into account as defined in
https://wiki.ubuntu.com/Bugs/Bug%20statuses . However, folks who want to
pursue fixes for prior releases do so via
As per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785481/comments/26
.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
kamiccolo, a 4.2.x kernel is EOL, and not supported in Ubuntu. For more on
this, please see:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
https://wiki.ubuntu.com/Releases
However, if you have an issue booting a supported version of Ubuntu, please
file a new report via:
** No longer affects: linux (Ubuntu)
** Project changed: xorg-server => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: High => Undecided
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Remote watch: freedesktop.org Bugzilla #89055 =>
I seems that HSP/HFP doesn't work at all on 18.04. I've tried a variety
of different Pulseaudio modules/settings, and also ofono. @vanvugt do
you know if a different issue tracks that?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
** Package changed: fedora => xorg (Fedora)
** Changed in: xorg (Fedora)
Importance: High => Undecided
** Changed in: xorg (Fedora)
Status: Confirmed => New
** Changed in: xorg (Fedora)
Remote watch: freedesktop.org Bugzilla #54133 => None
** No longer affects: linux (Ubuntu
Donk, to see if this is already resolved in ubuntu, could you please
test http://cdimage.ubuntu.com/daily-live/current/ and advise to the
results?
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
** Summary changed:
- System freeze on high memory usage when DMA is disabled
+ When DMA is disabled system freeze on high memory usage
** Tags removed: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Luís Correia, you don't have the same problem as this report is not
scoped to 18.04, or any Dell machine.
Hence, if you want your problem addressed, use the computer the problem is
reproducible with, and provide necessary debugging logs by filing a new report
with Ubuntu via a terminal:
** Tags removed: kernel-bug-exists-upstream-4.17
** Tags added: kernel-bug-exists-upstream-4.18.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go
I'm suffering with this again. Is the work around really to turn off
boot protection?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1775672
Title:
virtualbox-dkms installation hangs in
** Tags removed: kernel-fixed-upstream-4.17.13 kernel-fixed-upstream-4.18-rc8
** Tags added: reverse-bisect-done
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Donk, to confirm, you tested a kernel with the noted commit in place and
the problem was reproducible. Then, you tested a kernel with that commit
reverted, and the problem was gone. Correct?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
tazesimit (simitcii), it will help immensely if you use the computer the
problem is reproducible with, and provide necessary debugging logs by filing a
new report with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Changed in: linux (Ubuntu)
Status:
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: regression-release
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770166
Title:
The brightness of
** This bug is no longer a duplicate of bug 847001
Adjusting display brightness is very slow on several Dell laptops
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/828296
Title:
fokedFromTheLife:
1) Regarding the following non-default kernel parameters in use, could you
please advise to each individually on why it was put in place, and if it is
necessary for the touchpad to work:
nouveau.modeset=0
tpm_tis.interrupts=0
acpi_osi=Linux
i915.preliminary_hw_support=1
** Tags added: cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784998
Title:
After a while touchpad doesn't work
Status in linux package in Ubuntu:
Incomplete
Status in
whl2:
1) The latest mainline kernel is now 4.18 (not 4.18-rc). Could
you please advise to this?
2) When using 16.04, did you use 3rd party fan software or was it a
default install?
3) To further narrow down the regression, could you please test 4.4.5
and respond with the results?
--
You
tom, this report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785319/comments/34
regarding this is no longer reproducible. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then
fokedFromTheLife:
1)
>"so when i install ubuntu the touchpad don't work i go to
>http://pclub.in/2017/01/06/Linux-on-Asus-ROG.html and that' worked"
To clarify, you are stating that by default, the touchpad doesn't work
at all. However, after using the non-default kernel parameters, and
Zoltán Szabó, please answer all of the following:
1) Regarding the kernel trace, is this something that started to happen
after an update? if so, which and when precisely?
2) To see if this is already resolved in Ubuntu, could you please test
for this via
fokedFromTheLife, thank you for reporting this and helping make Ubuntu
better. Please answer all of the following:
1) Regarding your Bug Description comment:
>"after a while..."
1a) Could you please define specifically how long a while is? Seconds, minutes,
hours, etc.?
1b) Could you please
** Tags added: nondefault-kernel-parameters
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1785319
Title:
All kinds of problems on wake from lid close 18.04
Status in linux package in
Tom, in order to allow additional upstream mainline kernel developers to
examine the issue, at your earliest convenience, could you please test the
latest mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily
folder).
2)
** Tags removed: latest-bios-f.15
** Tags added: bios-outdated-f.22 needs-upstream-testing
** Changed in: linux (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Donk, the next step is to fully reverse commit bisect from kernel 4.15
to 4.16.18, in order to identify the latest kernel commit that did not
work followed immediately by the next kernel commit that did work. This
will allow a consideration of the fix commit for backporting. Could you
please do
Donk, in order to allow additional upstream mainline kernel developers to
examine the issue, at your earliest convenience, could you please test the
latest mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily
folder).
Donk, thank you for reporting this and helping make Ubuntu better.
Could you please run the following command in a terminal as it will
automatically gather and attach debug information to this report:
apport-collect 1785481
** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu)
**
Thanks Daniel. I've spent all morning testing kernels, and here're my
results. Spoiler nothing after 4.15 works reliably, and mostly doesn't
work at all.
In detail:
- 4.15.0-12-generic: Works
This is what I get after a minimal install where I don't allow the installer
to download updates.
-
** Description changed:
With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu Budgie),
the graphical installer works correctly, but on every post-install
login, the screen goes black at the disk decryption screen.
- The kernel version post-install is 4.14.0-29-generic.
+ The
Bougron (francis-bougron), it most helpful if you use the computer the problem
is reproducible with, and provide necessary debugging logs by filing a new
report with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Attachment removed: "seven seven failures on
fugounashi, it is most helpful if you use the computer the problem is
reproducible with, and provide necessary debugging logs by filing a new report
with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Changed in: linux (Ubuntu)
Status: Confirmed =>
Donk, it is most helpful if you use the computer the problem is reproducible
with, and provide necessary debugging logs by filing a new report with Ubuntu
via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** No longer affects: linux-hwe (Ubuntu)
--
You received this
Vinícius Milanez Couto, in order to allow additional upstream mainline kernel
developers to examine the issue, at your earliest convenience, could you please
test the latest mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the
Update: I wanted to make sure of the problem still existing in the
4.18.0 kernel, so I started from scratch again with the following steps:
1. Reinstall Ubuntu minimal install (without downloading updates which is what
updates the kernel to the problem version),
2. Update kernel to 4.18.0,
3.
Reverting "Fix Released" as requested commit not in diff:
https://launchpad.net/ubuntu/+source/linux/4.15.0-29.31
** Changed in: linux (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1767180
Title:
@jsalisbury: Thanks!
Tested with 4.18.0-041800rc6 & no change. Issue tags and status updated.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which
Hi Daniel. The backlight keys do not help.
Prior to the kernel version in question, Ubuntu 17.x and 18.x on this
machine had occasional backlight problems on waking from suspend that I
could resolve by closing the lid, waiting a few seconds and reopening
the lid.
As far as I can tell, this
Reverting Fix Released given:
1) diff contained no blk-core changes ->
https://launchpad.net/ubuntu/+source/linux/4.15.0-29.31
2) Kleber Sacilotto de Souza explicitly mentioned the updates were not in
-Proposed ->
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776887/comments/20
**
Sebastian Nohn, to keep this relevant to upstream, one will want to
continue testing the latest mainline kernel as it is released (now
4.18-rc5). Could you please advise?
** Tags added: bios-outdated-206 needs-upstream-testing regression-
release
** Changed in: linux (Ubuntu)
Status:
Paolo.Dirienzo, give you have different hardware, and root cause issue (the
reader stopped working, while this report is about it never worked in the
past), it will help immensely if you use the computer the problem is
reproducible with, and provide necessary debugging logs by filing a new
Andy Barry, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555775/comments/58
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow
** Tags added: needs-upstream-testing
** Changed in: linux (Ubuntu)
Importance: Medium => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1247723
Title:
[Samsung NP900X3C-A02US]
Thomas Diesenreiter, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771204/comments/22
regarding how you consider this issue closed. For future reference you
can manage the status of your own bugs by clicking on the current status
in
Thomas Diesenreiter:
1)
>"Yes, but thats a onetime thing."
To clarify, if you boot into one kernel back from Proposed, then back
into Proposed, do you then have the issue only on the first boot?
2)
>"See the link I posted in the original report"
That report has been resolved for the original
Thomas Diesenreiter, as per your comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771204/comments/16 :
>"Although it takes about 30 minutes after the booting with the new kernel for
>the lines to slowly vanish."
Were you mistaken that the Proposed kernel took 30 minutes after
Thomas Diesenreiter:
1) Given the Proposed kernel didn't resolve the issue, this is not a
duplicate of LP#1773520. Hence, to keep this relevant to upstream, one
would want to periodically check for, and test the latest mainline
kernel (now 4.18-rc4) as it is released.
Could you please advise?
Bob:
>"...is it just going from 4.17rc6 to 4.16.6 and seeing when bluetooth
started working?"
Yes. To advise, the article
https://wiki.ubuntu.com/Kernel/KernelBisection covers this answer
precisely, and was written for folks who don't know anything about
linux, so it's easy to follow.
--
You
Andy Barry, to keep this relevant to upstream, one will want to continue
to test the latest mainline kernel (now 4.18-rc3) as it is released.
Could you please advise?
** Tags removed: kernel-bug-exists-upstream latest-bios-1.2.8
** Tags added: bios-outdated-1.3.12 needs-upstream-testing
**
adin:
1) To keep this relevant to upstream, one will want to continue to test
the latest mainline release (now 4.18-rc3) as it is released. Could you
please advise?
2) Could you please advise if
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607571/comments/25
provides a WORKAROUND?
**
whl2:
1) To clarify, when you were using 16.04, were you using the nvidia or
nouveau driver? If nvidia, which version precisely?
2) If you uninstall the nvidia driver in your current OS, and use
nouveau is there any change?
3) To keep this relevant to upstream, one will want to test the latest
Markus Baumann:
>"Does it make sense to try the mainline kernel, since the error is
obviously fixed with 18.04?"
No, it doesn't. Given you reproduced this in 17.10 (which is EOL July
2018 as per https://wiki.ubuntu.com/Releases ), when you upgrade soon to
18.04, the issue would be gone.
--
You
jecks (slayerproof32), it is most unhelpful to post comments or
attachments here, or give pastebin links. If you want to motivate
developers to want to look into your issue, file a new report. If you
want developers to ignore your problem, continue posting here.
marco (nazgul17), one may always
jecks (slayerproof32), this report is poorly defined, and not root caused as no
debugging logs have been provided by the original reporter. However, what
little is known is that the issue for the original reporter was correlated to
when DMA was disabled in the BIOS, using a now old, and
** Package changed: linux (Arch Linux) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** No longer affects: linux (Ubuntu)
** Package changed: fedora => ubuntu
** Changed in: ubuntu
Importance: Medium => Undecided
** Changed in: ubuntu
Status: Won't
** Summary changed:
- System freeze on high memory usage
+ System freeze on high memory usage when DMA is disabled
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Not Fix Released as defined by https://wiki.ubuntu.com/Bugs/Status .
** Changed in: linux (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
sudo apt-get remove linux-image-ex
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-image-ex
I'm trying to free up space in my hard drive and i got this error i was
expecting to remove the
** Tags removed: performing-bisect
** Tags added: bisect-done reverse-bisect-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1773520
Title:
After update to 4.13-43 Intel Graphics
James (jamestheawesomedude), it will help immensely if you use the computer the
problem is reproducible with, file a new report with Ubuntu by first ensuring
the package xdiagnose is installed, and click the Yes button for attaching
additional debugging information after running the following
Thomas Diesenreiter, a potential fix for your problem is in the Proposed
repository. See https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed.
If you test this and it addresses the issue, this is likely a duplicate
of LP#1773520, so feel free to mark it
*** This bug is a duplicate of bug 1773520 ***
https://bugs.launchpad.net/bugs/1773520
** This bug has been marked a duplicate of bug 1773520
After update to 4.13-43 Intel Graphics are Laggy
--
You received this bug notification because you are a member of Kernel
Packages, which is
Merlin:
I) The scope of LP#1300349 is how a pre-3.18-rc4 kernel had an issue,
which 3.18-rc4 fixed. However, you are using a 4.15 kernel. Hence, the
scope and root cause are different (i.e. not relevant).
II) In order to allow additional upstream mainline kernel developers to examine
the issue,
Could you please advise what supported release you have reproduced this
in?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: kernel-fixed-upstream-4.18-rc1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1773581
Title:
[Samsung NP900X3G-S01US] Horizontal lines after update to 4.13.0-43
Status
Kafabih Rahmat, the issue you are reporting is an upstream one. Could
you please report this problem following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO: QCA ath9k Development and Johannes Berg CC: linux-wireless)?
Please provide a direct
This has been fixed for some time, so when can we expect this to be in
an updated Bionic kernel?
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1741655
Title:
Regression: KVM
Merlin:
1) For you personally with your hardware, what was the most recent
kernel/release where this issue did not happen?
2) As per the sticker of the monitor itself (not from the Bug
Description, or the result of a terminal command), could you please
provide the full manufacturer and model?
Kafabih Rahmat, to confirm, when you were using the previous release
Ubuntu 16.04.1, did this issue not happen?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775772
Title:
Atheros
** Tags removed: kernel-bug-exists-upstream-4.17.2 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.18-rc1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Kafabih Rahmat:
A) Regarding your comment:
>"When I turned on the bluetooth and connected to my bluetooth mouse
It's happened random segmentation fault. The bluetooth device is Atheros
AR3012."
Two follow up questions:
1. To advise, the scope of this report is regarding your wireless network
** Attachment removed: "results.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+attachment/5146961/+files/results.log
** Attachment removed: "dmidecode.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+attachment/5146962/+files/dmidecode.log
** Changed
Markus Baumann, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754759/comments/24
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the
Kafabih Rahmat:
1) To confirm a regression, did this issue start to happen after an
update? if so, which and when precisely?
2) To keep this relevant to upstream, please continue to test latest
mainline kernel (now 4.18-rc1) as it becomes available. Could you please
advise?
3) There is no need
Frank Winklmeier, mainline (i.e. kernel.org) is where Ubuntu sources
their kernel. drm-tip is an unsupported kernel which may or may not have
commits from it pulled into mainline. Reporting your results to Intel
will provide Intel developers support to review what fixes your problem,
and consider
Frank Winklmeier, the issue you are reporting is an upstream one. Could
you please report this problem to Intel following their instructions via
https://01.org/linuxgraphics/documentation/how-report-bugs ?
Please provide a direct URL to your report so that it may be tracked.
Thank you for your
Merlin, thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1777257
When reporting bugs in the future please use apport by using
Frank Winklmeier:
>"...what are the next steps?"
In order to upstream, please test the latest mainline kernel as it
becomes available (now 4.17.2).
If reproducible in latest mainline, then test drm-tip (not daily, drm-
intel, etc.).
--
You received this bug notification because you are a
Mikołaj Banasik, it will help immensely if you use the computer the problem is
reproducible with, and provide necessary debugging logs by filing a new report
with Ubuntu via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you
Tom:
A)
>"Now I can even burn the iso"
Did you mean you cannot burn an ISO? If so, you need to use a DVD or USB
drive.
B)
>"(cd does not work)"
Stating something doesn't work, without providing details (e.g. logs,
screenshot, etc.) doesn't allow anyone to know how it didn't work
precisely.
C)
Lea Lange:
A) The observation of the touchpad working after one cold boot doesn't confirm
it is not a kernel issue. Also, your touchpad is recognized as an Elantech as
documented in:
https://www.kernel.org/doc/html/latest/input/devices/elantech.html
B) Was there ever a time where the touchpad
whl2:
1) Regarding the use of non-default kernel parameter:
acpi_backlight=vendor
Is this required for something? If you boot without this parameter does
this change anything?
2) If you remove the nvidia proprietary drivers, does this provide a
WORKAROUND?
3) If you remove the 3rd party
Nando, the issue you are reporting is an upstream one. Could you please
report this problem with logs from the latest mainline kernel (not
Ubuntu kernel) following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO: Greg Kroah-Hartman, and QCA
** Tags removed: kernel-bug-exists-upstream-4.17
** Tags added: kernel-bug-exists-upstream-4.17.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775230
Title:
TP-LINK TL-WN722N causes
** Tags added: cherry-pick kernel-fixed-upstream regression-release
reverse-bisect-done
** Description changed:
This upstream bug has been confirmed to affect Ubuntu users[1]. As per
the fix commit (below), the most frequent symptom is a crash of
Xorg/Xwayland, i.e. killing the entire
Tom:
1) Is this something that started to happen after an update? If so,
which and when precisely?
2) To see if this is already resolved in Ubuntu, could you please test
the latest 64-bit release (not 32-bit) via http://cdimage.ubuntu.com
/daily-live/current/ and advise to the results?
** Tags
** Tags added: bios-outdated-fb06
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776941
Title:
Touchpad not detected on XMG C404 Ubuntu 16.04
Status in linux package in Ubuntu:
Lea Lange, thank you for reporting this and helping make Ubuntu better. Could
you please boot into a Ubuntu kernel (not third party kernel) and execute the
following command only once, as it will automatically gather debugging
information, in a terminal:
apport-collect 1776941
** Changed in:
Nando:
1) Could you please provide the full motherboard manufacturer and model?
2) Could you please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
3) To keep this relevant to upstream, one will want to test the latest
whl2, Ubuntu kernel only. My bad for not specifying precisely.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status
** Tags added: bionic kernel-bug-exists-upstream-4.17
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1775230
Title:
TP-LINK TL-WN722N causes 100% CPU usage due to trace logging
Status
301 - 400 of 20143 matches
Mail list logo
