Re: Akonadi 4:18.08.3-8 in experimental

2019-10-28 Thread Diederik de Haas
Hi, On maandag 28 oktober 2019 12:33:30 CET Sandro Knauß wrote: > Mmh, okay now the question is, if Akonadi was functional before you deleted > that file. Yes, it was functional. AFAIK akonadi uses my OS credentials, so it doesn't/ shouldn't need any creds that could be stored in that file. >

Re: Akonadi 4:18.08.3-8 in experimental

2019-10-28 Thread Sandro Knauß
Hey, > On vrijdag 25 oktober 2019 12:08:12 CEST John Scott wrote: > > You probably have apparmor-notify installed which displays the > > notifications. > > That is correct. Mmh, okay now the question is, if Akonadi was functional before you deleted that file. Because at least for me, I would

Re: Akonadi 4:18.08.3-8 in experimental

2019-10-25 Thread Diederik de Haas
On vrijdag 25 oktober 2019 12:08:12 CEST John Scott wrote: > You probably have apparmor-notify installed which displays the > notifications. That is correct. signature.asc Description: This is a digitally signed message part.

Re: Akonadi 4:18.08.3-8 in experimental

2019-10-25 Thread John Scott
On October 24, 2019 11:43:05 PM EDT, Diederik de Haas wrote: >On donderdag 24 oktober 2019 21:30:22 CEST Sandro Knauß wrote: >> thanks for the reply. How this notification is displayed? Like any >> notification e.g. "new mail" or is just seen in dmesg? > >I don't have "new mail" notifications,

Re: Akonadi 4:18.08.3-8 in experimental

2019-10-24 Thread Diederik de Haas
On donderdag 24 oktober 2019 21:30:22 CEST Sandro Knauß wrote: > thanks for the reply. How this notification is displayed? Like any > notification e.g. "new mail" or is just seen in dmesg? I don't have "new mail" notifications, but I'd guess that's what I meant. Every time an issue with AppArmor

Re: Akonadi 4:18.08.3-8 in experimental

2019-10-24 Thread Sandro Knauß
Hey, thanks for the reply. How this notification is displayed? Like any notification e.g. "new mail" or is just seen in dmesg? sandro -- On Mittwoch, 23. Oktober 2019 04:43:20 CEST Diederik de Haas wrote: > On woensdag 23 oktober 2019 04:06:29 CEST Diederik de Haas wrote: > > Right after

Re: Akonadi 4:18.08.3-8 in experimental

2019-10-22 Thread Diederik de Haas
On woensdag 23 oktober 2019 04:06:29 CEST Diederik de Haas wrote: > Right after sending that, I get the following notification: > Profile: /usr/bin/akonadiserver > Operation: open > Name: /home/diederik/.pgpass > Denied: r > Logfile: /var/log/kern.log > For more information, visit

Re: Akonadi 4:18.08.3-8 in experimental

2019-10-22 Thread Diederik de Haas
On woensdag 23 oktober 2019 04:02:45 CEST Diederik de Haas wrote: > On dinsdag 24 september 2019 22:30:38 CEST Sandro Knauß wrote: > > I uploaded Akonadi 4:18.08.3-8 to experimental, the main reason is, that I > > want to test further AppArmor support. If you use unstable, please gi

Re: Akonadi 4:18.08.3-8 in experimental

2019-10-22 Thread Diederik de Haas
On dinsdag 24 september 2019 22:30:38 CEST Sandro Knauß wrote: > I uploaded Akonadi 4:18.08.3-8 to experimental, the main reason is, that I > want to test further AppArmor support. If you use unstable, please give it a > try and give feedback if you see any new issues. I just

Re: Akonadi 4:18.08.3-8 in experimental

2019-09-25 Thread Martin Steigerwald
Martin Steigerwald - 25.09.19, 10:00:50 CEST: > Great. Looking forward to that! I am willing to set those from > experimental as well, in case you like to have some testers. s/set/test -- Martin

Re: Akonadi 4:18.08.3-8 in experimental

2019-09-25 Thread Martin Steigerwald
Sandro Knauß - 24.09.19, 22:30:38 CEST: > I uploaded Akonadi 4:18.08.3-8 to experimental, the main reason is, > that I want to test further AppArmor support. If you use unstable, > please give it a try and give feedback if you see any new issues. Is not allowed to use pg_ctl to start P

Akonadi 4:18.08.3-8 in experimental

2019-09-24 Thread Sandro Knauß
Hey, I uploaded Akonadi 4:18.08.3-8 to experimental, the main reason is, that I want to test further AppArmor support. If you use unstable, please give it a try and give feedback if you see any new issues. I will soon start packaging the current KDE Pim (19.08) packages. Before starting