Skip to content
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

Open
bradydean opened this issue Feb 13, 2023 · 7 comments
Open

pidof xfce4-panel killed by SIGABRT, gsettings killed by SIGABRT #375

bradydean opened this issue Feb 13, 2023 · 7 comments

Comments

@bradydean
Copy link

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

image

image

@bradydean bradydean changed the title pidof xfce4-panel killed by SIGABRT, gsettings killed by SIGABRT pidof xfce4-panel killed by SIGABRT, gsettings killed by SIGABRT Feb 13, 2023
@violetmage
Copy link

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?

@bradydean
Copy link
Author

bradydean commented Mar 2, 2023

Zoom seems to work fine. I am using Gnome on X11 actually.

@violetmage
Copy link

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.

@bradydean
Copy link
Author

bradydean commented Mar 2, 2023

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.

@violetmage
Copy link

If you want to keep troubleshooting, you can try running zoom like this:
flatpak run --verbose us.zoom.Zoom
Then try reproducing these error messages, to see if anything shows up on stdout / stderr

Otherwise, please consider closing this ticket.

@bradydean
Copy link
Author

I was able to trigger an error alert on pidof ksmserver killed by SIGABRT, but the logs don't look very helpful.

[brady@fedora ~]$ flatpak run --verbose us.zoom.Zoom
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/brady/.local/share/flatpak
F: Opening user flatpak installation at path /home/brady/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/brady/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: /var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/22.08/ac701b1959eae06fc84971174230f7fc7e825a7489c1751058c81a2ab92092b0/files/lib32 does not exist
F: Cleaning up unused container id 342056518
F: Cleaning up per-app-ID state for us.zoom.Zoom
F: Cleaning up unused container id 2265080390
F: Cleaning up per-app-ID state for us.zoom.Zoom
F: Allocated instance id 512027479
F: Add defaults in dir /us/zoom/Zoom/
F: Add locks in dir /us/zoom/Zoom/
F: Allowing wayland access
F: Allowing x11 access
F: Allowing pulseaudio access
F: Pulseaudio user configuration file '/home/brady/.config/pulse/client.conf': Error opening file /home/brady/.config/pulse/client.conf: No such file or directory
F: Running 'bwrap --args 42 xdg-dbus-proxy --args=44'
F: Running 'bwrap --args 42 zoom'

@violetmage
Copy link

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants