Hi Seth. After 'parsing' Pidgin profile with 'apparmor_parser' command everything seems to be okay. No errors related to TOK_PROFILE and TOK_OPEN. Really, it was pretty strange, but Pidgin profile was listed in profiles with 'enforce' mode. I checked AppArmor status to see what really happened with Pidgin profile;
,------- | $ sudo apparmor_status | apparmor module is loaded. | 33 profiles are loaded. | 30 profiles are in enforce mode. | (...) | /usr/bin/pidgin | /usr/bin/pidgin///usr/bin/gconftool-2 | /usr/bin/pidgin///usr/bin/xdg-open | (...) | 1 processes are unconfined but have a profile defined. | /usr/bin/pidgin (3515) `------- This profile was not in the '/etc/apparmor.d/' directory when I ran 'apparmor_parser' command for the first time (today). The profile file was 'parsering' in user home directory. As I already mentioned a Pidgin profile appeared on the list of programs with 'enforce' mode (see above note about 'apparmor_status' command result), but still, Pidgin profile WAS NOT in the '/etc/apparmor.d/' directory! It is normal? It seems to me, that this is not. When I perform those tasks - I mean parser Pidgin profile etc, generally everything mentioned above, Pidgin was enabled and worked okay. I was worried only about profile and that, it was not in the '/etc/apparmor.d/' directory. Of course I decided to check what will happen when I reenable Pidging. After disable and enable Pidgin, it seems, that this profile is not complete, because menu where I should enter my password were full of '[][][][][][][]' signs. Similar thing happens to the Pidgin contact list etc, everywhere only '[][][]' signs. Okay Seth, now let's check commands 'apparmor_parser' command with "-QN" options; ,------- | $ apparmor_parser -QN /etc/apparmor.d/usr.bin.pidgin | /usr/bin/pidgin | /usr/bin/pidgin///usr/bin/gconftool-2 | /usr/bin/pidgin///usr/bin/xdg-open `------- It looks like everything is okay, right? At least for me. Similar thing looks with setting Pidgin in 'enforce' mode; ,------- | sudo aa-enforce pidgin | Setting /etc/apparmor.d/usr.bin.pidgin to enforce mode. `------- After checking profiles status with 'apparmor_status' command, I see that Pidgin are in enforce mode. Unfortunately after enabling Pidgin, there are signs just like before - [][][][][][][] etc. After changing profile to a 'complain' mode, everything is returned to normal. Should I leave Pidgin in a 'complain' mode and use it for a some period of time, chat with people, add contacts, edit contacts and after a couple of days, again change profile to 'enforce' mode? Seth do you think, that it might work? Regards! Apologize for such a long comment. _____________ PS; I removed (previously I also used the # sign - you had mentioned about it in your comment above) 'Name' and 'Directory' entries from the top of the profile. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066369 Title: AppArmor parser error, Warning from stdin (line 1), syntax error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1066369/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
