Bug#925672: efivar: diff for NMU version 37-2.1

I don't have a concern to this, but would you mind also submitting it to Salsa and linking back so we can get it into VCS? > -Original Message- > From: David da Silva Polverari > Sent: Wednesday, June 10, 2020 12:06 AM > To: 925...@bugs.debian.org > Subject: Bug#925672: efivar: diff for

Bug#961490: fwupd: version in stable too old, no updates possible

> -Original Message- > From: Ansgar > Sent: Tuesday, May 26, 2020 8:01 AM > To: Steffen Schreiber; 961...@bugs.debian.org > Subject: Bug#961490: fwupd: version in stable too old, no updates possible > > > [EXTERNAL EMAIL] > > Hi, > > On Tue, 2020-05-26 at 13:56 +0200, Steffen

Bug#960688: fwupd: missing Breaks: fwupdate (<< 12-7)

Let me elaborate the timeline. * Originally fwupdate contained /usr/bin/fwupdate. * It was merged into fwupd and fwupdate went into maintenance only mode. * In Debian we made fwupdate a transition package with nothing in it. This is when the Replaces got put into place. * Because it was a

Bug#955387: Regression: flashrom programmer support reduced on non-x86

> -Original Message- > From: Carl-Daniel Hailfinger > Sent: Monday, March 30, 2020 5:06 PM > To: sub...@bugs.debian.org > Subject: Bug#955387: Regression: flashrom programmer support reduced on > non-x86 > > > [EXTERNAL EMAIL] > > Package: flashrom > Version: 1.2-5 > > Dear

Bug#955259: libjcat: Please add consider adding autopkgtest coverage

> -Original Message- > From: Simon McVittie > Sent: Monday, March 30, 2020 5:23 PM > To: Limonciello, Mario > Cc: 955...@bugs.debian.org; sub...@bugs.debian.org > Subject: Re: Bug#955259: libjcat: Please add consider adding autopkgtest > coverage > > > [EXTERNAL EMAIL] > > On Mon, 30

Bug#955258: libjcat-dev: -dev package missing some required dependencies

Thanks, I saw this was fixed by this MR: https://salsa.debian.org/efi-team/libjcat/-/merge_requests/2 > -Original Message- > From: Simon McVittie > Sent: Saturday, March 28, 2020 3:20 PM > To: Debian Bug Tracking System > Subject: Bug#955258: libjcat-dev: -dev package missing some

Bug#955259: libjcat: Please add consider adding autopkgtest coverage

Upstream the following was recently accepted to allow installed-tests to work Without the source tree nearby. https://github.com/hughsie/libjcat/commit/d6dc3e90b0c805cc50bff9d1d1b87ff575e53769 > -Original Message- > From: Simon McVittie > Sent: Saturday, March 28, 2020 3:29 PM > To:

Bug#932617: any update on this as I still got it today with the update (again)

1.3.9.2? You mean 1.3.9-2? They were supposed to be removed about 5 months ago. The preinst, postrm, and postinst has the stuff for doing these: https://salsa.debian.org/efi-team/fwupd/-/blob/debian/debian/fwupd.preinst https://salsa.debian.org/efi-team/fwupd/-/blob/debian/debian/fwupd.postrm

Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

> From: Limonciello, Mario > Sent: Thursday, March 19, 2020 8:58 AM > To: Diederik de Haas > Cc: 943...@bugs.debian.org > Subject: RE: Bug#943343: fwupd: fwupd-refresh.service failed to start > Refresh fwupd metadata and update motd. > > > -Original Message- > > From: Diederik de Haas >

Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

> -Original Message- > From: Diederik de Haas > Sent: Thursday, March 19, 2020 8:53 AM > To: Limonciello, Mario > Cc: 943...@bugs.debian.org > Subject: Re: Bug#943343: fwupd: fwupd-refresh.service failed to start > Refresh fwupd metadata and update motd. > > On donderdag 19 maart 2020

Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

> -Original Message- > From: Diederik de Haas > Sent: Thursday, March 19, 2020 7:57 AM > To: Limonciello, Mario > Cc: 943...@bugs.debian.org > Subject: Re: Bug#943343: fwupd: fwupd-refresh.service failed to start > Refresh fwupd metadata and update motd. > > On woensdag 18 maart 2020

Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

