** Description changed: Hello, during manually attempts to change Pidgin profile* from :complain: to >enforce< mode with 'aa-enforce /etc/usr.bin.pidgin' command, this error appears: - /* Setting /etc/apparmor.d/usr.bin.pidgin to complain mode. - Warning from stdin (line 1): /sbin/apparmor_parser: cannot use or update cache, disable, or force-complain via stdin - AppArmor parser error, in stdin line 1: syntax error, unexpected TOK_PROFILE, expecting TOK_OPEN */ + ,------- + |Setting /etc/apparmor.d/usr.bin.pidgin to complain mode. + |Warning from stdin (line 1): /sbin/apparmor_parser: cannot use or update cache, |disable, or force-complain via stdin + |AppArmor parser error, in stdin line 1: syntax error, unexpected TOK_PROFILE, |expecting TOK_OPEN + `------- As we can see, change Pidgin profile seems to work (`Setting (...) to complain mode` message), but there is not Pidgin when I check AppArmor status with 'apparmor_status' command. So, not everything works as I expected. A few days ago I managed to successfully toggles the mode for a couple applications, such as '/bin/ping' or '/usr/sbin/avahi-daemon'. Logs from 'ubuntu-bug' utility for `KernLog` and `ApparmorStatusOutput` looks okay. I do not see any problems. Just informations about e.g. (`KernLog`): - /* type = 1400 audit(numbers): apparmor="STATUS" - operation="profile_load" name="*" pid"*" (...) */ - - /* type = 1400 audit(numbers): apparmor="STATUS" - operation="profile_replace" name="*" pid"*" (...) */ - - /* (...) and many more, about all profiles. */ + ,------- + | type = 1400 audit(numbers): apparmor="STATUS" operation="profile_load" name="*" + | pid"*" (...) + `------- + ,------- + | type = 1400 audit(numbers): apparmor="STATUS" operation="profile_replace" name="*" + | pid"*" (...) and many more, about all profiles. + `------- And the log of `ApparmorStatusOutput` also seems to be okay - contains information about apparmor module, number of loaded profile etc. Nothing special, nothing more, nothing less. Some more distribution-specific information: +===================================+ ## Package: apparmor 2.7.102-0ubuntu3.1** ## Problem type: bug ## ApportVersion: 2.0.1-ubuntu13 ## EcryptfsInUse: yes ## NonFreeKernelModules: nvidia ## Architecture: i386 ## Distro release: 12.04 ## Uname: 3.2.0-32-generic $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 12.04.1 LTS Release: 12.04 Codename: precise +===================================+ Best regards! _____________ * taken from bazaar.launchpad.net website. ** 'apparmor-utils' and 'apparmor-profiles' have the same version.
** Description changed: Hello, during manually attempts to change Pidgin profile* from :complain: to >enforce< mode with 'aa-enforce /etc/usr.bin.pidgin' command, this error appears: - ,------- - |Setting /etc/apparmor.d/usr.bin.pidgin to complain mode. - |Warning from stdin (line 1): /sbin/apparmor_parser: cannot use or update cache, |disable, or force-complain via stdin - |AppArmor parser error, in stdin line 1: syntax error, unexpected TOK_PROFILE, |expecting TOK_OPEN - `------- + /* Setting /etc/apparmor.d/usr.bin.pidgin to complain mode. + Warning from stdin (line 1): /sbin/apparmor_parser: cannot use or update cache, disable, or force-complain via stdin + AppArmor parser error, in stdin line 1: syntax error, unexpected TOK_PROFILE, + expecting TOK_OPEN */ As we can see, change Pidgin profile seems to work (`Setting (...) to complain mode` message), but there is not Pidgin when I check AppArmor status with 'apparmor_status' command. So, not everything works as I expected. A few days ago I managed to successfully toggles the mode for a couple applications, such as '/bin/ping' or '/usr/sbin/avahi-daemon'. Logs from 'ubuntu-bug' utility for `KernLog` and `ApparmorStatusOutput` looks okay. I do not see any problems. Just informations about e.g. (`KernLog`): ,------- - | type = 1400 audit(numbers): apparmor="STATUS" operation="profile_load" name="*" + | type = 1400 audit(numbers): apparmor="STATUS" operation="profile_load" name="*" | pid"*" (...) - `------- - ,------- - | type = 1400 audit(numbers): apparmor="STATUS" operation="profile_replace" name="*" + | + | type = 1400 audit(numbers): apparmor="STATUS" operation="profile_replace" name="*" | pid"*" (...) and many more, about all profiles. `------- And the log of `ApparmorStatusOutput` also seems to be okay - contains information about apparmor module, number of loaded profile etc. Nothing special, nothing more, nothing less. Some more distribution-specific information: +===================================+ ## Package: apparmor 2.7.102-0ubuntu3.1** ## Problem type: bug ## ApportVersion: 2.0.1-ubuntu13 ## EcryptfsInUse: yes ## NonFreeKernelModules: nvidia ## Architecture: i386 ## Distro release: 12.04 ## Uname: 3.2.0-32-generic $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 12.04.1 LTS Release: 12.04 Codename: precise +===================================+ Best regards! _____________ * taken from bazaar.launchpad.net website. ** 'apparmor-utils' and 'apparmor-profiles' have the same version. -- 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
