apparmor-pipewire automated

medium

Image Types:
basesdk-amd64 / hmi-armhf / hmi-amd64 / sdk-amd64
Image Deployment:
APT, OSTree
Type:
functional

Description

Test that AppArmor profiles provided in PipeWire work without apparmor complaining.

Pre Conditions

  1. Clone the tests repository from another computer (Note that the branch being tested may change depending on the release, please make sure to clone the correct branch for the release in question):
    2. $ git clone --branch apertis/v2024dev2 https://gitlab.apertis.org/tests/apparmor-pipewire.git
  2. Copy the test directory apparmor-pipewire to the target device:
    3. $ DUT_IP=<device-ip>
    $ scp -r apparmor-pipewire user@$DUT_IP:
  3. Log into the target device:
    4. $ ssh user@$DUT_IP

Execution Steps

  1. Enter test directory:
    2. $ cd apparmor-pipewire
  2. Execute the following command:
    3. $ common/run-test-in-systemd --name=apparmor-pipewire --timeout 120 ./run-test.sh

Expected

Test should report pass and not fail:

pipewire.normal.expected: pass

Notes

  • The results of the test printed to the standard output are enough to determine whether it passed or fail.
  • If you get a failure and need to report a bug please check journalctl, run the test case again, and add the logs you get to the bug report.
  • If no Bluetooth dongle is attached to the board, the following message is expected:

    • #---8<--- raw apparmor output from journal

    # USER_AVC pid=416 uid=104 auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=690 label="/usr/bin/wireplumber"

    #  exe="/usr/bin/dbus-daemon" sauid=104 hostname=? addr=? terminal=?'

    #--->8---