On Sat, Jan 19, 2019 at 06:48:46PM +0100, Carsten Schoenert wrote: > > -- Configuration Files: > > /etc/apparmor.d/usr.bin.thunderbird [Errno 2] No such file or directory: > > '/etc/apparmor.d/usr.bin.thunderbird' > > you have AppAprmor installed and there is some problem with the AA > profile for TB which can't be found.
I do have apparmor installed, but it is not enabled. % sudo aa-status apparmor module is loaded. apparmor filesystem is not mounted. > I expect you will see some 'ACCESS denied' messages in the output of the > dmesg command so Thunderbird can't write the information to the > harddisk. Please check for such messages. I've cleared message buffer with "dmesg -c", run thunderbird and experienced problem, and then run "dmesg" again, which produced no output. So I would guess apparmor has not blocked anything. (on other machine where I do have it enabled, it always log to dmesg any access denied messages) Also, I do not think it is probable that it is permission problem with write access to "abook.mab" - if it were, I probably also couldn't delete entries from addressbook, which I CAN do. I just can't add new contact or modify existing ones. It feels like the OK button in GUI is not linked to doing anything. Could that perhaps be the case (linked to that "Gtk-WARNING **: Theme parsing error" messages when starting up Thunderbird)? > $ sudo apt install --reinstall thunderbird Interestingly enough, this did not reinstall /etc/apparmor.d/usr.bin.thunderbird file. I did "dpkg --purge thunderbird; apt-get install thunderbird" which did reinstall it. But since apparmor isn't enabled, it didn't help. > If you don't want to use the ApprArmor functionality you can disable the > profile for TB. But we prefer to fix such issues. Yeah, I would prefer that too, but too many things break on this system with apparmor, so I disabled it after some period of testing. Just to make sure, I have now completely removed apparmor, apparmor-utils, apparmor-profiles, and apparmor-profiles-extra packages from the system and rebooted. The same bug in thunderburd is still there. Any other ideas? Or can you reproduce the bug? -- Opinions above are GNU-copylefted.
