** Changed in: linux (Ubuntu Jammy)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1939528
Title:
Need support of Qualcomm WCN6856
Stat
Try installing a Nvidia driver from the Driver Manager and reboot.
--
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/2000800
Title:
Bluetooth is not being activated, I have updated with sud
Thanks for the great work!
Hotplugging thunderbolt docks definitely work better, but I still have a
couple issues.
Before I start, here is some info about my setup.
I use KDE on Arch Linux, but it shouldn't affect the problem. uname -a prints:
Linux MyPC 6.1.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed
By marking this bug Private Security it is not able to be seen by the
required developers - I am marking it public again as there doesn't
appear to be anything security relevant here.
** Information type changed from Private Security to Public
--
You received this bug notification because you a
By marking this bug Private Security it is not able to be seen by the
required developers - I am marking it public again as there doesn't
appear to be anything security relevant here.
** Information type changed from Private Security to Public
--
You received this bug notification because you ar
Thanks. So I installed 18 LTS again. A major PITA, but I used 18 LTS on
this laptop for 2 full years without a problem. Always fully upgraded,
so with all the standard permutations of kernel, modules and firmware,
on lots of different wifi networks. There was never a single issue. Nor
under 16.10 o
Public bug reported:
High-traffic ticket on stack-overflow:
https://askubuntu.com/questions/1249452/iptables-not-working-on-ubuntu-
server-raspberry-pi-4-module-ip-tables-not-fo
My own Pi4B is also failing, this prevents me from installing docker with the
following errors:
Jan 3 02:09:34 localh
MAAS deploy/release loop with focal[1] on d05-3 and has deployed for 82 times
without failure.
MAAS deploy/release loop with bionic-hwe on appleton run 100 times and 10 of
them are failed.
Look like this issue is only happened on appleton.
--
[1] For some reason I can not deploy bionic-hwe with
For next steps,
1) Find out why I can not use maas-cli to deploy bionic-hwe on d05-3
2) Collect failure logs on appleton
3) Find out the hardware difference
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
I feel your pain, having suffered the same issue just a few seconds ago.
Although there's a chance we're seeing the same symptoms with different
root causes so please be sure to open your own bug by running:
ubuntu-bug linux
Start by testing different display cables/connection types.
** Change
"Fix released" for mutter 43.0 only because a workaround was added,
which you can configure in ~/.config/monitors.xml as
...
8
But it may not help everyone. It didn't solve my issues. And so the bug
is still open for the Linux kernel.
--
You received this bug notif
11 matches
Mail list logo
