** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
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/1528684
Title:
Error parsing PCC subspaces from PCCT
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1782166
Title:
Invoking obsolete 'firmware_install'
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
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/1782540
Title:
Allow Raven Ridge's audio controller to be runtime
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1783418
Title:
Bionic update: upstream stable patchset
--- Comment From hbath...@in.ibm.com 2018-07-25 01:28 EDT---
(In reply to comment #34)
> Created attachment 128858 [details]
> sosreport_moduels=set
>
> Attached sosreport when MODULES=set used
Cascardo, is the sosreport no good?
Thanks
Hari
--
You received this bug notification
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1780499
Title:
Bionic update: upstream stable patchset
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1780858
Title:
Bionic update: upstream stable patchset
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1782846
Title:
Bionic update: upstream stable patchset
@#9, Supposedly rasdaemon could handle MCEs on bionic+. Have not yet
witnessed it working though, even on hardware that had dozen
reports/year shown with mcelog.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: hwe-next
Status: New => Fix Released
--
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/1723915
Title:
[Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse
Hi Rostislav and anyone who is affected by the similar touchpad issue,
As this bug has been set to "Fix released"
Please open a new bug report for your issue with command "ubuntu-bug linux" in
a terminal (ctrl + alt + t)
Thanks.
--
You received this bug notification because you are a member
** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1782070
Title:
[Redpine] Upgrades to improve throughput and
Today, just another "apt-get upgrade":
root@samson:~# apt-get upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete werden aktualisiert
Same as LP: #1779817?
--
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/1783367
Title:
Ethernet is disabled after resume
Status in linux package in Ubuntu:
Incomplete
Bug description:
Bionic's kernel doesn't have commit
b489141369f78ead6ed540cff29ac1974852cd7f.
--
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/1779817
Title:
r8169 no internet after suspending
Status in
Would it be possible for you to do a kernel bisection?
First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$
** Description changed:
+ == Justification ==
+ In the Bionic KVM kernel, the CONFIG_DEBUG_WX was not set, which is needed to
meet the security team's requirement.
+
+
+ == Test ==
+ Before enabling the config, test_330_config_debug_wx will fail in the kernel
security testsuite for the kernel
Almost, maybe related to bug 1782739
--
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 latest kernel
Status in linux package in Ubuntu:
Note to self: possibly related to bug 1782934.
--
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/1782739
Title:
Boot to Black
Status in gdm3 package in Ubuntu:
Incomplete
Status in
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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769443
Title:
[RTL8723BE] Bluetooth is not
OK. Try downloading all of these:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/linux-
headers-4.18.0-041800rc6_4.18.0-041800rc6.201807221830_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc6/linux-
headers-4.18.0-041800rc6-generic_4.18.0-041800rc6.201807221830_amd64.deb
Temporarily reopening the gnome-shell task, just so people can find the
bug. And are less likely to create more duplicates.
** Changed in: gnome-shell (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1769443
** Description changed:
https://gitlab.gnome.org/GNOME/mutter/issues/70
https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665
+
+ https://salsa.debian.org/gnome-team/mutter/merge_requests/6
---
The crash was reported after booting and logging in to an X.Org
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Won't Fix
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => In Progress
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Changed
The reporter states in the linuxcontainers.org discussion and in this
bug description that he's not using an Ubuntu kernel.
This is fixed in Ubuntu 18.04 and will soon be available in Ubuntu 16.04
via the hardware enablement kernel. I'm marking this Xenial task as
Won't Fix in regards to its 4.4
I tested v4.18-rc6 and v4.18-rc5. It is kernel panic at both variants.
** Attachment added: "v4.18-rc6"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783358/+attachment/5167347/+files/IMG_20180725_013633.jpg
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
See https://bugzilla.kernel.org/show_bug.cgi?id=200195
** Bug watch added: Linux Kernel Bug Tracker #200195
https://bugzilla.kernel.org/show_bug.cgi?id=200195
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
The commit mentioned in comment #4 has been upstream since kernel v4.5.
Marking the main linux task as fix released.
** 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
--- Comment From finne...@us.ibm.com 2018-07-24 18:04 EDT---
In response to
>Does that also happen with the current/latest kernel?
Host has been update to 4.15.0-23-generic
i.e.
root@ilzlnx4:~# uname -a
Linux ilzlnx4 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:58:29 UTC 2018
s390x
Hey thank you very much Joseph, this worked!!
But this isn't normal, isn't it?
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Applied fix as per Melissa Rice's post above and working fine on 16.04
on 4.15.0-29 kernel. Many thanks to all involved, it was getting tedious
to have to boot into the old kernel repeatedly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Launchpad has imported 38 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=108619.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Public bug reported:
This bug is for tracking the 4.17.0-6.7 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects:
I will try to get the point releases out today.
--
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/1780227
Title:
locking sockets broken due to missing AppArmor socket mediation
patches
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: Incomplete
** Changed in: linux (Ubuntu Cosmic)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: In Progress
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Do you have a way to reproduce this issue, or was it a one time event?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** 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.
https://bugs.launchpad.net/bugs/1782860
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Tags added: kernel-da-key xenial
--
You received this bug
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux-signed (Ubuntu)
Importance: Undecided => Low
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Cosmic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1782893
Title:
Bluetooth not working on
** Changed in: linux (Ubuntu)
Importance: Undecided => 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/1782910
Title:
In-kernel boot splash
Status in linux package in Ubuntu:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Can you try re-installing nvidia_384 after booting into the 4.15 kernel?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages,
Sorry for that. There is a ppc64el kernel now posted:
http://kernel.ubuntu.com/~jsalisbury/lp1781436
--
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/1781436
Title:
Update2 for ocxl
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
Hello,
There is not that message in this version of the kernel
Regards,
--
Cristian Aravena Romero (caravena)
** Attachment added: "dmesg_4.18.0-041800rc6-generic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782836/+attachment/5167247/+files/dmesg_4.18.0-041800rc6-generic.txt
** No longer affects: s390-tools (Ubuntu Artful)
--
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/1777600
Title:
chzdev can't find modprobe
Status in Ubuntu on IBM z Systems:
In
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
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/1777600
Title:
chzdev can't find modprobe
Status in Ubuntu on IBM z
This bug was fixed in the package s390-tools - 2.5.0-0ubuntu1
---
s390-tools (2.5.0-0ubuntu1) cosmic; urgency=medium
* New upstream release LP: #1776907 LP: #1775627 LP: #1775632
* Drop udevadm patch, no longer needed
* Refresh patches
* Import upstream patches since v2.5.0
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
**
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 1782880
and then change the status of the bug to 'Confirmed'.
If, due to the
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
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 1783267
and then change the status of the bug to 'Confirmed'.
If, due to the
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1783267
Title:
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/1783367
Title:
Ethernet is disabled after
You have been subscribed to a public bug:
linux-modules-extra-4.15.0-29-generic installs virtualbox guest modules
that are newer than what virtualbox-guest-dkms-hwe provides (5.2.8 vs
5.1.34):
$ modinfo
/lib/modules/4.15.0-29-generic/kernel/drivers/staging/vboxvideo/vboxvideo.ko
filename:
Public bug reported:
After resume Ethernet is disable. To re-enable it I must type theses commands :
rmmod r8169
modprobe r8169
In Ubuntu 16.04 it was working (most of the time).
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167199/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167196/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167201/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167194/+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/1783358
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167202/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167200/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167198/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167197/+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
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167195/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167192/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167193/+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/1783358
apport information
** Tags added: apport-collected
** Description changed:
After update to the 4.15.x kernel my system cannot boot. It freezes after
grub menu.
I tried to boot recovery mode and saw kernel panic. Now my system can boot
only on 4.13.x kernel.
I tried 4.15.0-25,
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1783358/+attachment/5167191/+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/1783358
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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 in
The fix for this bug is still in -proposed but will be released shortly.
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for finishing up the bisect!
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
--
You received this bug
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 1783358
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
After update to the 4.15.x kernel my system cannot boot. It freezes after grub
menu.
I tried to boot recovery mode and saw kernel panic. Now my system can boot only
on 4.13.x kernel.
I tried 4.15.0-25, 4.15.0-24, 4.15.0-23, 4.15.0-22, 4.15.0-20 and had the same
results.
Blocking launching (in useful ways) Debian testing & sid containers on
Ubuntu as well.
** Tags removed: block-proposed
--
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/1780227
Title:
Per discussion above:
- Closing the kernel tasks
- Raising priority on apparmor tasks to Critical (to match what kernel had)
- Assigning to jjohansen as the AppArmor maintainer
As we care about xenial, bionic and cosmic, we need point releases (or
cherry-pick) for:
- AppArmor 2.10 (2.10.95
In preparation for an SRU, here is a minimal C testcase provided by
Wolfgang Bumiller:
```
/*
# apparmor_parser -r /etc/apparmor.d/bug-profile
# (tested without the flags here as well btw.)
profile bug-profile flags=(attach_disconnected,mediate_deleted) {
network,
file,
unix,
}
# gcc
** Package changed: linux (Ubuntu) => ibm-java80 (Ubuntu)
--
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/1780735
Title:
[Comm] IBM JDK 8.0.5.17 integration into Ubuntu
Status in
** Tags added: block-proposed
--
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/1780227
Title:
locking sockets broken due to missing AppArmor socket mediation
patches
Status in apparmor
Hi,
Could anyone that has it working on 18.04 add plymouth:debug to their kernel
cmdline, reboot and share the /var/log/plymouth-debug.log?
I'm looking into this, but also experience the issue on 18.04. I'm
curious where the difference comes from.
Thanks!
--
You received this bug notification
Fix applied to the autotest-client-tests repo.
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
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/1751243
Title:
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16044
--
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/1780735
Title:
[Comm] IBM JDK 8.0.5.17 integration into
1 - 100 of 212 matches
Mail list logo
