Comment 5 for bug 438051

Well, just that command after editing etc/apparmor.d/abstractions/X didn't helped but after an /etc/init.d/apparmor reload it does, with your suggestions firefox has the wanted mouse theme and also no more message from apparmor in kernel log.

I am not sure it's ok to mention here, but I also got another problem I've just found while looking at output of command dmesg:

[440079.454359] type=1503 audit(1254230635.992:356): operation="file_mmap" pid=14648 parent=1 profile="/usr/lib/firefox-3.5.*/firefox" requested_mask="mr::" denied_mask="m::" fsuid=1000 ouid=1000 name="/<email address hidden>/plugins/libmoonloaderxpi.so"
[440079.454982] type=1503 audit(1254230635.992:357): operation="file_mmap" pid=14648 parent=1 profile="/usr/lib/firefox-3.5.*/firefox" requested_mask="mr::" denied_mask="m::" fsuid=1000 ouid=1000 name="/<email address hidden>/plugins/libmoonloaderxpi.so"

That's Moonlight extension for firefox, and it seems I have problems with that. Is it possible that this can cause the bug 438575 ? Maybe upgrading extensions has problem because with the new one it stops at moonlight because of apparmor restrictions so I have pending 'restart to firefox' messages in add-ons window all the time even after restarting. But just guessing .... Sorry for the noise here, I will test to disable apparmor and see if extension upgrade process is ok then or not, and I will report at the other bug, I've subscribed. Thanks for the patience.