You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The syslog contains a hint about this being related to apparmor:
Jun 05 15:05:22 parahippus kernel: audit: type=1400 audit(1717592722.495:328): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=1039661 comm="jitsi-meet" requested="userns_create" target="unprivileged_userns"
Jun 05 15:05:22 parahippus kernel: audit: type=1400 audit(1717592722.496:329): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=1039663 comm="jitsi-meet" capability=21 capname="sys_admin"
Jun 05 15:05:22 parahippus kernel: traps: jitsi-meet[1039661] trap int3 ip:56bf74d5c04a sp:7fffd038f590 error:0 in jitsi-meet[56bf710c4000+837d000]
Jun 05 15:05:22 parahippus systemd[1]: Started [email protected] - Process Core Dump (PID 1039666/UID 0).
Jun 05 15:05:22 parahippus systemd[1]: [email protected]: Deactivated successfully.
Jun 05 15:05:22 parahippus systemd[1]: [email protected]: Triggering OnSuccess= dependencies.
Jun 05 15:05:22 parahippus systemd[1]: Starting [email protected]...
Jun 05 15:05:25 parahippus systemd[1]: [email protected]: Deactivated successfully.
Jun 05 15:05:25 parahippus systemd[1]: Finished [email protected].
Jun 05 15:05:25 parahippus systemd[1]: [email protected]: Consumed 2.117s CPU time.
For some reason, the DENIED message only shows up the first time on a given boot, but otherwise, the behavior is the same.
Expected Behavior
It should just start up.
Possible Solution
Adding a standard chromium boilerplate apparmor profile to /etc/apparmor.d/jitsi-meet, such as the following one, and loading it into the kernel (for example with systemctl reload apparmor) makes jitsi-meet start up fine:
abi <abi/4.0>,
include <tunables/global>
profile jitsi-meet /opt/Jitsi\ Meet/jitsi-meet flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists <local/jitsi-meet>
}
Steps to reproduce
Install the 2024.5.0 version of jitsi-meet-amd64.deb on Ubuntu 24.04 with its default AppArmor configuration.
The text was updated successfully, but these errors were encountered:
Thank you for highlighting this. For reference, this is tracked upstream in electron as electron/electron#41066
csett86
changed the title
AppArmor profile required to start up on Ubuntu 24.04
Ubuntu 24.04: Crashing on Launch, AppArmor profile required to fix
Aug 5, 2024
csett86
changed the title
Ubuntu 24.04: Crashing on Launch, AppArmor profile required to fix
Ubuntu 24.04: Crashing on Launch, AppArmor profile or --no-sandbox required to fix
Aug 11, 2024
Description
An AppArmor profile is required for chromium (and therefore electron) based applications to start up on Ubuntu 24.04 in its default configuration.
Current behavior
Without the presence of an apparmor profile, jitsi-meet crashes on startup with the following output:
Unsurprisingly, the core dump doesn't give much useful information at all:
The syslog contains a hint about this being related to apparmor:
For some reason, the
DENIED
message only shows up the first time on a given boot, but otherwise, the behavior is the same.Expected Behavior
It should just start up.
Possible Solution
Adding a standard chromium boilerplate apparmor profile to
/etc/apparmor.d/jitsi-meet
, such as the following one, and loading it into the kernel (for example withsystemctl reload apparmor
) makes jitsi-meet start up fine:Steps to reproduce
Install the 2024.5.0 version of jitsi-meet-amd64.deb on Ubuntu 24.04 with its default AppArmor configuration.
The text was updated successfully, but these errors were encountered: