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
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
--
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
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:
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
** 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
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]
#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
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
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 th
*** 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
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
** 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
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.
> 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,
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
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:
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
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 ha
** 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
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.
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
** 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
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
> 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
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
--
> 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
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
> 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
> 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
** 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)
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
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:
** 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
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.
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
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
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:
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
$ 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
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
*
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
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
**
*** 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 →
*** 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
*** 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 →
*** 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 →
** 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
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
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
nic)
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)
** 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
*** 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
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.
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):
** 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
** 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
** 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
*** 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
*** 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
*** 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)
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:
*** 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
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
s bug notification because you are subscribed to the bug
> report.
> 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/
On an Dell XPS 9360 with a 3200x1800 display it also defaults to 200%
and I reliably reproduce this bug with the 18.04 final image.
I can confirm setting the scaling to 100% in the live session resolved
the crash.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Thanks for confirming. I'll close this issue then. If it happens
again for anyone, please open a new issue .
** Also affects: appstream-glib (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: fwupd (Ubuntu Xenial)
Importance: Undecided
Status: New
**
Unfortunately this stack trace is client side, but we don't know what
actually happened on the daemon during this situation to get to the
bottom of the problem.
Can you reproduce this again? If so, it would be really useful if you
could run the daemon under debug (or possibly valgrind) to figure
The rename is done upstream, it's now suspend-then-hibernate. I'm
uploading systemd with these patches.
As for G-S-D, I've adjusted it for the rename too but it's still waiting
to be merged.
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Summary changed:
- FFe: Support
** Also affects: klibc (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
In 4.17 a new attribute is introduced to configure the hibernation
resume offset. Since Ubuntu enables a swapfile by default this attribute
is important to be able to make hibernation work
** Also affects: systemd (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/1760106
Title:
Enable configuring resume offset via
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
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
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
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)
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.
@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)
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
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.
*** 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:
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
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
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
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
FYI:
Fixed in 3.26 branch here:
https://git.gnome.org/browse/gnome-software/commit/src/gs-shell.c?h=gnome-3-26=4b1f50c2cee422c2f12c3ca84004082329490106
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
** 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
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
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.
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
** 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.
** 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
** 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
** 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
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
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
** 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
What @grofaty was seeing was that his gnome-software was refreshing
constantly. He didn't say any warnings were emitted other than when he
ran fwupd in verbose mode.
If a user disconnected/reconnected a device gnome-software will refresh,
yes. But as mentioned in
** 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/1589585
Title:
Ubuntu Software tab Installed refreshing endlessly
@seb128:
Although he mentions audio and that other issue mentions audio I don't believe
them to be the same issue. Specifically that issue deals with USB Audio
devices that contain a DFU endpoint. He doesn't have a USB audio device
contained here.
@grofaty:
As long as you followed the steps
That no-open fix was specifically for the DFU endpoint wasn't it? So if
something like that is what's needed for this scenario probably still
needs to be put together.
Alright so I think there are a few more interesting data point that are needed
here.
1) What's the kernel got to say about all
1 - 100 of 409 matches
Mail list logo
