-
Notifications
You must be signed in to change notification settings - Fork 49
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
pidof xfce4-panel
killed by SIGABRT, gsettings
killed by SIGABRT
#375
Comments
pidof xfce4-panel
killed by SIGABRT, gsettings killed by SIGABRTpidof xfce4-panel
killed by SIGABRT, gsettings
killed by SIGABRT
Does zoom crash, or otherwise malfunction when you see these errors? If not, does zoom continue working anyway? Judging by these error messages, I am assuming you are using xfce for your desktop environment, and therefore X11 as your display server. Is this correct? |
Zoom seems to work fine. I am using Gnome on X11 actually. |
If you don't see any error messages in zoom or in zoom's logs, then I think that these messages are part of a different / bigger problem. |
Yeah, they are quite strange. I have another machine also with Gnome on X11 and this doesn't happen. Both machines were reformatted recently so I'm not really sure what difference between them could cause this. |
If you want to keep troubleshooting, you can try running zoom like this: Otherwise, please consider closing this ticket. |
I was able to trigger an error alert on
|
As far as I can tell, these seem like seperate issues, unless you can clearly correlate zoom doing something to these error messages appearing. Either way, they don't seem like flatpak problems, so if you can show that zoom is causing these issues, then the issue report should be filed directly with upstream (zoom.us). |
I'm getting some weird error reports in Fedora. (sorry for screenshots, this app doesn't let me copy the text...). I'm guessing this is due to flatpak permissions not allowing access to these executables?
Using version 5.13.7.683
The text was updated successfully, but these errors were encountered: