[Bug 1979118] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT") from IA__FcConfigGetSysRoot()
> Crashing in getenv with a valid parameter like this should not be
possible so I think some heap corruption must have occurred before the
crash.
So at least as a hint coming from a report that was marked as a
duplicate of this - at least for me it's specifically when the system
had a monitor connected and it was disconnected that this issue occurs.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1979118
Title:
gnome-shell crashed with SIGSEGV in __GI_getenv("NTCONFIG_SYSROOT")
from IA__FcConfigGetSysRoot()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1979118/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
I'm adding a task for gdm to this bug. The reason is that if simpledrm is used, we've found race conditions that occur where the transition from simpledrm to the proper KMS driver may race with gdm starting up the login screen. When gdm loses the race you end up with a black screen. So please make sure that any kernels that do adopt simpledrm the matching GDM for OS releases that run this kernel (think about HWE!) will need to pick up this GDM fix as well. https://gitlab.gnome.org/GNOME/gdm/-/commit/04e119c8332a564cfad05dfb9cb6ec547d5ba954 ** Also affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
** Also affects: gdm (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gdm (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: Confirmed ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: gdm (Ubuntu Mantic) Status: New => Triaged ** Changed in: gdm (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036190] Re: fwupd running in WSL 2 in Ubuntu-22.04 fails to start
I think that this should be changed in gnome software not to try to start fwupd then when in WSL2. ** Package changed: fwupd (Ubuntu) => gnome-software (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2036190 Title: fwupd running in WSL 2 in Ubuntu-22.04 fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2036190/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Mantic has 45~beta-1ubuntu1 which picks up the fix for this. Jammy is still open. ** Changed in: gdm3 (Ubuntu Mantic) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
** Description changed: - The fbdev subsystem has been deprecated for a long time. We should drop - it in favour of using simpledrm with fbdev emulation layer. + [ Impact ] + The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. - This requires config changes: + This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer - fedora bug: - https://bugzilla.redhat.com/show_bug.cgi?id=2022385 + When this stack is enabled, it changes boot timing such that some + drivers may take a longer time to boot and GDM may hang in a black + screen. + + [ Test Plan ] + * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) + + [ Where Problems could occur ] + * Race conditions could be exposed to DE environments + * Software that expects to find DRM device at /dev/dri/card0 may have a problem. + * Some older versions of NVIDIA driver might not work properly. + + [ Other Info ] + * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2909 https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 ** Also affects: gdm via https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #2022385 https://bugzilla.redhat.com/show_bug.cgi?id=2022385 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2022385 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
I've uploaded the jammy backport of this patch into the queue, so assigning it to myself. As I have readily seen this problem on my own test kernels I'll validate it with a local kernel with the matching kconfig options when it's accepted. This can then be done in advance of waiting for matching changes landing in OEM-6.5, or HWE-6.5. ** Changed in: gdm3 (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: gdm3 (Ubuntu Jammy) Assignee: (unassigned) => Mario Limonciello (superm1) ** Description changed: - [ Impact ] + [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. + This issue has been readily reproduced in Ubuntu and reported to upstream mutter. + https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 + [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
The kernel part yes. The bug fix in GDM to prepare for whenever the kernel part happens I would think not. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
The issue won't occur in Lunar. It's only specifically a problem with gdm when a kernel has been configured this way. It's not a problem in Jammy yet, but will be a problem when such a kernel gets backported as HWE. ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Lunar) Status: New => Fix Released ** Changed in: linux (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: gdm3 (Ubuntu Lunar) Status: New => Invalid ** Changed in: gdm3 (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
The problem is specifically when 24.04's kernel backports to 22.04 it will expose the race condition to GDM. If that kernel will never backport then it won't be a problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
> Oh, wait. You are just fixing the race condition? Yeah; I see the confusion. This issue got caught up by making sure the GDM race condition was fixed at the same as when this feature is enabled. Perhaps it's better to split the GDM part of it off to it's own bug instead then. > In that case, why can you not revert the kernel config change in the HWE backport to Jammy? That's certainly a possible solution, but what happens when people run mainline kernels for testing another issue and are exposed to this? That's how I discovered it, reported it upstream and got it fixed in GDM. It's a trivial fix. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
I've split up the GDM for Jammy change into https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757 ** No longer affects: gdm3 (Ubuntu Jammy) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039757] Re: Fix race condition in gdm with simpledrm and real drm drivers
** Description changed: [ Impact ] When the kernel has been compiled with FB_EFI=n, FB_VESA=n, SIMPLEDRM=y a series of events can occur that cause simpledrm to race with GDM. When GDM loses the race then a user is left with a black screen. This series of events doesn't currently happen in Jammy kernels, but can happen from a mainline kernel or HWE kernel that enables it. To protect users from this circumstance it is better to fix the race condition. - This issue has been readily reproduced in Ubuntu and reported to upstream mutter. + This issue has been readily reproduced in Ubuntu and reported to upstream mutter. It's also already fixed in GNOME 45, included in Mantic and later. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * GDM can take longer to start up while settling [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 * the changes needed to enable this in the kernel are tracked in bug 1965303 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2039757 Title: Fix race condition in gdm with simpledrm and real drm drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2039757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
This is the upstream fix for this issue: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3324 ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039958] Re: gnome-shell session dies when locking laptop screen
*** This bug is a duplicate of bug 2034619 *** https://bugs.launchpad.net/bugs/2034619 ** This bug has been marked a duplicate of bug 2034619 [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2039958 Title: gnome-shell session dies when locking laptop screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039958/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
The fixes are identified, I don't think this should wait until GNOME 45.1 release. This issue is totally breaking suspend on several of my test systems. I've backported the fixes from the GNOME 45 branch onto this PPA build: https://launchpad.net/~superm1/+archive/ubuntu/lp2034619/+packages I've also uploaded the mutter package into the proposed queue for SRU team to look at. ** Changed in: mutter (Ubuntu Mantic) Status: Fix Committed => In Progress ** Changed in: mutter (Ubuntu Mantic) Assignee: (unassigned) => Mario Limonciello (superm1) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Sure. It wasn't opened yet when I uploaded to mantic a few days ago. Since it's open now I've: 1. uploaded a *ubuntu4 version to noble (after a local test build with noble archive worked). 2. uploaded a *ubuntu3.1 version to mantic to make sure the version string doesn't conflict since they will be different binaries. Please reject the *ubuntu4 version from the mantic-proposed queue and accept the *ubuntu3.1 version (if it looks good). ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Mario Limonciello (superm1) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
#75 You can turn on proposed and then use ppa-purge command to remove my PPA. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
This should be a different issue than the mutter issue; please open it up separately for investigation. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Package changed: mutter (Ubuntu) => mesa (Ubuntu) ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Lunar) Status: New => Won't Fix ** Also affects: mesa via https://gitlab.freedesktop.org/drm/amd/-/issues/2971 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2043640 Title: amdgpu: GPU Recovery fails, frequent hangs To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2043640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
Is this happening possibly when there is a resolution change for the eDP? If so, can you please try the latest linux-6.5.y kernel: https://kernel.ubuntu.com/mainline/v6.5.13/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2039570 Title: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2039570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
OK thanks for clarifying. Can you please still try latest 6.5.13 and 6.6.6 and see if it happens in either of those? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2039570 Title: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2039570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046992] Re: ubuntu 22.04 fwupd apt package seems broken (library / daemon version mismatch)
Do you have something in /usr/local perhaps? Or did you have a snap installed for fwupd? ** Package changed: gnome-software (Ubuntu) => fwupd (Ubuntu) ** Changed in: fwupd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2046992 Title: ubuntu 22.04 fwupd apt package seems broken (library / daemon version mismatch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2046992/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2039757] Re: Fix race condition in gdm with simpledrm and real drm drivers
I've loaded up a system with a hand built kernel that has simpledrm enabled, and then verified the problem occurred. I then updated to proposed and verified it went away. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2039757 Title: Fix race condition in gdm with simpledrm and real drm drivers To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2039757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2053207] Re: glib requires gobject-introspection >= 1.78.1-13
It's marked failed to upload on all architectures right now: INFOgir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 INFOgir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 I guess that means an epoch is needed? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2053207 Title: glib requires gobject-introspection >= 1.78.1-13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 641606] Re: Something wrong with Yelp encoding or graphics
*** This bug is a duplicate of bug 641599 *** https://bugs.launchpad.net/bugs/641599 ** This bug has been marked a duplicate of bug 641599 yelp menu items appear as cubes with numbers * You can subscribe to bug 641599 by following this link: https://bugs.edge.launchpad.net/ubuntu/+source/yelp/+bug/641599/+subscribe -- Something wrong with Yelp encoding or graphics https://bugs.launchpad.net/bugs/641606 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 641599] Re: yelp menu items appear as cubes with numbers
** Changed in: yelp (Ubuntu) Status: New => Confirmed ** Also affects: yelp (Ubuntu Maverick) Importance: Undecided Status: Confirmed -- yelp menu items appear as cubes with numbers https://bugs.launchpad.net/bugs/641599 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 643509] Re: No text at top of help page looks like code.
*** This bug is a duplicate of bug 605577 *** https://bugs.launchpad.net/bugs/605577 ** This bug has been marked a duplicate of bug 605577 Help contents title bar shows cubes with numbers instead of a proper title * You can subscribe to bug 605577 by following this link: https://bugs.edge.launchpad.net/ubuntu/+source/language-pack-gnome-en-base/+bug/605577/+subscribe -- No text at top of help page looks like code. https://bugs.launchpad.net/bugs/643509 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 642717] Re: Menu bar headings and some menu options are displayed with incorrect characters
*** This bug is a duplicate of bug 605577 *** https://bugs.launchpad.net/bugs/605577 ** This bug is no longer a duplicate of bug 642704 Boxes with numbers inside appear instead of text ** This bug has been marked a duplicate of bug 605577 Help contents title bar shows cubes with numbers instead of a proper title * You can subscribe to bug 605577 by following this link: https://bugs.edge.launchpad.net/ubuntu/+source/language-pack-gnome-en-base/+bug/605577/+subscribe -- Menu bar headings and some menu options are displayed with incorrect characters https://bugs.launchpad.net/bugs/642717 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 642713] Re: Menu bar headings and some menu options are displayed with incorrect characters
*** This bug is a duplicate of bug 605577 *** https://bugs.launchpad.net/bugs/605577 ** This bug is no longer a duplicate of bug 642704 Boxes with numbers inside appear instead of text ** This bug has been marked a duplicate of bug 605577 Help contents title bar shows cubes with numbers instead of a proper title * You can subscribe to bug 605577 by following this link: https://bugs.edge.launchpad.net/ubuntu/+source/language-pack-gnome-en-base/+bug/605577/+subscribe -- Menu bar headings and some menu options are displayed with incorrect characters https://bugs.launchpad.net/bugs/642713 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 642704] Re: Boxes with numbers inside appear instead of text
*** This bug is a duplicate of bug 605577 *** https://bugs.launchpad.net/bugs/605577 ** This bug has been marked a duplicate of bug 605577 Help contents title bar shows cubes with numbers instead of a proper title * You can subscribe to bug 605577 by following this link: https://bugs.edge.launchpad.net/ubuntu/+source/language-pack-gnome-en-base/+bug/605577/+subscribe -- Boxes with numbers inside appear instead of text https://bugs.launchpad.net/bugs/642704 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 647063] Re: Jerky h.264 video playback
Mythbuntu doesn't use gstreamer at all, so not a big deal one way or the other for us. -- Jerky h.264 video playback https://bugs.launchpad.net/bugs/647063 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-good0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 272083] Re: Zenity windows appear underneath others
** Changed in: mythbuntu Status: Confirmed => Fix Released -- Zenity windows appear underneath others https://bugs.launchpad.net/bugs/272083 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 403291] Re: Unable to change the default session for GDM
We need a better solution for this as this causes some complications in that you can't log into gnome from mythbuntu or xubuntu anymore. pitti recommended adding support to choose default.desktop to gdm by default. That means that each *-default-settings should Provides:/Conflicts: ubuntu-derivative-default-settings or so as you can only have one *-default-settings at a time. ** Changed in: gdm (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: gdm (Ubuntu) Status: New => Triaged ** Changed in: gdm (Ubuntu) Milestone: None => karmic-alpha-6 -- Unable to change the default session for GDM https://bugs.launchpad.net/bugs/403291 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962277] Re: To support Synaptics fp device
** Also affects: libfprint (Ubuntu Jammy) Importance: Medium Status: New ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1962277 Title: To support Synaptics fp device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
> https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907 This appears to have caused a regression in fwupd in Ubuntu 20.04 with details at https://github.com/fwupd/fwupd/issues/3037 fwupd-refresh.service uses DynamicUser and now hits this upstream bug: https://github.com/systemd/systemd/issues/22737 ** Bug watch added: github.com/fwupd/fwupd/issues #3037 https://github.com/fwupd/fwupd/issues/3037 ** Bug watch added: github.com/systemd/systemd/issues #22737 https://github.com/systemd/systemd/issues/22737 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
> The comment at https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992 suggests that disabling the DynamicUser= setting makes the service work again. Maybe that's worth a try, in order to get both problems solved? (i.e. shipping an override config for fwupd) > $cat /etc/systemd/system/fwupd-refresh.service.d/override.conf > [Service] > DynamicUser=no The whole point of using DynamicUser in this case was so that fwupdmgr didn't run as root when it reached out to the web to get data. Yes, certainly turning off DynamicUser in fwupd-refresh.service will solve the problem, but that is then a different threat vector. I think if turning off DynamicUser=1, then we probably need to also create a new service account for that systemd service to use. I'll open a new bug to move this discussion to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969976 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817223] Re: [disco-proposed] The list of applications in Ubuntu Software is empty
** Changed in: libxmlb (Ubuntu) Status: Triaged => Fix Released ** Changed in: libxmlb (Ubuntu Disco) Status: Won't Fix => Fix Released ** Changed in: libxmlb (Ubuntu) Assignee: Robert Ancell (robert-ancell) => Mario Limonciello (superm1) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1817223 Title: [disco-proposed] The list of applications in Ubuntu Software is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1817223/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
That message is coming from appstream-glib, somewhere around here: https://github.com/hughsie/appstream- glib/blob/843caabdeca6ae15f400f38536bc666340c30465/libappstream-glib/as- store.c#L2329 I would recommend to start out with trying a newer appstream-glib to see if that helps. ** Also affects: appstream-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1829813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1780442 Title: Please backport fix for & in attributes To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1780442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780520] Re: fwupd fails to refresh because of badly encoded data
*** This bug is a duplicate of bug 1780442 *** https://bugs.launchpad.net/bugs/1780442 Can you please bring that comment into the duplicate that I just made this marked as. I started SRU process in making the bug, but you can continue it there as you already have a test build and can confirm from your PPA it works etc. ** This bug has been marked a duplicate of bug 1780442 Please backport fix for & in attributes -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1780520 Title: fwupd fails to refresh because of badly encoded data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1780520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780442] Re: Please backport fix for & in attributes
Per discussion upstream there is a commit needed for fwupd as well to make it not abort on the bad data. So the appstream-glib tasks should get a verification-done tag and flow through, but we also need to SRU fwupd with this commit: https://github.com/hughsie/fwupd/commit/fe1c4de5a4b178cae3e4e9325ea84ff85c4b1be3 ** Also affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1780442 Title: Please backport fix for & in attributes To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1780442/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791024] Re: BIOS Update offered for Thinkpad X270 fails to update from GNOME Software
*** This bug is a duplicate of bug 1719797 *** https://bugs.launchpad.net/bugs/1719797 @Will, I'm pretty sure this is that issue; https://gitlab.gnome.org/GNOME/gnome-software/issues/341 ** Changed in: fwupd (Ubuntu) Status: New => Invalid ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1791024 Title: BIOS Update offered for Thinkpad X270 fails to update from GNOME Software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791024] Re: BIOS Update offered for Thinkpad X270 fails to update from GNOME Software
*** This bug is a duplicate of bug 1719797 *** https://bugs.launchpad.net/bugs/1719797 I can't seem to add it as an upstream tracker for whatever reason though. ** This bug has been marked a duplicate of bug 1719797 Firmware update seemingly not working -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1791024 Title: BIOS Update offered for Thinkpad X270 fails to update from GNOME Software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773503] Re: should offer restart after system firmware upgrade
*** This bug is a duplicate of bug 1719797 *** https://bugs.launchpad.net/bugs/1719797 So this is actually a duplicate of a previous issue which links to this upstream issue. https://gitlab.gnome.org/GNOME/gnome-software/issues/341 Please subscribe to the upstream issue and add comments there, thanks! ** This bug has been marked a duplicate of bug 1719797 Firmware update seemingly not working -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1773503 Title: should offer restart after system firmware upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1773503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
** Bug watch added: Red Hat Bugzilla #1580450 https://bugzilla.redhat.com/show_bug.cgi?id=1580450 ** Also affects: gnome-software (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1580450 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
** Package changed: caribou (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1730211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
** Also affects: fwupd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
This issue has been fixed upstream. It requires fixes in both gnome- software and fwupd. gnome-software fix (on the Gnome Software 3-28 branch): https://gitlab.gnome.org/GNOME/gnome-software/commit/057eea7cc03d647544b5819ff37951f7bfffb77e fwupd fix (on the 1_0_X branch): https://github.com/hughsie/fwupd/commit/80f6e995f68ad7559c4a386a58e9ee43750bf6aa -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762561] Re: No message about plugging in laptop needed for updating firmware in Ubuntu software center
*** This bug is a duplicate of bug 1694076 *** https://bugs.launchpad.net/bugs/1694076 ** This bug has been marked a duplicate of bug 1694076 No error message on firmware update fail -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1762561 Title: No message about plugging in laptop needed for updating firmware in Ubuntu software center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1762561/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1694076] Re: No error message on firmware update fail
Since this was in 3-26 and now at 3-28 in bionic, closing this issue. ** Changed in: gnome-software (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1694076 Title: No error message on firmware update fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1694076/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
** Changed in: fwupd (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
** Also affects: gnome-software (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: fwupd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-software (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: fwupd (Ubuntu Bionic) Assignee: (unassigned) => Mario Limonciello (superm1) ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: fwupd (Ubuntu) Assignee: (unassigned) => Mario Limonciello (superm1) ** No longer affects: gnome-software -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756006] Re: FFe: Support suspend-then-hibernate
When I did those PR upstream I did it with a swapfile actually on Ubuntu. The key comes down to how initramfs-tools hands off the offsets. It's kinda a jumbled mess though. I started a discussion here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890950 but it got stalled and I got busy with other stuff and didn't resume it. ** Bug watch added: Debian Bug tracker #890950 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890950 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: FFe: Support suspend-then-hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756006] Re: FFe: Support suspend-then-hibernate
Try d-feet as root. I think I recalled seeing this too. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: FFe: Support suspend-then-hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
** Description changed: + The fix for this particular issue is tracked in SRU bug + https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 + + Regression potential: + Fixes for this particular bug would have the risk to manifest in devices not showing up in gnome-software, but this risk is very low. + + Test case: + 1) Run a UEFI firmware update from Gnome software. + 2) Make sure that the update disappears from the listing after pressing the update button. + + Original bug: + Ubuntu 17.10 On a dell latitude 5580, the firmware update seems to not work while it actually does. 1. Gnome software reports there is a new firmware update. 2. I click "update now" 3. The update disappears for a few seconds, then reappears. 4. When I reboot my laptop, the laptop goes into firmware update modus, updates the firmware, and starts Ubuntu. What I expect: After clicking "update now", Gnome software tells me my computer has to restart the update. Either the update is listed and greyed out with a "reboot required" message, or the update is not visible. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763390] Re: gnome-software crashed with signal 5
*** This bug is a duplicate of bug 1760795 *** https://bugs.launchpad.net/bugs/1760795 ** This bug is no longer a duplicate of bug 1756695 gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc ** This bug has been marked a duplicate of bug 1760795 gnome-software leaks file descriptors -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1763390 Title: gnome-software crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1761010] Re: gnome-software crashed with signal 5 in g_main_context_new → g_dbus_connection_send_message_with_reply_sync → g_dbus_connection_call_sync_internal → g_dbus_connection_call_with_unix_
*** This bug is a duplicate of bug 1760795 *** https://bugs.launchpad.net/bugs/1760795 ** This bug is no longer a duplicate of bug 1756695 gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc ** This bug has been marked a duplicate of bug 1760795 gnome-software leaks file descriptors -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1761010 Title: gnome-software crashed with signal 5 in g_main_context_new → g_dbus_connection_send_message_with_reply_sync → g_dbus_connection_call_sync_internal → g_dbus_connection_call_with_unix_fd_list_sync → g_dbus_proxy_call_sync_internal → g_dbus_proxy_call_sync → fwupd_client_get_devices → gs_plugin_fwupd_add_updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1761010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1761061] Re: gnome-software crashed with signal 5
*** This bug is a duplicate of bug 1760795 *** https://bugs.launchpad.net/bugs/1760795 ** This bug is no longer a duplicate of bug 1756695 gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc ** This bug has been marked a duplicate of bug 1760795 gnome-software leaks file descriptors -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1761061 Title: gnome-software crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1761061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756695] Re: gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc
*** This bug is a duplicate of bug 1760795 *** https://bugs.launchpad.net/bugs/1760795 I'll mark it as such, if we have evidence it's not at some point we can re-visit. ** This bug has been marked a duplicate of bug 1760795 gnome-software leaks file descriptors -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1756695 Title: gnome-software crashed with signal 5 in g_dbus_proxy_call_sync → fwupd_client_get_upgrades → gs_plugin_fwupd_add_updates → gs_plugin_loader_call_vfunc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1756695/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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_search_app_info
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 Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1614105/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
fwupd -- This has been fixed upstream in the 1.1.3 release, so marking the development release task complete. The 1.0.9 SRU bug for bionic is here: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999 gnome-software There is an SRU in progress for 3.28.1-0ubuntu4.18.04.4 that I don't want to de-rail by uploading a new patch for this bug. Once that one is in https://gitlab.gnome.org/GNOME/gnome-software/commit/057eea7cc03d647544b5819ff37951f7bfffb77e should be added to this SRU bug. ** Changed in: fwupd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798470] [NEW] gnome-software can't handle composite CAB files
Public bug reported: [Impact] Double clicking a composite CAB file containing multiple firmware files displays an error message in gnome-software. This prevents installing composite firmware CAB files via a GUI unless they come from LVFS. [Test Case] * Double click a composite CAB file * Make sure that it display in gnome software [Regression Potential] * Regression potential is low. The new code paths are only run when processing a CAB file with multiple payloads. [Other info] This patch is available here: https://gitlab.gnome.org/GNOME/gnome- software/commit/77248099f966cfbaa45542e2838b4b84a18e738f ** Affects: gnome-software (Ubuntu) Importance: Undecided Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: gnome-software (Ubuntu Bionic) Importance: Undecided Assignee: Robert Ancell (robert-ancell) Status: New ** Affects: gnome-software (Ubuntu Dd-series) Importance: Undecided Assignee: Robert Ancell (robert-ancell) Status: New ** Also affects: gnome-software (Ubuntu Dd-series) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Dd-series) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798470 Title: gnome-software can't handle composite CAB files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798470] Re: gnome-software can't handle composite CAB files
$ gnome-software --version gnome-software 3.30.2 $ xdg-open DellUsbCDockFirmwareUpdateLinux_00.00.07.cab Now does the right thing ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798470 Title: gnome-software can't handle composite CAB files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
I've tested the fwupd half of this SRU (couldn't test the gnome-software as it's not yet in place). The fwupd half works properly. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798470] Re: gnome-software can't handle composite CAB files
I've upgraded on a bionic machine to 3.28.1-0ubuntu4.18.04.5. xdg-open FirmwareUpdateLinux_00.00.07.cab opens a composite CAB file in gnome-software now. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798470 Title: gnome-software can't handle composite CAB files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
** Also affects: fwupd (Ubuntu) Importance: Undecided Status: New ** No longer affects: fwupd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1694076] Re: No error message on firmware update fail
FYI: Fixed in 3.26 branch here: https://git.gnome.org/browse/gnome-software/commit/src/gs-shell.c?h=gnome-3-26&id=4b1f50c2cee422c2f12c3ca84004082329490106 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1694076 Title: No error message on firmware update fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1694076/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
I've filed that issue upstream. ** Bug watch added: GNOME Bug Tracker #789574 https://bugzilla.gnome.org/show_bug.cgi?id=789574 ** Also affects: gnome-software via https://bugzilla.gnome.org/show_bug.cgi?id=789574 Importance: Unknown Status: Unknown ** Changed in: gnome-software (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
I suspect it to actually be gnome-session is the problem, but let's see what they say. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 185563] Re: seahorse agent doesn't work with gnupg smartcard readers
Closing this bug per https://mail.gnome.org/archives/distributor- list/2015-August/msg0.html and https://bugzilla.gnome.org/show_bug.cgi?id=644415 ** Changed in: seahorse (Ubuntu) Status: Triaged => Won't Fix ** Bug watch added: GNOME Bug Tracker #644415 https://bugzilla.gnome.org/show_bug.cgi?id=644415 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/185563 Title: seahorse agent doesn't work with gnupg smartcard readers To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/185563/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730343] Re: firmware update breaks Ubuntu
Adjusting various tasks for the relevant components. I'm pretty sure this is a regression that is only getting exercised in certain situations of boot entries. Most notably there was a change was that fwupdate was effectively updated to the "9" release in 0.5-2ubuntu5. This version adds the "Linux Firmware Updater" entry to the boot entry list at the end. If there isn't an "ubuntu" entry earlier on, it's possible that entry is sticking around. The BIOS will only try to build automatic entries if the list was empty, which it's not now. There are two fixes in upstream for this that may help, but that's predicated on my hypothesis being correct. https://github.com/rhboot/fwupdate/commit/9bebde2c8b8960d86326f805743edb9293a6d173 https://github.com/rhboot/fwupdate/commit/cd9ea4cbdc93da922ce9abc45c7de63fe252ecc8 My hypothesis can be confirmed by seeing efibootmgr -v output before a failed update. If currently in a failed state, booting a USB key in UEFI mode (without creating a boot entry in BIOS setup) should be able to indicate this too. ** No longer affects: ubiquity ** Package changed: gnome-software (Ubuntu) => fwupd (Ubuntu) ** Also affects: fwupdate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1730343 Title: firmware update breaks Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1730343/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
FYI - 1.8.4 synced from Debian to Ubuntu kinetic now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
> A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". It's not a function of the OS, it's a function of the underlying hardware, firmware, and firmware configuration for your given system. The "!" in the HSI string is controlled by OS behavior (such as encrypted swap, taint, etc). At least on a pre-production Lenovo Z13 I can get HSI-2, depending on whether Lenovo has SPI replay protection in the production hardware I might be able to get all the way to HSI 4. Host Security ID: HSI:2! (v1.8.4) HSI-1 ✔ Fused platform:Locked ✔ Rollback protection: Enabled ✔ Supported CPU: Valid ✔ TPM empty PCRs:Valid ✔ TPM v2.0: Found ✔ UEFI platform key: Valid HSI-2 ✔ IOMMU: Enabled ✔ Platform Debugging:Locked ✔ SPI write protection: Enabled ✔ TPM PCR0 reconstruction: Valid HSI-3 ✔ Pre-boot DMA protection: Enabled ✔ Suspend-to-idle: Enabled ✔ Suspend-to-ram:Disabled ✘ SPI replay protection: Disabled HSI-4 ✔ Encrypted RAM: Encrypted -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1985856] Re: Update Mutter to 42.5
I tested 42.5-0ubuntu1 on a Z13 (which prompted the heuristics change) and can confirm it's working with Wayland and the non-functional resolutions are no longer offered. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1985856 Title: Update Mutter to 42.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1985856/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
I just downgraded an XPS 9370 and then upgraded it again using gnome- software 3.28.1-0ubuntu4.18.04.8 and it works like I expected. ** Tags removed: artful verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798470] Re: gnome-software can't handle composite CAB files
Yes, confirmed this is still fixed in 3.18.1-0ubuntu4.18.04.8. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1798470 Title: gnome-software can't handle composite CAB files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1811169] Re: Device firmware update does not detect AC power
To me this sounds like it's probably Gnome Software not fwupd. ** Changed in: fwupd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1811169 Title: Device firmware update does not detect AC power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1811169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703445] [NEW] version comparisons are done wrong
Public bug reported: This was raised in https://github.com/hughsie/fwupd/pull/119: "version of bootloader incorrect: failed predicate [BOT01.0[0-3]_* regex BOT01.02_B0014]" This is a bug in appstream-glib, that was fixed in appstream-glib 0.6.13. https://github.com/hughsie/appstream-glib/commit/a7ca77c563fd6898928ed4b083d8b36b477f45cc Can this please be backported to Ubuntu zesty? It will allow better fwupd unifying plugin testing. ** Affects: appstream-glib (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: appstream-glib (Ubuntu Zesty) Importance: Undecided Status: New ** Affects: appstream-glib (Ubuntu Artful) Importance: Undecided Status: Fix Released ** Also affects: appstream-glib (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: appstream-glib (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: appstream-glib (Ubuntu Artful) Status: New => Incomplete ** Changed in: appstream-glib (Ubuntu Artful) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1703445 Title: version comparisons are done wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1703445/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
dell-recovery has dropped the code related to aptdaemon. https://github.com/dell/dell-recovery/commit/df1e943cd111c24e1cf3357701caace177f46de8 It will be part of the next release. ** Changed in: dell-recovery (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1591868] Re: fwupd consuming 100% CPU
** Also affects: appstream-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1591868 Title: fwupd consuming 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1591868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1589585] Re: Ubuntu Software tab Installed refreshing endlessly every 2 seconds
I'm going to set both of these to triaged. In order to resolve the warnings being emitted continually, it will require moving to: fwupd 0.7.1+ gnome-software 3.21 It won't fix grofaty's underlying issue (stuff falling off the bus continually) but it will at least prevent that from causing a check for FW updates over and over. ** Changed in: fwupd (Ubuntu) Status: New => Triaged ** Changed in: gnome-software (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1589585 Title: Ubuntu Software tab Installed refreshing endlessly every 2 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1589585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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_search_app_info
There's a bunch of reports of this on the error tracker. Here's the BT
from the most recent one (nothing private in there I can see).
Stacktrace
#0 0x7f5dcd1754a0 in as_store_load_yaml_file (error=0x7ffdd3cfeb40,
cancellable=0x0, file=0x55dc2db9a900, store=0x55dc2db4b880) at as-store.c:1135
tmp =
ctx = 0x55dc2db8e800
icon_path = 0x0
root = 0x55dc2db9be40
app_n =
n =
tok = 0x0
#1 as_store_from_file_internal (store=store@entry=0x55dc2db4b880,
file=file@entry=0x55dc2db9a900, id_prefix=id_prefix@entry=0x7f5dcd17e9ae
"system", cancellable=cancellable@entry=0x0, error=error@entry=0x7ffdd3cfeb40)
at as-store.c:1371
filename = 0x55dc2db6c890
"/var/lib/app-info/yaml/de.archive.ubuntu.com_ubuntu_dists_xenial-backports_main_dep11_Components-amd64.yml.gz"
icon_prefix = 0x0
error_local = 0x0
root = 0x0
ptask = 0x55dc2db8e870
__func__ = "as_store_from_file_internal"
#2 0x7f5dcd175ab7 in as_store_load_app_info_file (error=0x7ffdd3cfeb40,
cancellable=0x0, path_xml=0x55dc2dbebb20
"/var/lib/app-info/yaml/de.archive.ubuntu.com_ubuntu_dists_xenial-backports_main_dep11_Components-amd64.yml.gz",
id_prefix=0x7f5dcd17e9ae "system", store=0x55dc2db4b880) at as-store.c:2068
file = 0x55dc2db9a900
ptask = 0x55dc2db8ea90
#3 as_store_load_app_info (store=store@entry=0x55dc2db4b880,
id_prefix=id_prefix@entry=0x7f5dcd17e9ae "system",
path=path@entry=0x55dc2db57700 "/var/lib/app-info/yaml",
flags=flags@entry=AS_STORE_LOAD_FLAG_APP_INFO_SYSTEM,
cancellable=cancellable@entry=0x0, error=error@entry=0x7ffdd3cfecd8) at
as-store.c:2118
error_store = 0x0
filename_md = 0x55dc2dbebb20
"/var/lib/app-info/yaml/de.archive.ubuntu.com_ubuntu_dists_xenial-backports_main_dep11_Components-amd64.yml.gz"
tmp =
dir = 0x55dc2db6c420
error_local = 0x0
tok = 0x55dc2db4b868
#4 0x7f5dcd176131 in as_store_search_app_info
(store=store@entry=0x55dc2db4b880,
flags=flags@entry=AS_STORE_LOAD_FLAG_APP_INFO_SYSTEM,
id_prefix=id_prefix@entry=0x7f5dcd17e9ae "system",
path=path@entry=0x55dc2db4e440 "/var/lib/app-info",
cancellable=cancellable@entry=0x0, error=error@entry=0x7ffdd3cfecd8) at
as-store.c:2333
dest = 0x55dc2db57700 "/var/lib/app-info/yaml"
supported_kinds = {0x7f5dcd180d6d "yaml", 0x7f5dcd17f659 "xmls", 0x0}
i =
#5 0x7f5dcd176be4 in as_store_search_per_system (error=,
cancellable=0x0, flags=, store=) at
as-store.c:2535
dest1 = 0x55dc2db4e440 "/var/lib/app-info"
dest2 = 0x0
data_dirs = 0x55dc2db4e420
i =
ptask = 0x55dc2db4e2f0
#6 as_store_load (store=, flags=,
cancellable=0x0, error=) at as-store.c:2683
ptask = 0x55dc2db4e220
tok = 0x55dc2db4b868
#7 0x55dc2d1479c7 in main (argc=1, argv=0x7ffdd3cfee98) at fu-main.c:2126
priv = 0x55dc2db49700
immediate_exit = 0
ret =
timed_exit = 0
context = 0x55dc2db48af0
owner_id = 0
retval = 1
options = {{long_name = 0x55dc2d157408 "timed-exit", short_name = 0
'\000', flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x7ffdd3cfecd4,
description = 0x55dc2d157413 "Exit after a small delay", arg_description =
0x0}, {long_name = 0x55dc2d15742c "immediate-exit", short_name = 0 '\000',
flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x7ffdd3cfecd0, description =
0x55dc2d157ab0 "Exit after the engine has loaded", arg_description = 0x0},
{long_name = 0x0, short_name = 0 '\000', flags = 0, arg = G_OPTION_ARG_NONE,
arg_data = 0x0, description = 0x0, arg_description = 0x0}}
error = 0x0
config_file = 0x0
config = 0x0
Thread Stacktrace
.
Thread 2 (LWP 1639):
#0 0x7f5dcab45e8d in poll () at ../sysdeps/unix/syscall-template.S:84
No locals.
#1 0x7f5dcbe5f39c in g_main_context_poll (priority=2147483647, n_fds=2,
fds=0x7f5dbc0008c0, timeout=, context=0x55dc2db62d00) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135
poll_func = 0x7f5dcbe6e290
#2 g_main_context_iterate (context=context@entry=0x55dc2db62d00,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835
max_priority = 2147483647
timeout = -1
some_ready =
nfds = 2
allocated_nfds = 2
fds = 0x7f5dbc0008c0
#3 0x7f5dcbe5f4ac in g_main_context_iteration (context=0x55dc2db62d00,
may_block=may_block@entry=1) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901
retval =
#4 0x7f5dcbe5f4e9 in glib_worker_main (data=) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:5672
No locals.
#5 0x7f5dcbe85bc5 in g_thread_proxy (data=0x55dc2db4d850) at
/build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gthread.c:780
thread = 0x55dc2db4d850
#6 0x7f5dcae1b6fa in start_thread (arg=0x7f5dc3cc1700) at
pthread_create.c:333
__res =
[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 Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1591868 Title: fwupd consuming 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1591868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1591868] Re: fwupd consuming 100% CPU
** Also affects: libyaml (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1591868 Title: fwupd consuming 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1591868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1589585 Title: Ubuntu Software tab Installed refreshing endlessly every 2 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1589585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1627964] Re: fwupd assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/fwupd/fwupd': free(): invalid pointer: 0x000055f0c0f9f141 ***
** Information type changed from Private to Public ** Also affects: appstream-glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1627964 Title: fwupd assert failure: *** Error in `/usr/lib/x86_64-linux- gnu/fwupd/fwupd': free(): invalid pointer: 0x55f0c0f9f141 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1627964/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1637024] Re: fwupd consuming very high cpu after startup/login
This was confirmed upstream to be caused by a problem in appstream-glib. 16.10 will need to either move to 0.6.4 or backport a handful of patches. https://github.com/hughsie/fwupd/issues/70 ** Changed in: fwupd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1637024 Title: fwupd consuming very high cpu after startup/login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1637024/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1741632] Re: FW update error: could not find thunderbolt device
*** This bug is a duplicate of bug 1741509 *** https://bugs.launchpad.net/bugs/1741509 This was reported to me through Github. https://github.com/dell/thunderbolt-nvm-linux/issues/8 It's already been fixed upstream and I have an SRU bug filed here: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1741509 it's waiting for archive admin to accept. ** This bug has been marked a duplicate of bug 1741509 Thunderbolt updates on Dell systems fail to apply if nothing connected ** Bug watch added: github.com/dell/thunderbolt-nvm-linux/issues #8 https://github.com/dell/thunderbolt-nvm-linux/issues/8 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1741632 Title: FW update error: could not find thunderbolt device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1741632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719797] Re: Firmware update seemingly not working
That upstream issue has migrated to https://gitlab.gnome.org/GNOME /gnome-software/issues/253. It seems Launchpad can't track it anymore. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1719797 Title: Firmware update seemingly not working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1719797/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1750030 Title: Report fwupd version in user agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1750030 Title: Report fwupd version in user agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1750030 Title: Report fwupd version in user agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1707110] Re: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04
Hi All, Those affected by this, can anyone readily reproduce it still? If so, can you please try to upgrade to the version of fwupd in xenial-proposed to see if it persists? Thanks, ** Also affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Changed in: fwupd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1707110 Title: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1707110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756006] [NEW] FFe: Support suspend-to-hibernate
Public bug reported: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: FFe: Support suspend-to-hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756006] Re: FFe: Support suspend-to-hibernate
No, not on modern system. We haven't used that technology for a while. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: FFe: Support suspend-to-hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1756006] Re: FFe: Support suspend-to-hibernate
Gsd is pushing for the name change in systemd, so I'm going to get that upstreamed before bringing this into Ubuntu. (Suspend to hibernate to suspend then hibernate). In terms of UI where would it Land? I figure it should be a policy setting on systems that ship with it, but you're probably right that policy should be viewable and changeable if someone doesn't want this. On Wed, Mar 28, 2018, 09:21 Iain Lane wrote: > The systemd part is OK since it's cherry-picks - +1 for uploading that. > > For g-s-d I would prefer to wait for it to be more firm upstream, > especially with regard to the naming. So I vote for waiting until it's > committed there. It might be helpful/useful/necessary for that to hang > out on #control-center on gnome IRC. > > You don't plan any UI changes for 18.04, right? As an aside, it seems > like there probably should be some UI for this in the future. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1756006 > > Title: > FFe: Support suspend-to-hibernate > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: FFe: Support suspend-to-hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1544376] Re: Enable firmware support
fwupdate/fwupdate-signed's MIR was approved: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1508926/comments/9 Still waiting on fwupd. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1544376 Title: Enable firmware support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1544376/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1556586] [NEW] apt-plugin.patch causes failures with .CAB files
Public bug reported: I've got current version of gnome-software installed (3.19.92~git20160310.0c17ea0-0ubuntu1) but rebuilt with firmware support. No source changes, just build with libfwupd-dev in environment. When I double click a .CAB firmware package I get an error about dpkg- dev output format being incorrect. This is a bit odd since .CAB is only supposed to be handled by the fwupd plugin IIRC. Anyhow, I run gnome-software with --verbose and get this result: (gnome-software:14762): As-DEBUG: run 0x2404850~GsPlugin::fwupd(gs_plugin_filename_to_app) (gnome-software:14762): GsPlugin-DEBUG: key Version (gnome-software:14762): GsPlugin-DEBUG: key Guid (gnome-software:14762): GsPlugin-DEBUG: key Size (gnome-software:14762): GsPlugin-DEBUG: key Vendor (gnome-software:14762): GsPlugin-DEBUG: key Name (gnome-software:14762): GsPlugin-DEBUG: key Summary (gnome-software:14762): GsPlugin-DEBUG: key Description (gnome-software:14762): GsPlugin-DEBUG: key UrlHomepage (gnome-software:14762): GsPlugin-DEBUG: key License (gnome-software:14762): Gs-DEBUG: nonfree licence from (null): '@LicenseRef-proprietary' (gnome-software:14762): GsPlugin-DEBUG: key Trusted (gnome-software:14762): As-DEBUG: run 0x2404850~GsPlugin::apt(gs_plugin_filename_to_app) (gnome-software:14762): Gs-WARNING **: failed to convert to GsApp: dpkg-deb output format incorrect: "" As I can tell this stuff comes from apt-plugin.patch, so it's mistakenly processing .CAB files in addition to .DEB files. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1556586 Title: apt-plugin.patch causes failures with .CAB files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1556586/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
