Can you guys share the release plans for kernel-4.15.0-33.36?
We have a installation/boot failure with HBA330 and the patches in this list
are fixing it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
After discussion with Kamal, we will disable this test instead of enabling that
CONFIG_TRACEPOINTS for KVM kernels.
Thanks
** Changed in: linux-kvm (Ubuntu)
Status: New => Won't Fix
** No longer affects: linux (Ubuntu)
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Yes.
https://lkml.org/lkml/2018/8/20/42
--
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/1785780
Title:
TB 16 issue on Dell Lattitude 7490 with large amount of data
Status in Dell
[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu Bionic) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for grub2 (Ubuntu Bionic) because there has been no activity
for 60 days.]
** Changed in: grub2 (Ubuntu Bionic)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Time is limited and we would refer to the previous kernel
(3.13.0-154.204) test result.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1787544
Title:
linux-oem: 4.15.0-1017.20
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 1725836
and then change the status of the bug to 'Confirmed'.
If, due to the
Thanks. Comment #33 seems to be the most important one now. If the bug
occurs in XFCE as well then this is not a gnome-shell bug. Instead it
should be assigned to xorg-server, or the driver, or the kernel.
** No longer affects: mutter
** No longer affects: gnome-shell (Ubuntu)
** No longer
(In reply to Antoine Pitrou from comment #398)
> @Daniel what makes you think this bug is fixed? It certainly isn't for me.
> I have a ASRock Fatal1ty X370 Gaming X motherboard, a Ryzen 7 1700 CPU, have
> updated the motherboard BIOS to its latest version (4.80 with
> PinnaclePI-AM4_1.0.0.2
(In reply to Antoine Pitrou from comment #407)
> (In reply to Michaël Colignon from comment #400)
> >
> > Hi Antoine, i checked the manual of your Asrock motherboard quickly.
> > For your machine the "typical idle current" is named "c6 mode"
> > Disable it and you get the "typical idle current",
@Paul I understand this. I'm also monitoring the corresponding Ubuntu
issue. Still, I was asking whether there was a specific reason to
believe this bug was fixed upstream (as opposed to the fact that a
single person doesn't experience the issue anymore).
--
You received this bug notification
The title of the bug should be changed to include Ryzen 7 1700X, and the
reporter should follow up, if the problem still occurs with Linux 4.18.
For the other issues, separate bug reports should be submitted. Though
the mailing lists might be the better forum for this, as the Linux
kernel
(In reply to Michaël Colignon from comment #400)
>
> Hi Antoine, i checked the manual of your Asrock motherboard quickly.
> For your machine the "typical idle current" is named "c6 mode"
> Disable it and you get the "typical idle current", i think.
> While keeping the boost monothread.
Hi
I don't think there is any reason to think that the "c6 mode" option had
anything to do with "typical idle current". Its name implied that it
disabled C6 states, which it actually didn't (according to the Zenstates
script).
--
You received this bug notification because you are a member of Kernel
This is surprising. It sounds like reconnecting is disabled by default
unless you specify exactly which devices to reconnect in
/etc/bluetooth/main.conf:
# The ReconnectUUIDs defines the set of remote services that should try
# to be reconnected to in case of a link loss (link supervision
#
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1770166
Title:
The brightness of the
But the directions mentioned elsewhere from https://dev.solus-
project.com/T5224 do work even thought they appear to break Bluetooth
(even with the updated instructions workaround mentioned in that
thread).
--
You received this bug notification because you are a member of Kernel
Packages, which
Brightness and other custom keybindings are the responsibility of the
kernel. Although in some cases a BIOS update helps too.
** Changed in: xorg (Ubuntu)
Status: Expired => New
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a
You have been subscribed to a public bug:
The brightness of the notebook does not lower or rise with the FN key. Acer
Aspire 5742 i3-380m 6gb ram ssd kingston 120gb.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Regarding 2) - no 3d-party fan software on 16.04.
3) - running on 4.4.5-040405-generic now, but not for very long, can't be sure
yet if the issue is still present or not.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Description:Ubuntu 18.04.1 LTS
Release:18.04
libnvidia-compute-390:
Instalado: (nenhum)
Candidato: 390.48-0ubuntu3
Tabela de versão:
390.77-0ubuntu0~gpu18.04.1 -1
100 /var/lib/dpkg/status
390.48-0ubuntu3 500
500
Nope, getting rid of '/lib/udev/rules.d/71-nvidia.rules' does nothing.
It's a Mint 19 (Tara) with Cinnamon installation that I sometimes use on
a Dell E6400 which used to work well with it before with earlier
kernels.
--
You received this bug notification because you are a member of Kernel
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1787861
Title:
Displays not
Public bug reported:
I just upgraded from Ubuntu 16.04 LTS to 18.04 LTS. Previously, this
was all working correctly: I have 3 displays connected to an nVidia GT
730. VGA-0 (an old 21-inch CRT) is never enabled (just haven't got
around to removing it). DVI-D-0 is the primary display, always
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in
This is still broken in 18.10 and 18.04. Are there any plans to fix for
18.10? I can test if you give me instructions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1740231
Title:
I tried 4.15.0-33 in the hope of bluetooth again.
I should not have done. No ethernet, no wifi, and no bluetooth at all.
I know it's 'proposed', but I've been without a bionic bluetooth for
many months now. I just hope any official version is OK.
Yes, I know it's free. This is, however, the
I have the same issue with Linux Mint 19 (Ubuntu 18.04 based) using
kernel 4.15 but for QCA9377 chipset.
I compiled the 4.18 kernel using `make localmodconfig` and have the same
problem.
I had sources for kernel version 4.9.24 and it exhibits the same behavior
(failed to wake target for
The bug will be fixed once the zfs package and the bionic kernel (that
contains the zfs driver changes) will be released. So far, just the zfs
package has been released and we are waiting for the kernel to complete
the SRU update and verification phase - this takes a bit longer as the
kernel
I don't see the confirmation for Bionic in this bug report. Any update
when the 4.17 kernel lands in bionic-proposed? Or do I need another
kernel version for Bionic? What do I need exactly for my Bionic server?
This bug prevents me from updating my lxd containers, it will hang the
system
Linux Mint 19 Tara Live ISO has same issue with sleep (suspend) mode.
--
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/1780358
Title:
4.15.0-24 kernel doesn't return from sleep mode
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1787807
Title:
boot oops/4.15.0-32
please report this NULL pointer exception to bugzilla.kernel.org and CC
linuxw...@intel.com to the bug.
--
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/1733194
Title:
kernel NULL pointer
** Attachment added: "screenshot of boot oops"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787807/+attachment/5177502/+files/bootoops-32.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
4.15.0-32 is failing to boot on this core2 laptop, 4.15.0-30 (and
earlier) is fine.
(I'll attach the screenshot of the panic in a second)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-30-generic 4.15.0-30.32
ProcVersionSignature: Ubuntu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1787775/+attachment/5177477/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected bionic
** Description changed:
The touchpad is not working and does not show up in cat
/proc/bus/input/devices on multiple kernels. I've tried the newest
kernel to date (19.08.18) and a few others.
The touchpad works on windows.
+
For me the firmware also crashes on a
> 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
> Network Adapter (rev 32)
And it is always the same log.
I changed nothing on my wifi, so the issue must have been introduced by
some change in ubuntu.
** Attachment added:
*** This bug is a duplicate of bug 1542743 ***
https://bugs.launchpad.net/bugs/1542743
I don't think the duplicate status is correct as this device is
0930:0219 and the duplicate was device 0cf3:3004 and bug #1542743 should
be fixed in 4.15.0-31
*** This bug is a duplicate of bug 1787127 ***
https://bugs.launchpad.net/bugs/1787127
Just confirm, the 3.13.0-156 build from duplicate bug 1787127 resolved
this. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
It was in proposed 31, but not in the official release. How can I tell
if it will make official 33?
--
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/1764645
Title:
Bluetooth not working
Just installed the proposed 4.15.0-33. The fix is in. Bluetooth is
working.
--
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/1764645
Title:
Bluetooth not working
Status in linux package
47 matches
Mail list logo
