[Bug 1901348] Re: Ayatana indicators battery icon disappears
*** This bug is a duplicate of bug 1766108 *** https://bugs.launchpad.net/bugs/1766108 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ayatana-indicator-application (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901348 Title: Ayatana indicators battery icon disappears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1901348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ayatana-indicator-power (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901348] Re: Ayatana indicators battery icon disappears
*** This bug is a duplicate of bug 1766108 *** https://bugs.launchpad.net/bugs/1766108 ** This bug has been marked a duplicate of bug 1766108 Battery indicator crashes when unchecking "Show Percentage in Menu Bar" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901348 Title: Ayatana indicators battery icon disappears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1901348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830560] Re: suspend
Please try 20.04... Radeon support is much better in newer release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830560 Title: suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901694] Re: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series]
[39.611] (II) AIGLX: Screen 0 is not DRI2 capable [39.611] (EE) AIGLX: reverting to software rendering 16.04 is just old and you're not getting any (gfx) updates there anymore at this point -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901694 Title: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1901694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901803] [NEW] package grub-efi-amd64-signed 1.142.8+2.04-1ubuntu26.6 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess was killed by signal (
Public bug reported: When I command 'sudo apt upgrade', the progress bar stopped at 91%. A kworker related to grub consumed 100% CPU. (It uses only one CPU. The others were idle.) Dmesg message had error about watchdog and it occurred repeatedly. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-efi-amd64-signed 1.142.8+2.04-1ubuntu26.6 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 28 11:11:25 2020 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess was killed by signal (종료됨) InstallationDate: Installed on 2020-10-03 (24 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.142.8+2.04-1ubuntu26.6 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess was killed by signal (종료됨) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901803 Title: package grub-efi-amd64-signed 1.142.8+2.04-1ubuntu26.6 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess was killed by signal (종료됨) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1901803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
No they're not really. That's just recovery mode, required to log this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897934] Autopkgtest regression report (alsa-lib/1.2.2-2.1ubuntu2.1)
All autopkgtests for the newly accepted alsa-lib (1.2.2-2.1ubuntu2.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: asterisk/1:16.2.1~dfsg-2ubuntu1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#alsa-lib [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [SRU][Intel HDA] The initial sound level is set to zero (muted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1897934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901798] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901798 Title: Wireless-9560 limit speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend
** Tags added: xrandr-scaling -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868207 Title: Fractional scaling window sizes incorrect after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870886] Re: Window scales to 200% after screen unlocked, on desktop with external monitor
Please run this command to send us more information about the machine: apport-collect 1870886 ** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870886 Title: Window scales to 200% after screen unlocked, on desktop with external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870886] Re: Window scales to 200% after screen unlocked
Still reproducible on Groovy. It's not a laptop, it's a desktop with single monitor. Both AMD and Intel GFX have this issue. ** This bug is no longer a duplicate of bug 1868207 Fractional scaling window sizes incorrect after resume from suspend ** Summary changed: - Window scales to 200% after screen unlocked + Window scales to 200% after screen unlocked, on desktop with external monitor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870886 Title: Window scales to 200% after screen unlocked, on desktop with external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901798] [NEW] Wireless-9560 limit speed
Public bug reported: I am having wifi throughput issues. all other devices that connected to my wireless are getting 150 - 200+ Mbps download speed. I have an HP OMEN gaming laptop that cannot get pass 80mbps to download speed. Can you help me out with how to report this? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: krillavilla 5043 F pulseaudio /dev/snd/controlC1: krillavilla 5043 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 21:48:20 2020 InstallationDate: Installed on 2020-06-23 (126 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=98265a4d-5439-415e-b43c-904265a8559a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2020-10-19 (9 days ago) dmi.bios.date: 04/24/2019 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8466 dmi.board.vendor: HP dmi.board.version: 68.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 68.21 dmi.modalias: dmi:bvnAMI:bvrF.09:bd04/24/2019:br15.9:efr68.21:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn8466:rvr68.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop dmi.product.sku: 4CC49UA#ABA dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-06-26T00:47:21.524860 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901798 Title: Wireless-9560 limit speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
you're using 'nomodeset' boot option which disables things, don't do that -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901797] [NEW] The upgrade to 20.10 is not taking place
Public bug reported: The upgrade fails at new software channel's stage. It states that ubuntu-minimal cannot be located. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.8 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 28 10:11:50 2020 InstallationDate: Installed on 2019-11-13 (349 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2020-10-28 (0 days ago) VarLogDistupgradeAptlog: Log time: 2020-10-28 10:10:59.067532 Log time: 2020-10-28 10:11:17.048911 Log time: 2020-10-28 10:11:39.512525 Log time: 2020-10-28 10:12:01.084165 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901797 Title: The upgrade to 20.10 is not taking place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
** Changed in: gnome-shell (Ubuntu) Status: Expired => Incomplete ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.
That means the bluetooth controller really wakes up after started a scanning. Recent BT 4.0 controllers from Intel or Qualcomm shouldn't have this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth devices fail to re-connect after sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901790] Re: Install dual boot on Razer blade 15 pro
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD). You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM. You might also retry your installation with new media. In the event that is is not in fact an error with your installation media please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete ** Tags added: ident-mismatch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901790 Title: Install dual boot on Razer blade 15 pro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877185] Re: maxima-emacs returns LaTeX error
The attachment "latex_breqn_fix.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877185 Title: maxima-emacs returns LaTeX error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1877185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901242] Re: virt-manager local directory storage failing
** Description changed: [Impact] - * An upstream change in libvirt 6.6 [1] broke logic if creating a pool -without an explicit yes/now for COW handling. + * An upstream change in libvirt 6.6 [1] broke the logic of creating a +pool without an explicit yes/no for COW handling. - * Another upstream patch in libvirt 6.7 [2] fixes the issue. + * Another upstream patch in libvirt 6.7 [2] fixes the issue. - * Backport the patch to avoid issues with tools like virt-manager but -also with any other automation that uses define+build via api or -cmdline + * Backport the patch to avoid issues with tools like virt-manager but + also with any other automation that uses define+build via api or + cmdline [1]: https://gitlab.com/libvirt/libvirt/-/commit/7230bc95aa78379c9ee20cf59394c5fc4305b75b [2]: https://gitlab.com/libvirt/libvirt/-/commit/2edd63a0dbd445112db23596ee0128521e8f1ff5 [Test Case] - * Define a dir pool and call pool-build: + * Define a dir pool and call pool-build: $ virsh pool-define-as --name home --type dir --target /home --print-xml > home.xml $ virsh pool-define home.xml $ virsh pool-build home error: Failed to build pool home error: unable to control COW flag on '/home', not btrfs: Function not implemented $ virsh pool-start home With the fix (and with e.g. 6.0 in Focal) this works, but with libvirt 6.6 missing the fix it fails as shown above. [Regression Potential] - * Gladly a one line change there aren't much side effects to consider. -It will help a certain set of use-cases and if anything could influence -actual execution on filesystems with COW support in that case btrfs. -Now onw might think "but hey this influences BTRFS behavior", but no it -does not. The change is inside a "if btrfs magic" section. Therefore -BTRFS will not change, only the non-btrfs cases (formerly broken) will. -This is one of the rare cases I really fail to see an explicit -regression - implicit ones e.g. due to needing a rebuild could still -happen. + * Gladly a one line change there aren't many side effects to consider. + It will help a certain set of use-cases and if anything could influence + actual execution on filesystems with COW support in that case btrfs. + Now one might think "but hey this influences BTRFS behavior", but no it + does not. The change is inside an "if btrfs magic" section. Therefore + BTRFS will not change, only the non-btrfs cases (formerly broken) will. + This is one of the rare cases I really fail to see an explicit + regression - implicit ones e.g. due to needing a rebuild could still + happen. [Other Info] - - * This is upstream issue: -https://bugzilla.redhat.com/show_bug.cgi?id=1866157 + * This is upstream issue: + https://bugzilla.redhat.com/show_bug.cgi?id=1866157 --- --- - Installed KVM and Virt-Manager successfully. When trying to add storage pool as local directory on my ext4 file system, I get this error: Error creating pool: Could not build storage pool: unable to control COW flag on '/var/lib/libvirt/images/pool', not btrfs: Function not implemented Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/createpool.py", line 378, in _async_pool_create poolobj = pool.install(create=True, meter=meter, build=build) File "/usr/share/virt-manager/virtinst/storage.py", line 415, in install raise RuntimeError(errmsg) RuntimeError: Could not build storage pool: unable to control COW flag on '/var/lib/libvirt/images/pool', not btrfs: Function not implemented It seems that virt-manager is trying to disable the COW flag and returns an error because my file system is not BTRFS. Tested on 2 fresh installs of Ubuntu Studio 20.10 Tested on 1 install of Ubuntu 20.04.1 and virt-manager has no issues with local storage on ext4 file system. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: virt-manager 1:2.2.1-4ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-25.26-lowlatency 5.8.14 Uname: Linux 5.8.0-25-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Oct 24 02:15:08 2020 InstallationDate: Installed on 2020-10-07 (16 days ago) InstallationMedia: Ubuntu-Studio 20.10 "Groovy Gorilla" - Beta amd64 (20200930) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901242 Title: virt-manager local directory storage failing To manage notifications
[Bug 1893456] Re: Universal Access - Screen Keyboard Not working
[Expired for ubuntu-docs (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-docs (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893456 Title: Universal Access - Screen Keyboard Not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1893456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893497] Re: error in repositories, reinstalled ubuntu and error on installation, says disk error but is new, I changed recently
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893497 Title: error in repositories, reinstalled ubuntu and error on installation, says disk error but is new, I changed recently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890438] Re: Ubuntu Groovy proposed:networkd-dispatcher.service ModuleNotFoundError: No module named 'glib'
[Expired for networkd-dispatcher (Ubuntu) because there has been no activity for 60 days.] ** Changed in: networkd-dispatcher (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890438 Title: Ubuntu Groovy proposed:networkd-dispatcher.service ModuleNotFoundError: No module named 'glib' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1890438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions
Still broken in 5.8.0-26-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896091 Title: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1896091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
It exists in queue https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=network, which is network manager 1.22.10-1ubuntu2.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893538] Re: No bluetooth on Dell XPS 7390 with AX200 after upgrade to 20.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893538 Title: No bluetooth on Dell XPS 7390 with AX200 after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1893538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Marco, What the bluetooth module on your machine? Could you please upload the vendor ID:device ID like #49? thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901778] Re: Thunderbird crashes on start up
thunderbird running fine on my ubuntu 20.10! someone else said not running fine on 20.10 ubuntu mate ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901778 Title: Thunderbird crashes on start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866859] Re: SRU: backport Python 3.6.12, 3.7.9 and 3.8.6 to bionic
There seems to be at least one security issue with the current version of Python 3.8 in Bionic, which is still 3.8.0. See: What’s New In Python 3.8 — Python 3.8.6 documentation https://docs.python.org/release/3.8.6/whatsnew/3.8.html I.e.: Notable changes in Python 3.8.1 Due to significant security concerns, the reuse_address parameter of asyncio.loop.create_datagram_endpoint() is no longer supported. This is because of the behavior of the socket option SO_REUSEADDR in UDP. For more details, see the documentation for loop.create_ So thanks for putting this together, and I hope it is accepted soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866859 Title: SRU: backport Python 3.6.12, 3.7.9 and 3.8.6 to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/1866859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901770] Re: n_sign_posn from localeconv wrong for en_US locale
Indeed, declaring that a leading minus sign is "wrong", and parentheses are "right", for the US locale, is not supported by common usage. Both are widely used in different contexts, and Ubuntu does not deviate from the upstream behavior. We are also certainly not going to change the behavior on the 2-year-old stable release that you reported this against. To have this changed for future releases, please discuss with upstream as suggested. ** Changed in: glibc (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901770 Title: n_sign_posn from localeconv wrong for en_US locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1901770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: Boot animation never finishes, especially when external monitors (or just more than one) are connected
^^^ Is that failure reproducible? And if so, would it not be more related to the fix for bug 1880250? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: Boot animation never finishes, especially when external monitors (or just more than one) are connected To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866859] Re: SRU: backport Python 3.6.12, 3.7.9 and 3.8.6 to bionic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3.6 (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866859 Title: SRU: backport Python 3.6.12, 3.7.9 and 3.8.6 to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/1866859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866859] Re: SRU: backport Python 3.6.12, 3.7.9 and 3.8.6 to bionic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3.6 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866859 Title: SRU: backport Python 3.6.12, 3.7.9 and 3.8.6 to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-stdlib-extensions/+bug/1866859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901793] [NEW] dont know
Public bug reported: no idea ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Oct 28 08:44:30 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-01-13 (1383 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-28 (0 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.release-upgrades: [modified] mtime.conffile..etc.update-manager.release-upgrades: 2020-07-14T08:47:29.901912 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901793 Title: dont know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899633] Update Released
The verification of the Stable Release Update for v4l2loopback has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899633 Title: Repeated kernel warnings/stacktraces with kernel 5.4 and newer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1899633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: Boot animation never finishes, especially when external monitors (or just more than one) are connected
^^^ Perhaps that systemd test only used to work because it has: FSCKD_TIMEOUT = 30 which was much bigger than 2 seconds. Now that plymouth also uses 30 seconds, the systemd test might not be reliable and may need its timeout increased. If the failure continues to happen after a retry then I suggest raising the systemd test's FSCKD_TIMEOUT to 60. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: Boot animation never finishes, especially when external monitors (or just more than one) are connected To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873550] Re: Snappy daemon reaches 1min30s timeout during shutdown process
I have this bug in 20.10 (upgraded from 20.04). On shutdown it always waits for 90 seconds, then it times out and the shutdown proceeds normally. I have the same log as in: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1873550/comments/3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873550 Title: Snappy daemon reaches 1min30s timeout during shutdown process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1873550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901792] [NEW] [ICX] "perf c2c" segment fault on ICX
Public bug reported: [Feature Description] Running “perf c2c” on ICX always leads to Segment Fault, while same command works fine on CLX, as attached screenshots show with 5.8-rc6 upstream kernel. Commit Ids: 1101c872c8c7869c78dc106ae820040f36807eda (v5.9) Target Kernel: 5.9 Target Release: 21.04 [HW/SW Information] IceLake Server [Business Justification] Function enabling ** Affects: intel Importance: Undecided Status: Fix Committed ** Affects: ubuntu Importance: Undecided Status: New ** Tags: intel-kernel-21.04 ** Also affects: ubuntu Importance: Undecided Status: New ** Changed in: intel Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901792 Title: [ICX] "perf c2c" segment fault on ICX To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1901792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901129] Re: Fix broken Realtek 8821C BT after S3
Realtek's firmware was approved by upstream at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=09e8cfffdecc1f373a82e9456c6cd8810a831288 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901129 Title: Fix broken Realtek 8821C BT after S3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1901129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901791] [NEW] [ICX] Intel SST features enable for kernel config
Public bug reported: [Feature Description] enable the feature of SST in kernel config CONFIG_INTEL_SPEED_SELECT_INTERFACE Target Release: 20.10 [HW/SW Information] IceLake Server [Business Justification] Function enabling ** Affects: intel Importance: Undecided Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Tags: intel-kernel-21.04 ** Also affects: ubuntu Importance: Undecided Status: New ** Summary changed: - Intel SST features enable for kernel config + [ICX] Intel SST features enable for kernel config ** Tags added: intel-kernel-21.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901791 Title: [ICX] Intel SST features enable for kernel config To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1901791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901736] Re: Freeze
This sounds like either bug 1896110 or bug 1874578. Do you think? ** Summary changed: - Xorg freeze + Freeze ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901736 Title: Freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1901736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877185] Re: maxima-emacs returns LaTeX error
I have resolve the bug, but testing and releasing is necessary.
In a nutshell, the issue is caused by a clash of macro definitions
between `breqn` and `amsmath`.
According to http://mirror.physik-pool.tu-
berlin.de/pub/CTAN/macros/latex/contrib/breqn/breqn.pdf, Sec. 2 (package
loading), a certain order of loading packages in a document's preamble
is necessary:
```
The breqn package automatically loads amsmath to avoid loading order conflicts.
It also automatically loads flexisym and mathstyle, but in some cases these
packages need to be loaded separately.
The canonical order for package loading is:
3\usepackage{amsmath}
\usepackage{flexisym}
\usepackage{breqn}
```
That is, LaTeX template inside `imaxima.el` must be updated; patch is
attached.
A caveat though: there are TWO places where LaTeX template is defined
(see the patch), the bug is fixed by the second; I have introduced the
changes in the first part, but it must be tested.
** Patch added: "latex_breqn_fix.patch"
https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1877185/+attachment/5428184/+files/latex_breqn_fix.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877185
Title:
maxima-emacs returns LaTeX error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1877185/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814983] Re: zfs poor sustained read performance from ssd pool
Hi Colin, thanks so much for giving this another look. I don't see any
references to trying different zfs_arc_meta_limit* settings here!
I raised zfs_arc_meta_limit_percent from the default 75 to 95 and my
system has been running this ripgrep for four hours without falling to
pieces.
I think we can declare success on this one!
Thanks
# grep . /sys/module/zfs/parameters/zfs_arc_{dnode,meta}_limit*
/sys/module/zfs/parameters/zfs_arc_dnode_limit:0
/sys/module/zfs/parameters/zfs_arc_dnode_limit_percent:50
/sys/module/zfs/parameters/zfs_arc_meta_limit:0
/sys/module/zfs/parameters/zfs_arc_meta_limit_percent:95
7.97% [kernel] [k] SHA256TransformBlocks
3.33% [kernel] [k] _raw_spin_lock
2.59% [kernel] [k] arc_evict_state
2.39% [kernel] [k] mutex_lock
2.08% [kernel] [k] osq_lock
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
28555 sarnold 20 0 28.648g 0.023t 2160 S 262.8 18.8 546:39.58 rg
1567 root 20 0 0 0 0 R 71.4 0.0 1200:10 arc_reclaim
2 root 20 0 0 0 0 R 23.7 0.0 238:17.77 kthreadd
1966 root 0 -20 0 0 0 D 11.2 0.0 163:24.49 z_rd_int_2
1967 root 0 -20 0 0 0 S 11.2 0.0 163:25.54 z_rd_int_3
1968 root 0 -20 0 0 0 S 11.2 0.0 163:25.52 z_rd_int_4
# zpool iostat 1
capacity operations bandwidth
poolalloc free read write read write
[...]
-- - - - - - -
fst 2.11T 1.52T 13.8K 0 112M 0
srv 1.84T 6.32T 0 0 0 0
-- - - - - - -
fst 2.11T 1.52T 17.4K 0 146M 0
srv 1.84T 6.32T 0 0 0 0
-- - - - - - -
fst 2.11T 1.52T 17.3K 0 147M 0
srv 1.84T 6.32T 0 0 0 0
-- - - - - - -
# arc_summary
ZFS Subsystem ReportTue Oct 27 19:32:40 2020
ARC Summary: (HEALTHY)
Memory Throttle Count: 0
ARC Misc:
Deleted:688.20m
Mutex Misses: 115.54m
Evict Skips:99.92b
ARC Size: 89.14% 56.07 GiB
Target Size: (Adaptive) 9.30% 5.85GiB
Min Size (Hard Limit): 6.25% 3.93GiB
Max Size (High Water): 16:162.90 GiB
ARC Size Breakdown:
Recently Used Cache Size: 81.96% 24.51 GiB
Frequently Used Cache Size: 18.04% 5.39GiB
ARC Hash Breakdown:
Elements Max: 9.78m
Elements Current: 56.79% 5.55m
Collisions: 201.32m
Chain Max: 8
Chains: 736.70k
ARC Total accesses: 12.23b
Cache Hit Ratio:90.87% 11.12b
Cache Miss Ratio: 9.13% 1.12b
Actual Hit Ratio: 90.27% 11.04b
Data Demand Efficiency: 82.63% 666.79m
Data Prefetch Efficiency: 27.20% 14.18m
CACHE HITS BY CACHE LIST:
Most Recently Used: 30.85% 3.43b
Most Frequently Used: 68.49% 7.61b
Most Recently Used Ghost: 0.13% 13.99m
Most Frequently Used Ghost: 0.61% 67.51m
CACHE HITS BY DATA TYPE:
Demand Data: 4.96% 550.94m
Prefetch Data:0.03% 3.86m
Demand Metadata: 94.20% 10.47b
Prefetch Metadata:0.80% 89.48m
CACHE MISSES BY DATA TYPE:
Demand Data: 10.37% 115.85m
Prefetch Data:0.92% 10.32m
Demand Metadata: 82.55% 921.91m
Prefetch Metadata:6.15% 68.73m
L2 ARC Summary: (HEALTHY)
Low Memory Aborts: 116
Free on Write: 21.13k
R/W Clashes:3
Bad Checksums: 0
IO Errors: 0
L2 ARC Size: (Adaptive) 418.26 GiB
Compressed: 90.78% 379.71 GiB
Header Size:0.08% 360.27 MiB
L2
[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
OK, clarified somewhat now. This bug is back to being about just "no
screens found".
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no
screens found") from dix_main()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787332] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from systemd_logind_vtenter()
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
systemd_logind_vtenter()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
systemd_logind_vtenter()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787332
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
systemd_logind_vtenter()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1787332/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
It looks like bug 1897530 might cover this but it's unclear. The fix for that is only in Ubuntu 20.10 so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544252] Re: Xorg crashed with SIGABRT in OsAbort()
I can't see any evidence of which Xorg crash this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544252 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1544252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543141] Re: Xorg crashed with SIGABRT in OsAbort()
There's not enough information here to tell which FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543141 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545103] Re: Xorg crashed with SIGABRT in raise()
There's not enough information here to tell which FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545103 Title: Xorg crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1545103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1545158] Re: Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no screens found")
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort()
+ Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no screens
found")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545158
Title:
Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no
screens found")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1545158/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543706] Re: Xorg crashed with SIGABRT in OsAbort()
I can't tell *which* FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543706 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901790] [NEW] Install dual boot on Razer blade 15 pro
Public bug reported: crash during os install. Not sure what else to say. email me with specific questions, and I'll answer. Thanks!! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 22:27:12 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901790 Title: Install dual boot on Razer blade 15 pro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889637] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1889637 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889637 Title: Raspberry Pi 3B hangs - dev_pm_opp_set_rate: failed to find current OPP, Failed to get throttled, Failed to change plib frequency; mmc timeout waiting for hardware interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from WakeupHandler()
I think this is the wrong bug for all of those duplicates. There's no
evidence of either of those messages here. I'll see if I can split this
into other bugs...
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from
WakeupHandler()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Description changed:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
- https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics
Controller [17aa:21da]
InstallationDate: Installed on 2015-04-30 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0
panic=-1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8,
init=, fini=, rtld_fini=,
stack_end=0x7fffc9e34fc8) at libc-start.c:289
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit
code 2:
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Mon Feb 8 17:08:14 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 9847 does not
belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 728
vendor LGD
xserver.version: 2:1.17.3-2ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858351] Re: Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from AbortServer() from FatalError("no screens found")
*** This bug is a duplicate of bug 1813897 ***
https://bugs.launchpad.net/bugs/1813897
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Summary changed:
- Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("no screens found")
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError() from InitOutput()
** Summary changed:
- Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError() from InitOutput()
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("AddScreen/ScreenInit failed for driver %d\n")
from InitOutput()
** This bug has been marked a duplicate of bug 1813897
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("AddScreen/ScreenInit failed for driver %d\n")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858351
Title:
Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("AddScreen/ScreenInit failed for driver
%d\n") from InitOutput()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1858351/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276804] Re: Xorg crashed with SIGABRT in OsAbort(no screens found?)
Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from
WakeupHandler()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276804
Title:
Xorg crashed with SIGABRT in OsAbort(no screens found?)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276804/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276804] Re: Xorg crashed with SIGABRT in OsAbort(no screens found?)
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276804 Title: Xorg crashed with SIGABRT in OsAbort(no screens found?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901789] [NEW] Release upgrade 20.04 -> 20.10 removed input method from ibus
Public bug reported: What happened: === I'm using iBus as input "method" with - Japanese (Anthy) // primary - German set up. I upgraded from ubuntu 20.04 to 20.10. EXPECTED: No changes regarding input. ACTUAL: German input method was removed lsb_release -rd === Description:Ubuntu 20.10 Release:20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Oct 28 11:10:04 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901789 Title: Release upgrade 20.04 -> 20.10 removed input method from ibus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791981] Re: X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
** Summary changed: - X Server session crash for "No space left on device" + X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" ** Summary changed: - X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" + [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1791981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901695] Re: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver)
*** This bug is a duplicate of bug 1791981 *** https://bugs.launchpad.net/bugs/1791981 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1791981, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: focal ** This bug has been marked a duplicate of bug 1791981 X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901695 Title: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary driver) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
I spoke too soon. Deep sleep works now, and the touchpad keeps working, but only - even with the new motherboard - if I keep the NFC *enabled* in the BIOS. And the trackpoint does not work under Linux. At all. At any time (at least on my distro) and even with a very recent kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901694] Re: [radeon] No hardware aceleration
It appears the Xorg radeon driver is working. It's only 3D that's not working so that's Mesa. ** Summary changed: - No hardware aceleration + [radeon] No hardware aceleration ** Summary changed: - [radeon] No hardware aceleration + [radeon] No hardware acceleration ** Tags added: radeon ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Summary changed: - [radeon] No hardware acceleration + [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901694 Title: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1901694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889637] Re: Raspberry Pi 3B hangs - dev_pm_opp_set_rate: failed to find current OPP, Failed to get throttled, Failed to change plib frequency; mmc timeout waiting for hardware interrupt
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889637 Title: Raspberry Pi 3B hangs - dev_pm_opp_set_rate: failed to find current OPP, Failed to get throttled, Failed to change plib frequency; mmc timeout waiting for hardware interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
Yep, the detailed mode 2560x1440 is in the EDID returned by the monitor: Standard Timings: none Detailed mode: Clock 241.500 MHz, 598 mm x 336 mm 2560 2608 2640 2720 ( 48 32 80) 1440 1443 1448 1481 ( 3 5 33) +hsync -vsync VertFreq: 59.951 Hz, HorFreq: 88.787 kHz Display Product Serial Number: GBLMQS047683 Display Range Limits Monitor ranges (Bare Limits): 24-60 Hz V, 30-140 kHz H, max dotclock 300 MHz Display Product Name: ROG PG278QR -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901538] Re: Output Device selection messed (Line Out <-> HDMI)
No problem. If there are no more comments after 60 days then the bug will close automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901538 Title: Output Device selection messed (Line Out <-> HDMI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901724] Re: Systemd user environment generator is not executable.
I thought gnome-shell started its own agent for ssh on startup? Or did you configure your system to run the gnupg agent before starting gnome? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901724 Title: Systemd user environment generator is not executable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1901724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896482] Re: acpi event detection crashes
Hi Alex, my problem came back. Is it possible that livepatch has replaced my working kernel with the broken one again? --Jim On Thu, 24 Sep 2020, Alex Hung wrote: > A test kernel with target patches ready for SRU is available @ > https://people.canonical.com/~alexhung/LP1896482/fixes/ > > The patch in #23 requires three precedent patches. See SRU.log file for > more details. > > Note it is rebased Ubuntu-5.4.0-48.52 now. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] >
[Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
I would like to check to see if the problem is occurring in the kernel and not just in Xorg. Please run: grep . /sys/class/drm/*/modes > modes.txt and then attach the resulting text file here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894942] Autopkgtest regression report (qemu/1:2.11+dfsg-1ubuntu7.33)
All autopkgtests for the newly accepted qemu (1:2.11+dfsg-1ubuntu7.33) for bionic have finished running. The following regressions have been reported in tests triggered by the package: libvirt/4.0.0-1ubuntu8.17 (i386) systemd/237-3ubuntu10.42 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#qemu [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894942 Title: [UBUNTU 20.04] Lost virtio host --> guest notifications cause devices to cease normal operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1894942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861941] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf) python-dbusmock/0.19-1 (armhf) lxc/1:4.0.2-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895418] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf) python-dbusmock/0.19-1 (armhf) lxc/1:4.0.2-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895418 Title: systemd-resolved default config for Caching is still "yes" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892358] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf) python-dbusmock/0.19-1 (armhf) lxc/1:4.0.2-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897744] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf) python-dbusmock/0.19-1 (armhf) lxc/1:4.0.2-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897744 Title: VerifyHostKeyDNS not working due to missing trust-ad flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901119] Re: nvidia-340
*** This bug is a duplicate of bug 1872950 *** https://bugs.launchpad.net/bugs/1872950 ** This bug has been marked a duplicate of bug 1872950 Nvidia 340.108 fails to install with kernels 5.5 onward -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901119 Title: nvidia-340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1901119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882596] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf) python-dbusmock/0.19-1 (armhf) lxc/1:4.0.2-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882596 Title: systemd.unit(5) incorrectly refers to systemd.syntax(5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
** Summary changed: - Nvidia 340.108 fails to install with kernels 5.5 and 5.6 + Nvidia 340.108 fails to install with kernels 5.5 onward ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided => High ** Tags added: focal groovy ** Tags removed: focal ** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.
The fix was written by upstream, and the downstream fix is being packaged by Marco. So I'm not involved in either of those. ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Changed in: mutter (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: mutter (Ubuntu Groovy) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/199 Title: Window tiled to monitor where most of the window is in instead of where the mouse is. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873914] Re: initramfs clevis no carrier after 1s, no retry
This bug was fixed in the package clevis - 12-1ubuntu2.2 --- clevis (12-1ubuntu2.2) focal; urgency=medium * initramfs: Fix parsing of interface names when bringing the network back down in local-bottom, which also avoids a mess of "ip: can't find device '/sys/class/net/$iface'" errors on the console. LP: #1896294. * initramfs: Warn users with multiple interfaces that they should consider specifying an 'ip=' parameter for reliable operation. LP: #1896289. As a side-effect, also fix interface parsing while bringing links up. LP: #1873593. * initramfs: Wait for interface to appear before attempting configuration. LP: #1873914. * initramfs: Make network configuration as-needed. This functionality depends on the new clevis-luks-list command which is also backported. LP: #1896509. -- dann frazier Tue, 13 Oct 2020 17:00:47 -0600 ** Changed in: clevis (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873914 Title: initramfs clevis no carrier after 1s, no retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1873914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873593] Re: clevis-initramfs no ethernet because of Error: argument " enp2s0" is wrong: "dev" not a valid ifname
This bug was fixed in the package clevis - 12-1ubuntu2.2 --- clevis (12-1ubuntu2.2) focal; urgency=medium * initramfs: Fix parsing of interface names when bringing the network back down in local-bottom, which also avoids a mess of "ip: can't find device '/sys/class/net/$iface'" errors on the console. LP: #1896294. * initramfs: Warn users with multiple interfaces that they should consider specifying an 'ip=' parameter for reliable operation. LP: #1896289. As a side-effect, also fix interface parsing while bringing links up. LP: #1873593. * initramfs: Wait for interface to appear before attempting configuration. LP: #1873914. * initramfs: Make network configuration as-needed. This functionality depends on the new clevis-luks-list command which is also backported. LP: #1896509. -- dann frazier Tue, 13 Oct 2020 17:00:47 -0600 ** Changed in: clevis (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873593 Title: clevis-initramfs no ethernet because of Error: argument " enp2s0" is wrong: "dev" not a valid ifname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1873593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896509] Re: initramfs always tries to bring up the network even when unnecessary
This bug was fixed in the package clevis - 12-1ubuntu2.2 --- clevis (12-1ubuntu2.2) focal; urgency=medium * initramfs: Fix parsing of interface names when bringing the network back down in local-bottom, which also avoids a mess of "ip: can't find device '/sys/class/net/$iface'" errors on the console. LP: #1896294. * initramfs: Warn users with multiple interfaces that they should consider specifying an 'ip=' parameter for reliable operation. LP: #1896289. As a side-effect, also fix interface parsing while bringing links up. LP: #1873593. * initramfs: Wait for interface to appear before attempting configuration. LP: #1873914. * initramfs: Make network configuration as-needed. This functionality depends on the new clevis-luks-list command which is also backported. LP: #1896509. -- dann frazier Tue, 13 Oct 2020 17:00:47 -0600 ** Changed in: clevis (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896509 Title: initramfs always tries to bring up the network even when unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1896509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896294] Re: ip: can't find device '/sys/class/net/enp1s0'
This bug was fixed in the package clevis - 12-1ubuntu2.2 --- clevis (12-1ubuntu2.2) focal; urgency=medium * initramfs: Fix parsing of interface names when bringing the network back down in local-bottom, which also avoids a mess of "ip: can't find device '/sys/class/net/$iface'" errors on the console. LP: #1896294. * initramfs: Warn users with multiple interfaces that they should consider specifying an 'ip=' parameter for reliable operation. LP: #1896289. As a side-effect, also fix interface parsing while bringing links up. LP: #1873593. * initramfs: Wait for interface to appear before attempting configuration. LP: #1873914. * initramfs: Make network configuration as-needed. This functionality depends on the new clevis-luks-list command which is also backported. LP: #1896509. -- dann frazier Tue, 13 Oct 2020 17:00:47 -0600 ** Changed in: clevis (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896294 Title: ip: can't find device '/sys/class/net/enp1s0' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1896294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896289] Re: user should be warned about problems with multiple nics
This bug was fixed in the package clevis - 12-1ubuntu2.2 --- clevis (12-1ubuntu2.2) focal; urgency=medium * initramfs: Fix parsing of interface names when bringing the network back down in local-bottom, which also avoids a mess of "ip: can't find device '/sys/class/net/$iface'" errors on the console. LP: #1896294. * initramfs: Warn users with multiple interfaces that they should consider specifying an 'ip=' parameter for reliable operation. LP: #1896289. As a side-effect, also fix interface parsing while bringing links up. LP: #1873593. * initramfs: Wait for interface to appear before attempting configuration. LP: #1873914. * initramfs: Make network configuration as-needed. This functionality depends on the new clevis-luks-list command which is also backported. LP: #1896509. -- dann frazier Tue, 13 Oct 2020 17:00:47 -0600 ** Changed in: clevis (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896289 Title: user should be warned about problems with multiple nics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1896289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872159] Re: Boot animation never finishes, especially when external monitors (or just more than one) are connected
^^^ I am skeptical that's a real failure. Can someone hit retry? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: Boot animation never finishes, especially when external monitors (or just more than one) are connected To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1872159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894627] Re: [nvidia] Web browser distorted after hibernation/power save when idle
Please don't discuss that here. You should open a new bug by running: ubuntu-bug linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894627 Title: [nvidia] Web browser distorted after hibernation/power save when idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550779] Re: Black screen flickering and [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
** No longer affects: xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550779 Title: Black screen flickering and [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.
i just had a bug for 20.10 merged into this one. note that in my case, this just started happening since upgrading to 20.10, and it happens with multiple different brands of bluetooth adaptor. as well, if use my keyboard to open the bluetooth settings panel in gnome, then everything immediately reconnects as soon as the settings load, so it doesn't appear to be anything to do with hardware, but instead a bug in terms of what gnome services do when the system resumes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth devices fail to re-connect after sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896289] Update Released
The verification of the Stable Release Update for clevis has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896289 Title: user should be warned about problems with multiple nics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1896289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896509] Update Released
The verification of the Stable Release Update for clevis has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896509 Title: initramfs always tries to bring up the network even when unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1896509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873914] Update Released
The verification of the Stable Release Update for clevis has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873914 Title: initramfs clevis no carrier after 1s, no retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1873914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812430] Re: intel hd 500 - j3455 no graphic driver
This bug is closed. Please open a new bug if you have any problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812430 Title: intel hd 500 - j3455 no graphic driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1812430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896294] Update Released
The verification of the Stable Release Update for clevis has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896294 Title: ip: can't find device '/sys/class/net/enp1s0' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1896294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873593] Update Released
The verification of the Stable Release Update for clevis has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873593 Title: clevis-initramfs no ethernet because of Error: argument " enp2s0" is wrong: "dev" not a valid ifname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1873593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
I'm using Acer Swift SF514-52T (Intel 8th Gen Core i5) on Ubuntu 20.10 - Linux kernel 5.8. The default configuration has no sound working at all. I believe it uses the SOF driver (I could be wrong) which doesn't support the Kaby Lake platform, as the issues for supporting this platform have been closed ( https://github.com/thesofproject/sof/issues/1899 ). And the proposed workaround to support this platform have been discarded also ( https://github.com/thesofproject/sof/issues/2256 ). Therefore installing the latest version or any version of the SOF driver will not solve the issue. Force enable the HDA driver (snd_hda_intel) in /etc/modprobe.d/alsa- base.conf with options snd-intel-dspcfg dsp_driver=1, the sound output works fine but the internal mic (DMIC) doesn't work. And I believe we're moving to the SOF driver which doesn't support my device. Therefore I don't expect any fix will be done in HDA driver. I tried to use Intel's SST driver as it's the only solution left. I enabled it with options snd-intel-dspcfg dsp_driver=2 but both the sound output and the internal mic (DMIC) don't work. I also report this bug in https://bugzilla.kernel.org/show_bug.cgi?id=201251 Here is my alsa-info (with options snd-intel-dspcfg dsp_driver=2): http ://alsa-project.org/db/?f=db024ae3c924d318bda813f73c73e76df36bbca2 I attached my full dmesg also. ** Bug watch added: github.com/thesofproject/sof/issues #1899 https://github.com/thesofproject/sof/issues/1899 ** Bug watch added: github.com/thesofproject/sof/issues #2256 https://github.com/thesofproject/sof/issues/2256 ** Bug watch added: Linux Kernel Bug Tracker #201251 https://bugzilla.kernel.org/show_bug.cgi?id=201251 ** Attachment added: "dmesg on Acer Swift SF514-52T running Ubuntu 20.10" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+attachment/5428164/+files/dmesg_messages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896509] Re: initramfs always tries to bring up the network even when unnecessary
This bug was fixed in the package clevis - 8-1ubuntu0.2 --- clevis (8-1ubuntu0.2) bionic; urgency=medium * initramfs: Fix parsing of interface names when bringing the network back down in local-bottom, which also avoids a mess of "ip: can't find device '/sys/class/net/$iface'" errors on the console. LP: #1896294. * initramfs: Warn users with multiple interfaces that they should consider specifying an 'ip=' parameter for reliable operation. LP: #1896289. As a side-effect, also fix interface parsing while bringing links up. LP: #1873593. * initramfs: Wait for interface to appear before attempting configuration. LP: #1873914. * initramfs: Make network configuration as-needed. This functionality depends on the new clevis-luks-list command which is also backported. LP: #1896509. Requires new build-dep on asciidoctor in order to build the clevis-luks-list manpage. -- dann frazier Wed, 14 Oct 2020 11:23:01 -0600 ** Changed in: clevis (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896509 Title: initramfs always tries to bring up the network even when unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1896509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873593] Re: clevis-initramfs no ethernet because of Error: argument " enp2s0" is wrong: "dev" not a valid ifname
This bug was fixed in the package clevis - 8-1ubuntu0.2 --- clevis (8-1ubuntu0.2) bionic; urgency=medium * initramfs: Fix parsing of interface names when bringing the network back down in local-bottom, which also avoids a mess of "ip: can't find device '/sys/class/net/$iface'" errors on the console. LP: #1896294. * initramfs: Warn users with multiple interfaces that they should consider specifying an 'ip=' parameter for reliable operation. LP: #1896289. As a side-effect, also fix interface parsing while bringing links up. LP: #1873593. * initramfs: Wait for interface to appear before attempting configuration. LP: #1873914. * initramfs: Make network configuration as-needed. This functionality depends on the new clevis-luks-list command which is also backported. LP: #1896509. Requires new build-dep on asciidoctor in order to build the clevis-luks-list manpage. -- dann frazier Wed, 14 Oct 2020 11:23:01 -0600 ** Changed in: clevis (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873593 Title: clevis-initramfs no ethernet because of Error: argument " enp2s0" is wrong: "dev" not a valid ifname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1873593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873914] Re: initramfs clevis no carrier after 1s, no retry
This bug was fixed in the package clevis - 8-1ubuntu0.2 --- clevis (8-1ubuntu0.2) bionic; urgency=medium * initramfs: Fix parsing of interface names when bringing the network back down in local-bottom, which also avoids a mess of "ip: can't find device '/sys/class/net/$iface'" errors on the console. LP: #1896294. * initramfs: Warn users with multiple interfaces that they should consider specifying an 'ip=' parameter for reliable operation. LP: #1896289. As a side-effect, also fix interface parsing while bringing links up. LP: #1873593. * initramfs: Wait for interface to appear before attempting configuration. LP: #1873914. * initramfs: Make network configuration as-needed. This functionality depends on the new clevis-luks-list command which is also backported. LP: #1896509. Requires new build-dep on asciidoctor in order to build the clevis-luks-list manpage. -- dann frazier Wed, 14 Oct 2020 11:23:01 -0600 ** Changed in: clevis (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873914 Title: initramfs clevis no carrier after 1s, no retry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1873914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
