mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #561] Core dump on RedHat 8 #439
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#439
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @timeweaver on GitHub (Feb 12, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/561
Operating Systems
Server: RedHat 8.1
Client: none
Barrier Version
2.3.2-13
Steps to reproduce bug
I installed barrier via snap on my RHEL 8.1 workstation, and it fails to start.
Other info
Errors from Messages file:
Feb 12 12:46:56 ironman barrier_barrier.desktop[12199]: This application failed to start because it could not find or load the Qt platform plugin "wayland-egl"
Feb 12 12:46:56 ironman barrier_barrier.desktop[12199]: in "".
Feb 12 12:46:56 ironman barrier_barrier.desktop[12199]: Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Feb 12 12:46:56 ironman barrier_barrier.desktop[12199]: Reinstalling the application may fix this problem.
Feb 12 12:46:57 ironman systemd-coredump[12410]: Process 12199 (barrier) of user 31071 dumped core.#012#012Stack trace of thread 12199:#012#0 0x00007f1fd348ee97 n/a (/lib/x86_64-linux-gnu/libc-2.27.so)#012#1 0x0000000000000002 n/a (n/a)
I blindly installed egl-wayland.x86_64, but it didn't change anything.
@timeweaver commented on GitHub (Feb 18, 2020):
I realize this is probably not a bug, I just need some help figuring out what I need to do. Is there somewhere else I should be asking for advice?
@shymega commented on GitHub (Feb 22, 2020):
This seems to be an issue with the snap itself. I'm trying to reproduce locally, and test my fix. You shouldn't need to install anything on the host system. Could you try the Flatpak?
Thanks.
@shymega commented on GitHub (Feb 25, 2020):
My fix isn't strictly necessary, as PR #553 actually looks to have fixed the issue.
We need to make a new release to test if this PR fixes your issue.
CC: @AdrianKoshka
@timeweaver commented on GitHub (Feb 25, 2020):
Thanks for your help. I installed via Flatpak and it works now.
@shymega commented on GitHub (Feb 25, 2020):
Alright, glad to hear it. Once we make a new release with PR #553 included, the Snap should then be fixed.
Thanks for bringing this to our attention.