I suspect this is related to an upgrade from the intermediary version that had problematic objects/permissions created. Can you please try to check whether there are broken symlinks in /var/lib/private or /var/cache/private? Thanks, > -Original Message- > From: Diederik de Haas >

Bug#951589: flashrom: Update to version 1.2

With the new stuff I think you need to actually split it into 3 distinct binary packages in debian/ : flashrom libflashrom libflashrom-dev Also I think you need to explicitly build with meson rather than autotools to get it to make the pkgconfig file IIRC. From: Gürkan Myczko Sent: Tuesday,

Bug#943343:

I expect that this should not be happening with current systemd in testing and fwupd in testing (or unstable). Can you please confirm?

Bug#948546:

If you adopt this release, please also backport this commit: https://github.com/hughsie/libgusb/commit/17f9cda073459fc673a99bd281e929a999643374 To avoid causing significantly higher power consumption in software that uses libgusb.

Bug#947205: fwupd.shutdown failed with exit status 2

It's fixed upstream by this commit: https://github.com/fwupd/fwupd/commit/1db7e987ae9cf1b81117040762e90db6c15b5202 Which should be part of next release. On Dec 22, 2019 16:00, Jochen Sprickerhof wrote: [EXTERNAL EMAIL] Package: fwupd Version: 1.3.5-1 Severity: normal Hi, when shutting down

Bug#946072:

I've got a fix for this in https://salsa.debian.org/debian/tpm-udev/merge_requests/1

Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

Internal Use - Confidential > -Original Message- > From: Werner Mahr > Sent: Tuesday, December 3, 2019 6:52 AM > To: 943...@bugs.debian.org > Subject: Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh > fwupd > metadata and update motd. > > > [EXTERNAL EMAIL] > > > >

Bug#945203: fwupd: Cannot update firmware

Nothing fwupd can do about this. It's either efivarfs NV store is full on your box or BIOS is locking it down.

Bug#945204: Incorrect unversioned dependency on libxmlb1

I believe libxmlb1 may be missing debian/symbols leading to this behavior. On Nov 21, 2019 01:18, Arto Jantunen wrote: [EXTERNAL EMAIL] Package: fwupd Version: 1.3.3-3 Severity: serious The unversioned dependency on libxmlb1 is incorrect. On a partially upgraded system it reports this at

Bug#943465: fwupd is wrongly marked Multi-Arch: foreign

> On Mon, Oct 28, 2019 at 02:46:03PM +, mario.limoncie...@dell.com wrote: > > I guess by this argument it really should be made into a Depends not > > a Recommends not because fwupd internally needs it to work but to ensure > > those architecture constraints get met effectively. > >

Bug#943465: fwupd is wrongly marked Multi-Arch: foreign

> -Original Message- > From: Helmut Grohne > Sent: Saturday, October 26, 2019 1:16 AM > To: Steve McIntyre > Cc: 943...@bugs.debian.org; debian-cr...@lists.debian.org > Subject: Bug#943465: fwupd is wrongly marked Multi-Arch: foreign > > > [EXTERNAL EMAIL] > > Hi Steve, > > On Fri,

Bug#943465: fwupd is wrongly marked Multi-Arch: foreign

On Oct 25, 2019 14:46, Helmut Grohne wrote: [EXTERNAL EMAIL] On Fri, Oct 25, 2019 at 04:01:10PM +, mario.limoncie...@dell.com wrote: > I made some modifications and think I captured your suggestion here > https://github.com/fwupd/fwupd/commit/3508aecefdbd81924314834ac9e14bcd71aa253f > >

Bug#943465: fwupd is wrongly marked Multi-Arch: foreign

> -Original Message- > From: Helmut Grohne > Sent: Friday, October 25, 2019 9:30 AM > To: Limonciello, Mario > Cc: 943...@bugs.debian.org > Subject: Re: Bug#943465: fwupd is wrongly marked Multi-Arch: foreign > > > [EXTERNAL EMAIL] > > On Fri, Oct 25, 2019 at 02:08:34PM +,

Bug#943465: fwupd is wrongly marked Multi-Arch: foreign

