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

[Mario.Limonciello]

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 NMU version 37-2.1
> 
> 
> [EXTERNAL EMAIL]
> 
> Control: tags 925672 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for efivar (versioned as 37-2.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer or cancel the NMU.
> 
> Regards,
> 
> David Polverari.

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

[Mario.Limonciello]

> -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 Schreiber wrote:
> > So I see you marked this bug as fixed/resolved.
> 
> Someone (not the maintainer) did so, but please note that the bug
> remains open even when marked as fixed in a newer version.  Debian's
> stable release team prefers bugs to be fixed in unstable/testing before
> they get fixed in (old)stable, so this is good.

The particular circumstances of this issue are that the update in question 
requires
a newer version of fwupd than is in stable.  This is not a matter of just 
backporting
a change or two and it works.  There are daemon and plugin level changes that 
have to
go together to guarantee a proper update.

This seems incompatible with the documentation around uploading to stable.
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable
> 
> > What's the way going forward for users of stable? Installing packages
> > from testing? Are you recommending to just forget about running Debian
> > stable as is?
> 
> The maintainer hasn't yet commented on how he wants to proceed.
> Reasonable options seem to be to either update stable to the version
> currently in testing (1.3.9) or to update to a later version of 1.2.X.
> 
> Ansgar

If a particular update requires a newer fwupd version I don't think it's 
reasonable
to push that version to all Debian users who may not need the newer fwupd 
version
and might not be willing to accept the risk of regressions in a newer version.

"Fixes must be minimal and relevant"

So in this circumstance if your device needs the newer version you should 
probably
take the package from testing instead.

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

[Mario.Limonciello]

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 transition package, there is a chance that a user already
removed /var/lib/fwupdate and so a request was put in for fwupd to clean that 
up.

* Later, a compatibility binary /usr/bin/fwupdate was added into fwupd.
This performs similar actions as the old fwupdate provided /usr/bin/fwupdate.

Hopefully that illustrates the timeline.  As fwupdate is a transition package 
now,
I don't know that it makes sense to add the Breaks now, please advise.


> -Original Message-
> From: Andreas Beckmann 
> Sent: Friday, May 15, 2020 7:28 AM
> To: Debian Bug Tracking System
> Subject: Bug#960688: fwupd: missing Breaks: fwupdate (<< 12-7)
> 
> 
> [EXTERNAL EMAIL]
> 
> Package: fwupd
> Version: 1.3.9-4
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts replaces-without-breaks
> 
> Hi,
> 
> during a test with piuparts and DOSE tools I noticed your package causes
> removal of files that also belong to another package.
> This is caused by using Replaces without corresponding Breaks.
> 
> The installation sequence to reproduce this problem is
> 
>   apt-get install fwupdate/stable
>   # (1)
>   apt-get install fwupd
>   apt-get remove fwupd
>   # (2)
> 
> The list of installed files at points (1) and (2) should be identical,
> but the following files have disappeared:
> 
>   /usr/bin/fwupdate
>   /usr/share/man/man1/fwupdate.1.gz
>   /var/lib/fwupdate/
> 
> This is a serious bug violating policy 7.6, see
> https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-
> files-and-replacing-packages-replaces
> and also see the footnote that describes this incorrect behavior:
> https://www.debian.org/doc/debian-policy/ch-relationships.html#id13
> 
> The fwupd package has the following relationships with fwupdate:
> 
>   Conflicts: n/a
>   Breaks:n/a
>   Replaces:  fwupdate (<< 12-7)
>   Provides:  fwupdate
> 
> >From the attached log (scroll to the bottom...):
> 
> 0m32.0s ERROR: FAIL: After purging files have disappeared:
>   /usr/bin/fwupdate  owned by: fwupd
>   /usr/share/man/man1/fwupdate.1.gz  owned by: fwupd
>   /var/lib/fwupdate/ owned by: fwupdate
> 
> 0m32.0s ERROR: FAIL: After purging files have been modified:
>   /var/lib/dpkg/info/fwupdate.list   not owned
> 
> 
> cheers,
> 
> Andreas

Bug#945204: Incorrect unversioned dependency on libxmlb1

[Mario.Limonciello]

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 startup (all dependencies are satisfied):

fwupdmgr: /lib/x86_64-linux-gnu/libxmlb.so.1: version `LIBXMLB_0.1.7' not
found (required by fwupdmgr)
fwupdmgr: /lib/x86_64-linux-gnu/libxmlb.so.1: version `LIBXMLB_0.1.13' not
found (required by fwupdmgr)

This may also be a bug in libxmlb, depending on how the dependency is being
generated. I did not check, please reassign if needed.

-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (90, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fwupd depends on:
ii  libarchive13   3.3.3-4+deb10u1
ii  libc6  2.29-2
ii  libefiboot137-2
ii  libefivar1 37-2
ii  libelf10.176-1.1
ii  libfwupd2  1.3.3-3
ii  libgcab-1.0-0  1.2-3~deb10u1
ii  libglib2.0-0   2.58.3-2+deb10u2
ii  libgnutls303.6.7-4
ii  libgpg-error0  1.35-1
ii  libgpgme11 1.12.0-6
ii  libgudev-1.0-0 232-2
ii  libgusb2   0.3.0-1
ii  libjson-glib-1.0-0 1.4.4-2
ii  libpolkit-gobject-1-0  0.105-25
ii  libsmbios-c2   2.4.1-1
ii  libsoup2.4-1   2.64.2-2
ii  libsqlite3-0   3.29.0-2
ii  libtss2-esys0  2.1.0-4
ii  libxmlb1   0.1.6-2
ii  shared-mime-info   1.10-1

Versions of packages fwupd recommends:
pn  bolt  
pn  fwupd-signed  
ii  python3   3.7.3-1

fwupd suggests no packages.

-- no debconf information

Bug#941661: daemon fails to start

[Mario.Limonciello]

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, 2019 8:29 AM
> To: Debian Bug Tracking System
> Subject: Bug#941661: daemon fails to start
> 
> 
> [EXTERNAL EMAIL]
> 
> Package: fwupd
> Version: 1.3.2-1
> Severity: serious
> 
> Hi,
> 
> It seems that the fwupd daemon fails to start:
> 
> oct 03 15:23:38 edoras systemd[1]: Starting Firmware update daemon...
> oct 03 15:23:38 edoras systemd[3854]: fwupd.service: Failed to set up special
> execution directory in /var/cache: Not a directory
> oct 03 15:23:38 edoras systemd[3854]: fwupd.service: Failed at step
> CACHE_DIRECTORY spawning /usr/lib/fwupd/fwupd: Not a directory
> oct 03 15:23:38 edoras systemd[1]: fwupd.service: Main process exited,
> code=exited, status=239/CACHE_DIRECTORY
> oct 03 15:23:38 edoras systemd[1]: fwupd.service: Failed with result 
> 'exit-code'.
> oct 03 15:23:38 edoras systemd[1]: Failed to start Firmware update daemon.
> 
> 
> Looking at /var/cache, I see:
> 
> ls -la /var/cache/fwupd/
> [...]
> lrwxr-xr-x.  1 root  root13 sep 28 22:49 fwupd -> 
> private/fwupd
> [...]
> 
> /var/cache/private/fwupd also exists
> 
> Kind regards,
> 
> Laurent Bigonville
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
> 'experimental-debug'),
> (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
> Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
> LANGUAGE=fr_BE:fr (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
> 
> Versions of packages fwupd depends on:
> ii  libarchive13   3.4.0-1
> ii  libc6  2.29-2
> ii  libefiboot137-2
> ii  libefivar1 37-2
> ii  libelf10.176-1.1
> ii  libfwupd2  1.3.2-1
> ii  libgcab-1.0-0  1.2-5
> ii  libglib2.0-0   2.62.0-3
> ii  libgnutls303.6.9-5
> ii  libgpg-error0  1.36-7
> ii  libgpgme11 1.13.1-1
> ii  libgudev-1.0-0 233-1
> ii  libgusb2   0.3.0-1
> ii  libjson-glib-1.0-0 1.4.4-2
> ii  libpolkit-gobject-1-0  0.105-26
> ii  libsmbios-c2   2.4.1-1
> ii  libsoup2.4-1   2.68.1-2
> ii  libsqlite3-0   3.29.0-2
> ii  libtss2-esys0  2.1.0-4+b1
> ii  libxmlb1   0.1.8-1+b1
> ii  shared-mime-info   1.10-1
> 
> Versions of packages fwupd recommends:
> ii  bolt   0.8-4
> ii  fwupd-amd64-signed [fwupd-signed]  1.3.2+1
> ii  python33.7.5-1
> 
> fwupd suggests no packages.
> 
> -- no debconf information

Bug#918973:

[Mario.Limonciello]

With Buster out now, can this effort be resumed?

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

[Mario.Limonciello]

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:
https://github.com/hughsie/fwupd/commit/e43765e9a4ff378d612a932c4637ef0a766cc4a0

> -Original Message-
> From: Santiago Vila [mailto:sanv...@debian.org]
> Sent: Friday, August 17, 2018 6:20 AM
> To: Debian BTS
> Subject: Bug#906357: fwupd: FTBFS in buster/sid (dh_missing: missing files,
> aborting)
> 
> Package: src:fwupd
> Version: 1.1.1-1
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> I tried to build this package in buster but it failed:
> 
> 
> [...]
>  debian/rules build-indep
> [ -f debian/control ] || debian/rules regenerate_control
> dh build-indep --with gir,systemd
>dh_update_autotools_config -i
>dh_autoreconf -i
>debian/rules override_dh_auto_configure
> make[1]: Entering directory '/<>'
> if pkg-config --exists libsmbios_c; then \
>   export DELL="-Dplugin_dell=true"; \
> else \
>   export DELL="-Dplugin_dell=false"; \
> fi; \
> if pkg-config --exists efivar; then \
>   export UEFI="-Dplugin_uefi=true -Dplugin_redfish=true"; \
> 
> [... snipped ...]
> 
> Installing /<>/obj-x86_64-linux-gnu/meson-private/fwupd.deps to
> /<>/debian/tmp/usr/share/vala/vapi
> Installing /<>/policy/org.freedesktop.fwupd.rules to
> /<>/debian/tmp/usr/share/polkit-1/rules.d
> Installing /<>/src/org.freedesktop.fwupd.xml to
> /<>/debian/tmp/usr/share/dbus-1/interfaces
> Installing /<>/plugins/dfu/dfu.quirk to
> /<>/debian/tmp/usr/share/fwupd/quirks.d
> Installing /<>/plugins/colorhug/colorhug.quirk to
> /<>/debian/tmp/usr/share/fwupd/quirks.d
> Installing /<>/plugins/ebitdo/ebitdo.quirk to
> /<>/debian/tmp/usr/share/fwupd/quirks.d
> Installing /<>/plugins/steelseries/steelseries.quirk to
> /<>/debian/tmp/usr/share/fwupd/quirks.d
> Installing /<>/plugins/nitrokey/nitrokey.quirk to
> /<>/debian/tmp/usr/share/fwupd/quirks.d
> Installing /<>/plugins/wacomhid/wacomhid.quirk to
> /<>/debian/tmp/usr/share/fwupd/quirks.d
> Installing /<>/plugins/csr/csr-aiaiai.quirk to
> /<>/debian/tmp/usr/share/fwupd/quirks.d
> Installing /<>/plugins/altos/altos.quirk to
> /<>/debian/tmp/usr/share/fwupd/quirks.d
> Installing /<>/plugins/redfish/redfish.conf to
> /<>/debian/tmp/etc/fwupd
> Installing /<>/plugins/dell/dell.quirk to
> /<>/debian/tmp/usr/share/fwupd/quirks.d
> Installing /<>/plugins/uefi/uefi.conf to
> /<>/debian/tmp/etc/fwupd
> Installing /<>/contrib/firmware-packager/firmware-packager to
> /<>/debian/tmp/usr/share/fwupd
> Running custom install script '/usr/bin/python3 /usr/bin/meson --internal 
> gtkdoc --
> sourcedir=/<> --builddir=/<>/obj-x86_64-linux-gnu
> --subdir=docs/libfwupd --
> headerdirs=/<>/libfwupd@@/<>/src@@/< UILDDIR>>/obj-x86_64-linux-gnu/libfwupd@@/<>/obj-x86_64-
> linux-gnu/src --mainfile=libfwupd-docs.xml --modulename=libfwupd --mode=auto -
> -content-files= --cflags=-g -O2 -fdebug-prefix-map=/<>=. -fstack-
> protector-strong -Wformat -Werror=format-security -Wdate-time -
> D_FORTIFY_SOURCE=2 --ldflags=-g -O2 -fdebug-prefix-map=/<>=. -
> fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
> -Wl,-z,now -
> -cc=cc --ld=cc'
> Running custom install script '/usr/bin/python3 /usr/bin/meson --internal 
> gettext
> install --subdir=po --localedir=share/locale --pkgname=fwupd'
> Running custom install script '/<>/po/make-images.sh
> /usr/share/locale'
> Running custom install script '/<>/meson_post_install.sh
> /lib/systemd/system /var'
>debian/rules override_dh_install
> make[1]: Entering directory '/<>'
> find debian/tmp/usr -type f -name "*a" -print | xargs rm -f
> sed -i 's,wheel,sudo,' ./debian/tmp/usr/share/polkit-
> 1/rules.d/org.freedesktop.fwupd.rules
> dh_install
> #install the EFI binaries if needed
> if [ -d debian/tmp/usr/lib/fwupd/efi/ ]; then \
>   dh_install -pfwupd usr/lib/fwupd/efi ;\
>   dh_install -pfwupd usr/lib/fwupd/fwupdate; \
> fi
> dh_install: No packages to build. Architecture mismatch: amd64, want: all 
> amd64
> arm64 armhf i386 linux-any
> dh_install: No packages to build. Architecture mismatch: amd64, want: all 
> amd64
> arm64 armhf i386 linux-any
> dh_missing --fail-missing
> dh_missing: usr/lib/fwupd/fwupdate exists in debian/tmp but is not installed 
> to
> anywhere
> dh_missing: usr/lib/fwupd/efi/fwupdx64.efi exists in debian/tmp but is not
> installed to anywhere
> dh_missing: missing files, aborting
>   The following debhelper tools have reported what they installed (with 
> files
> per package)
>* dh_install: fwupd (48), fwupd-amd64-signed-template (0), fwupd-arm64-
> signed-template (0), fwupd-armhf-signed-template (0), fwupd-doc (1), 
> fwupd-i386-
> signed-template (0), fwupd-tests (3), gir1.2-fwupd-2.0 (1), libfwupd-dev (6),
> 

Bug#904671: fwupd: Incomplete debian/copyright?

[Mario.Limonciello]

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?

[Mario.Limonciello]

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 [mailto:la...@debian.org]
> Sent: Thursday, July 26, 2018 8:09 AM
> To: sub...@bugs.debian.org
> Subject: Bug#904671: fwupd: Incomplete debian/copyright?
> 
> Source: fwupd
> Version: 1.1.0-1
> Severity: serious
> Justication: Policy 12.5
> X-Debbugs-CC: Mario Limonciello 
> 
> Hi,
> 
> I just ACCEPTed fwupd from NEW but noticed it was missing attribution
> in debian/copyright for at least a bunch of code copies (or similar)
> under "plugins/".
> 
> This is in no way exhaustive so please check over the entire package
> carefully and address these on your next upload. :)
> 
> 
> Regards,
> 
> --
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-

Bug#878311:

[Mario.Limonciello]

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#874521: 1.0.0

[Mario.Limonciello]

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#874521:

[Mario.Limonciello]

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 you're running on (OEM, model)?
  3.  Is this a notebook?  Are you docked?  What dock?
  4.  Any USB devices that you have plugged in.  Especially interesting is if 
you have a USB Logitech unifying dongle plugged in.
  5.  If you have a Logitech unifying dongle plugged in can you reproduce this 
without it plugged in?

If you can share a core dump, that would be especially useful too.

Thanks,

Bug#874521: fwupd segfaults at start

[Mario.Limonciello]

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
Version: 0.9.7-2
Severity: grave
Justification: renders package unusable

Hi,

fwupd segfaults at start with the following trace:

#0  0x556f337e7dd2 in FU_IS_DEVICE (ptr=0x556f34bdc170) at 
../src/fu-device.h:31
#1  0x556f337e7dd2 in fu_plugin_device_add (plugin=0x556f34bab840 
[FuPlugin], device=0x556f34bdc170) at ../src/fu-plugin.c:317
#2  0x556f337e7eed in fu_plugin_device_add_delay_cb 
(user_data=0x556f34bdedf0, user_data@entry=) at ../src/fu-plugin.c:374
#3  0x7fe839841853 in g_timeout_dispatch 
(source=source@entry=0x556f34bde830, callback=, 
user_data=) at ../../../../glib/gmain.c:4633
#4  0x7fe839840dd5 in g_main_dispatch (context=0x556f34b6c800) at 
../../../../glib/gmain.c:3148
#5  0x7fe839840dd5 in g_main_context_dispatch 
(context=context@entry=0x556f34b6c800) at ../../../../glib/gmain.c:3813
#6  0x7fe8398411a0 in g_main_context_iterate (context=0x556f34b6c800, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../../glib/gmain.c:3886
#7  0x7fe8398414b2 in g_main_loop_run (loop=0x556f34b4edf0) at 
../../../../glib/gmain.c:4082
#8  0x556f337d9dca in main (argc=, argv=) at 
../src/fu-main.c:947

Regards,

Laurent Bigonville

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-rc5-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fwupd depends on:
ii  libappstream-glib8 0.7.1-2
ii  libarchive13   3.2.2-2
ii  libc6  2.24-17
ii  libcolorhug2   1.3.3-2
ii  libdfu10.9.7-2
ii  libefivar1 31-1
ii  libfwup1   9-2
ii  libfwupd1  0.9.7-2
ii  libglib2.0-0   2.53.6-1
ii  libgnutls303.5.15-2
ii  libgpg-error0  1.27-3
ii  libgpgme11 1.9.0-4
ii  libgudev-1.0-0 232-1
ii  libgusb2   0.2.11-1
ii  libpolkit-gobject-1-0  0.113-6
ii  libsmbios2 2.3.1-2
ii  libsoup2.4-1   2.59.90.1-1
ii  libsqlite3-0   3.20.1-1
ii  libuuid1   2.29.2-4

Versions of packages fwupd recommends:
ii  fwupdate  9-2
ii  python3   3.5.3-3

fwupd suggests no packages.

-- no debconf information

Bug#853409:

[Mario.Limonciello]

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

Bug#856145: /usr/lib/fwupd/fwupd: Segfault everytime it starts

[Mario.Limonciello]

Yes,

It's caused by protection in the systemd service. It doesn't replicate if 
manually started.

Upstream is discussing the proper fixes and I'll issue an updated package early 
next week with the results.

Sent using Boxer
On Feb 25, 2017 09:31, Laurent Bigonville  wrote:
Package: fwupd
Version: 0.8.0-2
Severity: grave
File: /usr/lib/fwupd/fwupd
Justification: renders package unusable

Hi,

On both my laptop and my desktop, fwupd segfaults at every startup.

Same when using fwupdmgr, the daemon crashes.

I feel that some of the system protections from the .service file

If I'm adding -v in the service file, I see the following output:

fév 25 16:24:58 fornost systemd[1]: Starting Firmware update daemon...
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0770 Fu  Verbose debugging 
enabled (on console 0)
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0770 As  run AsStore:load
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0770 As  run 
AsStore:load{per-user}
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0770 As  run 
AsStore:load{per-system}
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0772 As  run 
AsStore:store-from-file{/usr/share/app-info/xmls/org.freedesktop.fwupd.xml}
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0773 As  run 
AsStore:store-from-root
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0773 As  using icon path 
/usr/share/app-info/icons/fwupd
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0773 As  run AsStore:match-addons
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0773 As  adding existing file: 
/usr/share/app-info/xmls/org.freedesktop.fwupd.xml
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0773 As  run 
AsStore:store-from-file{/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_non-free_dep11_Components-amd64.yml.gz}
fév 25 16:24:58 fornost fwupd[5038]: 15:24:58:0779 As  run 
AsStore:store-from-file{/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_main_dep11_Components-amd64.yml.gz}
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0466 As  run 
AsStore:store-from-file{/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_contrib_dep11_Components-amd64.yml.gz}
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0469 As  adding existing file: 
/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_non-free_dep11_Components-amd64.yml.gz
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0469 As  adding existing file: 
/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_main_dep11_Components-amd64.yml.gz
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0469 As  adding existing file: 
/var/lib/app-info/yaml/ftp.nl.debian.org_debian_dists_sid_contrib_dep11_Components-amd64.yml.gz
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0469 As  run 
AsStore:store-from-file{/var/cache/app-info/xmls/fwupd.xml}
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0470 As  run 
AsStore:store-from-root
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0470 As  using icon path 
/var/cache/app-info/icons/debian-sid-contrib
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0471 As  run AsStore:match-addons
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0472 As  adding existing file: 
/var/cache/app-info/xmls/fwupd.xml
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0472 As  run AsStore:match-addons
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0472 As  Emitting ::changed() 
[store-load]
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0472 Fu  Loading fallback values 
from /etc/fwupd.conf
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0479 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_steelseries.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0480 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_test.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0480 Fu  performing init() on 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_test.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0480 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_ebitdo.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0480 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_usb.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0480 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_colorhug.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0482 Fu  performing init() on 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_colorhug.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0482 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_udev.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0483 Fu  performing init() on 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_udev.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0483 Fu  adding plugin 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_dfu.so
fév 25 16:24:59 fornost fwupd[5038]: 15:24:59:0484 Fu  performing init() on 
/usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_dfu.so
fév 25 16:24:59 fornost fwupd[5038]: