$ 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
I see the same behavior on a display with the same dimensions on a different
laptop:
Asus ZenBook Flip 15 UX561UD
15.6 inch 16:9, 3840 x 2160 pixel, 282 PPI
On both the Dell and the Asus:
Without the experimental setting, options offered are 100, 200 (too small), 300
(too large), 400%.
With the
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
** Description changed:
On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available
- scaling options in the Gnome 3.30.1 (Cosmic) display settings are
- limited to 100, 200, 300, and 400%. This is insufficient as 200% is too
- small and 300% is too large. The missing fractional scaling
Daniel, new gnome-control-center bug #1795483
--
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/1687246
Title:
GNOME Shell should support fractional (non-integer) Hi-DPI scaling
Public bug reported:
On my laptop's 15.6 inch, 3840 x 2160 pixel display, the available
scaling options in the Gnome 3.30.1 (Cosmic) display settings are
limited to 100, 200, 300, and 400%. This is insufficient as 200% is too
small and 300% is too large. The missing fractional scaling options are
For my 15" display with 3840*2160, without the workaround I get 100, 200 (too
small), 300 (too large), and 400. Is it intentional that with the experimental
workaround from the first comment enabled, I have 125, 150, 175 and 200% but
nothing above it?
The maximum of 200% is too small and I use
Following upstream suggestion
** Package changed: gnome-settings-daemon (Ubuntu) => xkeyboard-config
(Ubuntu)
--
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/1791367
>From the upstream report:
"A possible explanation would be that gnome-settings-daemon is not handling one
of the keys that it should be handling. And gnome-settings-daemon also disables
the kernels handling of the RFKill keys at the same time.
What you could do:
Check which key is emitted
As per analysis result in upstream report
** Package changed: gnome-shell (Ubuntu) => gnome-settings-daemon
(Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
In the upstream report for gnome-shell (https://gitlab.gnome.org/GNOME
/gnome-shell/issues/555) some analysis steps were kindly provided. It
seems that the actual cause is that gnome-settings-daemon's rfkill
plugin fails to turn on airplane mode. Following the instructions, I can
turn it on with
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)
Sorry my earlier removal of the tag was unintentional, readding
** Tags added: universalaccess
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1760399
Title:
New On-screen
Got instructions from upstream. Probably not a gnome-shell issue but I
will need a few days to run tests and figure out where the problem ist
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/726692
Title:
Screen backlight
Filed as https://gitlab.gnome.org/GNOME/gnome-shell/issues/555
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
They had both been there from the start, but I typoed it into an ii when
adding "cosmic" tag and so I restored the original
--
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/1687246
** Description changed:
The new OSK does not auto-activate reliably by selecting any text widget as
the Gnome 3.28 release notes claim:
"The new keyboard automatically activates when a text area is selected, ..."
-- https://help.gnome.org/misc/release-notes/3.28/
This does not work
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1740599
Title:
Selecting multiple files and dragging them to file manager is broken
in a Wayland
Public bug reported:
The new OSK does not auto-activate reliably by selecting any text widget as the
Gnome 3.28 release notes claim:
"The new keyboard automatically activates when a text area is selected, ..."
-- https://help.gnome.org/misc/release-notes/3.28/
This does not work with text
Bug report for discoverability:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1760399
Title:
New On-screen
Bug report for Ubuntu documentation:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1760399
Title:
New On-screen
** Tags removed: universalaccess
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1760399
Title:
New On-screen keyboard cannot be manually triggered to appear
To manage
Duh. In the above comment, it should have been:
"1. (**Chrome** [not Gnome], Firefox, Qt, whatever other toolkits...)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1760399
Title:
So after much hair pulling I contacted the author of the above mentioned
Gnome extension and he set me on the right track (thank you):
1. Auto-summon of OSK only works with application/toolkit support. Text
widgets in alien (non-Gnome or non-Gtk?) toolkits don't summon the OSK
(Gnome, Firefox,
** Tags added: touch universalaccess
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1760399
Title:
New On-screen keyboard cannot be manually triggered to appear
To manage
It seems to me that either the bug title is overly specific or the issue is
slightly different with Gnome 3.30 in Cosmic.
In Cosmic it happens for single files as well, but only when dragging between
desktop and a nautilus window. It's fine to drag between nautilus windows, and
you can drag
** Tags added: cosmic
** Tags removed: highdpi
** Tags added: highdpii
** Tags removed: highdpii
** Tags added: highdpi
--
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/1687246
Just realized that Gnome 3.30 and/or the new theme in Cosmic shows all
"Places" icons in black & white, so bookmarking makes no difference to
this. Though the inconsistency with the colorful icon in the Home folder
remains
--
You received this bug notification because you are a member of Ubuntu
The Ubuntu help for 18.04 says that you need to activate it in the
Accessibility settings, and "When you next have the opportunity to type, the
on-screen keyboard will open at the bottom of the screen."
https://help.ubuntu.com/stable/ubuntu-help/keyboard-osk.html
Neither is true for me:
1. I
Gnome 2.28 release notes: https://help.gnome.org/misc/release-
notes/3.28/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1760399
Title:
New On-screen keyboard cannot be manually
I notice that the release notes for Gnome 2.28 say "The new keyboard
automatically activates when a text area is selected". If this worked,
no activation button would be needed as far as I can tell, and I suppose
this is why there is none. However as I said in my previous comment this
is not the
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to caribou in Ubuntu.
https://bugs.launchpad.net/bugs/1760399
Title:
New On-screen keyboard cannot be manually triggered to appear
To manage notifications about
There is an extension to show a panel button to trigger it:
https://extensions.gnome.org/extension/1061/on-screen-keyboard-button/
Unfortunately, its panel button itself does not react to touch at least
for me (on Cosmic, Gnome 3.30, Wayland), which kind of defeats the
purpose
That said, in
I still have the same machine (upgraded/reinstalled to each Ubuntu
version since) and the problem has not happened in agesa
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
Still the same in Cosmic. In the upstream bug it does not seem that they
want to add it back by default (as expected really), so I'd think it's
up to Ubuntu if files on desktop remain in contrast to upstream.
"António Fernandes @antoniof · 8 months ago
Developer
The Desktop folder should become
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1720089
Title:
Desktop isn't part of "places" (left bar) in artful
To manage notifications about this bug go
Same for me on Cosmic 18.10, fresh install and up to date. I works in X
session.
I can repro it also with a single file.
nautilus version 1:3.26.4-0ubuntu3
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Description changed:
Please forgive if filed for wrong package. Problem occurs in X and
Wayland sessions but not on console, so does not seem to be kernel.
Repro on Asus UX561UD with Ubuntu 18.10 up to date:
1. Log into Gnome X or Gnome Wayland session
2. Press Fn+F2 which is the
** Description changed:
Please forgive if filed for wrong package. Problem occurs in X and
Wayland sessions but not on console, so does not seem to be kernel.
Repro on Asus UX561UD with Ubuntu 18.10 up to date:
1. Log into Gnome X or Gnome Wayland session
2. Press Fn+F2 which is the
** Description changed:
Please forgive if filed for wrong package. Problem occurs in X and
Wayland sessions but not on console, so does not seem to be kernel.
Repro on Asus UX561UD with Ubuntu 18.10 up to date:
1. Log into Gnome X or Gnome Wayland session
2. Press Fn+F2 which is the
In case it matters, the keyboard backlight is filed as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791372
--
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/1791367
Title:
Bios version is the latest from Asus
** Summary changed:
- Airplane mode key on Asus UX561UD laptop not working under X or Wayland but
working on console
+ Airplane mode key on Asus UX561UD laptop not working in gnome-shell (X or
Wayland) but working on console
** Summary changed:
- Airplane
Forgot to add: Nvidia binary drivers are installed but Nvidia is
switched off via Prime setting in nvidia-settings. Running with Intel
drivers
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
Please forgive if filed for wrong package. Problem occurs in X and
Wayland sessions but not on console, so does not seem to be kernel.
Repro on Asus UX561UD with Ubuntu 18.10 up to date:
1. Log into Gnome X or Gnome Wayland session
2. Press Fn+F2 which is the airplane mode
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.
Sorry for dropping the ball on this one, for some reason I completely
missed all notifications and I only happened to find this bug today
almost by chance :-)
Anyway, if you don't mind me asking... I understand that my workaround
of passing --with-system-groups='lpadmin root' to configure when
*** 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:
I have the same crash as Rachel whenever I unplug the DVI from my NVidia
graphics card or switch the KVM to another monitor. I use Ubuntu 17.10
latest, with mutter 3.26.2-0ubuntu0.1 installed. This does not fix the
crash.
I also get the assertion:
://bugzilla.gnome.org/attachment.cgi?id=361644)
and
compositor: Ignore offscreen windows when unredirecting
(https://bugzilla.gnome.org/attachment.cgi?id=361648)
into ubuntu packages.
Best regards,
Mario
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Tags: gnome-3.26
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
I got this error by doing nothing in particular. I was just checking
Facebook on Google Chrome when the error message popped up. Sadly I had
just made a fresh install of Ubuntu 17.10 and then installed a lot of
metapackages which I need to work.
--
You received this bug notification because you
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.
Public bug reported:
system error after the boot
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic i686
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
Date: Mon May
/~george-edison55/+archive/ubuntu/gnome-settings-
daemon
(no support yet for 17.04 though).
It seems this issue is very well documented:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/871133
https://bugzilla.gnome.org/show_bug.cgi?id=650371
Thanks.
Mario Gómez.
** Affects
Muon did not work.
sudo apt install libappstreamqt1/xenial-proposed did work after
following the EnableProposed on Xenial 16.04.2.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
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.
101 - 200 of 871 matches
Mail list logo