Thanks for the heads up. I took a stab at how this should work here (not yet merged): https://github.com/fwupd/fwupd/commit/809eb181f57dc5158b5d37d2855a0a48eafc3565 Can you please review that and make sure you agree it's done correctly? > -Original Message- > From: Helmut Grohne >

Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

Internal Use - Confidential In 1.3.2-5 the service is disabled by default (and also this issue should be fixed). > -Original Message- > From: Jean-Marc > Sent: Wednesday, October 23, 2019 11:37 AM > To: Debian Bug Tracking System > Subject: Bug#943343: fwupd: fwupd-refresh.service

Bug#942567: Info received (Bug#942567: fwupd: fails to update metadata)

I had a newer systemd on my system when I tested. It is specifically a bug in systemd leading to this behavior. 1.3.2-3 will work around it until newer systemd lands. On Oct 19, 2019 09:15, Debian Bug Tracking System wrote: [EXTERNAL EMAIL] Thank you for the additional information you have

Bug#942567: fwupd: fails to update metadata

Ah yes. It's the same as I reported upstream to systemd. https://github.com/systemd/systemd/issues/13688 I just uploaded fwupd 1.3.2-3. * For now the motd part of the unit is disabled unless on systemd 243+ From: Ritesh Raj Sarraf on behalf of Ritesh Raj

Bug#942568: [fwupd] busy spinning in fu_util_prompt_for_boolean

Thanks for submitting. I guess you don't have LVFS remote enabled for your setup and it's hanging trying to enable it. I've filed this upstream to try to fix it: https://github.com/fwupd/fwupd/pull/1484 Sent from Workspace ONE Boxer On Oct 18, 2019 03:30, Giovanni Mascellani wrote: Package:

Bug#942567: fwupd: fails to update metadata

Could you please try to remove "StandardError=null" from the service and see if the errors are clearer on the failure? Sent from Workspace ONE Boxer On Oct 18, 2019 03:37, Ritesh Raj Sarraf wrote: [EXTERNAL EMAIL] Package: fwupd Version: 1.3.2-2 Severity: important So what is happening now,

Bug#941661: daemon fails to start

This is a duplicate of 941360, which is fixed in git but waiting for review on some other important changes before upload: https://salsa.debian.org/efi-team/fwupd/commit/04cb53bdce9037c4af09b70486efd26eb89686e0 > -Original Message- > From: Laurent Bigonville > Sent: Thursday, October 3,

Bug#941360: fwupd: Failed to activate service: timed out

Here is a fix for it. I believe it's because of a clash with fwupd-refresh and fwupd specifically in systemd 242 and newer. https://github.com/fwupd/fwupd/commit/dc7e7c3808d564d5769b2845dbd66a3651f72e07 On Sep 30, 2019 10:37, Francois Marier wrote: [EXTERNAL EMAIL] On 2019-09-29 at 23:57:02,

Bug#941360: fwupd: Failed to activate service: timed out

What version did you upgrade from? And was that directory already existing or did it get created with the package? On Sep 29, 2019 08:21, definetti wrote: [EXTERNAL EMAIL] Package: fwupd Version: 1.3.2-1 Severity: important Dear Maintainer, after updating to 1.3.2-1 the fwupd service fails

Bug#941048: fwupd: provide option to never send report

> -Original Message- > From: brian m. carlson > Sent: Tuesday, September 24, 2019 5:38 PM > To: Limonciello, Mario > Cc: 941...@bugs.debian.org > Subject: Re: Bug#941048: fwupd: provide option to never send report > > On 2019-09-24 at 02:22:44, mario.limoncie...@dell.com wrote: > > Oh it

Bug#941048: fwupd: provide option to never send report

Oh it looks like that just stops it from actually going out. To prevent the prompt you'll need to launch fwupdmgr with --no-unreported-check. https://github.com/fwupd/fwupd/blob/ce94d163f8d7bef4748a75def1ace0326083eea5/src/fu-util.c#L2092 > -Original Message- > From: brian m. carlson

Bug#941048: fwupd: provide option to never send report

To accomplish this, I believe you can just comment out ReportURI= in the LVFS remote and restart the daemon. (IE /etc/fwupd/remotes.d/lvfs.conf) > -Original Message- > From: brian m. carlson > Sent: Monday, September 23, 2019 7:02 PM > To: Debian Bug Tracking System > Subject:

Bug#939604: /var/lib/fwupdate/done not removed on uninstall

Yeah I think that shouldn't be a problem to cleanup, especially given it's a transition package. Overall did everything else go smoothly? > -Original Message- > From: dann frazier > Sent: Friday, September 6, 2019 2:07 PM > To: Debian Bug Tracking System > Subject: Bug#939604:

Bug#918973:

With Buster out now, can this effort be resumed?

Bug#912414: Workaround failed

The issue reported here is different than the CNAME issue. Basically LVFS has gotten a lot bigger and the fwupd 0.7.x release couldn't handle the size of the metadata now. Please reference this bug in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813 This workaround can be

Bug#932757: fwupd: should include Built-Using fields in the signed packages

Dell Customer Communication - Confidential Sure. Will be part of next fwupd release. https://github.com/hughsie/fwupd/commit/09700bbce8b2016056079cf73b0408e9afbc5301 > -Original Message- > From: Adam D. Barratt > Sent: Monday, July 22, 2019 2:05 PM > To: sub...@bugs.debian.org >

Bug#931794:

Now that buster is out, I've just uploaded the latest released 1.2.9 to unstable. Dell Corporation Limited is registered in England and Wales. Company Registration Number: 2081369 Registered address: Dell House, The Boulevard, Cain Road, Bracknell, Berkshire, RG12 1LF, UK. Company details for

Bug#921820: fwupd: provide a network service file

I think for some people downloading metadata automatically in a timer/cron type way, may be useful but I think it's missing the last piece of integration to notify folks; motd messaging to let people know updates are available. Would you please consider bringing this discussion upstream? I

Bug#926596: fwupdate: arm64 version of PE/COFF efi binary is corrupt

Would you be able to check if this also affects fwupd? The fwupdate binary was also merged into that project a while back and I would suspect it's affecting both. -Original Message- From: Ard Biesheuvel Sent: Sunday, April 7, 2019 10:46 PM To: Debian Bug Tracking System Subject:

Bug#922770: lvfs: GRUB disappeared after Thinkpad T480s firmware update

> -Original Message- > From: Steve McIntyre > Sent: Wednesday, February 20, 2019 7:29 AM > To: Alejandro Sanchez; 922...@bugs.debian.org > Subject: Bug#922770: lvfs: GRUB disappeared after Thinkpad T480s firmware > update > > > [EXTERNAL EMAIL] > > Control: severity -1 normal > >

Bug#922331: Info received (Bug#922331: Info received (Bug#922331: fwupd: autopkgtest regression: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached))

I've made some headway in figuring out whats going on. I've compared the qemu and lxc backends for autopkgtest and found two very notable differences. 1) The qemu one installs shared-mime-info. lxc doesn't. 2) Apparmor rules in lxc lead to namespace failures. Here's how I compared the two.

Bug#922331: Info received (Bug#922331: fwupd: autopkgtest regression: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached)

After hacking around bug 916493 I did manage to run autopkgtest locally with a qemu backends and it runs just fine. autopkgtest fwupd -- qemu ./qemu-unstable.img So what's different with LXC and QEMU backends? > -Original Message- > From: Debian Bug Tracking System > Sent: Thursday,

Bug#922331: fwupd: autopkgtest regression: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached

I'm aware of this failure, but rather confused on how to debug it. I just set up a buster machine and installed fwupd from unstable (using pinning) but fwupd runtime tests work just fine (and talking to real hardware does too) > -Original Message- > From: Paul Gevers > Sent: Thursday,

Bug#921820: fwupd: provide a network service file

Per design this functionality exists in the frontend that runs as reduced privilege user. For example gnome-software which runs in a users session and regularly checks for apt metadata also will automatically check for firmware updates too.

Bug#920777: Acknowledgement (ITP: libxmlb -- XML binary library)

Packaging moved to https://salsa.debian.org/efi-team/libxmlb/tree/debian > -Original Message- > From: Limonciello, Mario > Sent: Monday, January 28, 2019 8:44 PM > To: 920...@bugs.debian.org > Subject: Bug#920777: Acknowledgement (ITP: libxmlb -- XML binary library) > > > [EXTERNAL

