[Group.of.nepali.translators] [Bug 2050051] Re: Security policy update for not supporting version < 1.7.x
** Also affects: fwupd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: New => Invalid ** Changed in: fwupd (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: fwupd (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: fwupd (Ubuntu Trusty) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2050051 Title: Security policy update for not supporting version < 1.7.x Status in fwupd package in Ubuntu: Invalid Status in fwupd source package in Trusty: Won't Fix Status in fwupd source package in Xenial: Won't Fix Status in fwupd source package in Bionic: Won't Fix Bug description: The system has fwupd < 1.7.x won't be able to update device firmware, because of [1]. Here is the announcement from upstream [2]. Would like to know the policy of Ubuntu for the codename <= 18.04. [1] https://gitlab.com/fwupd/lvfs-website/-/commit/e9a0fbd20b28ae230ff283cbc0915d2ea065f161 [2] https://github.com/fwupd/fwupd/blob/main/SECURITY.md#security-policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2050051/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Invalid ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system Status in linux package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in linux source package in Xenial: Won't Fix Status in xserver-xorg-video-amdgpu source package in Xenial: Invalid Bug description: COMPUTER: Dell Inspiron 5548 laptop CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz GRAPHICS: Intel-AMD hybrid: - CPU-integrated: Intel Corporation Broadwell-U Integrated Graphics (driver: i915) - GPU: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] (driver: amdgpu) OPERATING SYSTEM: 64-bit GNU/Linux XUbuntu 16.04 "Xenial" KERNEL: 4.4.0-31-generic PROBLEM: system hangs / freezes very frequently. I have Xscreensaver installed and noticed that when it's running an OpenGL animation (screensaver) and I move the touchpad pointer the screen freezes. I can still turn the keyboard LED backlight on and off (hence: keyboard doesn't stop working) but the pointer won't move (touchpad is locked) and I can't Ctrl-Alt-F[1-6] (switch TTY/terminals). Only solution is to power off my laptop (press and hold the power button). I usually select the "Molecule" screensaver (it uses OpenGL), then I click the "preview" button and wait for about 20 seconds, then I click the touchpad and the computer hangs. When I used XUbuntu 14.04 "Trusty" with AMD's fglrx (proprietary) driver I didn't experience such issue. After upgrading to 16.04 "Xenial" (which doesn't support fglrx module/driver) amdgpu module is loaded by default but very frequently hangs the entire system. Sometimes I'm quick enough to go to TTYS1 and then I get to see some messages such as "HARD LOCKUP on CPU0" and "HARD LOCKUP on CPU1". However, it's not a hardware problem because I've already executed the Dell Hardware Diagnostics straight from the boot (it's an EFI utility), it tested all the hardware components (CPU, GPU, RAM, keyboard, touchpad, hard disk etc.) and didn't detect any faulty component. The attached file "amdgpu-bug.txt" is the reason why I'm pretty convinced that the problem is being caused by the amdgpu driver (although it seems to be related to how it interacts with the kernel, thus maybe the problem is kernel-related). WORKAROUND: Boot from GRUB with the nomodeset parameter. The graphics performance becomes terribly slow. - Apport output: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:0643] Subsystem: Dell Topaz XT [Radeon R7 M260/M265] [1028:0643] InstallationDate: Installed on 2016-07-29 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 5548 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=24cb3fff-5c01-4674-9c59-58d7d776fd70 ro quiet splash nomodeset vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Renderer: Software Tags: xenial ubuntu Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape users video _MarkForUpload: True dmi.bios.date: 10/12/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0YDTG3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/12/2015:svnDellInc.:pnInspiron5548:pvrA06:rvnDellInc.:rn0YDTG3:rvrA02:cvnDellInc.:ct8:cvrA06: dmi.product.name: Inspiron 5548 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
[Group.of.nepali.translators] [Bug 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
** No longer affects: initramfs-tools (Ubuntu Xenial) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Bug description: [Impact] initramfs-tools would always include all "framebuffer" drivers/firmware inside initramfs, which was making it ever more huge. In some systems with low memory, that would even prevent systems to boot. kdump, for example, had an impact. [Test case] Different systems on different arches were tested. When cryptsetup (or cryptsetup-initramfs) was installed, framebuffer drivers were included in the ramdisk. When not installed, the initramfs was smaller. Systems booted on both cases. Systems with encrypted disks were tested as well. [Regression Potential] Systems may not boot because of missing drivers. Users may have a different experience during boot because of missing "framebuffer" drivers. == initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
I reported this upstream here: https://github.com/hughsie/lvfs- website/issues/335 It looks like it's related to the metadata being too big. ** No longer affects: appstream-glib (Ubuntu) ** Bug watch added: github.com/hughsie/lvfs-website/issues #335 https://github.com/hughsie/lvfs-website/issues/335 ** Changed in: fwupd (Ubuntu) Status: New => Triaged ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: Triaged => Fix Released ** Changed in: fwupd (Ubuntu Xenial) Status: New => Triaged ** Changed in: fwupd (Ubuntu Xenial) Importance: Undecided => Critical -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Triaged Bug description: Execute the `fwupdmgr refresh` command shows "Mismatched XML" message in a fully updated Ubuntu 16.04 desktop, To reproduce on any Ubuntu 16.04 classic (Xenial): #apt install fwupd #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML The core snap `uefi-fw-tools` used in Ubuntu Core 16 also affected with same issue. This is worked in Ubuntu 18.04 (bionic) #fwupdmgr refresh Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***] Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc The `fwupd` classic confined snap also works. === Distributor ID: Ubuntu Description: Ubuntu 16.04.6 LTS Release: 16.04 Codename: xenial ii fwupd 0.8.3-0ubuntu4 #fwupdmgr refresh failed to update metadata: Failed to parse XML: Mismatched XML To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1762617] Re: gnome-software crashed with SIGSEGV in fwupd_device_from_key_value → fwupd_device_set_from_variant_iter → fwupd_device_from_variant → fwupd_client_signa
** Changed in: fwupd (Ubuntu Xenial) Status: Fix Committed => Won't Fix ** No longer affects: fwupd (Ubuntu Xenial) ** Also affects: fwupd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: fwupd (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1762617 Title: gnome-software crashed with SIGSEGV in fwupd_device_from_key_value → fwupd_device_set_from_variant_iter → fwupd_device_from_variant → fwupd_client_signal_cb Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Bionic: Fix Committed Status in fwupd source package in Cosmic: Fix Released Bug description: Failed on start right after login ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 10 01:19:41 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7efc46a3d326:mov(%rax),%rsi PC (0x7efc46a3d326) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libfwupd.so.2 fwupd_device_from_variant () at /usr/lib/x86_64-linux-gnu/libfwupd.so.2 () at /usr/lib/x86_64-linux-gnu/libfwupd.so.2 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-software crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-04-10 (0 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1762617/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1614105] Re: /usr/lib/x86_64-linux-gnu/fwupd/fwupd:11:as_store_load_yaml_file:as_store_from_file_internal:as_store_load_app_info_file:as_store_load_app_info:as_store
This particular issue hasn't received reports in anything newer than Ubuntu 16.04. The fwupd version in 16.04 is in deep maintenance mode and issues on the branches contained there (0.7.x and 0.8.x) will not be fixed. ** Changed in: appstream-glib (Ubuntu) Status: Triaged => Invalid ** Changed in: fwupd (Ubuntu) Status: Triaged => Fix Released ** Also affects: appstream-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1614105 Title: /usr/lib/x86_64-linux- gnu/fwupd/fwupd:11:as_store_load_yaml_file:as_store_from_file_internal:as_store_load_app_info_file:as_store_load_app_info:as_store_search_app_info Status in appstream-glib package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Status in appstream-glib source package in Xenial: New Status in fwupd source package in Xenial: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding fwupd. This problem was most recently seen with version 0.7.0-0ubuntu4.2, the problem page at https://errors.ubuntu.com/problem/383fc92e3f070ac2836bf575ac0ddc40814a5427 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1614105/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1762617] Re: gnome-software crashed with SIGSEGV in fwupd_device_from_key_value → fwupd_device_set_from_variant_iter → fwupd_device_from_variant → fwupd_client_signa
Just to connect the dots, this particular fix is: https://github.com/hughsie/fwupd/commit/86fdd975adbb725965d8a015994f023469e697d8 #diff-22684cccbec07d4328eaef43086e6f47 It's in the 1.0.9 release that will be SRUed by https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 ** Changed in: fwupd (Ubuntu) Status: New => Fix Committed ** Also affects: fwupd (Ubuntu Cosmic) Importance: Medium Status: Fix Committed ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: fwupd (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1762617 Title: gnome-software crashed with SIGSEGV in fwupd_device_from_key_value → fwupd_device_set_from_variant_iter → fwupd_device_from_variant → fwupd_client_signal_cb Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Fix Committed Status in fwupd source package in Cosmic: Fix Released Bug description: Failed on start right after login ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 10 01:19:41 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-04-07 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7efc46a3d326:mov(%rax),%rsi PC (0x7efc46a3d326) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libfwupd.so.2 fwupd_device_from_variant () at /usr/lib/x86_64-linux-gnu/libfwupd.so.2 () at /usr/lib/x86_64-linux-gnu/libfwupd.so.2 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-software crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-04-10 (0 days ago) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1762617/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1785033] Re: GRUB needs to support 64-bit efi linear frame buffer address
** Also affects: grub2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1785033 Title: GRUB needs to support 64-bit efi linear frame buffer address Status in grub2 package in Ubuntu: New Status in grub2 source package in Trusty: New Status in grub2 source package in Xenial: New Status in grub2 source package in Bionic: New Status in grub2 source package in Cosmic: New Bug description: [Rationale] More firmwares support above 4G mmio configureation and the EFI Graphics Output Protocol can return a 64-bit linear frame buffer address have been implemented in some firmware/BIOS. Grub2 currently only pass 32-bit framebuffer base to kernel. The Linux kernel has already added support to handle 64-bit linear framebuffer address in the efifb driver now. So GRUB2 should support 64-bit EFI linear frame buffer address. [Impact] Some machines block booting with firmware/bios implemented 64-bit EFI linear frame buffer address,due to Grub passing incorrect(only 32-bit) EFI linear frame buffer. [Test cases] Need Bios/Firmware support, 1) Make sure the machine with the Bios implemented 64-bit EFI linear frame buffer address. some machine need to enable above 4G mmio on bios setup menu. 2) Boot up. [Solution] A patch has been committed and accepted by maintainer http://git.savannah.gnu.org/cgit/grub.git/commit/?id=886edba8770ccbc3def0af2a7d6b346d00d0af2f [Regression Potential] Minimal, it's unlikely completing the whole framebuffer address will affect those which hasn't used above 32-bits framebuffer address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1780442] [NEW] Please backport fix for & in attributes
Public bug reported: [Impact] There are instances of fwupd being unable to run updates on certain devices on Ubuntu 16.04. due to a "&" in metadata. [Test Case] * Try to perform an update on a 8bitdo affected device. [Regression Potential] * Regressions would occur in metadata processing where the fwupd daemon wouldn't be able to process it. [Other Info] This was discussed here: https://github.com/hughsie/fwupd/issues/565#issuecomment-402534337 This has been fixed in appstream-glib to prevent & in the metadata. This fix is already in 18.04 and just needs to be backported to 16.04. https://github.com/hughsie/appstream-glib/commit/6048520484101df5d33f3c852c10640e630d20cf ** Affects: fwupd Importance: Unknown Status: Unknown ** Affects: appstream-glib (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: appstream-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: appstream-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: appstream-glib (Ubuntu) Status: New => Fix Released ** Description changed: - There are instances of fwupd being unable to run updates on certain devices on Ubuntu 16.04. due to a "&" in metadata. + [Impact] + + There are instances of fwupd being unable to run updates on certain + devices on Ubuntu 16.04. due to a "&" in metadata. + + [Test Case] + + * Try to perform an update on a 8bitdo affected device. + + [Regression Potential] + + * Regressions would occur in metadata processing where the fwupd daemon + wouldn't be able to process it. + + [Other Info] + + This was discussed here: https://github.com/hughsie/fwupd/issues/565#issuecomment-402534337 This has been fixed in appstream-glib to prevent & in the metadata. This fix is already in 18.04 and just needs to be backported to 16.04. https://github.com/hughsie/appstream-glib/commit/6048520484101df5d33f3c852c10640e630d20cf ** Bug watch added: github.com/hughsie/fwupd/issues #565 https://github.com/hughsie/fwupd/issues/565 ** Also affects: fwupd via https://github.com/hughsie/fwupd/issues/565 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1780442 Title: Please backport fix for & in attributes Status in Fwupd: Unknown Status in appstream-glib package in Ubuntu: Fix Released Status in appstream-glib source package in Xenial: New Bug description: [Impact] There are instances of fwupd being unable to run updates on certain devices on Ubuntu 16.04. due to a "&" in metadata. [Test Case] * Try to perform an update on a 8bitdo affected device. [Regression Potential] * Regressions would occur in metadata processing where the fwupd daemon wouldn't be able to process it. [Other Info] This was discussed here: https://github.com/hughsie/fwupd/issues/565#issuecomment-402534337 This has been fixed in appstream-glib to prevent & in the metadata. This fix is already in 18.04 and just needs to be backported to 16.04. https://github.com/hughsie/appstream-glib/commit/6048520484101df5d33f3c852c10640e630d20cf To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1780442/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1707110] Re: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04
Thanks for confirming. I'll close this issue then. If it happens again for anyone, please open a new issue . ** Also affects: appstream-glib (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: fwupd (Ubuntu Xenial) Status: New => Fix Released ** Changed in: appstream-glib (Ubuntu) Status: Confirmed => Invalid ** Changed in: appstream-glib (Ubuntu Xenial) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1707110 Title: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04 Status in appstream-glib package in Ubuntu: Invalid Status in fwupd package in Ubuntu: Fix Released Status in appstream-glib source package in Xenial: Invalid Status in fwupd source package in Xenial: Fix Released Bug description: Even though this bug is reported [https://bugs.launchpad.net/ubuntu/+source/appstream- glib/+bug/1591868] and marked as fixed, I am having the same issue on a up to date Ubuntu 16.04 system (as you can see in the attachment). Rebooting doesn't fix the problem. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1707110/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1761005] Re: Change metadata server to upstream requested one
Already fixed in 1.0.6 release, marking bionic fix released. ** Also affects: fwupd (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: New => Fix Released ** Changed in: fwupd (Ubuntu Xenial) Status: New => Confirmed ** Changed in: fwupd (Ubuntu Artful) Status: New => Confirmed ** Changed in: fwupd (Ubuntu Xenial) Importance: Undecided => High ** Changed in: fwupd (Ubuntu Artful) Importance: Undecided => High -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1761005 Title: Change metadata server to upstream requested one Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Confirmed Status in fwupd source package in Artful: Confirmed Bug description: [Impact] fwupd is configured to use an Amazon server for downloading firmware metadata. As requested by upstream: "The current CDN (~$100/month) is kindly sponsored by Amazon, but that won't last forever. In the future we can switch to a 'dumb' provider like BunnyCDN for 1/10th of the cost. Use a CNAME we control to make switching CDN providers easy in the future." [Test Case] Still able to install firmware as before [Regression Potential] Some risk of breaking firmware updates due to server configuration, but this matches upstreams setup and is the behaviour in fwupd 1.0.6 (in bionic onwards). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1761005/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1750030] Re: Report fwupd version in user agent
Thanks Robert. I guess please re-upload for xenial then. ** Changed in: gnome-software (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1750030 Title: Report fwupd version in user agent Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Bug description: [Impact] Some firmware updates fail require a recent version of fwupd to work. Upstream has requested we update the user agent sent in HTTP requests so that they can stop sending firmware to clients that may not work. [Test Case] Check with the fwupd server that the correct user agent is being sent. [Regression Potential] Low. The fix is simply to add to the user-agent string used in HTTP requests. There are some situations that LVFS shouldn't be offering firmware to certain machines. Upstream is going to use the user agent for filtering these firmware offerings and it would be good if gnome-software can report the user agent. The following has been added to the gnome 3.20 tree: https://gitlab.gnome.org/GNOME/gnome-software/commit/9bf4ecef4daa2d31827810d672458768c3c2a2b3 Can this please be backported to xenial? Bionic can already report this as part of 3.26 gnome-software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750030/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1750030] Re: Report fwupd version in user agent
@lukasz, Thanks for looking closely. I double checked upstream more closely and it's in 3.27.4 not 3.26. So you're right it needs to be brought into bionic separately (or gnome-software in bionic needs to move to 3.27.x) https://gitlab.gnome.org/GNOME/gnome-software/commit/269337e27a044d2b0543bf06a5dd725ad3cff383 ** Changed in: gnome-software (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1750030 Title: Report fwupd version in user agent Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Xenial: Fix Committed Bug description: [Impact] Some firmware updates fail require a recent version of fwupd to work. Upstream has requested we update the user agent sent in HTTP requests so that they can stop sending firmware to clients that may not work. [Test Case] Check with the fwupd server that the correct user agent is being sent. [Regression Potential] Low. The fix is simply to add to the user-agent string used in HTTP requests. There are some situations that LVFS shouldn't be offering firmware to certain machines. Upstream is going to use the user agent for filtering these firmware offerings and it would be good if gnome-software can report the user agent. The following has been added to the gnome 3.20 tree: https://gitlab.gnome.org/GNOME/gnome-software/commit/9bf4ecef4daa2d31827810d672458768c3c2a2b3 Can this please be backported to xenial? Bionic can already report this as part of 3.26 gnome-software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750030/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1750030] [NEW] Report fwupd version in user agent
Public bug reported: There are some situations that LVFS shouldn't be offering firmware to certain machines. Upstream is going to use the user agent for filtering these firmware offerings and it would be good if gnome-software can report the user agent. The following has been added to the gnome 3.20 tree: https://gitlab.gnome.org/GNOME/gnome-software/commit/9bf4ecef4daa2d31827810d672458768c3c2a2b3 Can this please be backported to xenial? Bionic can already report this as part of 3.26 gnome-software. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: gnome-software (Ubuntu Xenial) Importance: High Assignee: Robert Ancell (robert-ancell) Status: Triaged ** Also affects: gnome-software (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1750030 Title: Report fwupd version in user agent Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Triaged Bug description: There are some situations that LVFS shouldn't be offering firmware to certain machines. Upstream is going to use the user agent for filtering these firmware offerings and it would be good if gnome-software can report the user agent. The following has been added to the gnome 3.20 tree: https://gitlab.gnome.org/GNOME/gnome-software/commit/9bf4ecef4daa2d31827810d672458768c3c2a2b3 Can this please be backported to xenial? Bionic can already report this as part of 3.26 gnome-software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750030/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1746114] Re: Move xenial to fwupd 0.8.x branch
@kabirdkng, the fwupd_0.8.3-0ubuntu2 has not yet been accepted into xenial. It's awaiting an archive administrator to perform this action. ** Changed in: fwupd (Ubuntu Xenial) Status: Opinion => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1746114 Title: Move xenial to fwupd 0.8.x branch Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: In Progress Bug description: [Impact] * Upstream has declared that 0.7.x is EOL - No further security updates will be performed for it. * Many crashers were fixed in 0.8.x. * Upstream can better maintain fwupd ecosystem wide if Ubuntu (the last ones using 0.7.x release) move to 0.8.x or newer. * Latest upstream release is 1.0.4 release, but moving to 0.9.x or 1.0.x is difficult due to many dependencies not present in Ubuntu 16.04. * Upstream spun this point release specifically for getting Ubuntu xenial on a newer maintainable version. https://groups.google.com/forum/#!topic/fwupd/R6UyaCtWbqo New Features: - Add --version option to fwupdmgr (Richard Hughes) Bugfixes: - Add a delay when calling update_prepare (Mario Limonciello) - Block owned Dell TPM updates (#339) (Mario Limonciello) - Catch invalid Dell dock component requests (Mario Limonciello) - Disable the dell plugin if libsmbios fails (Mario Limonciello) - Do not re-download firmware that exists in the cache (Richard Hughes) - Ensure the 8bitdo version is set in non-bootloader mode (Richard Hughes) - Fix a logic error with testing for a dell system (Mario Limonciello) - Fix compile with newer versions of GUdev (Richard Hughes) - Fix crash with dock connected but UEFI capsule off (Mario Limonciello) - Use new VID for 8bitdo (Richard Hughes) [Test Case] * Use fwupdmgr to check for and apply a firmware update * Use gnome-software to check for and apply a firmware update [Regression Potential] * This is a point release of the 0.8.x release which has been deemed stable. * Potential regressions would more likely exist in gnome-software which uses fwupd's interfaces to perform firmware updates. * If a regression were to occur, gnome-software may crash or not display a firmware update anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1746114/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1746114] [NEW] Move xenial to fwupd 0.8.x branch
Public bug reported: [Impact] * Upstream has declared that 0.7.x is EOL - No further security updates will be performed for it. * Many crashers were fixed in 0.8.x. * Upstream can better maintain fwupd ecosystem wide if Ubuntu (the last ones using 0.7.x release) move to 0.8.x * Upstream spun this release specifically for getting Ubuntu xenial on a newer maintainable version. https://groups.google.com/forum/#!topic/fwupd/R6UyaCtWbqo New Features: - Add --version option to fwupdmgr (Richard Hughes) Bugfixes: - Add a delay when calling update_prepare (Mario Limonciello) - Block owned Dell TPM updates (#339) (Mario Limonciello) - Catch invalid Dell dock component requests (Mario Limonciello) - Disable the dell plugin if libsmbios fails (Mario Limonciello) - Do not re-download firmware that exists in the cache (Richard Hughes) - Ensure the 8bitdo version is set in non-bootloader mode (Richard Hughes) - Fix a logic error with testing for a dell system (Mario Limonciello) - Fix compile with newer versions of GUdev (Richard Hughes) - Fix crash with dock connected but UEFI capsule off (Mario Limonciello) - Use new VID for 8bitdo (Richard Hughes) [Test Case] * Use fwupdmgr to check for and apply a firmware update * Use gnome-software to check for and apply a firmware update [Regression Potential] * This is a point release of the 0.8.x release which has been deemed stable. * Potential regressions would more likely exist in gnome-software which uses fwupd's interfaces to perform firmware updates. * If a regression were to occur, gnome-software may crash or not display a firmware update anymore. ** Affects: fwupd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: New => Fix Released ** Description changed: - [Impact] - * Upstream has declared that 0.7.x is EOL -- No further security updates will be performed for it. - * Many crashers were fixed in 0.8.x. - * Upstream can better maintain fwupd ecosystem wide if Ubuntu (the last ones using 0.7.x release) move to 0.8.x + [Impact] + * Upstream has declared that 0.7.x is EOL + - No further security updates will be performed for it. + * Many crashers were fixed in 0.8.x. + * Upstream can better maintain fwupd ecosystem wide if Ubuntu (the last ones using 0.7.x release) move to 0.8.x + + Here is the upstream changelog from the point release made for this: + + New Features: + - Add --version option to fwupdmgr (Richard Hughes) + + Bugfixes: + - Add a delay when calling update_prepare (Mario Limonciello) + - Block owned Dell TPM updates (#339) (Mario Limonciello) + - Catch invalid Dell dock component requests (Mario Limonciello) + - Disable the dell plugin if libsmbios fails (Mario Limonciello) + - Do not re-download firmware that exists in the cache (Richard Hughes) + - Ensure the 8bitdo version is set in non-bootloader mode (Richard Hughes) + - Fix a logic error with testing for a dell system (Mario Limonciello) + - Fix compile with newer versions of GUdev (Richard Hughes) + - Fix crash with dock connected but UEFI capsule off (Mario Limonciello) + - Use new VID for 8bitdo (Richard Hughes) + [Test Case] - * Use fwupdmgr to check for and apply a firmware update - * Use gnome-software to check for and apply a firmware update + * Use fwupdmgr to check for and apply a firmware update + * Use gnome-software to check for and apply a firmware update - [Regression Potential] - * This is a point release of the 0.8.x release which has been deemed stable. - * Potential regressions would more likely exist in gnome-software which uses fwupd's interfaces to perform firmware updates. - * If a regression were to occur, gnome-software may crash or not display a firmware update anymore. + [Regression Potential] + * This is a point release of the 0.8.x release which has been deemed stable. + * Potential regressions would more likely exist in gnome-software which uses fwupd's interfaces to perform firmware updates. + * If a regression were to occur, gnome-software may crash or not display a firmware update anymore. ** Description changed: [Impact] * Upstream has declared that 0.7.x is EOL - No further security updates will be performed for it. * Many crashers were fixed in 0.8.x. * Upstream can better maintain fwupd ecosystem wide if Ubuntu (the last ones using 0.7.x release) move to 0.8.x - - Here is the upstream changelog from the point release made for this: + * Upstream spun this release specifically for getting Ubuntu xenial on a newer maintainable version. + https://groups.google.com/forum/#!topic/fwupd/R6UyaCtWbqo New Features: - - Add --version option to fwupdmgr (Richard Hughes) + - Add --version option to fwupdmgr (Richard Hughes) Bugfi
[Group.of.nepali.translators] [Bug 1642812] Re: USB devices are not closed when error occurs
** Changed in: fwupd (Ubuntu Yakkety) Status: New => Won't Fix ** Changed in: fwupd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1642812 Title: USB devices are not closed when error occurs Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: New Status in fwupd source package in Yakkety: Won't Fix Status in fwupd source package in Zesty: Fix Released Bug description: In fwupd, a few of USB devices are not closed when there are some failures of operations. This issue will cause fwupd has some orphan USB nodes inside during fwupd is running. A orphan USB node might introduce memory leak and block some runtime power features as well. I proposed a upstream PR, and also put the link here. https://github.com/hughsie/fwupd/pull/73 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1642812/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
FWIW this bug was fixed upstream already. https://github.com/torvalds/linux/commit/d9018976cdb6eefc62a7ba79a405f6c9661b08a7 https://bugzilla.kernel.org/show_bug.cgi?id=195951 ** Bug watch added: Linux Kernel Bug Tracker #195951 https://bugzilla.kernel.org/show_bug.cgi?id=195951 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=195951 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Xenial: Invalid Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Status in linux-hwe-edge source package in Artful: Invalid Status in linux-oem source package in Artful: Invalid Status in linux package in openSUSE: New Bug description: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (20/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer TravelMate B113 Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell XPS 13 9350 I7. Bug may effect machines from any manufacturer that uses BIOS based on Insyde Software --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1734278] Re: Grub2 cannot boot up when 8254 time function disable
** Also affects: grub2 (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Also affects: grub2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu Xenial) Status: New => Triaged ** Changed in: grub2 (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: grub2 (Ubuntu Bionic) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: grub2 (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: grub2 (Ubuntu Bionic) Importance: Undecided => Critical -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1734278 Title: Grub2 cannot boot up when 8254 time function disable Status in HWE Next: Triaged Status in OEM Priority Project: Triaged Status in grub2 package in Ubuntu: Triaged Status in grub2 source package in Xenial: Triaged Status in grub2 source package in Bionic: Triaged Status in grub2 package in Debian: Unknown Status in grub2 package in Fedora: Confirmed Bug description: Fail to boot into Ubuntu GRUB on the platforms which legacy(8254) timer function is disabled. "8254 clock gating" is provided to disable 8254 timer to get rid of legacy and save power. The platforms with the firmware which disable the 8254 timer will fail to boot up and block on grub2 which uses the 8254 timer to calibrate the TSC. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1734278/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1730343] Re: firmware update breaks Ubuntu
I've done uploads for 1.14.1 and 1.13.1 for artful and zesty respectively. ** Tags removed: verification-needed-artful verification-needed-zesty ** Tags added: verification-failed-artful verification-failed-zesty ** Changed in: fwupdate-signed (Ubuntu Xenial) Status: New => Triaged ** Changed in: fwupdate-signed (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1730343 Title: firmware update breaks Ubuntu Status in Fwupd: New Status in fwupd package in Ubuntu: Invalid Status in fwupdate package in Ubuntu: Fix Released Status in fwupdate-signed package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Invalid Status in fwupdate source package in Xenial: Triaged Status in fwupdate-signed source package in Xenial: Triaged Status in fwupd source package in Zesty: Invalid Status in fwupdate source package in Zesty: Fix Committed Status in fwupdate-signed source package in Zesty: Fix Committed Status in fwupd source package in Artful: Invalid Status in fwupdate source package in Artful: Fix Committed Status in fwupdate-signed source package in Artful: Fix Committed Status in fwupd source package in Bionic: Invalid Status in fwupdate source package in Bionic: Fix Released Status in fwupdate-signed source package in Bionic: Fix Released Bug description: [Impact] * A few users have reported instances of not being able to boot into Ubuntu after a firmware update. This is suspected to be caused by a missing Ubuntu boot entry. * fwupdate adds an entry for doing the update to the BootOrder, but doesn't remove it. BIOS auto-creation for making boot entries typically depends on the BootOrder being empty. * This affects all releases of fwupdate since the code to add to BootOrder was also backported into the Ubuntu 16.04 release of fwupdate (0.5-2ubuntu5) [Test Case] * Perform a UEFI BIOS update after installing this package. * Ensure the system boots and there is no longer a "Linux Firmware Updater" entry present in the efibootmgr -v output. [Regression Potential] * Regressions are possible to manifest if any BIOS depends on the previous behavior. * The fixes that were backported have been upstream for a few months and no concerns have been raised upstream from them. [Other Info] Two users have reported that fwupd breaks their Ubuntu installation because the "Ubuntu" EFI boot option disappears after an update. Upstream issue: https://github.com/rhboot/fwupdate/issues/86 To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1730343/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1731252] Re: SFC30 doesn't update to the latest version
As far as I can tell, the improvements to 8bitdo came in a newer version of fwupd than exists in 16.04. https://github.com/hughsie/fwupd/commit/0abde9c39ab18cfa2dec0e651b741ea59acbf519#diff-504d274506bc17713c5afaf24682f7ae and many others. Backporting newer fwupd to Ubuntu 16.04 is not however a trivial effort due to other challenges. I would recommend that you try to run the update from a live USB stick for Ubuntu 17.10 which contains a newer fwupd. ** Also affects: fwupd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Bionic) Status: New => Fix Released ** Changed in: fwupd (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1731252 Title: SFC30 doesn't update to the latest version Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Won't Fix Status in fwupd source package in Bionic: Fix Released Bug description: Description: Ubuntu 16.04.3 LTS Release: 16.04 fwupd: Installed: 0.7.0-0ubuntu4.3 Candidate: 0.7.0-0ubuntu4.3 Version table: *** 0.7.0-0ubuntu4.3 500 500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.7.0-0ubuntu4 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages When listing devices I get: %fwupdmgr get-devices usb:00:01 Guid: a7fcfbaf-e9e8-59f4-920d-7691dc6c8699 DisplayName: SFC30 Joystick Provider: USB Flags:none Version: 0.1 Created: 2017-11-09 Trusted: none Checking the lvfs web page I see that there is newer versions available. https://fwupd.org/lvfs/device/8baed357-638e- 5b54-b582-0476bf7d6348 However when I run the update, I get this output: % fwupdmgr --verbose update Downloading 4.01 for SFC30 Joystick... Updating 4.01 on SFC30 Joystick... * Decompressing firmware Retrying as an offline update... usb:00:01 is already scheduled to be updated After this command if I list the devices, I get this output: usb:00:01 Guid: a7fcfbaf-e9e8-59f4-920d-7691dc6c8699 DisplayName: SFC30 Joystick Description: Updating the firmware on your SNES30 device improves performance and adds new features. Provider: USB Flags:none Version: 0.1 Created: 2017-11-09 AppstreamId: com.8bitdo.sfc30.firmware Name: SFC30 Summary: Firmware for the 8Bitdo SFC30 Game Controller UpdateDescription:Fixed input lag problem when used with other controllers. UpdateVersion:4.01 UpdateHash: 78ef2663beaa952415c3719447b0d2ff43e837d8 UpdateChecksumKind: sha1 License: Proprietary UpdateUri: https://fwupd.org/downloads/fe066b57c69265f4cce8a999a5f8ab90d1c13b24-8Bitdo-SFC30_NES30_SFC30_SNES30-4.01.cab UrlHomepage: http://www.8bitdo.com/sfc30/ Vendor: 8Bitdo Trusted: none What can I do to update it to the latest version? Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1731252/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1730343] Re: firmware update breaks Ubuntu
fixed in unstable via https://anonscm.debian.org/cgit/uefi/fwupdate.git/commit/?id=7b6d96818db166456bbd9aafb031e7d990e06ef8, should sync to ubuntu for bionic ** Changed in: fwupdate (Ubuntu Bionic) Status: New => Fix Committed ** Also affects: fwupdate-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1730343 Title: firmware update breaks Ubuntu Status in Fwupd: New Status in fwupd package in Ubuntu: Invalid Status in fwupdate package in Ubuntu: Fix Committed Status in fwupdate-signed package in Ubuntu: New Status in fwupd source package in Xenial: Invalid Status in fwupdate source package in Xenial: New Status in fwupdate-signed source package in Xenial: New Status in fwupd source package in Zesty: Invalid Status in fwupdate source package in Zesty: New Status in fwupdate-signed source package in Zesty: New Status in fwupd source package in Artful: Invalid Status in fwupdate source package in Artful: New Status in fwupdate-signed source package in Artful: New Status in fwupd source package in Bionic: Invalid Status in fwupdate source package in Bionic: Fix Committed Status in fwupdate-signed source package in Bionic: New Bug description: Two users have reported that fwupd breaks their Ubuntu installation because the "Ubuntu" EFI boot option disappears after an update. It might be best to consider turning off firmware updates until this issue is fixed. Upstream issue: https://github.com/rhboot/fwupdate/issues/86 To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1730343/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1730343] Re: firmware update breaks Ubuntu
Yeah I agree it's better avoided. It should SRU to 16.04's 05-2ubuntu5 too actually. ** Changed in: fwupd (Ubuntu) Status: New => Invalid ** Bug watch removed: github.com/juju-solutions/charms.reactive/issues #139 https://github.com/juju-solutions/charms.reactive/issues/139 ** Also affects: fwupdate (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: fwupdate (Ubuntu Bionic) Importance: High Status: New ** Also affects: fwupd (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Also affects: fwupdate (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fwupdate (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Xenial) Status: New => Invalid ** Changed in: fwupd (Ubuntu Zesty) Status: New => Invalid ** Changed in: fwupd (Ubuntu Artful) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1730343 Title: firmware update breaks Ubuntu Status in Fwupd: New Status in fwupd package in Ubuntu: Invalid Status in fwupdate package in Ubuntu: New Status in fwupd source package in Xenial: Invalid Status in fwupdate source package in Xenial: New Status in fwupd source package in Zesty: Invalid Status in fwupdate source package in Zesty: New Status in fwupd source package in Artful: Invalid Status in fwupdate source package in Artful: New Status in fwupd source package in Bionic: Invalid Status in fwupdate source package in Bionic: New Bug description: Two users have reported that fwupd breaks their Ubuntu installation because the "Ubuntu" EFI boot option disappears after an update. It might be best to consider turning off firmware updates until this issue is fixed. Upstream issue: https://github.com/rhboot/fwupdate/issues/86 To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1730343/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1721781] [NEW] missing firmware for i915 KBL
Public bug reported: XPS 9360 (KBL) I was running a newer kernel on xenial userspace and noticed the following in syslog: i915 :00:02.0: Direct firmware load for i915/kbl_dmc_ver1_01.bin failed with error -2 i915 :00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/downloads/firmware], disabling runtime power management. Checking in /lib/firmware/i915 and comparing https://01.org/linuxgraphics/downloads/firmware I noticed that none of the KBL firmware is available (DMC, GuC, or HuC). These commits are needed to backport this firmware into Xenial: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_dmc_ver1_01.bin?id=9facc31d772a3ed399760d2168d644f9de84d6db https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_huc_ver02_00_1810.bin?id=56016d2019e1335ed9739a3d31636db058d72d68 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_guc_ver9_14.bin?id=d7fe1272a38777a41ce9d1df80f58ace2d9e3d27 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_guc_ver9_14.bin?id=a22b7703f88a85180f00a1088cdbe739222f9cd5 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1721781 Title: missing firmware for i915 KBL Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Xenial: New Bug description: XPS 9360 (KBL) I was running a newer kernel on xenial userspace and noticed the following in syslog: i915 :00:02.0: Direct firmware load for i915/kbl_dmc_ver1_01.bin failed with error -2 i915 :00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/downloads/firmware], disabling runtime power management. Checking in /lib/firmware/i915 and comparing https://01.org/linuxgraphics/downloads/firmware I noticed that none of the KBL firmware is available (DMC, GuC, or HuC). These commits are needed to backport this firmware into Xenial: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_dmc_ver1_01.bin?id=9facc31d772a3ed399760d2168d644f9de84d6db https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_huc_ver02_00_1810.bin?id=56016d2019e1335ed9739a3d31636db058d72d68 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_guc_ver9_14.bin?id=d7fe1272a38777a41ce9d1df80f58ace2d9e3d27 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/i915/kbl_guc_ver9_14.bin?id=a22b7703f88a85180f00a1088cdbe739222f9cd5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1721781/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1642812] Re: USB devices are not closed when error occurs
** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Zesty) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1642812 Title: USB devices are not closed when error occurs Status in fwupd package in Ubuntu: New Status in fwupd source package in Xenial: New Status in fwupd source package in Yakkety: New Status in fwupd source package in Zesty: Fix Released Bug description: In fwupd, a few of USB devices are not closed when there are some failures of operations. This issue will cause fwupd has some orphan USB nodes inside during fwupd is running. A orphan USB node might introduce memory leak and block some runtime power features as well. I proposed a upstream PR, and also put the link here. https://github.com/hughsie/fwupd/pull/73 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1642812/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1646537] Re: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100%
This is actually a kernel bug where the PWM isn't saved. It affects the specific display type in this machine. It's been fixed upstream already, and was brought into Ubuntu 16.04 (See SRU https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625932). The Precision 5510 however ships with Ubuntu 14.04 + vivid HWE stack. The vivid HWE stack does not contain the fix, which is why this issue is happening. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: xorg (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Changed in: xorg (Ubuntu Xenial) Status: New => Invalid ** Changed in: xorg (Ubuntu Vivid) Status: New => Incomplete ** Changed in: xorg (Ubuntu Vivid) Status: Incomplete => Invalid ** Changed in: xorg (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1646537 Title: Backlight sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Invalid Status in linux source package in Vivid: New Status in xorg source package in Vivid: Invalid Status in linux source package in Xenial: Fix Released Status in xorg source package in Xenial: Invalid Bug description: Back-light sometimes fails to resume from suspend & screen brightness sometimes will not dim below 100% Issue is interment in occurrence. Will be reproducible with the command "sudo pm-suspend" & or close/reopen laptop lid for a period of time days or hours, then go a period of time, days or hours without being able to trigger it again. This is irrespective of running "apt-get update && apt-get upgrade -y" and has continued to be intermittent on last 3 versions of 3.19 kernel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-74.82~14.04.1-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 1 10:06:43 2016 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06e5] InstallationDate: Installed on 2016-11-22 (8 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic.efi.signed root=UUID=8eaa6744-6718-456a-bda0-762475144d35 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.14 dmi.board.name: 0W7V82 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.14:bd08/31/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0W7V82:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 5510 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev:
[Group.of.nepali.translators] [Bug 1574079] Re: USB audio device is not recognized after startup in 16.04
** Package changed: fwupdate-signed (Ubuntu) => fwupd (Ubuntu) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1574079 Title: USB audio device is not recognized after startup in 16.04 Status in fwupd package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Fix Released Status in fwupd source package in Yakkety: Fix Released Bug description: [Impact] High end USB audio devices don't work properly after fwupd is started from gnome-software. [Test case] Login to Ubuntu session and try to use a USB audio device. See if it works properly. If you are applying this upgrade and testing a regression it's important that the device isn't in a bad state to start. To guarantee this doesn't happen: 1) Apply the update 2) Power off your machine 3) Unplug device 4) Plug in device 5) Power on machine 6) Check if it works. [Regression Potential] This affects the DFU provider in Ubuntu. The fix is only made to that part of the fwupd stack. No firmware for DFU has been published to the LVFS yet, so this shouldn't have any regression risk to Ubuntu. [Original bug] Hi @all, I used the same USB audio device in all previous Ubuntu versions (Focusrite Scarlet 2i2). It is supposed to be class compliant and works an all distros flawless (even RPI2 and OSMC). After upgrading from 15.10 to 16.04 it stopped to work: after start-up it does not show up as an audio device at all (also not recognized by aplay -l). I can workaround this by unplugging it and plugging it in again after Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time plugging it in again it shows up and works great without any further issues until next restart. Maybe worth to note that I recognized today that fwupd uses continuously 100% CPU load, so I just killed it today. My Hardware (Main-board/CPU) is a bit older (Intel E8400), so could probably be some compatibility issue... regards, Tobias ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: tobias 1553 F...m pulseaudio /dev/snd/controlC1: tobias 1553 F pulseaudio /dev/snd/controlC0: tobias 1553 F pulseaudio /dev/snd/controlC2: tobias 1553 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 20:09:04 2016 InstallationDate: Installed on 2015-09-19 (217 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1574079/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1630480] Re: libsmbios doesn't support SMBIOS version 3
It's upstream too. https://github.com/dell/libsmbios/commit/3ff0ae3de6ef17eb45015c5749807419698d4490 I'll ask internally to verify nothing else is needed for libsmbios 3.0 support and when we can get a new release made. ** Also affects: libsmbios (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libsmbios (Ubuntu Yakkety) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1630480 Title: libsmbios doesn't support SMBIOS version 3 Status in libsmbios package in Ubuntu: New Status in libsmbios source package in Xenial: New Status in libsmbios source package in Yakkety: New Bug description: The upstream has a patch in the mailing list. http://lists.us.dell.com/pipermail/libsmbios- devel/2016-June/000659.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsmbios/+bug/1630480/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1621500] Re: SRU: backport fwupd 0.7.3 to xenial
** Changed in: fwupd (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1621500 Title: SRU: backport fwupd 0.7.3 to xenial Status in fwupd package in Ubuntu: Invalid Status in fwupd source package in Xenial: Triaged Bug description: [background] fwupd 0.7.3 adds support for flashing capsule updates not placed in the ESRT. It uses libsmbios to query the flashability of these packages. It also resolves the fwupd half of https://launchpad.net/bugs/1589585 which will fix unplugging a USB device causing gnome-software to check for software updates. Currently this bug will be blocked by a variety of other bugs: 1) MIR of libsmbios https://bugs.launchpad.net/ubuntu/+source/libsmbios/+bug/1603072 If/when that MIR is resolved it will need to be made effective in xenial and development release both. If any changes are required for libsmbios, they'll need to be backported to xenial too. 2) FFe for EFI tools transition in yakkety: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1620698 The rest of the tools don't need to be backported to xenial, only fwupd. In development release upgrading the other tools REQUIRES upgrading fwupd though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1621500/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1621500] [NEW] SRU: backport fwupd 0.7.3 to xenial
Public bug reported: [background] fwupd 0.7.3 adds support for flashing capsule updates not placed in the ESRT. It uses libsmbios to query the flashability of these packages. It also resolves the fwupd half of https://launchpad.net/bugs/1589585 which will fix unplugging a USB device causing gnome-software to check for software updates. Currently this bug will be blocked by a variety of other bugs: 1) MIR of libsmbios https://bugs.launchpad.net/ubuntu/+source/libsmbios/+bug/1603072 If/when that MIR is resolved it will need to be made effective in xenial and development release both. If any changes are required for libsmbios, they'll need to be backported to xenial too. 2) FFe for EFI tools transition in yakkety: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1620698 The rest of the tools don't need to be backported to xenial, only fwupd. In development release upgrading the other tools REQUIRES upgrading fwupd though. ** Affects: fwupd (Ubuntu) Importance: Undecided Status: Triaged ** Affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: Triaged ** Changed in: fwupd (Ubuntu) Status: New => Triaged ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1621500 Title: SRU: backport fwupd 0.7.3 to xenial Status in fwupd package in Ubuntu: Triaged Status in fwupd source package in Xenial: Triaged Bug description: [background] fwupd 0.7.3 adds support for flashing capsule updates not placed in the ESRT. It uses libsmbios to query the flashability of these packages. It also resolves the fwupd half of https://launchpad.net/bugs/1589585 which will fix unplugging a USB device causing gnome-software to check for software updates. Currently this bug will be blocked by a variety of other bugs: 1) MIR of libsmbios https://bugs.launchpad.net/ubuntu/+source/libsmbios/+bug/1603072 If/when that MIR is resolved it will need to be made effective in xenial and development release both. If any changes are required for libsmbios, they'll need to be backported to xenial too. 2) FFe for EFI tools transition in yakkety: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1620698 The rest of the tools don't need to be backported to xenial, only fwupd. In development release upgrading the other tools REQUIRES upgrading fwupd though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1621500/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1589585] Re: Ubuntu Software tab Installed refreshing endlessly every 2 seconds
** Also affects: gnome-software (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Yakkety) Importance: High Status: Triaged ** Also affects: fwupd (Ubuntu Yakkety) Importance: High Status: Triaged ** Changed in: fwupd (Ubuntu Xenial) Status: New => Triaged ** Changed in: gnome-software (Ubuntu Xenial) Status: New => Triaged ** Changed in: gnome-software (Ubuntu Xenial) Importance: Undecided => High ** Changed in: fwupd (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1589585 Title: Ubuntu Software tab Installed refreshing endlessly every 2 seconds Status in fwupd package in Ubuntu: Triaged Status in gnome-software package in Ubuntu: Triaged Status in fwupd source package in Xenial: Triaged Status in gnome-software source package in Xenial: Triaged Status in fwupd source package in Yakkety: Triaged Status in gnome-software source package in Yakkety: Triaged Bug description: I have fresh installed Ubuntu 16.04 Desktop 32-bit. After each install for years one of the first thing I do is uninstall some of the applications that I don't need to preserve some downloading/installing of applications that I don't need. I opened Ubuntu Software, click on Installed tab and now the problem appears. Every two seconds whole screen gets to gray and refreshing appears which takes 2 seconds. This loops endlessly. It is very frustrating, because Ubuntu Software is unusable in my case. I have asked the question on forum: http://ubuntuforums.org/showthread.php?t=2326701=13498876 and one of suggestion was to remove the software and install it back. I did: sudo apt install gnome-software sudo apt purge gnome-software sudo apt autoremove sudo apt autoclean sudo apt install gnome-software Started Ubuntu Software and the problem remains the same. P.S. New problem appeared now Ubuntu Software icon on Launcher is not the same (orange color), but it has changed (white color). But this is not huge problem, just annoyance. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jun 6 18:18:47 2016 InstallationDate: Installed on 2016-06-03 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1589585/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1591868] Re: fwupd consuming 100% CPU
** Also affects: appstream-glib (Ubuntu Yakkety)
Importance: Undecided
Status: Confirmed
** Also affects: fwupd (Ubuntu Yakkety)
Importance: Undecided
Status: Incomplete
** Also affects: appstream-glib (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: fwupd (Ubuntu Xenial)
Status: New => Invalid
** Changed in: fwupd (Ubuntu Yakkety)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1591868
Title:
fwupd consuming 100% CPU
Status in appstream-glib package in Ubuntu:
Confirmed
Status in fwupd package in Ubuntu:
Invalid
Status in appstream-glib source package in Xenial:
New
Status in fwupd source package in Xenial:
Invalid
Status in appstream-glib source package in Yakkety:
Confirmed
Status in fwupd source package in Yakkety:
Invalid
Bug description:
fwupd process has been consuming 100% of my CPU for several days now
(IBM Thinkpad x250 running fully updated 16.04).
gdb backtrace below.
Thread 2 (Thread 0x7f3272cf5700 (LWP 4496)):
#0 0x7f3279b79e8d in poll () at ../sysdeps/unix/syscall-template.S:84
No locals.
#1 0x7f327ae9331c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f327ae9342c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7f327ae93469 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f327aeb9b45 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7f3279e4f6fa in start_thread (arg=0x7f3272cf5700) at
pthread_create.c:333
__res =
pd = 0x7f3272cf5700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139854651283200,
418179942412000561, 0, 140731891236207,
139854651283904, 0, -312637405101744847,
-312613451844084431}, mask_was_saved = 0}}, priv = {pad = {
0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call =
pagesize_m1 =
sp =
freesize =
__PRETTY_FUNCTION__ = "start_thread"
#6 0x7f3279b85b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
No locals.
Thread 1 (Thread 0x7f327c926900 (LWP 4486)):
#0 0x7f3279e542b7 in __GI___pthread_rwlock_rdlock (rwlock=0x7f3279e43920
<__libc_setlocale_lock>)
at pthread_rwlock_rdlock.c:135
result = 0
wake = false
#1 0x7f3279aaf0e9 in __dcigettext (domainname=0x7f327aedee63 "glib20",
msgid1=0x7f327b4ca11a "Invalid compressed data", msgid2=0x0, plural=0,
n=0, category=5) at dcigettext.c:527
__p =
domain =
binding =
categoryname =
categoryvalue =
dirname =
xdomainname =
single_locale =
retval =
retlen = 93892446493824
saved_errno = 0
search = {domainname = 0x7ffeb262bb00 "`\234\353\teU", category =
166588464,
localename = 0x556509ededa8 "p\362\355\teU", counter = 166589040,
domain = 0x23,
translation = 0x5565fffb ,
translation_length = 93892446493792, msgid = {appended =
0x7ffeb262bb08 "",
ptr = 0x52fb0a5631f15a00 }}
foundp = 0x0
localename =
domainname_len =
#2 0x7f327b44338c in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
No symbol table info available.
#3 0x7f327b3e95f9 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
No symbol table info available.
#4 0x7f327b40d315 in g_input_stream_read () from
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
No symbol table info available.
#5 0x7f327c1ae569 in ?? () from
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
No symbol table info available.
#6 0x7f3278c51a15 in ?? () from /usr/lib/x86_64-linux-gnu/libyaml-0.so.2
No symbol table info available.
#7 0x7f3278c51cde in yaml_parser_update_buffer () from
/usr/lib/x86_64-linux-gnu/libyaml-0.so.2
No symbol table info available.
#8 0x7f3278c56498 in yaml_parser_fetch_more_tokens () from
/usr/lib/x86_64-linux-gnu/libyaml-0.so.2
No symbol table info available.
#9 0x7f3278c5b32f in yaml_parser_parse () from
/usr/lib/x86_64-linux-gnu/libyaml-0.so.2
No symbol table info available.
#10 0x7f327c1ae39b in ?? () from
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
No symbol table info available.
#11 0x7f327c1ae890 in as_yaml_from_file () from
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
No symbol table info available.
#12 0x7f327c1a9231
[Group.of.nepali.translators] [Bug 1577898] Re: thunderbolt hotplug is broken
** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Trusty) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1577898 Title: thunderbolt hotplug is broken Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Thunderbolt hotplug is broken on type-c ports. Redhat already submitted a patch for this that was accepted into upstream ACPICA, but it needs to be backported into Ubuntu's kernel. I've verified that the patch works properly using a type-C USB Ethernet dongle as well as hot-plugging a Dell TB15 dock. http://www.spinics.net/lists/linux-acpi/msg65578.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577898/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
