Bug#885851: Seems to be related to AppArmor

2018-01-01 Thread Dirk Heinrichs
Hi, > your snippets are a bit short to see if there was no active AppArmor > profile for Thunderbird, if so you would have seen this one extra line > from AppArmor. >> Skipping profile in /etc/apparmor.d/disable: usr.bin.thunderbird <- Yes, I indeed have this line the log, but only when down

Bug#885851: Seems to be related to AppArmor

2018-01-01 Thread Carsten Schoenert
Hello Dirk, On Sun, Dec 31, 2017 at 11:28:12PM +0100, Dirk Heinrichs wrote: > Am 31.12.2017 um 12:05 schrieb Carsten Schoenert: > > > You don't provide any information about the state of your machine before > > you startetd the update nor after the update. You also don't have > > appended any log

Bug#885851: Seems to be related to AppArmor

2017-12-31 Thread Dirk Heinrichs
Am 31.12.2017 um 12:05 schrieb Carsten Schoenert: > You don't provide any information about the state of your machine before > you startetd the update nor after the update. You also don't have > appended any logging information, so how can I unpuzzle that and see > what was going maybe wrong? Wha

Bug#885851: Seems to be related to AppArmor

2017-12-31 Thread Carsten Schoenert
Hello Dirk, On Sat, Dec 30, 2017 at 10:34:31PM +0100, Dirk Heinrichs wrote: > I don't understand the question. What exactly is missing in > > "After update of thunderbird to above version, it doesn't start anymore. > I only get a popup window, telling me "Your Thunderbird profile cannot > be lo

Bug#885851: Seems to be related to AppArmor

2017-12-30 Thread Dirk Heinrichs
Am 30.12.2017 um 17:28 schrieb Carsten Schoenert: > Hello Dirk, Am 30.12.2017 um 13:34 schrieb Dirk Heinrichs: >> Hi, after removing apparmor and retrying the update, it worked just >> fine. So the problem might be somehow related to apparmor. > unfortunately you give no detailed information what

Bug#885851: Seems to be related to AppArmor

2017-12-30 Thread Carsten Schoenert
Hello Dirk, Am 30.12.2017 um 13:34 schrieb Dirk Heinrichs: > Hi, > > after removing apparmor and retrying the update, it worked just fine. So > the problem might be somehow related to apparmor. unfortunately you give no detailed information what did not work for you and also no logs. It's quite

Bug#885851: Seems to be related to AppArmor

2017-12-30 Thread Dirk Heinrichs
Hi, after removing apparmor and retrying the update, it worked just fine. So the problem might be somehow related to apparmor. HTH...     Dirk -- Dirk Heinrichs GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015 Sichere Internetkommunikation: http://www.retroshare.org Privacy Handbuch: