** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930783/+attachment/5502296/+files/journalctl.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930783
T
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930783/+attachment/5502291/+files/version.log
** Description changed:
Following error shows on Acer machines while booting when UEFI boot is
enabled.
integrity: Problem loading X.509 certificate
Public bug reported:
Following error shows on Acer machines while booting when UEFI boot is
enabled.
integrity: Problem loading X.509 certificate -65
The issue is discussed at
https://bugzilla.opensuse.org/show_bug.cgi?id=1129471 and a patch is
available at https://lkml.org/lkml/2019/7/16/23. Se
Please fix this bug soon. It affects many distributions based on Ubuntu
and there are no workarounds available for Ubuntu 18.04. I have attached
my system details. I couldn't find any relevant logs in syslog or pm
logs which leads to failure in hibernation.
** Attachment added: "details.txt"
h
Public bug reported:
No sound card detected at all, no sound for laptop/bluetooth headphones
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubu
this also affects budgie-remix 16.04, no gnome-flashback involved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1502476
Title:
Totem menubar is displayed in fullscreen mode during gnome-flaskback
Yes, I submitted v2 version of the patch yesterday. The two versions are
functionally equivalent and obviously I would prefer you pick up the
second version. However if the kernel is built and ready to go, I would
go with the first version. Andy is right in that there will be one more
patch that wi
This is a known bug. Our host cannot handle the WRITE_SAME command. The
fix for this bug has already been checked into the upstream kernel:
commit 3e8f4f4065901c8dfc51407e1984495e1748c090
Author: Olaf Hering
Date: Thu Feb 21 12:04:51 2013 -0800
[SCSI] storvsc: avoid usage of WRITE_SAME
