$ 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
Bugs, wh
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
* Mak
Since the backport of bolt 0.4 (with force power support that conflicted
with fwupd) is what introduced the need for this SRU adjusting the
importance.
** Changed in: bolt (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubunt
As another point to be made; the 1.0.6 release was reported by Valve to
cause problems in Steam with Nintendo switch controllers. The issue was
fixed in the 1.0.8 release included in this SRU (mentioned in the
changelog above).
--
You received this bug notification because you are a member of Ub
The fwupd 1.0.9 SRU bug is here: #1791999
SRU team:
Ideally, please process these at the same time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798014
Title:
[sru] backport 0.5 release to bionic
Public bug reported:
[Impact]
* The bolt 0.4 release introduced support for Thunderbolt force power, but it
has been reported that this conflicts with the fwupd force power support. This
is a regression as a result of 0.4 being backported to bionic.
* Bolt 0.5 will work together with other ap
** Changed in: fwupd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740889
Title:
Logitech K780 Firmware Update Fails
To manage notifications about t
The Logitech plugin was re-written in fwupd 1.1.2. can you please re-
retry this again?
You can install a snap now to easily try:
1) apt remove fwupd
2) snap install fwupd --classic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
This particular plugin has been made more resilient in future releases.
Can you please see if you can still reproduce this issue in Ubuntu
18.04? If so, please file a new bug with the relevant details.
** Changed in: fwupd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug
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.
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
** Ch
Given it can't be reproduced anymore, I'm going to mark this one
invalid.
If you do happen to reproduce this issue, please re-open or open a new bug with
the following:
1) test with 1.0.x or 1.1.x versions (either packaged or from a snap are fine)
2) Test if running the daemon under valgrind trig
** Changed in: fwupd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631002
Title:
fwupd crashed with SIGSEGV in malloc_consolidate()
To manage notificat
*** 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 n
Just to connect the dots, this particular fix is:
https://github.com/hughsie/fwupd/commit/86fdd975adbb725965d8a015994f023469e697d8
#diff-22684cccbec07d4328eaef43086e6f47
It's in the 1.0.9 release that will be SRUed by
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999
** Changed in: fwu
*** 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
I don't see any evidence this is a problem with fwupd. Marking invalid.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644899
Title:
pac
*** 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 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
** Changed in: fwupd (Ubuntu)
Status: New => Confirmed
** Changed in: fwupd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793965
Title:
Firmware upd
I've double checked the reports on this error and it hasn't occurred since
16.04 on anything. It also doesn't occur on the 0.8 based release in 16.04.
At this point the 0.7 release is in deep maintenance mode and it won't be fixed.
** Changed in: fwupd (Ubuntu)
Status: New => Won't Fix
-
** 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
** Description changed:
- Software & Updates keeps notifying me there is a new update available
- related to Thunderbolt NVM for Xps notebook 9360, from version 00.00 to
- version 21.00. See the attached screenshot.
+ The fix for this particular issue is tracked in SRU bug
+ https://bugs.launchpad
@brian-murray,
I've updated those two bugs with those two fields. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791999
Title:
Update to the 1.0.9 release
To manage notifications about this
@seb128, given my above comments will you also SRU to 18.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795864
Title:
[ffe] Update to 0.5
To manage notifications about this bug go to:
https://b
Actually depending on order of events, I could envision that bolt 0.4 is
going to cause problems with earlier fwupd version too though even. If
it gets dbus activated before fwupd starts there will be potentially a
timing problem
There was a reason we added the API to let bolt and fwupd communica
@seb128,
Yes, this can cause problems in bionic too if on fwupd 1.0.9 or later
(which also has the backport for bolt force power). Currently bionic
has fwupd 1.0.6. There is an SRU (bug 1791999) to upgrade to 1.0.9, so
I believe it's worth upgrading to 0.5 in bionic as well.
--
You received th
Actually we recently debugged upstream that the 0.4 release is causing
problems with fwupd 1.1.2 in fighting for who controls Thunderbolt force
power.
If you can upgrade to 0.5 I believe that @BjoernDaase should be able to
help to validate it.
https://github.com/hughsie/fwupd/issues/774#issuecomm
Try d-feet as root. I think I recalled seeing this too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756006
Title:
FFe: Support suspend-then-hibernate
To manage notifications about this bug go t
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 wit
Hi, any progress on reviewing this item? It's been in the queue for a
while now with no comments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791999
Title:
Update to the 1.0.9 release
To manage
** Also affects: fwupd (Ubuntu Cosmic)
Importance: Medium
Status: Confirmed
** Also affects: fwupd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: fwupd (Ubuntu Cosmic)
Status: Confirmed => Fix Released
** Changed in: fwupd (Ubuntu Bionic)
Statu
My suspicion around this is that it's not actually the dock being reset, but
rather an MST hub being placed into "high" power mode. The TB16 contains two
MST hubs.
The current configuration of monitors you have plugged in probably doesn't
exercise both MST hubs, so one of them is operating in "
Can you please add --verbose to the ExecStart line of the systemd unit
and share journal output?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793965
Title:
Firmware update daemon resets Dell TB16
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719797
Title:
Firmware update seemingly not working
To manage notifications about this bug
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
*** 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
Bugs, which is subscribed to Ubun
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/hugh
** Also affects: fwupd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719797
Title:
Firmware update seemingly not working
To manage notification
** Package changed: caribou (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730211
Title:
Unable to type capital letters using onscreen keyboard
To manage notifications a
@grainert,
There is a BIOS option that will allow thunderbolt to work pre-boot, but
FYI it's a security risk to do so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778020
Title:
devices not autho
** Changed in: fwupd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791407
Title:
Thinkpad L570 UEFI destroyed after BIOS update
To manage notifica
** 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
*** 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 ther
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311908
Title:
Installer on mythbuntu is too wide and cannot be resized
To manag
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446099
Title:
mythbuntu installer crash: Unable to install 'cryptsetup' due to
** Changed in: ubiquity (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613129
Title:
1st install would not boot. Crashed when trying to reinstall
To manage
*** 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 notificat
*** 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)
** Changed in: fwupd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791999
Title:
Update to the 1.0.9 release
To manage notifications about this bug go to
Panamera chip (Mario Limonciello)
- - Add validation for Titan Ridge Thunderbolt devices (Andrei Emeltchenko)
- - Use boltd force power API if available (Mario Limonciello)
+ - Add support for more Wacom tablets (Richard Hughes)
+ - Add support for the Synaptics Panamera chip (Mario Limonciello)
28058?utm_source=github_status&utm_medium=notification
[Other Info]
Here is the changelog for 1.0.9:
New Features:
- Add support for more Wacom tablets (Richard Hughes)
- Add support for the Synaptics Panamera chip (Mario Limonciello)
- Add validation for Titan Ridge Thunderbolt devices (Andrei Em
*** This bug is a duplicate of bug 1780442 ***
https://bugs.launchpad.net/bugs/1780442
** 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
Bugs, which is subscribed to Ubunt
** Bug watch added: github.com/hughsie/lvfs-website/issues #163
https://github.com/hughsie/lvfs-website/issues/163
** Also affects: fwupd via
https://github.com/hughsie/lvfs-website/issues/163
Importance: Unknown
Status: Unknown
--
You received this bug notification because you a
*** This bug is a duplicate of bug 1791407 ***
https://bugs.launchpad.net/bugs/1791407
** This bug has been marked a duplicate of bug 1791407
Thinkpad L570 UEFI destroyed after BIOS update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Duplicate of https://launchpad.net/bugs/1780442 perhaps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788175
Title:
AppStream system cache was updated, but problems were found: Metadata
files hav
** Also affects: grub2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Trusty)
Impor
@Robert
I've uploaded a fwupd package with the designated above fix.
@gumbeto
Watch this bug for when an archive admin releases the fix and you can try it
out by putting in some corrupted data back into the cache again (you can
manually modify it to "corrupt" it).
--
You received this bug noti
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/fe1c4de5a4b178cae3e4e932
As also found by this, the signing source packages from debian need to
be blocked too. That's filed here:
https://bugs.launchpad.net/ubuntu/+source/fwupdate-
amd64-signed/+bug/1787315
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
These packages are used for Debian's signed binaries and should be
blacklisted from coming into Ubuntu
** Affects: fwupd-amd64-signed (Ubuntu)
Importance: Undecided
Status: New
** Affects: fwupdate-amd64-signed (Ubuntu)
Importance: Undecided
Statu
Thanks Steve. I've made the matching change in packaging so any future
fwupdate uploads to Debian that sync won't try to make signed packages
again.
https://salsa.debian.org/efi-
team/fwupdate/commit/104e1e86d9b318fd9831ecc16112d3d3c060426e
** Changed in: fwupdate (Ubuntu)
Status: New =>
Public bug reported:
In cosmic there has been a major transition in the firmware updating
stack. fwupdate's library and EFI application were subsumed into fwupd
1.1.0+.
fwupd will manage the installation of the EFI binary now at runtime.
fwupdate is still around as a reference implementation tha
Here is the IRC transcript that prompted this bug:
hi can an AA remove and block these from syncing
https://launchpad.net/ubuntu/+source/fwupdate-amd64-signed
https://launchpad.net/ubuntu/+source/fwupdate-arm64-signed
https://launchpad.net/ubuntu/+source/fwupdate-i386-signed ? They're causing
This bug has been fixed in the fwupd 1.1.1 release that's now in cosmic.
** Changed in: fwupd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753655
Tit
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896012
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765134
Title:
Update from 7.3.0-15 to 7.3.0-16 based GCC causes lintian problems
To manage no
The fix is contained in
https://github.com/hughsie/fwupd/commit/60c845627d3b5ad0beb56d85fbe5bdd47ad7d70e
for the 1_0_X branch and will be in the 1.0.9 release of fwupd and
master
(https://github.com/hughsie/fwupd/commit/25d51d14297713b4817ef9644f83e07e71344b0a)
which will be in the 1.2.0 release of
One more dimension to add to this.
Fwupd supports a "requirements" option on firmware. This allows
manufacturers to prohibit installation on particular software
combinations. If firmware doesn't work properly on fwupdate 10 then the
manufacturer should be setting the requirement on com.redhat.fwup
Ivan,
Well specifically I'm worried that
https://github.com/rhboot/fwupdate/commit/3480d52310fc3f2bc3f7df83f19e9868678e6563
is not included with this approach.
Also
https://github.com/rhboot/fwupdate/commit/9493b9b537bcff8eefb06c9fd5e3f686defea305
is missing then.
Those are all related, so if yo
That patch alone shouldn't turn on ux capsule upgrades. Are you sure
it's all that is needed?
In my opinion it would be better to jump up to fwupdate 12 rather than
just the single bandaid.
Also AMI is the IBV used in some other OEM boxes with no problem. This
must be specific to some implementat
Great!
I do see this:
15:14:06:0715 Thunderbolt Attempt 0: Failed to read NVM version
Which means it did use the new logic. Please leave a comment in the PR
on GitHub to assist in it getting accepted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
That's good to hear. Would you mind confirming that in your debug log it
is trying to read a second time? When you have verbose mode activated it
will log a message indicating it retried.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://github.com/hughsie/fwupd/pull/609
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
Update loop for Thunderbolt NVM for Xps notebook 9360. Installed
version is not recognized (0
If you can please test this branch instead to see if it helps for you.
Same thing provide the debug log if it isn't helping still.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768627
Title:
Update
@Mauro,
Okay, perfect thanks. So from this debug log we can tell for sure that this
isn't caused by thunderbolt power, but rather the value read from the kernel
immediately is invalid.
This tells me that this is probably a case of fwupd racing with the kernel
based off the uevent that came thr
@Mauro,
Thanks for checking, that's unfortunate that it's still happening.
To modify that file open it with an editor as root. For example:
sudo nano /lib/systemd/system/fwupd.service
or
sudo gedit /lib/systemd/system/fwupd.service
To view output from the journal:
journalctl -u fwupd.service
Y
This was built in docker? Or built locally? That's odd if in docker
since CI ran the same test just fine.
One solution can be to turn off unit tests (locally add to the environment
DEB_BUILD_OPTIONS=nocheck)
http://www.ducea.com/2008/12/07/deb_build_optionsnocheck/
To do this with docker you w
So I think I might have a PR that will help this bug. Can you please try this
PR?
https://github.com/hughsie/fwupd/pull/605#issuecomment-407097175
You can generate Ubuntu 18.04 packages following instructions here:
https://github.com/hughsie/fwupd/tree/master/contrib
If it persists, can you ple
OK. So is it happening reproducibly like every boot for you now?
If so, can you please try to do the steps in #12 I listed above, but
please make sure that step 2 is included? That's what I'm most
interested to see.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The first 2 I have no concerns, but would like to see a tested-by
submitted back to that patch to encourage it to land upstream.
The third patch, there has been a second submission (and will likely be a 3rd
based on feedback).
https://patchwork.kernel.org/patch/10522375/
Conceptually I have no c
@Mauro,
It looks like you skipped step 2.
Would you please upgrade to NVM 26 and see if it's still happening? It's
available here:
https://github.com/dell/thunderbolt-nvm-linux/issues/11
** Bug watch added: github.com/dell/thunderbolt-nvm-linux/issues #11
https://github.com/dell/thunderbolt
Is the step to delete old metadata actually required? That will complicate
the SRU if so..
On Wed, Jul 11, 2018, 13:25 François Marier wrote:
> >From https://bugs.launchpad.net/ubuntu/+source/appstream-
> glib/+bug/1780520/comments/2:
>
> "I have uploaded a fixed package to my PPA:
>
> https://l
Another upstream report of this was here:
https://github.com/hughsie/fwupd/issues/590
** Bug watch added: github.com/hughsie/fwupd/issues #590
https://github.com/hughsie/fwupd/issues/590
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
I'm also encountering
cannot perform readlinkat() on the mount namespace file descriptor of the init
process
When trying to use a snap with an upstream kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Thanks for confirming it's a HW issue.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780731
Title:
USB Mouse stopped working. Tried liv
Thanks for confirming it's a HW issue.
** Changed in: fwupd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780391
Title:
Mouse Begins To Work In Jumpy
*** 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 wh
** Changed in: fwupd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780391
Title:
Mouse Begins To Work In Jumpy Horizontal Steps Then Stops Working
To mana
Can you please test if this happens in 18.04? You can verify from live
media. No need to perform an installation.
Please check with fwupd in verbose mode and share the log.
systemctl stop fwupd.service
/usr/lib/fwupd/fwupd -v
--
You received this bug notification because you are a member of Ubun
@Kat,
Can you please confirm the particular Ubuntu kernel that you are still
encountering the need to run this command? As I understood this patch
(that effectively does what that command does) is backported into all
the latest Ubuntu kernels, so if it's still happening that is important
informat
** Changed in: fwupd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753655
Title:
fwupd doesn't release hidraw devices
To manage notifications about this bug
Only if you have userspace that uses other 1.5 features, which doesn't
exist today in Linux. The patch and fw 1.0 should be functionally
equivalent for Linux.
On Fri, May 11, 2018, 17:01 alkemyst <1763...@bugs.launchpad.net> wrote:
> @Mario
> Well, 1.0 already works without any patch. It'just dow
@Josef,
Glad to hear that confirmation. It may be useful to respond with a Tested-by
to the patch upstream.
https://patchwork.kernel.org/patch/10388043/
@Stefano
No need to upgrade again. You can stay at 1.0 and it's functionally
just fine with Ubuntu.
Thanks,
--
You received this bug noti
@Kai Heng,
Can you share a test kernel with that patch for folks in this thread
affected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam Realtek Integrated_Webcam_HD
All,
The patch has been submitted here:
https://lkml.org/lkml/2018/5/8/1117
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763748
Title:
Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4)
I don't believe we'll SRU any fix into artful as it is interim release
that will EOL soon and the fix is in bionic.
For those affected in artful I would recommend to either:
1) Upgrade to bionic
2) Remove fwupd
3) blacklist the unifying plugin.
To blacklist the unifying plugin:
1) Modify /etc/fwu
This is going to expire in a few days, if this continues to happen in
18.04 for someone, please re-open it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753655
Title:
fwupd doesn't release hidraw
OK can you both please do the following:
0) Observe where the end of your current dmesg output is
1) Manually turn on force power
# echo 1 | sudo tee
/sys/bus/wmi/devices/86CCFD48-205E-4A77-9C48-2021CBEDE341/force_power
2) Check in /sys/bus/thunderbolt/devices/0-0/ and read the NVM version sysfs
701 - 800 of 6946 matches
Mail list logo
