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:abhijithoskeri@icloud.com]
> Sent: Wednesday, January 10, 2018 1:40 PM
> To: Debian Bug Tracking System <submit@bugs.debian.org>
> Subject: Bug#886878: fwupd service startup fails.
>
> Package: fwupd
> Version: 1.0.3-1
> Severity: important
>
> Dear Maintainer,
>
> fwupd startup fails with the default systemd service configuation - the
> service seems to require libffi generated code, and the systemd
> directive 'MemoryDenyWriteExecute=yes' prevents libffi from executing
> generated code.
>
> Disabling this in the systemd service MemoryDenyWriteExecute allows the
> service startup to proceed as expected.
>
> Thanks,
> Abhijit
>
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers unstable-debug
> APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500,
> 'testing'), (1, 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages fwupd depends on:
> ii libappstream-glib8 0.7.4-1
> ii libarchive13 3.2.2-3.1
> ii libc6 2.26.9000+20180108.401311cf-0experimental0
> ii libcolorhug2 1.3.3-2
> ii libefivar1 32-2
> ii libelf1 0.170-0.2
> ii libfwup1 10-1
> ii libfwupd2 1.0.3-1
> ii libglib2.0-0 2.54.3-1
> ii libgnutls30 3.6.1-1
> ii libgpg-error0 1.27-5
> ii libgpgme11 1.10.0-1
> 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.60.2-2
> ii libsqlite3-0 3.21.0-1
> ii libuuid1 2.30.2-0.1
>
> Versions of packages fwupd recommends:
> ii fwupdate 10-1
> ii python3 3.6.4-1
>
> fwupd suggests no packages.
>
> -- no debconf information
Reply to: