[Bug 1897378] Re: [SRU] liblzf backport to focal
** Changed in: liblzf (Ubuntu) Status: Confirmed => 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/1897378 Title: [SRU] liblzf backport to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblzf/+bug/1897378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
Based on this new result, SRU libjcat back to focal is optional. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
This build ran 10:26 -> 10:33 and the crash happened "in between". As i said in local sbuild those are not fatal but on LP they are. Therefore attaching the build log ... ** Attachment added: "build log that did not exit fatally, but triggered the crash we also see on LP (there fatally)" https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1958389/+attachment/774/+files/xen_4.16.0-1~ubuntu1~jammyppa3_amd64-2022-01-18T10%3A26%3A25Z.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
The build log I attached above shall help to spot the versions needed for debug symbols to read this crash correctly. ** Attachment added: "Crash file of x86_64-linux-gnu-ld.bfd as seen in local sbuild" https://bugs.launchpad.net/ubuntu/+source/xen/+bug/1958389/+attachment/775/+files/_usr_bin_x86_64-linux-gnu-ld.bfd.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
Thanks for the hint, in case anyone needs to do the same - you can see the associated builder right when the build starts - then abort it immediately, refresh and rebuild. That way you get 1 build try <1min, I got lgw01 018 lgw01 044 lgw01 023 lcy02 001 And the build on the latter I let finish which indeed let it build successfully. That also means the crash I got locally is actually relevant to doko or anyone else looking for this from binutils POV. Therefore I'll attach mine. ** Changed in: xen (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
** Changed in: snapd (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/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958022] Re: fish integration broken in focal
*** This bug is a duplicate of bug 1957948 *** https://bugs.launchpad.net/bugs/1957948 ** This bug has been marked a duplicate of bug 1957948 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958022 Title: fish integration broken in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1958022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958109] Re: [MIR] v4l2-relayd
** Description changed: [Background] https://gitlab.com/vicamo/v4l2-relayd [Impact] With this package, we can use the v4l2loopback device to bridge any video content by gstreamer as a virtual camera device. We need this with LP: #1958108 - [Canonical Partners] ipu6-camera-bins, ipu6-camera-hal, gst-plugins-icamera to enable Intel MIPI camera. [Testing] 1. Install v4l2-relayd and v4l2loopback-dkms. - 2. Modify /etc/default/v4l2-relayd to make VIDEOSRC=videotestsrc, FORMAT=YUV2, WIDTH=1280, HEIGHT=720, FRAMERATE=30/1 and CARD_LABEL="Intel MIPI Camera". + 2. Modify /etc/default/v4l2-relayd to make VIDEOSRC=videotestsrc, FORMAT=YUY2, WIDTH=1280, HEIGHT=720, FRAMERATE=30/1 and CARD_LABEL="Intel MIPI Camera". 3. Reboot the system 4. We should be able to use the virtual camera. [Regression Potential] None [Availability] You can find the package on https://launchpad.net/~oem-solutions- group/+archive/ubuntu/intel-ipu6. [Rationale] We want to improve the hardware support for some Dell/HP/Lenovo laptops. [Security] No CVE/known security issue. [Quality assurance] We have used this package to enable Intel MIPI camera on some Dell laptops and some of them will be cerified by Ubuntu certification soon. [Dependencies] This package can be executed with videotestsrc or other video source of gstreamer. [Standards compliance] [Maintenance] [Background information] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958109 Title: [MIR] v4l2-relayd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders
Thanks Colin, even without debug symbols that still is probably enough to confirm it is actually the same crash that I see on my laptop. While I do not see why it is fatal for the build on LP but not on local sbuild or dpkg-buildpkg in a local VM it means that most likely someone looking into this from the binutils POV can reproduce it the way I outlined in my report on most common intel laptops. In use here I have: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz Maybe you could add what chip the failing lgw01 builders use to try isolating the affected series? /me is trying to retry until it ran on an lcy02 builder now ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958389 Title: Jammy builds of xen segfault, but only on launchpad x86 builders To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
I was able to fix it for Pop!_Os 21.10 only with 5.16.1 kernel, the model is ThinkPad E14 G2 (20ta002grt), updates to any 5.15 didn't help me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking
** Attachment added: "IMG_20220120_073821207.jpg" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+attachment/771/+files/IMG_20220120_073821207.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958494] [NEW] After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking
Public bug reported: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/770/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/767/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/765/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/769/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/768/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/766/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/764/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/759/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/763/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/762/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/761/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/758/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/760/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/757/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/756/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/755/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/754/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Re: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility
apport information ** Tags added: apport-collected staging ** Description changed: On reboot, I can login with my password without the virtual keyboard, and if my screen locks I can type my password. However, when I open up terminal, Firefox, any text box in any application, it fails to input the text I enter from my keyboard as if my keyboard is unplugged. But when I enable on-screen keyboard in the accessibility menu, my keyboard functions as it should. I just now have a virtual keyboard taking up the bottom 1/3 of my screen. I'm running 21.10 on a Raspberry Pi 4 Model B with 4Gb of RAM. My keyboard is a Corsair K100 RGB. I've tried multiple USB ports and multiple reboots and I still am required to enable my virtual keyboard in order for my real keyboard to work. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1015-raspi 5.13.0-1015.17 ProcVersionSignature: Ubuntu 5.13.0-1015.17-raspi 5.13.19 Uname: Linux 5.13.0-1015-raspi aarch64 ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 16:18:11 2022 ImageMediaBuild: 20211013 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: arm64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: eric 1007 F pulseaudio + /dev/snd/controlC0: eric 1007 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.10 + ImageMediaBuild: 20211013 + Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller + Package: linux-raspi 5.13.0.1015.20 + PackageArchitecture: arm64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 vc4drmfb + ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=E4:5F:01:2D:89:75 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash + ProcVersionSignature: Ubuntu 5.13.0-1015.17-raspi 5.13.19 + RelatedPackageVersions: + linux-restricted-modules-5.13.0-1015-raspi N/A + linux-backports-modules-5.13.0-1015-raspi N/A + linux-firmware 1.201.3 + StagingDrivers: bcm2835_mmal_vchiq bcm2835_codec bcm2835_v4l2 vc_sm_cma bcm2835_isp snd_bcm2835 + Tags: wayland-session arm64-image raspi-image impish staging + Uname: Linux 5.13.0-1015-raspi aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + acpidump: ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1958462/+attachment/753/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
** Description changed:
+ [Impact]
+
+ * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
+ * If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
+
+ [Test Plan]
+
+ * The environment:
+ 1. A desktop or workstation which containing an iGPU.
+ 2. Plug a nvidia graphic card to the system and installing proprietary
+ nvidia driver (470 in my case)
+ 3. Attach a monitor to dGPU and leave iGPU connect to nothing.
+ (in my test environment, there is the other ethernet card and TBT4 cards)
+ * Setup a cronjob,
+e.g. @reboot /home/u/test.sh
+ * Have a test script in something like /home/u/test.sh as
+
+ #!/bin/bash
+
+ sleep 20
+ count="$(cat /home/u/count)"
+ count=$((count+1))
+ echo $count | tee /home/u/count
+ journalctl -b | grep -q -i wayland || sudo reboot
+
+ * the system will probably stuck in black-screen or boot LOGO.
+ * Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
+ * After applying the fix, it got pass within 90 reboot cycles.
+
+ [Where problems could occur]
+ * The patch checkes device/boot_vga with tag "master-of-seat". If a system
without any GPU as boot_vga then it will fall in infinite loop.
+ * I tried to detach all monitors from the system and the boot_vga still
exist (default to use iGPU, the first device found during initialization)
+ * I don't think they will a case which boot_vga doesn't exist in this moment
because:
+ In drivers/gpu/vga/vgaarb.c (linux package)
+ vga_arb_select_default_device() has a fallback function to determine the
boot_vga device to prevent firmware doesn't pass correct efifb to linux-kernel.
+
+ ---
+
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
-
- The gdm-wait-for-drm is intend to make sure all drm udev devices enumerated
before launching gdm.
+ The gdm-wait-for-drm is intend to make sure all drm udev devices
+ enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
** Description changed:
[Impact]
- * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
- * If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
+ * In Ubuntu 20.04 (which using Xorg with proprietary nvidia driver), in some
cases, the nvidia driver will probe later than launching gdm.
+ * If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
- * The environment:
- 1. A desktop or workstation which containing an iGPU.
- 2. Plug a nvidia graphic card to the system and installing proprietary
- nvidia driver (470 in my case)
- 3. Attach a monitor to dGPU and leave iGPU connect to nothing.
- (in my test environment, there is the other ethernet card and TBT4 cards)
- * Setup a cronjob,
-e.g. @reboot /home/u/test.sh
- * Have a test script in something like /home/u/test.sh as
+ * The environment:
+ 1. A desktop or workstation which containing an iGPU.
+ 2. Plug a nvidia graphic card to the system and installing proprietary
+ nvidia driver (470 in my case)
+ 3. Attach a monitor to dGPU and leave iGPU
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
OK so KDE discover in 5.18 version downloads natively in QT using a QNetworkRequest. AFAICT QNetworkRequest doesn't by default request a compressed file, but needs to explicitly request this to the server: https://stackoverflow.com/questions/2340548/does-qnetworkmanager-get- accept-compressed-replies-by-default Because of that this bug occurs with KDE discover. KDE discover 5.20.90 and newer have adopted libfwupd for doing the download and should no longer encounter this. ** No longer affects: libjcat (Ubuntu Focal) ** No longer affects: libjcat (Ubuntu Hirsute) ** No longer affects: libjcat (Ubuntu Impish) ** Also affects: fwupd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: plasma-discover (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libjcat (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: plasma-discover (Ubuntu Jammy) ** Changed in: plasma-discover (Ubuntu) Status: New => Fix Released ** No longer affects: libjcat (Ubuntu Focal) ** Changed in: fwupd (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951779] Re: tempfile command removed from debianutils
And as comment #8 and #3 outlined the use of it in boost is not a real problem for build or usage in the distribution, setting that task to invalid. ** Changed in: boost1.74 (Ubuntu) Status: New => Invalid ** Changed in: grub-legacy-ec2 (Ubuntu) Assignee: Miriam España Acebal (mirespace) => (unassigned) ** Tags removed: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951779 Title: tempfile command removed from debianutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost1.74/+bug/1951779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951779] Re: tempfile command removed from debianutils
Per comment #7 and bzip2 | 1.0.8-5| jammy | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x Setting that to fix released. ** Changed in: bzip2 (Ubuntu) Status: Won't Fix => 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/1951779 Title: tempfile command removed from debianutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost1.74/+bug/1951779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
"boot_vga" only exists for PCI device, so this change will make VMs and boards that don't use PCI GFX wait for straight 10 seconds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english
** Description changed: Disclaimer: This is my first ever ubuntu bug report... and this isn't a mozc bug per-se, but more like an overall integration glitch. But this is the closest place I could think of. - Change the but report package accordingly, please. + Change the bug report package accordingly, please. Steps to reproduce: 1) Install Ubuntu 20.04. 1.1) Select English as the system language. 1.2) Select "Japanese 109-key" as the keyboard. 1.3) Select "English (US, intl, dead keys)" as the keyboard layout. 2) On the newly installed system, run "sudo apt install ibus-mozc" 3) Add Japanese in "Region & Language" with "Japanese (Mozc)" as input source. Problem: super+space changes the systray icon, but the keyboard layout isn't switched. Another noticeable error is that when using "Show Keyboard Layout", the layout name is displayed as "?" in the window title. (see attached img) fix: Edit /usr/share/ibus/component/mozc.xml and change "default" to "jp" as stated in https://help.ubuntu.com/community/JapaneseInput Comments: I don't know what mozc "default" layout means. does it get the layout from /etc/default/keyboard? If it does, it's set to XKBLAYOUT=us and XKBVARIANT=intl (as per installation instructions) so no wonder mozc gets confused. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ibus-mozc 2.23.2815.102+dfsg-8ubuntu1 [modified: usr/share/ibus/component/mozc.xml] ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 14:50:45 2022 InstallationDate: Installed on 2022-01-19 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mozc 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/1958492 Title: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878359] Re: [needs-packaging] libfprint-2-tod1-goodix
** Changed in: oem-priority Assignee: Alex Tu (alextu) => Andy Chi (andch) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878359 Title: [needs-packaging] libfprint-2-tod1-goodix To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958369] Re: dep8 test bug81235.phpt fails with php8.1
This bug was fixed in the package php-imagick - 3.6.0-4ubuntu1 --- php-imagick (3.6.0-4ubuntu1) jammy; urgency=medium * d/p/php8.1-disable-failing-test.patch: Drop test failing php8.1 (LP: #1958369) -- Bryce Harrington Wed, 19 Jan 2022 09:22:11 + ** Changed in: php-imagick (Ubuntu) Status: New => 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/1958369 Title: dep8 test bug81235.phpt fails with php8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-imagick/+bug/1958369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958462] Re: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility
Can you run 'apport-collect 1958462' when in this situation? ** Also affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Impish) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi (Ubuntu Impish) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958462 Title: Keyboard doesn't type in text fields without virtual keyboard enabled in accessibility To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1958462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958492] Re: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english
** Description changed: Disclaimer: This is my first ever ubuntu bug report... and this isn't a mozc bug per-se, but more like an overall integration glitch. But this is the closest place I could think of. Change the but report package accordingly, please. Steps to reproduce: 1) Install Ubuntu 20.04. 1.1) Select English as the system language. 1.2) Select "Japanese 109-key" as the keyboard. 1.3) Select "English (US, intl, dead keys)" as the keyboard layout. 2) On the newly installed system, run "sudo apt install ibus-mozc" 3) Add Japanese in "Region & Language" with "Japanese (Mozc)" as input source. Problem: super+space changes the systray icon, but the keyboard layout isn't switched. Another noticeable error is that when using "Show Keyboard Layout", the layout name is displayed as "?" in the window title. (see attached img) fix: Edit /usr/share/ibus/component/mozc.xml and change "default" to "jp" as stated in https://help.ubuntu.com/community/JapaneseInput Comments: I don't know what mozc "default" layout means. does it get the layout from /etc/default/keyboard? - If it does, it's set to XKBLAYOUT=us and XKBVARIANT=intl (as per installation instructons) so no wonder mozc gets confused. + If it does, it's set to XKBLAYOUT=us and XKBVARIANT=intl (as per installation instructions) so no wonder mozc gets confused. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ibus-mozc 2.23.2815.102+dfsg-8ubuntu1 [modified: usr/share/ibus/component/mozc.xml] ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 14:50:45 2022 InstallationDate: Installed on 2022-01-19 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mozc 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/1958492 Title: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958343] Re: Internal monitor of AMD based laptop not working after update
*** This bug is a duplicate of bug 1958283 *** https://bugs.launchpad.net/bugs/1958283 [1.226233] amdgpu :03:00.0: Direct firmware load for amdgpu/renoir_ta.bin failed with error -2 [1.226235] amdgpu :03:00.0: amdgpu: psp v12.0: Failed to load firmware "amdgpu/renoir_ta.bin" Missing firmware file in combination with 5.13 kernel, see bug 1958283. ** This bug has been marked a duplicate of bug 1958283 linux-firmware missing renoir_ta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958343 Title: Internal monitor of AMD based laptop not working after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
Note that gnome-shell (which also renders the login screen for gdm) always uses the primary iGPU for rendering regardless of whether some monitors are plugged into a dGPU port. The latter get their framebuffers rendered on the iGPU but copied to the dGPU for output on every frame. This makes sense for the common dual-GPU case of a laptop where you want to be able to connect an external monitor to any port (even if that port is wired to dGPU) while still using the iGPU for efficiency by default. But enough from me. You should propose any patches to https://gitlab.gnome.org/GNOME/gdm/ (or to https://gitlab.gnome.org/GNOME/mutter) to get more authoritative information from the developers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958492] [NEW] Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english
Public bug reported: Disclaimer: This is my first ever ubuntu bug report... and this isn't a mozc bug per-se, but more like an overall integration glitch. But this is the closest place I could think of. Change the but report package accordingly, please. Steps to reproduce: 1) Install Ubuntu 20.04. 1.1) Select English as the system language. 1.2) Select "Japanese 109-key" as the keyboard. 1.3) Select "English (US, intl, dead keys)" as the keyboard layout. 2) On the newly installed system, run "sudo apt install ibus-mozc" 3) Add Japanese in "Region & Language" with "Japanese (Mozc)" as input source. Problem: super+space changes the systray icon, but the keyboard layout isn't switched. Another noticeable error is that when using "Show Keyboard Layout", the layout name is displayed as "?" in the window title. (see attached img) fix: Edit /usr/share/ibus/component/mozc.xml and change "default" to "jp" as stated in https://help.ubuntu.com/community/JapaneseInput Comments: I don't know what mozc "default" layout means. does it get the layout from /etc/default/keyboard? If it does, it's set to XKBLAYOUT=us and XKBVARIANT=intl (as per installation instructions) so no wonder mozc gets confused. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ibus-mozc 2.23.2815.102+dfsg-8ubuntu1 [modified: usr/share/ibus/component/mozc.xml] ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 14:50:45 2022 InstallationDate: Installed on 2022-01-19 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mozc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mozc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Show Keyboard Layout error" https://bugs.launchpad.net/bugs/1958492/+attachment/746/+files/Screenshot%20from%202022-01-20%2014-12-01.png ** Description changed: Disclaimer: - This is my first ever ubuntu bug report... and this isn't a mozc bug per-se, but more like an overall integration glitch. But this is the closest place I could think of. + This is my first ever ubuntu bug report... and this isn't a mozc bug per-se, but more like an overall integration glitch. But this is the closest place I could think of. Change the but report package accordingly, please. Steps to reproduce: 1) Install Ubuntu 20.04. - 1.1) Select English as the system language. - 1.2) Selecting "Japanese 109-key" as the keyboard. - 1.3) Select "English (US, intl, dead keys)" as the keyboard layout. + 1.1) Select English as the system language. + 1.2) Select "Japanese 109-key" as the keyboard. + 1.3) Select "English (US, intl, dead keys)" as the keyboard layout. 2) On the newly installed system, run "sudo apt install ibus-mozc" 3) Add Japanese in "Region & Language" with "Japanese (Mozc)" as input source. - Problem: + Problem: super+space changes the systray icon, but the keyboard layout isn't switched. Another noticeable error is that when using "Show Keyboard Layout", the layout name is displayed as "?" in the window title. (see attached img) - fix: + fix: Edit /usr/share/ibus/component/mozc.xml and change "default" to "jp" as stated in https://help.ubuntu.com/community/JapaneseInput - Comments: I don't know what mozc "default" layout means. does it get the layout from /etc/default/keyboard? If it does, it's set to XKBLAYOUT=us and XKBVARIANT=intl (as per installation instructons) so no wonder mozc gets confused. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ibus-mozc 2.23.2815.102+dfsg-8ubuntu1 [modified: usr/share/ibus/component/mozc.xml] ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 14:50:45 2022 InstallationDate: Installed on 2022-01-19 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mozc 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/1958492 Title: Keyboard layout doesn't switch to japanese when using a Japanese (109-key) keyboard and the system language is english To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1958492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
OK so comparing the good and bad - the downloads are both "good" downloads but the bad is an already extracted tarball! Unpacking the good, the good and bad both have the same checksums. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
This patch doesn't need to apply to jammy/impish because debian/patches/gdm.rules-Keep-wayland-enabled-in-all-nvidia-configuratio.patch Please let me know if my assumption is incorrect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958435] Re: Icons on Dock get stuck in Dragging Mode
This is probably a duplicate of one of these: bug 1847102 bug 1867613 bug 1846477 but you will need at least Ubuntu 20.04 to ensure you have all those fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958435 Title: Icons on Dock get stuck in Dragging Mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1958435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
for focal ** Patch added: "lp1958488_gdm-wait-for-drm_wait_for_boot_vga.debdiff" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488/+attachment/742/+files/lp1958488_gdm-wait-for-drm_wait_for_boot_vga.debdiff ** Tags added: oem-priority originate-from-1956556 sutton ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958488] [NEW] [nvidia][xorg] display hangs on boot LOGO
Public bug reported:
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices enumerated
before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Assignee: jeremyszu (os369510)
Status: New
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => jeremyszu (os369510)
** Description changed:
- Test environment:
+ Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
- $ cat /lib/udev/rules.d/61-gdm.rules
+ $ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
- But in some race condition cases, the nvidia probe is later than gnome
launches.
+ But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
- The gdm-wait-for-drm is intend to make sure all drm udev devices
- enumerated before launching gdm.
+
+ The gdm-wait-for-drm is intend to make sure all drm udev devices enumerated
before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
[1] https://www.freedesktop.org/wiki/Software/systemd/multiseat/
/lib/udev/rules.d/71-seat.rules
/lib/udev/rules.d/71-nvidia.rules
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958183] Re: Ubuntu 20.04 installer crashes when "download updates" selected
** Description changed: Seems to be similar or a duplicate of https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1880277 + https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1954955 The Ubuntu 20.04 Desktop Live CD installer crashes when trying to install. Installing without updates succeeds, but results in a broken install (no ethernet, or dkms for some reason). How the error occurred: - Run Live CD (normal graphics mode) - Run installer - Select "Minimal install" and "install third-party software" - Set up partition table (2GB EFI partition, rest of disk Ubuntu) - Installer crashes at last stage Expected behaviour: Installer doesn't crash Actual behaviour: Installer crashes. Note, I have installed ubuntu 20.04 on this system before, so I have no idea why the installer would crash here. + EDIT: Problem appears to be caused by nvidia-driver-440 package. + Installing with 21.10 (which defaults to nvidia-driver-470) appeared to + fix the problem. + 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 Date: Mon Jan 17 15:35:53 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity 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/1958183 Title: Ubuntu 20.04 installer crashes when "download updates" selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1958183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867578] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLU
Possibly related to https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4957 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4957 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4957 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867578 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLUTTER_ACTOR_IS_MAPPED (self))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958318] Re: Desktop hangs - Status reg 3.
Hi Rob, The kernel team enabled Intel IOMMU by default for the 5.15 kernel, since upstream has now turned it on by default. This happened in: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440 We are aware that it will cause boot issues for older hardware that has buggy firmware, and we hope to try get things running at smoothly as we can. I looked up the firmware for your Thinkpad 510, and it seems version 1.52 is the latest. You might have to run with intel_iommu=off, which can be added to your grub config in /etc/default/grub by appending it to GRUB_CMDLINE_LINUX_DEFAULT, and running "sudo update-grub". On an installed system, anyway. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958318 Title: Desktop hangs - Status reg 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958466] Re: sudo wminput give me an error
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1958466 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958466 Title: sudo wminput give me an error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cwiid/+bug/1958466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958455] Re: Discover crashes on start (since Plasma 5.24 beta update)
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1958455 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958455 Title: Discover crashes on start (since Plasma 5.24 beta update) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1958455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958484] Re: Add Python support for Vitis AI v1.3.2 package in focal
The patch in comment#1 and test packages have been reviewed and verified by Xilinx. Here is the feedback from Xilinx: I think this is good to go - my tests are working, and another one of our apps guys tested with their larger application and it is working. You can move forward with the SRU process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958484 Title: Add Python support for Vitis AI v1.3.2 package in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vitis-ai/+bug/1958484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958484] Re: Add Python support for Vitis AI v1.3.2 package in focal
** Patch added: "focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/vitis-ai/+bug/1958484/+attachment/740/+files/focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958484 Title: Add Python support for Vitis AI v1.3.2 package in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vitis-ai/+bug/1958484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems
** Changed in: hwe-next Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958484] [NEW] Add Python support for Vitis AI v1.3.2 package in focal
Public bug reported: [Impact] * Xilinx wants to add python support for Vitis AI v1.3.2 package The following files will be added after applying the patch for python support. /usr/lib/python3/dist-packages/runner.py /usr/lib/python3/dist-packages/vart.cpython-38-aarch64-linux-gnu.so /usr/lib/python3/dist-packages/xir.cpython-38-aarch64-linux-gnu.so * Xilinx doesn't intend to support v1.3.2 package in Jammy. Vitis AI package in Jammy will be upgraded to newer version with python support. So, the patch for python support won't be applied to jammy. [Test Plan] * Xilinx will perform validation of these packages [Where problems could occur] * This is a low-risk SRU as python libraries do not exist on focal yet, so in theory no current user would be affected ** Affects: vitis-ai (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1956367 ** Tags added: oem-priority originate-from-1956367 ** Description changed: [Impact] - * Xilinx wants to add python support for Vitis AI v1.3.2 package + * Xilinx wants to add python support for Vitis AI v1.3.2 package The following files will be added after applying the patch for python support. /usr/lib/python3/dist-packages/runner.py /usr/lib/python3/dist-packages/vart.cpython-38-aarch64-linux-gnu.so /usr/lib/python3/dist-packages/xir.cpython-38-aarch64-linux-gnu.so - * Xilinx doesn't intend to support v1.3.2 package in Jammy. -Vitis AI package in Jammy will be upgraded to newer version with python support. -So, the patch for python support won't be applied to jammy. + * Xilinx doesn't intend to support v1.3.2 package in Jammy. Vitis AI + package in Jammy will be upgraded to newer version with python support. + So, the patch for python support won't be applied to jammy. [Test Plan] - * Xilinx will perform validation of these packages + * Xilinx will perform validation of these packages [Where problems could occur] - * This is a low-risk SRU as python libraries do not exist on focal yet, + * This is a low-risk SRU as python libraries do not exist on focal yet, so in theory no current user would be affected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958484 Title: Add Python support for Vitis AI v1.3.2 package in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vitis-ai/+bug/1958484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958481] Re: check_disk forcibly ignores tmpfs
The attachment "An updated version of the patch with my alternative solution" 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/1958481 Title: check_disk forcibly ignores tmpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1958481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
full journal log from fwupd, most are not verbose, just for reference. ** Attachment added: "fwupd.journal.all.log" https://bugs.launchpad.net/oem-priority/+bug/1943833/+attachment/737/+files/fwupd.journal.all.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
Below is the log of fwupd during running discover in verbose mode. (-v) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(acpi_dmar) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuCommon reading /sys/firmware/acpi/tables/DMAR with 184 bytes 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPluginAcpiDmar OemTableId: Dell Inc 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPluginAcpiDmar CreatorId: 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPluginAcpiDmar Flags: 0x05 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(linux_lockdown) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(pci_bcr) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(uefi_pk) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(acpi_facp) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuCommon reading /sys/firmware/acpi/tables/FACP with 276 bytes 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPluginAcpiFacp Flags: 0x20c4f5 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(linux_tainted) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(linux_sleep) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(tpm) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(cpu) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(pci_mei) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0328 FuPlugin add_security_attrs(linux_swap) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0343 FuPluginLinuxSwap/swapfile file is unencrypted 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0343 FuPlugin add_security_attrs(iommu) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0343 FuPlugin add_security_attrs(msr) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0343 FuPlugin add_security_attrs(tpm_eventlog) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0343 FuPlugin add_security_attrs(uefi_capsule) 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0346 FuMain Called GetRemotes() 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0391 FuMain Called GetDevices() 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0393 FuMain Called GetRemotes() 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0400 FuBackendadding rate-limited timeout for /sys/devices/virtual/block/loop0 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0428 FuBackendre-adding rate-limited timeout for /sys/devices/virtual/block/loop0 一 20 11:53:11 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:11:0929 FuPlugin udev_device_changed(synaptics_mst) 一 20 11:53:12 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:12:0426 FuMain Called UpdateMetadata(lvfs,31,36) 一 20 11:53:12 ycheng-Latitude-7330-Rugged-Extreme fwupd[2317]: 03:53:12:0446 FuMain Called GetDevices() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958481] Re: check_disk forcibly ignores tmpfs
On the stock version, tmpfs filesystems do not show up, even if I specify -X: $ /usr/lib/nagios/plugins/check_disk -w 10 -c 10 DISK OK - free space: /dev 5944 MB (100% inode=99%); / 2357 MB (28% inode=75%); /srv 17618 MB (94% inode=99%); /boot/efi 498 MB (98% inode=-);| /dev=0MB;5934;5934;0;5944 /=5993MB;8807;8807;0;8817 /srv=1009MB;18634;18634;0;18644 /boot/efi=5MB;494;494;0;504 $ /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -X devpts DISK OK - free space: /dev 5944 MB (100% inode=99%); / 2357 MB (28% inode=75%); /srv 17618 MB (94% inode=99%); /boot/efi 498 MB (98% inode=-);| /dev=0MB;5934;5934;0;5944 /=5993MB;8807;8807;0;8817 /srv=1009MB;18634;18634;0;18644 /boot/efi=5MB;494;494;0;504 With this version using my alternative patch, they still don't show up by default, but do if I specify something with -X: $ ./check_disk -w 10 -c 10 DISK OK - free space: /dev 5944 MB (100% inode=99%); / 2357 MB (28% inode=75%); /srv 17618 MB (94% inode=99%); /boot/efi 498 MB (98% inode=-);| /dev=0MB;5934;5934;0;5944 /=5992MB;8807;8807;0;8817 /srv=1009MB;18634;18634;0;18644 /boot/efi=5MB;494;494;0;504 $ ./check_disk -w 10 -c 10 -X devpts DISK CRITICAL - free space: /dev 5944 MB (100% inode=99%); /run 1076 MB (89% inode=99%); / 2357 MB (28% inode=75%); /dev/shm 5987 MB (100% inode=99%); /run/lock 5 MB (100% inode=99%); /sys/fs/cgroup 5987 MB (100% inode=99%); /tmp 5986 MB (99% inode=99%); /srv 17618 MB (94% inode=99%); /boot/efi 498 MB (98% inode=-); /run/user/25045 1197 MB (100% inode=99%);| /dev=0MB;5934;5934;0;5944 /run=120MB;1187;1187;0;1197 /=5992MB;8807;8807;0;8817 /dev/shm=0MB;5977;5977;0;5987 /run/lock=0MB;-5;-5;0;5 /sys/fs/cgroup=0MB;5977;5977;0;5987 /tmp=0MB;5977;5977;0;5987 /srv=1009MB;18634;18634;0;18644 /boot/efi=5MB;494;494;0;504 /run/user/25045=0MB;1187;1187;0;1197 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958481 Title: check_disk forcibly ignores tmpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1958481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958481] Re: check_disk forcibly ignores tmpfs
** Patch added: "An updated version of the patch with my alternative solution" https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1958481/+attachment/736/+files/exclude-tmpfs-squashfs-tracefs.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958481 Title: check_disk forcibly ignores tmpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1958481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958481] Re: check_disk forcibly ignores tmpfs
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958481 Title: check_disk forcibly ignores tmpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1958481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
all good and bad files attached ** Attachment added: "lvfs.tar" https://bugs.launchpad.net/oem-priority/+bug/1943833/+attachment/735/+files/lvfs.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958283] Re: linux-firmware missing renoir_ta
Thanks, dmesg doesn't show any error. Anyway, Juerg is SRU the amdgpu renoir firmware that is the same as impish linux-firmware_1.201 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958283 Title: linux-firmware missing renoir_ta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Tags added: originate-from-1955956 ** Tags added: originate-from-1955628 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
Booting Ubuntu Desktop (groovy RC 2020-10-16.4) - - motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series) and plymouth takes ~8 mins to appear on screen the maybe-ubiquity (try or install) screen took >10 mins I did mention groovy in comment #17, but I don't believe I filed bugs, just noted on iso.qa.ubuntu.com QA-test reports. I didn't use stop-watch, but looked at room clock in room (digital without seconds so my times are approx only).. My ISO may also not have been released groovy; just last I zsync'd prior to release for QA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958481] [NEW] check_disk forcibly ignores tmpfs
Public bug reported:
check_disk ignores tmpfs filesystems due to an Ubuntu patch
(debian/patches/exclude-tmpfs-squashfs-tracefs.patch) added for LP
#1827159. This is a bad idea.
On my servers, I have a tmpfs mounted at /tmp. Last night, /tmp filled
up on one of them, resulting in significant breakage. My Icinga disk
alerting did not notify me, because it's ignoring all tmpfs filesystems.
I looked to see why and found that ignoring tmpfs is the Icinga default,
so I adjusted that in my configuration. Unfortunately, that still didn't
work. I eventually tracked that down to this patch. Because this tmpfs
exclusion has been hardcoded in, it is impossible for me to override
this decision.
While I think you should simply remove tmpfs from that patch, an
alternative approach would be to move the code lower, after the
arguments have been parsed, and conditionalize it. Something like this:
if (!fs_exclude_list) {
np_add_name(_exclude_list, "squashfs");
np_add_name(_exclude_list, "tmpfs");
np_add_name(_exclude_list, "tracefs");
}
np_add_name(_exclude_list, "iso9660");
Note that iso9660 is outside the conditional and thus always added as
per the upstream behavior. Thus the default behavior would be the same
as now with the patch, but if the user customizes the exclude list with
-X (e.g. in Icinga, or just via the command line), that would be
honored.
** Affects: monitoring-plugins (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958481
Title:
check_disk forcibly ignores tmpfs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1958481/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942653] Re: RandR fractional scaling patch interferes with manual RandR output scaling
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (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/1942653 Title: RandR fractional scaling patch interferes with manual RandR output scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1942653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958017] Re: [nvidia] Screen scaling reset every reboot
*** This bug is a duplicate of bug 1942653 *** https://bugs.launchpad.net/bugs/1942653 On second thoughts this is really the same kind of issue as bug 1942653. ** This bug has been marked a duplicate of bug 1942653 RandR fractional scaling patch interferes with manual RandR output scaling -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958017 Title: [nvidia] Screen scaling reset every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1958017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
And does the daemon verbose log show anything? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
Can you upload those bad files that discover fetched? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
** Changed in: oem-priority Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
fwupd 1.5.11 + libjcat 0.1.3 on kubuntu/focal 1. fwupdmgr refresh (with non-root account) metadata.xml.gz metadata.xml.gz.jcat goes to /var/lib/fwupd/remotes.d/lvfs sha1sum and sha256sum: match # sha1sum * a6a3e64a224ff04142c1d693f3c6e201a79d2dbb metadata.xml.gz 8a72e4e6b2280d81bc630807e58a1eef852dc595 metadata.xml.gz.jcat 2. clean up /var/lib/fwupd/remotes.d/lvfs and run discover metadata.xml.gz metadata.xml.gz.jcat goes to ~/.cache/fwupd/remotes.d/lvfs sha1sum and sha256sum: not match $ sha1sum * ebda81ea07252679f402904c6172e4707fc60884 metadata.xml.gz 8a72e4e6b2280d81bc630807e58a1eef852dc595 metadata.xml.gz.jcat PS: this is not consistent with my 2nd statement in #19. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943833] Re: fwupd failed to update metadata for lvfs
fwupd 1.7.3 + jcat 0.1.9 on kubuntu/focal 1. fwupdmgr refresh (with non-root account) metadata.xml.gz metadata.xml.gz.jcat goes to /var/lib/fwupd/metadata/lvfs sha1sum and sha256sum: match # sha1sum * a6a3e64a224ff04142c1d693f3c6e201a79d2dbb metadata.xml.gz 8a72e4e6b2280d81bc630807e58a1eef852dc595 metadata.xml.gz.jcat 2. clean up /var/lib/fwupd/metadata/lvfs and run discover metadata.xml.gz metadata.xml.gz.jcat goes to /var/lib/fwupd/metadata/lvfs sha1sum and sha256sum: not match $ sha1sum * ebda81ea07252679f402904c6172e4707fc60884 metadata.xml.gz 8a72e4e6b2280d81bc630807e58a1eef852dc595 metadata.xml.gz.jcat Based on the above result, it's likely that discover downloaded the wrong metadata.xml.gz AI: revert to fwupd 1.5.11 + jcat 0.1.3 and test again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943833 Title: fwupd failed to update metadata for lvfs To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958436] Re: Cant autocomplete symbol to rm file that was generated from error in some script
** Package changed: xorg (Ubuntu) => bash-completion (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958436 Title: Cant autocomplete symbol to rm file that was generated from error in some script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1958436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958472] 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/1958472 Title: package linux-image-5.4.0-94-generic (not installed) failed to install/upgrade: installed linux-image-5.4.0-94-generic package pre- removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958435] Re: Icons on Dock get stuck in Dragging Mode
Thanks for the bug report. It appears gnome-shell-extension-ubuntu-dock for 18.04 has not been updated in 3 years. This is unsurprising as we usually focus on the most recent releases including the most recent LTS which was 20.04. Please try Ubuntu 20.04 when you can and tell us if the problem still exists there: https://ubuntu.com/download/desktop Or even better try live booting the preview of 22.04: http://cdimage.ubuntu.com/daily-live/current/ ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958435 Title: Icons on Dock get stuck in Dragging Mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1958435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958443] Re: Ubuntu randomly freezes with 5.13.0-27
Thanks for the bug report. Next time the freeze happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Changed in: linux-hwe-5.13 (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/1958443 Title: Ubuntu randomly freezes with 5.13.0-27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958444] Re: Xorg sometimes seems to crash when Plover is running
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** 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/1958444 Title: Xorg sometimes seems to crash when Plover is running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880764] Re: Dragging icons frozen in place without finishing
*** This bug is a duplicate of bug 1958435 *** https://bugs.launchpad.net/bugs/1958435 ** This bug has been marked a duplicate of bug 1958435 Icons on Dock get stuck in Dragging Mode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880764 Title: Dragging icons frozen in place without finishing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958412] Re: at startup and shutdown screen gets white noise
** Tags added: amdgpu ** Summary changed: - at startup and shutdown screen gets white noise + [amdgpu] at startup and shutdown screen gets white noise ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958412 Title: [amdgpu] at startup and shutdown screen gets white noise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958435] Re: Icons on Dock get stuck in Dragging Mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (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/1958435 Title: Icons on Dock get stuck in Dragging Mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1958435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958147] Re: Nvidia acceleration has gone
The only evidence of an nvidia driver provided in this bug report is nvidia-installer.log.txt which shows 367.48 was installed in 2016, and the bug tag 'possible-manual-nvidia-install'. Both of which indicate an unsupported driver was installed. I'm just going on the facts provided. Anyway it sounds like the problem is solved based on your last comment. ** Changed in: ubuntu Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958147 Title: Nvidia acceleration has gone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1958147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958357] Re: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-450 (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/1958357 Title: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1958357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958472] [NEW] package linux-image-5.4.0-94-generic (not installed) failed to install/upgrade: installed linux-image-5.4.0-94-generic package pre-removal script subprocess returned error exit sta
Public bug reported: The system goes black, and all operations cannot be invoked ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-94-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lihongbin 1180 F pulseaudio CasperMD5CheckResult: skip Date: Tue Jan 18 19:17:56 2022 ErrorMessage: installed linux-image-5.4.0-94-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2022-01-17 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: ens33 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=1195a5cd-9516-4ccb-8076-b962558803cb ro rw quiet splash nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux Title: package linux-image-5.4.0-94-generic (not installed) failed to install/upgrade: installed linux-image-5.4.0-94-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958472 Title: package linux-image-5.4.0-94-generic (not installed) failed to install/upgrade: installed linux-image-5.4.0-94-generic package pre- removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938591] Re: update 18.04 to readline8
Affecting me too on Ubuntu 19.04 also. Also causing GitHub "issues" being (incorrectly) filed on other upstream projects and distracting the maintainer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938591 Title: update 18.04 to readline8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/readline/+bug/1938591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958046] Re: Cant get bug report again, if i didnt send it in 1st 2 times that i came up. Could come back all the time so latest bug reports can be easy sent.
** Description changed: Cant get bug report again, if i didnt send it in 1st 2 times that i came up. Could come back all the time so latest bug reports can be easy sent. Screenshot- notifications cant click old ones. Also shows only 2 crashes bug reports, but i opened more times crashing app in a row. - Ideas for missing bug report if this would be fixed. #1958044 and #1958045 - cant click in notifications. + Ideas for missing bug report if this would be fixed. bug 1958044 and bug 1958045 - cant click in notifications. But this bug is about that apport even doesnt make new reports after 2nd time, so no new notifications not comming up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.27 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic i686 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: i386 CurrentDesktop: KDE Date: Sun Jan 16 04:10:40 2022 InstallationDate: Installed on 2022-01-15 (0 days ago) InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 (20200806.1) PackageArchitecture: all SourcePackage: apport 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/1958046 Title: Cant get bug report again, if i didnt send it in 1st 2 times that i came up. Could come back all the time so latest bug reports can be easy sent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1958046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957716] Re: Update for CVE-2021-43860 and CVE-2022-21682
** Description changed: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j ( CVE-2021-43860 ) https://security-tracker.debian.org/tracker/CVE-2021-43860 https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx ( CVE-2022-21682 ) https://security-tracker.debian.org/tracker/CVE-2022-21682 [Impact] Versions in Ubuntu right now: Jammy: 1.12.2-2 Impish: 1.10.2-3ubuntu0.1 Focal: 1.6.5-0ubuntu0.4 Bionic: 1.0.9-0ubuntu0.4 Affected versions: all Patched versions: - 1.12.3, 1.10.6 + 1.12.4, 1.10.7 [Test Case] Unknown [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Patches] The first CVE has 4 patches (+ 1 test patch), the second CVE has 1 patch (+ 6 doc/test patches). [Other Information] For the first advisory with the CVE: Ryan Gonzalez discovered that Flatpak doesn't properly validate that the permissions displayed to the user for an app at install time match the actual permissions granted to the app at runtime, in the case that there's a null byte in the metadata file of an app. Therefore apps can grant themselves permissions without the consent of the user. Flatpak shows permissions to the user during install by reading them from the "xa.metadata" key in the commit metadata. This cannot contain a null terminator, because it is an untrusted GVariant. Flatpak compares these permissions to the actual metadata, from the "metadata" file to ensure it wasn't lied to. However, the actual metadata contents are loaded in several places where they are read as simple C-style strings. That means that, if the metadata file includes a null terminator, only the content of the file from before the terminator gets compared to xa.metadata. Thus, any permissions that appear in the metadata file after a null terminator are applied at runtime but not shown to the user. Maliciously crafted apps can use this to give themselves hidden permissions. In addition, a similar weakness was discovered, where if the permissions in the summary metadata are invalid, they would not be displayed to the user, but the the actual permissions would be granted, even though it didn't match the invalid version. - For the second advisory: flatpak-builder applies finish-args last in the build. At this point the build directory will have the full access that is specified in the manifest, so running flatpak build against it will gain that permissions. Normally this will not be done, so this is not problem. However, if --mirror-screenshots-url is specified, then flatpak-builder will launch flatpak build --nofilesystem=host appstream-utils mirror- screenshots after finalization, which can lead to issues even with the --nofilesystem=host protection. There are two issues: - --nofilesystem=host only overrides the access to the full host. The app can still request access to a specific directory, like --filesystem=~/some-dir, which is not affected by this. - If a filesystem is specified like --filesystem=~/foobar:create, then that directory will be created before running the command. + --nofilesystem=host only overrides the access to the full host. The app can still request access to a specific directory, like --filesystem=~/some-dir, which is not affected by this. + If a filesystem is specified like --filesystem=~/foobar:create, then that directory will be created before running the command. In normal use the only issue is that these empty directories can be created wherever the user has write permissions. However, a malicious application could replace the appstream-util binary and potentially do something more hostile. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957716 Title: Update for CVE-2021-43860 and CVE-2022-21682 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1957716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957716] Re: Update for CVE-2021-43860 and CVE-2022-21682
** Description changed: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j ( CVE-2021-43860 ) https://security-tracker.debian.org/tracker/CVE-2021-43860 https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx ( CVE-2022-21682 ) https://security-tracker.debian.org/tracker/CVE-2022-21682 - [Impact] Versions in Ubuntu right now: Jammy: 1.12.2-2 Impish: 1.10.2-3ubuntu0.1 Focal: 1.6.5-0ubuntu0.4 Bionic: 1.0.9-0ubuntu0.4 Affected versions: all Patched versions: 1.12.3, 1.10.6 [Test Case] Unknown [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Patches] - There are two separate github advisories but only one of them has a CVE. - - The advisory with the CVE has 5 patches, the other has 2 patches. + The first CVE has 4 patches (+ 1 test patch), the second CVE has 1 patch (+ 6 doc/test patches). [Other Information] For the first advisory with the CVE: Ryan Gonzalez discovered that Flatpak doesn't properly validate that the permissions displayed to the user for an app at install time match the actual permissions granted to the app at runtime, in the case that there's a null byte in the metadata file of an app. Therefore apps can grant themselves permissions without the consent of the user. Flatpak shows permissions to the user during install by reading them from the "xa.metadata" key in the commit metadata. This cannot contain a null terminator, because it is an untrusted GVariant. Flatpak compares these permissions to the actual metadata, from the "metadata" file to ensure it wasn't lied to. However, the actual metadata contents are loaded in several places where they are read as simple C-style strings. That means that, if the metadata file includes a null terminator, only the content of the file from before the terminator gets compared to xa.metadata. Thus, any permissions that appear in the metadata file after a null terminator are applied at runtime but not shown to the user. Maliciously crafted apps can use this to give themselves hidden permissions. In addition, a similar weakness was discovered, where if the permissions in the summary metadata are invalid, they would not be displayed to the user, but the the actual permissions would be granted, even though it didn't match the invalid version. + For the second advisory: flatpak-builder applies finish-args last in the build. At this point the build directory will have the full access that is specified in the manifest, so running flatpak build against it will gain that permissions. Normally this will not be done, so this is not problem. However, if --mirror-screenshots-url is specified, then flatpak-builder will launch flatpak build --nofilesystem=host appstream-utils mirror- screenshots after finalization, which can lead to issues even with the --nofilesystem=host protection. - These changes result in a behaviour change as debian have noted in their - changelog: + There are two issues: - * Behaviour changes, as a result of how GHSA-8ch7-5j3h-g4fx was fixed: - - --nofilesystem=host is now special-cased to negate all --filesystem - permissions. Previously, it would cancel out --filesystem=host but - not --filesystem=/some/dir. - - --nofilesystem=home is now special-cased to negate several - home-directory-related filesystem permssions such as - --filesystem=xdg-config/foo, not just --filesystem=host. + --nofilesystem=host only overrides the access to the full host. The app can still request access to a specific directory, like --filesystem=~/some-dir, which is not affected by this. + If a filesystem is specified like --filesystem=~/foobar:create, then that directory will be created before running the command. + + In normal use the only issue is that these empty directories can be + created wherever the user has write permissions. However, a malicious + application could replace the appstream-util binary and potentially do + something more hostile. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957716 Title: Update for CVE-2021-43860 and CVE-2022-21682 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1957716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954955] Re: Unable to install 'nvidia-driver-440' due to conflicts.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (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/1954955 Title: Unable to install 'nvidia-driver-440' due to conflicts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1954955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958467] [NEW] focal linux-firmware package omits amdgpu/navi12 firmware
Public bug reported: The 20.04 LTS linux-firmware package list was cut before the amdgpu/navi12* firmware files were upstreamed to the Linux kernel repository, which is unfortunate because this hardware is older than some other included firmware (navi14*), and the firmware is required for using the AMDGPU kernel module on AWS EC2 cloud instances with AMD GPUs. The files are included in 21.04 and 21.10, but to date they have not been included in the LTS hardware-enablement releases for 20.04. It would be helpful to include the navi12 firmware files for the next LTS+HWE release, since 22.04 isn't due out for a while. Without this firmware it is difficult to get AWS EC2 G4ad instances working with Ubuntu, as customers need to manually download and install the firmware from a reputable source and put it into the appropriate directory, which is not the experience they expect on hardware that is over a year old with the most recent HWE release. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958467 Title: focal linux-firmware package omits amdgpu/navi12 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942648] Re: restart button remains visible in the advanced partitioner after the bitlocker page is shown
I repeated the test based on the package from proposed and things still look good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942648 Title: restart button remains visible in the advanced partitioner after the bitlocker page is shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1942648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958183] Re: Ubuntu 20.04 installer crashes when "download updates" selected
** Summary changed: - Ubuntu 20.04 installer crashes when on ubiquity network + Ubuntu 20.04 installer crashes when "download updates" selected ** Description changed: Seems to be similar or a duplicate of https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1880277 The Ubuntu 20.04 Desktop Live CD installer crashes when trying to - install Ubiquity (as I am on a ubiquity network, and selected "download - third party software"). + install. Installing without updates succeeds, but results in a broken + install (no ethernet, or dkms for some reason). How the error occurred: - - Run Live CD (normal graphics mode) - - Run installer - - Select "Minimal install" and "install third-party software" - - Set up partition table (2GB EFI partt=ition, rest of disk Ubuntu) - - Installer crashes at last stage + - Run Live CD (normal graphics mode) + - Run installer + - Select "Minimal install" and "install third-party software" + - Set up partition table (2GB EFI partition, rest of disk Ubuntu) + - Installer crashes at last stage Expected behaviour: Installer doesn't crash - Actual behaviour: Ubiquity ruins my life + Actual behaviour: Installer crashes. + + Note, I have installed ubuntu 20.04 on this system before, so I have no + idea why the installer would crash here. 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 Date: Mon Jan 17 15:35:53 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ubiquity 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/1958183 Title: Ubuntu 20.04 installer crashes when "download updates" selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1958183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947043] Re: nvidia drivers do not update initramfs properly
@xnox: Upon investigation, and per our conversation on IRC, I did some experimenting with the prebuilt modules. Unfortunately, these use llvmpipe and don't interface well with nvidia-settings. Using ubuntu-drivers to install the drivers used *the exact same mechanism* as installing nvidia-drivers-470 directly, but also configured our systems to use the hybrid graphics mode, which has been known to cause performance issues on our branded CLEVO chassis computers especially when connected to external displays. Your suggestions were good, but in this instance they don't make a whole lot of sense. I do, however, understand your reluctance to rebuild all initramfs for each kernel as it might break things. I feel as though we can probably close this bug as your rationale is sound, and the mechanism we have works for our customers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947043 Title: nvidia drivers do not update initramfs properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1947043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958466] [NEW] sudo wminput give me an error
Public bug reported: when i run sudo wminput it gives me ImportError: /usr/lib/python3/dist- packages/cwiid.cpython-39-x86_64-linux-gnu.so: undefined symbol: PyVarObject_CallFunction ** Affects: cwiid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958466 Title: sudo wminput give me an error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cwiid/+bug/1958466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952093] Update Released
The verification of the Stable Release Update for livecd-rootfs 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/1952093 Title: Seeded snaps broken in the Focal dailies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1952093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952093] Re: Seeded snaps broken in the Focal dailies
This bug was fixed in the package livecd-rootfs - 2.664.36 --- livecd-rootfs (2.664.36) focal; urgency=medium * live-build/ubuntu-server/hooks/032-installer-squashfs.binary: be more careful in deleting snaps that snap-preseed has copied up into the live installer layer. (LP: #1952093) -- Michael Hudson-Doyle Thu, 02 Dec 2021 12:05:00 +1300 ** Changed in: livecd-rootfs (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/1952093 Title: Seeded snaps broken in the Focal dailies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1952093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952093] Re: Seeded snaps broken in the Focal dailies
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952093 Title: Seeded snaps broken in the Focal dailies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1952093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
