Public bug reported:
Hi, Hope you are keeping well and sorry that I have to post this bug.
First I'll get the 4 questions listed here first, then add more info
afterwards:
1) lsb_release -rd
Description:Ubuntu 22.04.4 LTS
Release:22.04
2) apt-cache policy nvidia-driver-535
nvidia-d
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
bluez:
Installed: 5.64-0ubuntu1
Candi
Public bug reported:
Hi Devs,
Hope you're all keeping well.
The problem I have is similar to:
https://answers.launchpad.net/ubuntu/+question/699306
Basically Bluetooth doesn't work on installed Ubuntu 22.04.2 neither the
laptop (Dell Inspirion 7577) internal device (Intel 8265) or a USB
dongle
This issue still exists, when trying to figure out why bug #1962308 was
happening, this exact same problem still happens on 5.8.0-63 (originally
reported on 5.8.0-40).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Public bug reported:
This issue seems to have been introduced in 5.13 somewhere, I only had
5.13.0-30 and 5.13.0-28 available in grub on the 5.13 branch to test
against, but in both instances all capture devices are labelled as
"Video Capture 3" where previously it would show the device's actual
n
Fixed it! However I'm not sure why the file was created when I'm running
on AMD hardware and requiring the use of the APU.
The bug is that a blacklist file was created in:
/etc/modprobe.d/blacklist-amdgpu.conf
With the following line:
blacklist amdgpu
That obviously prevented the APU drivers t
Wow, lots of different devices have started shipping the same
fingerprint scanner since I first raised this issue.
Is there anything we can do in the community to help? Clearly there is a
need for this to be included.
--
You received this bug notification because you are a member of Kernel
Packa
I got the same as above, except I'm coming from 16.04.5.
The other thing is I only upgrade from 16.04.5 because I couldn't
actually boot into it. See bug here:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1800250
I had to upgrade using the debian-method because all normal Ubunu
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename: xenial
-
$ uname -a
Linux shark 4.10.0-35-generic #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
-
This also a
9 matches
Mail list logo