[ 7609.135055] [ cut here ]
[ 7609.135057] kernel BUG at /home/kernel/COD/linux/drivers/md/raid5.c:1762!
[ 7609.135065] invalid opcode: [#1] SMP PTI
[ 7609.135069] CPU: 2 PID: 302 Comm: md0_raid5 Not tainted
4.18.0-041800rc5-generic #201807152130
[ 7609.135071] Hardwar
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Also affects: qa-regression-testing
Importance: Undecided
Status: New
** Also affects: apparmor
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Pa
The CONFIG_CC_STACKPROTECTOR issue was addressed in bug 1776242, leaving
the apparmor test failure to resolve.
--
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/1779314
Title:
linux 4.17.0-
ged in: apparmor
Assignee: (unassigned) => Steve Beattie (sbeattie)
** Changed in: qa-regression-testing
Assignee: (unassigned) => Steve Beattie (sbeattie)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
** Changed in: dkms (Ubuntu)
Status: New => Fix Committed
** Changed in: dkms (Ubuntu)
Importance: Undecided => High
--
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/1781001
Title:
** Description changed:
[Impact]
- All users of third-party modules on Ubuntu.
+ All users of third-party modules on Ubuntu when running under SecureBoot
experience a package manager hang trying to initially configure the dkms
package.
[Test cases]
1) Install Ubuntu on an UEFI system
Hello rew, or anyone else affected,
Accepted dkms into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu9.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubunt
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
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/1782173
Title:
linux: 4.15.0-29.31 -proposed
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1782176
Title:
linux-aws: 4.15.0-1016.16
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
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/1782181
Title:
linux-oem: 4.15.0-1012.15
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1782180
Title:
linux-kvm: 4.15.0-1016.16
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1782184
Title:
linux-gcp: 4.15.0-1014.14
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
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/1782478
Title:
linux: 4.15.0-29.31 -proposed
> Test seems to be renamed
Correct, I restructured the test script in question a bit, separating
out the config checks from the behavioral checks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad
lp1779817 kernel from #19 doesn't help me, last working kernel is
4.15.0-23.
--
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 l
Hi Po-Hsu,
Alas, I'm not able to reproduce this in a kvm guest with only 768k:
Ran 56 tests in 1026.130s
OK
ubuntu@sec-bionic-amd64:~/tests/qrt-test-apparmor$ free -m
totalusedfree shared buff/cache available
Mem:733 543 59
A bit off-topic but: on a third machine of mine, booting into into
Bionic leaves the network card in a state where WoL won't work at all,
even after rebooting back into Trusty (3.13.0.) Have to power cycle the
machine, then WoL is fine.. (r8169 driver again, obviously)
--
You received this bug no
** Changed in: debian-installer (Ubuntu)
Milestone: None => ubuntu-16.04.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/1784454
Title:
kernel panic on booting kernel 4.4 based d-i
Is this even from a cold boot? Similar issues being discussed at bug
#1779817 and bug #1752772 but that is only after suspension.
--
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/1784542
Tit
I still think there are multiple bugs here. Some of us have a network that
absolutely will not come back up after suspend with kernel version
>4.15.0-23, even after reloading the driver. So there is a very clear
regression that I would really like see resolved / rolled back. Breaking
stuff in an LT
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
I've just built net-next direct from git and still have the same issue -
the NIC doesn't come back after suspend, even with rmmod / modprobe.
Is there any upstream awareness of this? Bug tracker and/or mailing list
discussion?
--
You received this bug notification because you are a member of Ker
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
I can't even boot Kai's latest kernel! The system hard locks early in the
boot process, I have tried blacklisting r8169 and rebuilding the initramfs,
pretty sure it is not loaded by the point at which it hangs. My hardware is
cursed...
On 7 August 2018 at 21:13, Jan Rathmann wrote:
> @Kai-Heng
>
Progress!
I have built ubuntu-bionic.git myself and discovered the only commit I
have to revert to get things working again is this one:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=41450d46ba126887b9548cfcdf99957da5418ca5
@Kai, does that help you at all? If nothing else mig
I'm about to dash out, but will try the above change later. Meanwhile,
relevant bits of dmesg:
[4.440185] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[4.445120] r8169 :01:00.0: enabling device ( -> 0003)
[4.458178] r8169 :01:00.0 eth0: RTL8168g/8111g at 0x
(ptrval), 84:
Hmm, no "IOMMU" messages in dmesg, and the CPU is supposed to support it,
so I guess it is disabled,
however this machine really doesn't have a BIOS to speak of, in terms of
configurable settings anyway :(
On 8 August 2018 at 14:42, Heiner Kallweit <1779...@bugs.launchpad.net>
wrote:
> One more h
Ok, testing now... will report back...
--
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/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux package in U
@kalle1
Your one liner seems to fix things - thank you! Also discovered I can
work around by writing 0 to /sys/devices/pci//msi_bus, which will
at least mean I can run unpatched Ubuntu kernels until we figure this
out :)
Anybody still having problems and wanting to test if this is their issue
is
Just double-checked with lspci -vvv and indeed the Realtek NIC is the only
MSI-X capable device. Is there anyway to disable MSI-X globally but leave
MSI on? All I can find is pci=nomsi which seems a bit heavy handed..
On 9 August 2018 at 10:08, Steve Dodd wrote:
> Yup, afraid so, Beelink
Yup, afraid so, Beelink S1: https://www.amazon.co.uk/dp/B077HKCT78 - I'm
basically using it as an old-fashioned X Terminal. They promised a BIOS
update to "make it work with Linux" but I never got it to install and they
stopped answering my emails :( Happy to put it down to broken hardware so
long
$ cat /proc/cmdline
BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-3-generic
root=UUID=0885f579-b2ff-4c94-964c-d65c30bb7761 ro rootflags=subvol=@
nvme_core.force_apst=1
Been through several cycles of suspend and resume, without any apparent
issues.
But I note:
$ sudo nvme id-ctrl /dev/nvme0n1
ps0 :
It's was only Kai's kernel from comment #39 that didn't boot - I've not had
any other problems on that front.
On 9 August 2018 at 12:05, Heiner Kallweit <1779...@bugs.launchpad.net>
wrote:
> Whether other systems suffer from the same MSI-X incompatability we'll
> know only once I get more such bu
@Heiner, I know a number of other modules have a "use_msi_x" option - I
guess that would be too much to ask given I'm the only one who seems to
need it so far? :)
On 9 August 2018 at 16:54, David Jordan wrote:
> I can reproduce the issue with ethernet failing on the r8169 on resume
> from suspen
The log output included in your bug report appears to show a hang in the
kernel video driver; reassigning.
But also, your bug description mentions a bios virus. If your bios is
compromised, it's unlikely we can do anything to fix it from Ubuntu.
** Package changed: plymouth (Ubuntu) => linux (Ub
t/?id=1261ef7eb84dd5eeafcf4bca6e20ae50422d029a
Thanks!
** Also affects: qa-regression-testing
Importance: Undecided
Status: New
** Changed in: qa-regression-testing
Status: New => Fix Released
** Changed in: qa-regression-testing
Assignee: (unassigned) => Steve Beattie (sbeattie)
** Changed in
commit/?id=9040cc59e48f12a8aa586db383464553956ed656
Thanks!
** Changed in: qa-regression-testing
Status: New => Fix Released
** Changed in: qa-regression-testing
Assignee: (unassigned) => Steve Beattie (sbeattie)
** Changed in: linux-aws (Ubuntu)
Status: New => Invalid
--
You received th
The bug description now says "but more testing may be desirable."
Please be explicit and detailed, here. We need a test plan for what
that testing is going to be, otherwise there's no reason to expect that
it will happen.
** Changed in: crash (Ubuntu Bionic)
Status: In Progress => Incomple
According to https://wiki.debian.org/Arm64Port, gcc-4.8 did not support
libssp/-fstack-protector on arm64. I've committed a fix that should
address this in QRT in https://git.launchpad.net/qa-regression-
testing/commit/?id=63a5c8e6ab8f82817337ffdac0258c17ef443b48
Please let me know if this does no
** Changed in: qa-regression-testing
Status: Fix Released => 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/1747852
Title:
test_072_strict_devmem in ubuntu_qrt_kernel_se
Actually, this is an accidental pass, the reason is that the
CONFIG_DEVMEM option did not come into being until the 3.19 kernel. I've
adjusted the tests for that in https://git.launchpad.net/qa-regression-
testing/commit/?id=f405927a76483d29f3a6bde092ebc29d7de6d945 .
Given that CONFIG_STRICT_DEVME
Can we cherry-pick
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=7c53a722459c1d6ffb0f5b2058c06ca8980b8600
for bionic?
On 10 August 2018 at 12:49, Heiner Kallweit <1779...@bugs.launchpad.net>
wrote:
> @Steve, there's some resistance amongst kern
** Changed in: kernel-sru-workflow/security-signoff
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/1811419
Title:
linux: 4.15.0-44.47 -proposed
** Changed in: kernel-sru-workflow/security-signoff
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/1811846
Title:
linux: 4.4.0-142.168 -propose
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1811847
Title:
linux-aws: 4.4.0-1038.41
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1811857
Title:
linux-lts-trusty:
** Changed in: kernel-sru-workflow/security-signoff
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/1811856
Title:
linux: 3.13.0-165.215 -propos
** Changed in: grub2 (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/1528345
Title:
grub or kernel update broke Secure Boot by putting grubx64
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
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/1811850
Title:
linux-ibm-gt: 4.15.0-1015.17
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
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/1813779
Title:
linux: 4.15.0-45.48 -proposed
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve
Langasek (vorlon)
** Changed in: kernel-sru-workflow/promote-to-se
Public bug reported:
Have installed this twice through Update Manager. It does not function
on my Sony Vaio laptop running Mint 19. I have to select previous
kernel, then computer is fine.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug
d64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: steve 1230 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 19
+ HibernationDevice: RESUME=UUID=260db35a-0a3f-4f50-ad5c-a4ba614b4ba1
+ InstallationDate: Installed on 2018-07-10 (211 days
roblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f
mType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f-4f50-ad5c-a4
mType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f-4f50-ad5c-a4
roblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f
mType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f-4f50-ad5c-a4
er is fine.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a
roblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f
mType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f-4f50-ad5c-a4
mType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f-4f50-ad5c-a4
roblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f
mType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f-4f50-ad5c-a4
er is fine.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f
mType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f-4f50-ad5c-a4
roblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: steve 1230 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19
HibernationDevice: RESUME=UUID=260db35a-0a3f-4f50-ad5c-a4
** Package changed: plymouth (Ubuntu) => linux (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/1815152
Title:
kernel hangs on boot after "fb: switching to inteldrmfb from VESA VG
I think the test and regression potential templates on this bug are not
up to the normal SRU standard. There are a number of firmware blobs
updated, what is the set of chips that make use of these firmware blobs
that could potentially be affected by this update? Why is this complete
range of firm
This SRU claims for regression-potential:
> Low. The quirk uses strict DMI to match affected systems.
This doesn't appear to be true for the changes to upower, which include
no DMI quirking whatsoever. Please clarify this.
** Changed in: upower (Ubuntu Bionic)
Status: Fix Committed => In
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
Mint 19.1 now boots using the latest kernel 4.18.0-15.16
--
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/1814555
Title:
Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)
Status
Marek, Secure Boot is a UEFI feature. It is not possible for you to
have Secure Boot blocking a kernel boot if you do not have UEFI.
It is possible that your EFI System Partition is not mounted at
/boot/efi, if you have modified your /etc/fstab since installation. For
the system to boot at all u
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
On Thu, Feb 14, 2019 at 10:44:34PM -, Marek Hák wrote:
> The output of 'efibootmgr -v' showed me where the EFI partition is, but
> I have no idea where it's mounted or how to get to it.
> Boot0004* ubuntuHD(2,GPT,83484852-541d-401e-
> 84e7-6e6e8549496a,0x1f4800,0x82000)/File(\EFI\ubunt
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a
1401 - 1500 of 9340 matches
Mail list logo
