[opensuse-factory] Apparmor problems with kdm3
Hi! After recent update to 11.4 kdm3 (KDE3's display manager) does not start with normal boot, leaving me with console screen. Only sequence of init 3 init 5 from root account helps. On the other hand, gdm works well. I also receive the following in dmesg when using kdm3: [ 53.186180] type=1400 audit(1320709759.623:2): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=2875 comm="login" [ 53.186193] type=1400 audit(1320709759.623:3): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=2875 comm="login" [ 76.645315] type=1400 audit(1320709783.082:4): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=3050 comm="kdm" [ 76.645328] type=1400 audit(1320709783.082:5): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=3050 comm="kdm" [ 165.897837] type=1400 audit(1320709872.333:6): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=3962 comm="kdm" [ 165.897849] type=1400 audit(1320709872.333:7): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=3962 comm="kdm" which is why I suspect apparmor even though it is switched off in Yast2 (switching it on does not help). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Dienstag, 8. November 2011 schrieb Ilya Chernykh:
After recent update to 11.4 kdm3 (KDE3's display manager) does not start with normal boot, leaving me with console screen.
Are you talking about an openSUSE 11.4 system here or about a 12.1 installation? I'm asking because they have different versions of AppArmor which also means some differences in the default profiles.
Only sequence of
init 3 init 5
from root account helps.
Hmm, sounds interesting[tm] - and I'm quite surprised that this "fix" works...
On the other hand, gdm works well.
I also receive the following in dmesg when using kdm3:
[ 53.186180] type=1400 audit(1320709759.623:2): apparmor="DENIED" operation="c hange_hat" info="unconfined" error=-1 pid=2875 comm="login" [ 53.186193]
That's only part of what I need to check this issue. Basically you have two options: a) send me your /var/log/audit/audit.log (off-list or attached to a bugreport) b) run aa-logprof yourself and send me the profile diff
which is why I suspect apparmor even though it is switched off in Yast2 (switching it on does not help).
Just check it with "rcapparmor status" ;-) Regards, Christian Boltz -- Neue Windows-Tastatur seit heute zu kaufen. Hier ein erstes Bild: ,-----, ,-----, ,------, | Str | | Alt | | Entf | '-----' '-----' '------' -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 08 November 2011 15:06:32 Christian Boltz wrote:
Hmm, sounds interesting[tm] - and I'm quite surprised that this "fix" works...
This post is outdated now. I found the actual cause of the problem, and it is unrelated to apparmor. The problem was due to NTP was updating time exactly during kdm start which disrupted its work. The fix is already submitted to Factory https://build.opensuse.org/request/show/90539
which is why I suspect apparmor even though it is switched off in Yast2 (switching it on does not help).
Just check it with "rcapparmor status" ;-)
As it already turned out the problem was unrelated to apparmor and happened even with apparmor uninstalled. But the strange output in dmesg is still quite curious. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Christian Boltz -
Ilya Chernykh