Your message dated Tue, 26 Jun 2018 11:23:45 +0200
with message-id <[email protected]>
and subject line Invalid report
has caused the Debian Bug report #902411,
regarding upower fails to start with MemoryDenyWriteExecute=true
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
902411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902411
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: upower
Version: 0.99.8-1
Severity: important

Dear Maintainer,

upower fails to start with the following error:

/usr/lib/upower/upowerd: error while loading shared libraries: libffi.so.6: 
cannot enable executable stack as shared object requires: Operation not 
permitted


setting MemoryDenyWriteExecute=false in the systemd service file, upower
starts up again.



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

Kernel: Linux 4.16.0-2-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)
LSM: AppArmor: enabled

Versions of packages upower depends on:
ii  dbus               1.12.8-3
ii  libc6              2.27-3
ii  libglib2.0-0       2.56.1-2
ii  libgudev-1.0-0     232-2
ii  libimobiledevice6  1.2.1~git20180302.3a37a4e-1
ii  libplist3          2.0.0-3
ii  libupower-glib3    0.99.8-1
ii  libusb-1.0-0       2:1.0.22-2
ii  udev               239-1

Versions of packages upower recommends:
ii  policykit-1  0.105-20

upower suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
looks like this was caused by an outdated version of libffi6 from experimental

--- End Message ---

Reply via email to