@askalski: this could be due to the change in procedure for installing
packages from the proposed repository since Noble. After enabling the
pre-release updates in the 'Developer options' tab of 'Software &
updates', enter the following on the command line to selectively install
the bluez package:
I installed the bluez package from the proposed repository and my
bluetooth audio devices are finally reconnecting again automatically
after a reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.
I have tried kernel 5.15.0-68.75 in jammy on a Precision 5720 AIO and I
no longer see messages that it "Could not resolve symbol
[\_PR.CPU*._CPC]". In that sense, this fix partially addresses
https://bugzilla.kernel.org/show_bug.cgi?id=213023. However, acpi_cppc
support still appears to be absent a
@il_santo: you should probably submit a separate bug report for this
issue as it is likely unrelated to the module signing issue that was
addressed here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Ah, my apologies. After reinstalling from the -proposed pocket the
5.3.0-23.25~18.04.2 kernel is indeed booting properly.
--
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/1852581
Title:
hw
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
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/1852581
Title:
hwe-edge kernel 5.3.0-23.25 kernel doe
I gave 5.3.0-23.25~18.04.2 on the canonical kernel team ppa a try, but
it looks like the signing issue still persists.
--
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/1852581
Title:
hwe-e
Ok, scratch that. I had an external monitor connected and didn't realize
a configure dialog appeared on reboot. After disabling validation the
vboxdrv module now loads as expected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Thanks, I just gave this a shot after installing 4.4.0-21-generic #37
from -proposed but after running 'sudo mokutil --disable-validation' and
rebooting I still have the same 'Required key not available' error when
I 'sudo modprobe vboxdrv'.
--
You received this bug notification because you are a
I'm not sure if this is the right venue for discussion, but ever since
this change was implemented in 4.4.0-18 I have been unable to load the
VirtualBox vboxdrv kernel module built through dkms (fails with
'required key not available'). I understand this is probably the
intended behavior but becaus
Public bug reported:
There is a conflict between packages linux-tools-common and linux-lts-
vivid-tools-common
ProblemType: Package
DistroRelease: Ubuntu 14.04
ProcVersionSignature: Ubuntu 3.19.0-16.16~14.04.2-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.10
11 matches
Mail list logo
