-
Notifications
You must be signed in to change notification settings - Fork 814
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
[Crash]: Ubuntu 24.04 LTS - Core dump exit-code 133 #3050
Comments
@floviolleau Is this consistently reproducible? Are you running as |
Hi, I reproduce it all the time. No root usage I don't have account on mattermost community so I cannot download. I think it is an issue with electron |
Hi, I found the workaround. The issue is for ALL Electron apps. As a workaround for now, we must do Here for more information: |
Good find! Closing this issue for now, will re-open if there's anything needed from our end. |
Hi, Sorry to add a new comment but you need to reopen the issue. As mentioned in the issue linked with electron repository, this issue is caused by apparmor's default policy, which lacks a specific profile in the /etc/apparmor.d/ directory. Mattermost installation need to add a profile in /etc/apparmor.d/ directory. Here is an exemple from Matrix Element app:
|
Thanks for the insight, created a ticket here: https://mattermost.atlassian.net/browse/MM-59486 |
Going to open this as HW as we probably won't get to work on this internally anytime soon. If anyone is open to making changes to get this working (perhaps writing a script to drop the profile where it needs to be) I can help guide/merge the changes :) |
Before you file a crash report
Mattermost Desktop Version
5.8.0
Operating System
Ubuntu Linux 24.04 LTS x64
Mattermost Server Version
9.7.2
What type of crash did you experience?
System crash (The application quit unexpectedly with no warning, or the operating system reported a crash)
Crash report details
Core dump at startup. Same issue with tar.gz installation and from depots I deleted ~/.config/Mattermost folder before trying
Log Output
Additional Information
No response
The text was updated successfully, but these errors were encountered: