[Bug 1971987] Re: On release upgrade, Snaps don't change channel
I'll attach mine since it was asked. However mine is a very old original installation and I can't remember the complete history of what I've done with snap. ** Attachment added: "upgrade log from an old installation" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1971987/+attachment/5588559/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971987 Title: On release upgrade, Snaps don't change channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1971987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880570] Re: Dock - running applications are not/delayed updated
If it helps I got the behaviour mostly fixed by disabling show-mounts and clearing out some of the desktop files in ~/.gnome/apps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880570 Title: Dock - running applications are not/delayed updated To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1880570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880570] Re: Dock - running applications are not/delayed updated
I've had this bug constantly since I updated to 20.04. Installing gnome- shell-extension-ubuntu-dock/ 67ubuntu20.04.5 did NOT fix the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880570 Title: Dock - running applications are not/delayed updated To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1880570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846016] Re: Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD GEO_TX_POWER_LIMIT
This fix is in the latest eoan kernel on the live repository. Just do standard update and reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846016 Title: Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD GEO_TX_POWER_LIMIT To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1846016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
I've fixed my problem by applying the kernel suggested in [1] [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846016 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
Same on dell Latitude E7470, only appeared after upgrading to eoan. Still present after installing backport-iwlwifi-dkms Without backport-iwlwifi-dkms iwconfig showed power management on. After backport it shows no results. Wifi still functions but crashes randomly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899806] Re: fprobe start fails with bind(): Invalid argument
Can confirm that this is resolved in lucid. With 2.6.32-37-generic install of fprobe via apt-get fails with Starting fprobe: bind(): Invalid argument With 2.6.32-38-generic install of fprobe via apt-get is successful Starting fprobe: fprobe fprobe is running and sending netflow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899806 Title: fprobe start fails with bind(): Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprobe/+bug/899806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 541512] Re: open-iscsi shutdown failure due to missing dir
I can confirm that problem replicates in our own Lucid 10.04.3. I also agree that a bug that impacts an current LTS should be fixed in the updates for the current LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/541512 Title: open-iscsi shutdown failure due to missing dir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/541512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs