[Pkg-kde-extras] Bug#919242: fails to start with apparmor enabled

[Hendrik Jaeger]

Hi

I run into a similar problem running quassel-core with the provided
init-script as a system service.
Excerpts from the audit.log are attached.

The problem is first that the ssl keyfile in /etc/ssl/private/ can not
be read. After adding this line to
/etc/apparmor.d/local/usr.bin.quasselcore
a number of other files are becoming the issue.
Also the process cannot be handled by the init-script anymore because
it’s not allowed to receive signals, it seems.
I added the following lines the local apparmor profile before giving up:
/usr/bin/quasselcore {
  #include <abstractions/qt5>

  /etc/ssl/private/quassel.example.org.key r,
  /lib/i386-linux-gnu/libdl-2.28.so rm,
  /lib/i386-linux-gnu/libz.so.1.2.11 rm,
  signal (receive),
}

I then decided to just disable the apparmor profile.

This profile is provided by the apparmor package, so I’m adding onto
this package.

As it seems to make the package unusable (or maybe just with sysvinit?)
this is IMHO not wishlist but at least serious.

Is this possibly related to and fixed by #940482?

Thanks!

Hendrik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: quassel-core_audit.log
Type: text/x-log
Size: 9260 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-extras/attachments/20210501/7f3786b9/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-extras/attachments/20210501/7f3786b9/attachment.sig>