-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Mattermost 5.2.1 crashes due to AppArmor denial #66
Comments
I experience the same issue, but on Ubuntu 20.04. Additionally my journal is flooded with:
|
It is not clear that is crash is due to the AppArmor denial - more likely I suspect some issue between mattermost and libayatana-indicator given the first line of the output above. |
Okay, this looks very related: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996 |
@kenvandine it sounds like @jugmac00 also suffered a crash while using the branch you published for the gnome-42-2204 snap :/ Update including the error that preceded the crash:
|
Since installing the latest candidate version on Wednesday, 2023-04-05, I do not experience crashes anymore.
@najamansari Could you also update and check whether this issue is fixed for you? |
I have just installed it on my machine, will update here after a day or two of usage. |
I have also been seeing this same issue On Ubuntu 22.04 using regolith-desktop DE. The version of mattermost-desktop that is installed that I noticed the crashes is 5.2.2 and I see dmesg with very similar logs:
I have just updated mattermost with
To version 5.3.1 and will update if I see any more crashes. |
I had mattermost-desktop crash on me again, but did not see the above segfault - instead I saw the following in
It is to be noted that
|
Coming back to this issue, |
Maybe close this issue since 5.4.0 is out now? |
What happened?
mattermost-desktop 5.2.1
randomly crashes.dmesg
output shows an AppArmor denial for the file/proc/${PID}/oom_score_adj
What should have happened?
Mattermost should not crash. It should also not attempt to adjust its own OOM score but that is probably a separate bug report.
Output of
snap info $snap_name
Output of
snap connections $snap_name
Output of
snap version
Relevant log output
Teminal output of app
No response
The text was updated successfully, but these errors were encountered: