weVeg, your solution is useless.
I have finally solved this problem, AppArmor is all healthy and working without no problems again!
/proc/cmdline contained:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae
root=UUID=26ada0c0-1165-4098-884d-aafd2220c2c6 ro
Adding "apparmor=1 security=apparmor" to GRUB_CMDLINE_LINUX_DEFAULT in
/etc/default/grub and running "sudo update-grub" and "sudo reboot" fixed this issue.
another fix of this problem is:
$ sudo perl -pi -e 's,GRUB_CMDLINE_LINUX="(.*)"$,GRUB_CMDLINE_LINUX=" $1 apparmor=1 security=apparmor",' /etc/default/grub
$ sudo update-grub
$ sudo reboot
P.S: mounting /sys/kernel/security seemed pretty suspicious as one can say, and that had nothing to do with AppArmor's disablement as the main module itself wasn't working. It had something to do with the GRUB configurations.
(weVeg, stop googling every question :p)