Bug#920777: Acknowledgement (ITP: libxmlb -- XML binary library)

Initial packaging available here: https://github.com/superm1/libxmlb/tree/debian

Bug#920012: fwupd breaks xbox360 controller support

Moving to a newer release is problematic because newer releases need libxmlb which isn't in Debian and doesn't yet have an ITP or team willing to adopt it yet even. This commit has been backported to 1_1_X branch so when a 1.1.5 release is released it will be included. Alternatively this commit

Bug#916036: Install fwupd on a default installation

> Just the fact that the update claims that the hardware only accepts > signed updates or something else? :) At a minimum a claim. > I will note - although slightly off-topic to the discussion at hand - > that it would be useful to people to be able to run their own repository > of updates and

Bug#916036: Install fwupd on a default installation

Something I think worth mentioning is that LVFS is being transitioned to being run and managed by the Linux Foundation. >Interestingly enough the vendor signs a blob (CAB file) and LVFS throws > it away and re-signs the blob with its own key. But then again I think > the base assumption is that

Bug#911505: fwupd: Change package description to be more open ended

I've committed this upstream. https://github.com/hughsie/fwupd/commit/2aaa38d77df06f10968bda089156a29446435141 It will be included the 1.2.0-1 release into Debian.

Bug#911023: memory leak in the backlight control of the dell-laptop module

We did fix a memory leak recently. Please backport this and see it it helps https://github.com/torvalds/linux/commit/affab51082174f60ef71ced8ab5fbe71f00e9ae3 On Oct 14, 2018 15:26, Pali Rohár wrote: Adding Mario to loop. Memory leak can be also in ACPI/WMI or in the new dell-smbios.ko module.

Bug#906599:

Fixed for next upload. https://github.com/hughsie/fwupd/commit/840920e928df4026652dc15fec86633c945eeb7a

Bug#906357: fwupd: FTBFS in buster/sid (dh_missing: missing files, aborting)

It's a bit odd to me that reproducible builds is failing like that. The upload was built using git-pbuilder and it built just fine. Also it builds fine in Ubuntu cosmic (who synced from sid). I don't believe your failure is the same root cause. I believe this will fix your failure:

Bug#906216: Info received (Bug#906216: fwupd: ESP filesystem detection code does not like autofs)

Can you please try this patch? https://github.com/hughsie/fwupd/pull/661 > -Original Message- > From: Debian Bug Tracking System [mailto:ow...@bugs.debian.org] > Sent: Wednesday, August 15, 2018 10:24 AM > To: Limonciello, Mario > Subject: Bug#906216: Info received (Bug#906216: fwupd:

Bug#906216: fwupd: ESP filesystem detection code does not like autofs

Forwarded upstream here https://github.com/hughsie/fwupd/issues/660 Please subscribe and comment as necessary. > -Original Message- > From: Sam Morris [mailto:s...@robots.org.uk] > Sent: Wednesday, August 15, 2018 9:56 AM > To: Debian Bug Tracking System > Subject: Bug#906216: fwupd: ESP

Bug#905570: Info received (Bug#905570: fwupd: Firmware update failed on Lenovo P50)

This bug will be fixed in the fwupd 1.1.1 release. > -Original Message- > From: Debian Bug Tracking System [mailto:ow...@bugs.debian.org] > Sent: Monday, August 6, 2018 7:39 AM > To: Limonciello, Mario > Subject: Bug#905570: Info received (Bug#905570: fwupd: Firmware update failed > on

Bug#905570: fwupd: Firmware update failed on Lenovo P50

This sounds like it matches https://github.com/hughsie/fwupd/issues/619 pretty closely if I'm not mistaken, just a different model number. Can you please comment there?

Bug#904671: fwupd: Incomplete debian/copyright?

Chris, OK. Can you please look again? I've adjusted the script to group together files in the same directory. https://github.com/hughsie/fwupd/pull/611 Thanks,

Bug#904671: fwupd: Incomplete debian/copyright?

