Bug#941118: akonadi-server: fails to start after upgrade to 4:18.08.3-8: apparmor denied access to pg_ctl

Hey intrigeri, I now pushed a first version of Akonadi with the new AppArmor profile, but as you see down here it fails and I'm not sure, what went wrong. What we need to do to debug this? Those AppArmor profiles are in place:

plasma-workspace_5.14.5.1-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Oct 2019 20:43:23 +0200 Source: plasma-workspace Architecture: source Version: 4:5.14.5.1-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano

Processing of plasma-workspace_5.14.5.1-2_source.changes

plasma-workspace_5.14.5.1-2_source.changes uploaded successfully to localhost along with the files: plasma-workspace_5.14.5.1-2.dsc plasma-workspace_5.14.5.1-2.debian.tar.xz plasma-workspace_5.14.5.1-2_source.buildinfo Greetings, Your Debian queue daemon (running on host

kscreen_5.14.5-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Oct 2019 19:32:29 +0200 Source: kscreen Architecture: source Version: 4:5.14.5-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Changes:

Processing of kscreen_5.14.5-2_source.changes

kscreen_5.14.5-2_source.changes uploaded successfully to localhost along with the files: kscreen_5.14.5-2.dsc kscreen_5.14.5-2.debian.tar.xz kscreen_5.14.5-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

gwenview_19.08.1-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Oct 2019 19:04:17 +0200 Source: gwenview Architecture: source Version: 4:19.08.1-3 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Changes:

Bug#941505: plasma-framework: Num lock key is always ON at startup, even if in the configuration is forced to OFF

I had already reported this bug, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872

Processing of gwenview_19.08.1-3_source.changes

gwenview_19.08.1-3_source.changes uploaded successfully to localhost along with the files: gwenview_19.08.1-3.dsc gwenview_19.08.1-3.debian.tar.xz gwenview_19.08.1-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

purpose_5.62.0-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Oct 2019 18:44:52 +0200 Source: purpose Architecture: source Version: 5.62.0-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Pino Toscano Changes: purpose

Processing of purpose_5.62.0-2_source.changes

purpose_5.62.0-2_source.changes uploaded successfully to localhost along with the files: purpose_5.62.0-2.dsc purpose_5.62.0-2.debian.tar.xz purpose_5.62.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#941505: plasma-desktop: Plasma Desktop does not respect its numlock configuration.

Package: plasma-desktop Version: 4:5.14.5.1-2 Severity: normal Hi. Event with the keyboard NumLock configuration set to "Activated" at Plasma startup, the numlock led is still off and keypad presses are not giving numbers anymore unless I manually press the NumLock key. --

Bug#941504: sddm: SDDM does not respect config "NumLock=on" in /etc/sddm.conf

Package: sddm Version: 0.18.0-1 Severity: normal Tags: upstream Hi. Since several days, SDDM does not respect the NumLock=on directive in its local configuration file. Indeed, even with NumLock=on the numlock LED is still off and, of course, no keypad number can be typed unless

kwayland-integration_5.14.5-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Oct 2019 14:19:28 +0200 Source: kwayland-integration Architecture: source Version: 5.14.5-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Maximiliano Curia

Processing of kwayland-integration_5.14.5-2_source.changes

kwayland-integration_5.14.5-2_source.changes uploaded successfully to localhost along with the files: kwayland-integration_5.14.5-2.dsc kwayland-integration_5.14.5-2.debian.tar.xz kwayland-integration_5.14.5-2_source.buildinfo Greetings, Your Debian queue daemon (running on host

Bug#941298: marked as done (kwayland-integration FTBFS: method incorrectly marked "override")

Your message dated Tue, 01 Oct 2019 12:34:11 + with message-id and subject line Bug#941298: fixed in kwayland-integration 5.14.5-2 has caused the Debian Bug report #941298, regarding kwayland-integration FTBFS: method incorrectly marked "override" to be marked as done. This means that you

Bug#941481: kalarm: The Akonadi personal information management service is not running

Package: kalarm Version: 4:18.08.3-1 Severity: important Dear Maintainer, When installing kalarm on mate desktop environment, program is not working. It shows just message "The Akonadi personal information management service is not running. This application cannot be used without it". Pressing