Why is this still an issue? Why is it not resolved? It's been 2 years?
Consider this simple scenario right now as I apt-get autoremove and it
removes 4 old kernels. It also keeps 3 kernels.
Generating the initrd for a single kernel takes ballpark 45 seconds.
First step: remove one kernel and gen
This bug has started affecting me on 4.15.0-20-generic #21-Ubuntu. Not
sure if it's been reported on that release, not sure how to report it on
the correct release.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Anil Gobburi, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766006/comments/21
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 yellow
Daniel Nespoulous, please advise to all of the following:
1) To see if this still affects upstream, could you please test the
latest mainline kernel (now 4.17-rc5) and advise to the results?
Also, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it be
Maximilian Federle, the next step is to fully reverse commit bisect from
kernel 4.16.3 to 4.17-rc1 in order to identify the last bad commit,
followed immediately by the first good one. Once this good commit has
been identified, it may be reviewed for backporting. Could you please do
this following
Bob, to confirm this is an upstream issue, could you please test the
latest mainline kernel available (4.17-rc5) and advise to the results?
Also, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.
** Tags removed: kernel-bug-exists
deeks9000, 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 available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
1) The one
Rod B., the next step is to fully reverse commit bisect from kernel 4.4
to 4.16 in order to identify the last bad commit, followed immediately
by the first good one. Once this good commit has been identified, it may
be reviewed for backporting. Could you please do this following
https://wiki.ubuntu
Frew Schmidt, please address all of the following:
1) Could you please execute the following via a terminal to attach debugging
logs:
apport-collect 1767452
2) The next step is to fully reverse commit bisect from kernel 4.16.6 to
4.17-rc3 in order to identify the last bad commit, followed immedi
Philip Taylor, please advise to all of the following:
1) While booted into default Ubuntu kernel 4.15 and having removed all
WORKAROUNDs, could you please execute the following from a terminal to gather
relevant debug logs:
apport-collect 1767603
2) The next step is to fully commit bisect from
Mitch, please address all of the following:
1) To gather system debugging information, could you please execute the
following via a terminal:
apport-collect 1767611
2) To clarify, this issue only happens after resuming from suspend (i.e.
after booting from a shutdown, performing subsequent power
Jochen Schroeder, please respond to all of the following:
1) To capture relevant debugging logs, could you please undo the WORKAROUND,
boot into a Ubuntu kernel (not upstream) and execute the following in a
terminal:
apport-collect 1767701
2) The next step is to fully reverse commit bisect from
Sandy Patterson, please address all of the following:
1. Is this something that started to happen after an update? If so,
which and when precisely?
2. In order to allow additional upstream mainline kernel developers to examine
the issue, at your earliest convenience, could you please test the la
Thomas, the next step is to fully commit bisect from kernel 4.4 to 4.15
in order to identify the last good kernel commit, followed immediately
by the first bad one. This will allow for a more expedited analysis of
the root cause of your issue. Could you please do this following
https://wiki.ubuntu.
Scott Testerman, the next step is to fully commit bisect from kernel
4.7.10 to 4.8 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following https://w
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141786/+files/PulseList.txt
--
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/
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141788/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
Jacob Zimmermann, 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 available from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind
the following:
1) T
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141787/+files/UdevDb.txt
--
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/1772212
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141785/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
marvin, please address the all of the following:
1. When using 16.10, were you able to adjust the brightness via keyboard
key press, or you could only adjust the brightness via xrandr?
2. In order to allow additional upstream mainline kernel developers to examine
the issue, at your earliest conv
stre...@bluewin.ch, please respond to all of the following:
1) Could you please perform the following in Ubuntu 17.10 to gather information
about your working setup via a terminal:
apport-collect 1769331
2) Could you please provide debugging logs from a live environment of
http://cdimage.ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141777/+files/CRDA.txt
--
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/1772212
Ti
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141783/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141784/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141780/+files/Lspci.txt
--
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/1772212
apport information
** Attachment added: "HookError_generic.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141779/+files/HookError_generic.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141778/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141781/+files/Lsusb.txt
--
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/1772212
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1772212/+attachment/5141782/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Tags added: apport-collected bionic
** Description changed:
Hi,
The GNOME night light only seems to work on the first half of the first
screen within a dual monitor setup (Ubuntu 18.04 stock, using X11 with
Gefore GT240, NVIDIA proprietary drivers). See attached
I will attach /var/run/thermald/thermal-conf.xml.auto, and
thermal.log (generated by sudo thermald --no-daemon --loglevel=debug)
to illustrate thermald's bad behaviour.
Thermal.log up to line 500 shows the output when the laptop was idling:
sensor B0D4 stayed cooler than 40°C, the CPUs ran at 900
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1772212
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Attachment added: "Screenshot from 2018-05-19 23-33-18.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772212/+attachment/5141772/+files/Screenshot%20from%202018-05-19%2023-33-18.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
koen@beite-f1:~$ cat /proc/version_signature
Ubuntu 4.15.0-20.21-generic 4.15.17
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-05 (14 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
NonfreeKernelModules: nvidia
Package: linux-image-4
** Attachment added: "thermal-conf.xml.auto"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769236/+attachment/5141771/+files/thermal-conf.xml.auto
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Attachment added: "Screenshot from 2018-05-19 23-35-45.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772212/+attachment/5141774/+files/Screenshot%20from%202018-05-19%2023-35-45.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Should this bug be reassigned to thermald?
--
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/1769236
Title:
CPU frequency stuck at minimum value
Status in linux package in Ubuntu:
Confir
Public bug reported:
Hi,
The GNOME night light only seems to work on the first half of the first
screen within a dual monitor setup (Ubuntu 18.04 stock, using X11 with
Gefore GT240, NVIDIA proprietary drivers). See attached screenshots.
br, Koen.
** Affects: linux (Ubuntu)
Importance: Und
With thermald stopped, and with the laptop displaying a desktop but not
running any heavy loads, all 8 threads idle at 900 MHz, with all 4 cores
typically running under 40°C.
When I run c-ray with thermald stopped, all 8 threads run at 2400 MHz and the
cores warm up as high as 82°C, with short sp
Anupam Datta, could you please run the following command from a terminal
as it will automatically gather and attach updated debug information to
this report:
apport-collect 1751198
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecid
Anupam Datta, the next step is to fully commit bisect from kernel 4.4 to
4.15 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following https://wiki.u
You have been subscribed to a public bug:
The problem is with ethernet. After sometime ethernet network doesn't
work. LAN works well but internet connectivity has problem. I can
connect to same network via wifi and there is no problem. Bu through
Ethernet for this particular machine I am seeing th
sorry i continued posting with information i thought might be relevant or
helpful without reloading the page and did not see the new comments.
I did now send the report as requested. How do i know when it is available in
the archives?
--
You received this bug notification because you are a me
I also faced the same issue and thanks to the Lumar's comment, workaround
mentioned in the link worked for me too:
https://dev.solus-project.com/T5224
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad
Mio, if you want an upstream developer to review your problem and submit
a fix patch, you *need* to file a *new* upstream report as previously
advised (not continue to post here on Launchpad). Otherwise your issue
may never be addressed.
** Tags removed: regression-potential
** Tags added: needs-f
Public bug reported:
1) ubuntu 10.04
2) No package
3) On exiting from console, I expected to get a new login prompt.
4) Ubuntu switches back to graphics mode frozen. Screen looks normal but with
no arrow.
Keyboard is frozen. I can only stop by using the power switch.
ProblemType: Bug
DistroRe
I did some more research and found this kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=53071 which seems to descibe
exactly this issue. In that thread there is mentioned that a bios update might
fix the problem.
Thus I went hunting for an update for my model since the Software Update to
typically it waited for me to report that it worked before failing.
Proving a negative blah indeed.
This time my wifi adapter also didn't come back. I suspect this isn't
entirely unrelated as aren't they actually the same physical device? In
fact that almost makes it weird that usually *only* blue
Thanks for the ping, Dan. No worries. Looking forward to it as this issue
seems to be biting us more frequently nowadays so really interested to see
if this kernel helps.
On Sat, May 19, 2018 at 7:19 AM, Dan Streetman
wrote:
> > Would you be able to build a test kernel against this version?
>
>
Catching up as I came at this from another direction. Having got a
Windows-installed XPS 13 9370 and installed 18.04 freshly on it itself,
its default suspend mode is s2idle, which means lots of battery life
gets lost while suspended. But no bluetooth problems. See askubuntu:
https://askubuntu.com/
I've just sent apport-collect information.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1666109
Title:
Optimal I/
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141557/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141550/+files/CRDA.txt
--
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/1666109
Ti
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141560/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141555/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141554/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141559/+files/UdevDb.txt
--
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/1666109
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141551/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141558/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141553/+files/Lsusb.txt
--
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/1666109
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141552/+files/Lspci.txt
--
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/1666109
apport information
** Tags added: apport-collected bionic
** Description changed:
1) Ubuntu release
Ubuntu 16.04.2 LTS x86_64 desktop
2) package name
linux-generic-hwe-16.04 (4.8.0.36.8)
3) Expected behavior
When I attached more than 3 uas devices, all uas devices would be probe
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1666109/+attachment/5141556/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
The WiFi adapter Gigabyte GC-WB867D-I is quite unstable on Ubuntu 18.04.
I do not have data relative to previous versions of Ubuntu since this
PCIe card is part of a new build that has had 18.04 as the first
installed version.
The reason why I can point the finger at the Linu
Thank you Geoff for pointing to the real solution. I am a bit scared of
making this kind of changes to a system file, but I will give it a try.
Anyway, looking forward to see the fix implemented by Canonical.
Hibernate / Resume from hibernation is for me the solution for my PCs
(not notebooks) sin
Mio, please don't change the Description. It is filled with old,
irrelevant, and speculative statements that confuse and hinder
developers resolving the problem.
Despite this, have you reported this upstream as noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087010/comments/73
?
**
** Description changed:
- I see high (70-90%) cpu usage from a kworker thread. Usually kworker/0:1 or
kworker/0:2.
- This does not always happen. On some boots all is fine but once it shows,
rebooting does not make it go away.
+ I see high cpu usage from a kworker thread. Usually kworker/0:1 or
68 matches
Mail list logo