Chris, Thanks for accepting it. I've made this PR upstream to fill in debian/copyright properly automatically. We'll pull that in in the future (unless you or anyone else has a concern). https://github.com/hughsie/fwupd/pull/611 Thanks, > -Original Message- > From: Chris Lamb

Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

> -Original Message- > From: Joel Cross [mailto:j...@kazbak.co.uk] > Sent: Saturday, July 7, 2018 10:00 AM > To: Michael Biebl; Limonciello, Mario; 902...@bugs.debian.org > Subject: Re: Bug#902416: systemd: systemctl hibernate: unable to resume after > upgrade > > On Fri, 6 Jul 2018, at

Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

> -Original Message- > From: Michael Biebl [mailto:bi...@debian.org] > Sent: Friday, July 6, 2018 9:53 AM > To: Limonciello, Mario; j...@kazbak.co.uk; 902...@bugs.debian.org > Subject: Re: Bug#902416: systemd: systemctl hibernate: unable to resume after > upgrade > > Am 06.07.2018 um

Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

> -Original Message- > From: Michael Biebl [mailto:bi...@debian.org] > Sent: Friday, July 6, 2018 5:46 AM > To: Joel Cross; 902...@bugs.debian.org; Limonciello, Mario > Subject: Re: Bug#902416: systemd: systemctl hibernate: unable to resume after > upgrade > > Am 06.07.2018 um 12:32

Bug#896148: fwupd: Please add ia64, riscv64 and x32 to the ports without valgrind

-Original Message- > From: Adrian Bunk [mailto:b...@debian.org] > Sent: Friday, April 20, 2018 3:32 AM > To: Debian Bug Tracking System > Subject: Bug#896148: fwupd: Please add ia64, riscv64 and x32 to the ports > without > valgrind > > Source: fwupd > Version: 1.0.6-2 > Severity:

Bug#896012: Regression from gcc-7 7.3.0-16

> -Original Message- > From: Matthias Klose [mailto:d...@debian.org] > Sent: Wednesday, April 18, 2018 9:29 PM > To: Limonciello, Mario; 896...@bugs.debian.org > Subject: Re: Bug#896012: Regression from gcc-7 7.3.0-16 > > On 18.04.2018 19:34, mario.limoncie...@dell.com wrote: > > Package:

Bug#896012: Regression from gcc-7 7.3.0-16

Package: gcc-7 Version: 7.3.0-16 The fwupd project as one of the CI tasks runs packaged builds and lintian after the build. CI recently started failing with this error: E: fwupd: library-not-linked-against-libc usr/lib/x86_64-linux-gnu/fwupd-plugins-3/libfu_plugin_upower.so E: fwupd-tests:

Bug#890950: Info received (Bug#890950: initramfs-tools: Resuming from hibernated swapfile fails)

Hi, I've had some more testing this week and developed some changes that I think are more sustainable. 1) No longer revert the setting offset via /bin/resume. I've started a discussion upstream to allow reading offset this way. If it's adopted then this should definitely stay. Otherwise it's

Bug#890064: smbios-utils: properly clean up legacy config files

Th warnings come from the dpkg maintscript helper. You're supposed to put it in all the helper scripts and they show warnings for the prerm IIRC. I guess a separate upgrade task may be needed to delete the directories then too if empty. > -Original Message- > From: Christoph Anton

Bug#890950:

I've reworked my patches and split to 3 segments that take your feedback into account. Can you please review these? With setting resume_offset on kernel command line I confirmed this works out of the box for me.

Bug#890950: initramfs-tools: Resuming from hibernated swapfile fails

