pitti asked me for testing the -proposed package with my Bluetooth printer (HP PhotoSmart A710 with Bluetooth plug in its USB memory/camera port).
As I do not have Gutsy, I have tried with Hardy but with the Gutsy kernel booted (2.6.22), as the Hardy kernel (2.6.24) has no AppArmor support compiled in.
Unfortunately, AppArmor does not work with this configuration. It seems that the AppArmor profile format has changed in an incompatible way. On restart of AppArmor I get something like
Profile /etc/apparmor.d/usr.sbin.ntpd failed to load
/sbin/apparmor_parser: Unable to replace "/usr/sbin/smbd". Profile doesn't conform to protocol
on nearly every profile.
I get
till@till-laptop:~/ubuntu/cupsys/proposed$ sudo aa-status cupsdapparmor module is loaded.
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode :
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
till@till-laptop:~/ubuntu/cupsys/proposed$
which shows that the cupsd profile did not get accepted, too.
So in my environment I cannot test, and AppArmor needs to be sorted out that it works on Hardy.
pitti asked me for testing the -proposed package with my Bluetooth printer (HP PhotoSmart A710 with Bluetooth plug in its USB memory/camera port).
As I do not have Gutsy, I have tried with Hardy but with the Gutsy kernel booted (2.6.22), as the Hardy kernel (2.6.24) has no AppArmor support compiled in.
Unfortunately, AppArmor does not work with this configuration. It seems that the AppArmor profile format has changed in an incompatible way. On restart of AppArmor I get something like
Profile /etc/apparmor. d/usr.sbin. ntpd failed to load parser: Unable to replace "/usr/sbin/smbd". Profile doesn't conform to protocol
/sbin/apparmor_
on nearly every profile.
I get
till@till- laptop: ~/ubuntu/ cupsys/ proposed$ sudo aa-status cupsdapparmor module is loaded. laptop: ~/ubuntu/ cupsys/ proposed$
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode :
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
till@till-
which shows that the cupsd profile did not get accepted, too.
So in my environment I cannot test, and AppArmor needs to be sorted out that it works on Hardy.