Hey,
> There are two unrelated things in this discussion:
thanks for clarification.
> a) the need to update the pstgresql_akonadi AppArmor profile when using
>the internal postgres service (= this mail)
>
> b) Sedat switched to using the system wide postgres (not relevant for
>the AppA
Hello,
Am Sonntag, 6. September 2020, 21:31:45 CEST schrieb Sandro Knauß:
> Christian is trying to replace the Akonadi internal postgres service
> with a system wide service. Is that correct?
No ;-)
There are two unrelated things in this discussion:
a) the need to update the pstgresql_akonadi A
Hey,
Christian is trying to replace the Akonadi internal postgres service with a
system wide service. Is that correct?
(This in itself is not really supported by Akonadi; normally Akonadi is taking
care about starting and stopping the database itself). So what is the
advantage of starting/stopp
Hello,
Am Freitag, 4. September 2020, 10:30:25 CEST schrieb Sedat Dilek:
> I followed some weird howtos in the WildWildWild-Internet and did a
> wrong setup. [1] has the correct instructions.
>
> The issue was when the akonadi-database ran as an own
> postgresql-instance/process when looking with
On Thu, Sep 3, 2020 at 8:44 PM Christian Boltz
wrote:
>
> Hello,
>
> Am Donnerstag, 3. September 2020, 17:15:54 CEST schrieb Sedat Dilek:
> > root# LC_ALL=C dmesg -T | egrep apparmor | grep akonadi
> > [Thu Sep 3 15:27:34 2020] audit: type=1400 audit(1599139654.969:28):
> > apparmor="DENIED" oper
Hi,
the corresponding AppArmor policy is shipped by akonadi packages and
maintained by the Debian/Kubuntu Qt/KDE Maintainers, so I'm relaying
this info there.
Dear Debian/Kubuntu Qt/KDE Maintainers, see Christian Boltz reply on
this thread :)
Sedat Dilek (2020-09-03):
> I switched over the datab
6 matches
Mail list logo
