Bugzilla – Bug 1214418
yast2 apparmor: crash when choosing "
Last modified: 2023-08-23 08:40:03 UTC
Created attachment 868897 [details] y2log Precondition: make sure you have an "exec" event in your audit.log, for example by adding the following (made-up) line to your /var/log/audit/audit.log: type=AVC msg=audit(1692535178.922:9306963): apparmor="ALLOWED" operation="exec" class="file" profile="ping" name="/usr/bin/cat" pid=25489 comm="hello" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 target="ping//null-/usr/bin/cat" Then - start yast2 apparmor - select "Scan Audit logs" - click "Launch" - when asked for the execute mode, choose "Named" - in the following dialog ("transition to local profile?), click "yes" - get the following error dialog: === Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Caller: /usr/share/YaST2/lib/apparmor/apparmor_ui_dialog.rb:128:in `run' Details: uninitialized constant AppArmor::GetStringDialog::Label === Only y2log (attached) got updated while reproducing this bug.
Christian, you know the deal: We need the full y2logs tarball produced by the "save_y2logs" script, not some randomly selected single file. It's in the FAQ since 20+ years.
Created attachment 868898 [details] full y2logs As you wish ;-) - here are the full logs. In case you wonder - I have AppArmor 4.0 alpha2 installed. The json format didn't change since 3.1.x *), therefore this shouldn't be relevant for this bug. Nevertheless, if you want me to double-check, i can temporarily downgrade to the official Tumbleweed packages. *) The question I asked in yast-devel a few weeks ago only affects cases where aa-logprof crashes on startup, which is not the case here.
(hopefully) fixed in yast2-apparmor 4.6.2