-
Notifications
You must be signed in to change notification settings - Fork 37
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
Slack crashes in fedora 38 #194
Comments
I had the same issue and I resolved it by resetting the application's permissions, using Flatseal. Maybe this will help you as well. |
Thanks a lot, @adandreou. Resetting permissions seems to solve the issue for me. |
Many thanks, Andreas! Worked for me too |
I have a related issue on fedora 37, where it only crashes if using the video features |
Yeah, I have the same issue when screen sharing. I tested it using the instructions here |
well it even crashes during the test, but not at the camera, that part works fine, only when it comes to screen sharing the complete app crashes, as reported here (backtrace attached): |
Seems to me that enabling "Run in Background" in GNOME's app settings is the key for Slack to run. I'm not sure why this is required, as Slack runs fine without it enabled in Fedora 37. Maybe it's related to flatpak/xdg-desktop-portal#899? |
This worked for me. Thank you! |
I've reset permissions using Flatseal and have made sure Slack can run in the background in system settings. I am still getting a crash when trying to share my screen in a huddle. |
Same here, when pushing the share button, the application crashes, also during the integrated test at the screen sharing stage. Don't know if this changes anything but I have laptop connected to 2 additional screens through DisplayLink dock. Everything worked fine on Fedora 37. |
Related to #101 |
After updating to fedora 38, Slack application installed via flathub has started to crash. I'm currently on version 4.31.155. Steps to reproduce:
rm --rf /home/$USER/.var/app/com.slack.Slack
All files fetched and put in cache 867.9000000059605ms
The text was updated successfully, but these errors were encountered: