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

2019-10-02 Thread Francois Marier
On 2019-09-30 at 19:53:03, mario.limoncie...@dell.com wrote:
> 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

Looks like it worked. I manually applied this on my machine and haven't seen
the messages in 2 days.

Francois

-- 
https://fmarier.org/



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

2019-09-30 Thread Mario.Limonciello
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, mario.limoncie...@dell.com wrote:
> What version did you upgrade from? And was that directory already existing or 
> did it get created with the package?

I'm also affected by this problem. In my case, I also purged the package and
reinstalled it. The problem persists and the cache symlink looks like this:

$ ls -l /var/cache/fwupd
lrwxr-xr-x 1 root root 13 sep 28 20:48 /var/cache/fwupd -> private/fwupd

Francois

--
https://fmarier.org/


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

2019-09-30 Thread Francois Marier
On 2019-09-29 at 23:57:02, mario.limoncie...@dell.com wrote:
> What version did you upgrade from? And was that directory already existing or 
> did it get created with the package?

I'm also affected by this problem. In my case, I also purged the package and
reinstalled it. The problem persists and the cache symlink looks like this:

$ ls -l /var/cache/fwupd
lrwxr-xr-x 1 root root 13 sep 28 20:48 /var/cache/fwupd -> private/fwupd

Francois

-- 
https://fmarier.org/



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

2019-09-30 Thread Mario.Limonciello
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 to run. I think this depends
on the permissions on the /var/cache/fwupd folder, which is a link to
/var/cache/private/fwupd.


● fwupd.service - Firmware update daemon
   Loaded: loaded (/lib/systemd/system/fwupd.service; static; vendor preset:
enabled)
   Active: failed (Result: exit-code) since Sun 2019-09-29 15:15:51 CEST; 24s
ago
 Docs: https://fwupd.org/
  Process: 16141 ExecStart=/usr/lib/fwupd/fwupd (code=exited,
status=239/CACHE_DIRECTORY)
 Main PID: 16141 (code=exited, status=239/CACHE_DIRECTORY)

running fwupd with superuser permissions results in no error



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

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.61.2-2
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
pn  fwupd-signed  
ii  python3   3.7.3-1

fwupd suggests no packages.

-- no debconf information


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

2019-09-29 Thread definetti
Package: fwupd
Version: 1.3.2-1
Severity: important

Dear Maintainer,

after updating to 1.3.2-1 the fwupd service fails to run. I think this depends
on the permissions on the /var/cache/fwupd folder, which is a link to
/var/cache/private/fwupd.


● fwupd.service - Firmware update daemon
   Loaded: loaded (/lib/systemd/system/fwupd.service; static; vendor preset:
enabled)
   Active: failed (Result: exit-code) since Sun 2019-09-29 15:15:51 CEST; 24s
ago
 Docs: https://fwupd.org/
  Process: 16141 ExecStart=/usr/lib/fwupd/fwupd (code=exited,
status=239/CACHE_DIRECTORY)
 Main PID: 16141 (code=exited, status=239/CACHE_DIRECTORY)

running fwupd with superuser permissions results in no error



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

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.61.2-2
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
pn  fwupd-signed  
ii  python3   3.7.3-1

fwupd suggests no packages.

-- no debconf information