Bug 156990

Summary:	Apparmor gets started automatically on update
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Reinhard Max <max>
Component:	AppArmor	Assignee:	Dominic W Reynolds <dreynolds>
Status:	RESOLVED FIXED	QA Contact:	Dominic W Reynolds <dreynolds>
Severity:	Critical
Priority:	P5 - None	CC:	aj, suse-beta
Version:	Beta 7
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Reinhard Max 2006-03-10 11:25:13 UTC

After updating from beta3 to beta7 I found that apparmor was running without me having enabled it. It might be OK to enable apparmor on a fresh installation, but it shouldn't be enabled on an update if it wasn't running before.

See the next bug I am going to submit for the reason.

Comment 1 Dominic W Reynolds 2006-03-10 20:43:53 UTC

This makes sense. Code 10 precursers (SLES9, SL10.1) won't have it enabled by default so we shouldn't change behavior without an explicit user ack during installation. 

We can make the chkconfig changes contingent on a new install rather than upgrade.

For sles9 we will need some special handling as the packages are renamed and obsolete the previous ones (rather than upgrade).

Comment 2 Dominic W Reynolds 2006-03-26 19:07:55 UTC

Marking this as critical rather than blocker. The related profile problems for mail have been adressed.

Comment 3 Dominic W Reynolds 2006-04-03 05:43:26 UTC

Fixed. Checked into autobuild.