Thanks, I appreciate your feedback. Some more comments nested below. > > > > 1) It requires that uswpswp is installed (to provide /bin/resume)[...] > > No, it runs /bin/resume which is installed by klibc-utils. (uswsusp > installs its resume implementation as /sbin/resume. That's what the >

Bug#890950: initramfs-tools: Resuming from hibernated swapfile fails

Package: initramfs-tools Version: 0.130ubuntu2 Severity: important Dear Maintainer, I've found that resuming from a hibernated swapfile using the kernel hibernate implementation fails. This is due to some assumptions made in initramfs-tools: 1) It requires that uswpswp is installed (to provide

Bug#822078:

This is a big of an old issue, but I got referred to it from someone else. As a hunch - can you (or anyone else who comes to this) please try to disable Legacy option ROMs in BIOS setup and try again?

Bug#890064: smbios-utils: properly clean up legacy config files

Thanks for the report. I've added this for the next upload: https://github.com/dell/libsmbios/commit/42379a462ec777cf5ae8ba87df40e5432faa8585 > -Original Message- > From: Christoph Anton Mitterer [mailto:cales...@scientia.net] > Sent: Saturday, February 10, 2018 11:28 AM > To: Debian Bug

Bug#832558: [Pkg-dkms-maint] Bug#832558: Fix dkms mkdeb / mkdsc / mkbmdeb

Pierre, There have been a few times the patches got synced between the two, but I'll admit I don't know the current home to the patches that live in the Debian package. Hopefully some of the Debian maintainers can speak up since I haven't tracked it. I think it would be good to make sure that

Bug#832558: [Pkg-dkms-maint] Bug#832558: Fix dkms mkdeb / mkdsc / mkbmdeb

> -Original Message- > From: Pkg-dkms-maint [mailto:pkg-dkms-maint- > bounces+mario_limonciello=dell@lists.alioth.debian.org] On Behalf Of > Pierre > Neyron > Sent: Monday, February 12, 2018 11:21 AM > To: 832...@bugs.debian.org > Subject: [Pkg-dkms-maint] Bug#832558: Fix dkms mkdeb /

Bug#887263: [Pkg-dkms-maint] Bug#887263: dkms should depend on e2fsprogs explicitly

> -Original Message- > From: Pkg-dkms-maint [mailto:pkg-dkms-maint- > bounces+mario_limonciello=dell@lists.alioth.debian.org] On Behalf Of > Andreas Henriksson > Sent: Sunday, January 21, 2018 3:47 AM > To: Helmut Grohne ; 887...@bugs.debian.org > Subject:

Bug#886878:

I tried in a fully up to date debian unstable VM and can not reproduce this myself.

Bug#886878: fwupd service startup fails.

The 4.14 kernel you are running, does it have the various spectre and meltdown fixes integrated already? If so, could you please check with an older kernel without them to see if it's also affected? I'm wondering if those might be causing a problem.

Bug#886878: fwupd service startup fails.

I couldn't reproduce this myself. As far as I'm aware there is no FFI generated code in fwupd. I think we'll need to see some more logs and/or journal output to figure out what's going on for you. Also filed this upstream, so please feel free to discuss there as well.

Bug#886878: fwupd service startup fails.

Thanks for filing this. Can you please share the associated journal output when it tries to launch? Does it hang? Or does it just not launch at all? > -Original Message- > From: Abhijit Hoskeri [mailto:abhijithosk...@icloud.com] > Sent: Wednesday, January 10, 2018 1:40 PM > To: Debian

Bug#886349: initramfs-tools: Missing vmd driver in hook-functions

Package: initramfs-tools Version: 0.130 Severity: important Dear Maintainer, initramfs-tools is missing the Intel Volume Management Device (vmd.ko) that was included in kernel 4.9 and later. This sets up NVME disks in a separate PCI domain and is needed to access them when the system is

Bug#882524:

Does it even make sense to compile on kFreeBSD? This package relies on the behavior of the thunderbolt module in the Linux kernel.

Bug#883489: fwupdate FTCBFS: multiple reasons

Thank you for the diff. It looks fine to me and something we can apply for the next upload. Would you please also submit a PR to upstream for the upstream applicable parts (0003-cross.patch). > -Original Message- > From: Helmut Grohne [mailto:hel...@subdivi.de] > Sent: Monday, December

Bug#878311:

This particular issue is fixed with https://github.com/hughsie/appstream-glib/commit/a1481d201d089f9e70a0cf48a0424315e0f6cdaf which is part of the recently tagged 0.7.4 release.

Bug#879022: fwupd: FTBFS on alpha and hppa: -fstack-protector not supported

> -Original Message- > From: Aaron M. Ucko [mailto:u...@debian.org] > Sent: Wednesday, October 18, 2017 9:47 AM > To: Debian Bug Tracking System > Subject: Bug#879022: fwupd: FTBFS on alpha and hppa: -fstack-protector not > supported > > Source: fwupd > Version:

Bug#874521: 1.0.0

I've uploaded 1.0.0-1 into unstable recently. Although the patch that was submitted didn't work for you on top of 0.9.7, can you please check if the problem persists in 1.0.0? There have been other changes that may affect this. If not, please continue with debugging upstream.

Bug#877991: fwupd: Missing call to dh_systemd

Thanks, added this to upstream packaging. https://github.com/hughsie/fwupd/commit/a46c01905b9a62c09a4654e86748c7f82d86eed5 Holding off on a new release to unstable until we've got a solution to that segfault problem though. > -Original Message- > From: Laurent Bigonville

Bug#874521:

So I can't reproduce this. More details will be needed. If you can please file a bug upstream (https://github.com/hughsie/fwupd/) it would be best for upstream to work on solving this. The following items are needed: 1. /usr/lib/fwupd/fwupd -v output 2. Information about the hardware

Bug#874521: fwupd segfaults at start

Is this 100% reproductible for you? Can you describe more about your machine? I suspect this is an upstream issue, it may be useful to file it upstream so that it can be debugged there. Sent from VMware Boxer On Sep 6, 2017 15:27, Laurent Bigonville wrote: Package: fwupd

Bug#872458: closed by Mario Limonciello <mario.limoncie...@dell.com> (Bug#872458: fixed in fwupd 0.9.7-1)

Hi Chris, > If this is a commonly-owned directory, perhaps we should add an > exception to Lintian instead of overriding in leaf packages? Lintian didn't actually complain. It was just a common added to fwupd-tests.install so that if another developer is looking at this they can understand why

Bug#872458: fwupd-tests: Please don't ship test files to generic /usr/share/installed-tests dir

> -Original Message- > From: Chris Lamb [mailto:la...@debian.org] > Sent: Thursday, August 17, 2017 11:59 AM > To: Limonciello, Mario ; 872...@bugs.debian.org > Subject: Re: Bug#872458: fwupd-tests: Please don't ship test files to generic >

Bug#872458: fwupd-tests: Please don't ship test files to generic /usr/share/installed-tests dir

Chris, That's actually how gnome-desktop-testing's installed-tests stuff works. https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests With the files in that directory like they are it's executed like this: # gnome-desktop-testing-runner fwupd > -Original Message- > From: Chris

Bug#853409:

This particular problem is fixed upstream but not yet in a release of fwupdate. https://github.com/rhboot/fwupdate/commit/cd8f7d79f84155d1dfbff3bb169558a8b06fb719

Bug#868465: Leaves behind /var/cache/app-info/xmls/fwupd.xml

Thanks, I've committed a fix to git. Will be in next upload. https://anonscm.debian.org/cgit/uefi/fwupd.git/commit/?h=debian-next=68dd0bf14227aad93d906b2a47a1803be5790191 https://anonscm.debian.org/cgit/uefi/fwupd.git/commit/?h=debian-next=5cdc4900c5fe43575dfc4d7d5b1f8d0a66b7067c >

Bug#868464: Leaves behind /var/lib/fwupd/ directory

Thanks, I've committed a fix to git. Will be in next upload. https://anonscm.debian.org/cgit/uefi/fwupd.git/commit/?h=debian-next=68dd0bf14227aad93d906b2a47a1803be5790191 https://anonscm.debian.org/cgit/uefi/fwupd.git/commit/?h=debian-next=5cdc4900c5fe43575dfc4d7d5b1f8d0a66b7067c >

Bug#868457: fwupd: Upload new 0.9.5 version

s/unstable/experimental/ Sent from VMware Boxer On Jul 15, 2017 14:46, "Limonciello, Mario" wrote: Matthias, Can you sponsor it to unstable in the meanwhile? I can't upload it because it has NEW binary package introduced (fwupd-tests). Sent from VMware Boxer On

Bug#868457: fwupd: Upload new 0.9.5 version

Matthias, Can you sponsor it to unstable in the meanwhile? I can't upload it because it has NEW binary package introduced (fwupd-tests). Sent from VMware Boxer On Jul 15, 2017 11:30, Matthias Klumpp wrote: 2017-07-15 18:15 GMT+02:00 Nelson A. de Oliveira

  1   2   >