github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #362] Segmentation Fault on Linux server #286

New issue

Open

opened 2026-05-05 05:57:22 -06:00 by gitea-mirror · 10 comments

gitea-mirror commented

2026-05-05 05:57:22 -06:00

Owner

Originally created by @jasuka on GitHub (Jul 11, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/362

Operating Systems

Server: Arch Linux / SDDM / Plasma Desktop 5.16.2

Client: Windows 10

2.3.0

Steps to reproduce bug

Compiled the latest version 2.3.0
When starting the server, it causes segmentation fault

Other info

Does this bug prevent you from using Barrier entirely? Yes

barrier.log

[157509.250357] barriers[15154]: segfault at e861 ip 000000000000e861 sp 00007ffc63f4cf68 error 14 in barriers[5558f6191000+18000]
[157509.250362] Code: Bad RIP value.
[157509.250377] audit: type=1701 audit(1562863395.123:1413): auid=1000 uid=1000 gid=100 ses=2 pid=15154 comm="barriers" exe="/usr/bin/barriers" sig=11 res=1

Originally created by @jasuka on GitHub (Jul 11, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/362 ### Operating Systems ### Server: Arch Linux / SDDM / Plasma Desktop 5.16.2 Client: Windows 10 2.3.0 ### Steps to reproduce bug ### 1. Compiled the latest version 2.3.0 2. When starting the server, it causes segmentation fault ### Other info ### * Does this bug prevent you from using Barrier entirely? Yes [barrier.log](https://github.com/debauchee/barrier/files/3383105/barrier.log) [157509.250357] barriers[15154]: segfault at e861 ip 000000000000e861 sp 00007ffc63f4cf68 error 14 in barriers[5558f6191000+18000] [157509.250362] Code: Bad RIP value. [157509.250377] audit: type=1701 audit(1562863395.123:1413): auid=1000 uid=1000 gid=100 ses=2 pid=15154 comm="barriers" exe="/usr/bin/barriers" sig=11 res=1

gitea-mirror added the

bug

linux

labels 2026-05-05 05:57:22 -06:00

gitea-mirror commented

2026-05-05 05:57:25 -06:00

Author

Owner

@shymega commented on GitHub (Aug 11, 2019):

Can you try installing Barrier from the binary releases? I'd like to see if that makes a difference.

Also, can you try pasting into a Gist the output file from the following command (You'll need strace installed; this is available in Arch's repos): strace path/to/barriers > barriers_strace.txt.

Thanks!

@shymega commented on GitHub (Aug 11, 2019): Can you try installing Barrier from the binary releases? I'd like to see if that makes a difference. Also, can you try pasting into a Gist the output file from the following command (You'll need `strace` installed; this is available in Arch's repos): `strace path/to/barriers > barriers_strace.txt`. Thanks!

gitea-mirror commented

2026-05-05 05:57:28 -06:00

Author

Owner

@paul-theorem commented on GitHub (Jul 27, 2020):

I'm interested in a solution here. I'm using xubuntu 20.04, and i've used snap to install latest stable(2.3.2-13), and edge (2.3.3-2) - both same failure - "segfault at 1a1" ... "Code: Bad RIP value."

I'm happy to install an earlier version. I have had great luck using barrier on xubuntu 18.04, and Mac OS. I've actually become dependent on it. I've been waiting for a fix - but at this point i think i may need to back my desktop off to 18.04 just to get barrier back.

Any workaround is appreciated.

@paul-theorem commented on GitHub (Jul 27, 2020): I'm interested in a solution here. I'm using xubuntu 20.04, and i've used snap to install latest stable(2.3.2-13), and edge (2.3.3-2) - both same failure - "segfault at 1a1" ... "Code: Bad RIP value." I'm happy to install an earlier version. I have had great luck using barrier on xubuntu 18.04, and Mac OS. I've actually become dependent on it. I've been waiting for a fix - but at this point i think i may need to back my desktop off to 18.04 just to get barrier back. Any workaround is appreciated.

gitea-mirror commented

2026-05-05 05:57:31 -06:00

Author

Owner

@shymega commented on GitHub (Jul 28, 2020):

I'm interested in a solution here. I'm using xubuntu 20.04, and i've used snap to install latest stable(2.3.2-13), and edge (2.3.3-2) - both same failure - "segfault at 1a1" ... "Code: Bad RIP value."

I'm happy to install an earlier version. I have had great luck using barrier on xubuntu 18.04, and Mac OS. I've actually become dependent on it. I've been waiting for a fix - but at this point i think i may need to back my desktop off to 18.04 just to get barrier back.

Any workaround is appreciated.

Could you do what I said in my previous comment, and grab a strace from Barrier, into a pastebin? Cheers.

@shymega commented on GitHub (Jul 28, 2020): > I'm interested in a solution here. I'm using xubuntu 20.04, and i've used snap to install latest stable(2.3.2-13), and edge (2.3.3-2) - both same failure - "segfault at 1a1" ... "Code: Bad RIP value." > > I'm happy to install an earlier version. I have had great luck using barrier on xubuntu 18.04, and Mac OS. I've actually become dependent on it. I've been waiting for a fix - but at this point i think i may need to back my desktop off to 18.04 just to get barrier back. > > Any workaround is appreciated. Could you do what I said in my previous comment, and grab a strace from Barrier, into a pastebin? Cheers.

gitea-mirror commented

2026-05-05 05:57:33 -06:00

Author

Owner

@paul-theorem commented on GitHub (Jul 28, 2020):

Yea, i can do that - sadly not until the weekend. I operate out of 2 locations - and the 20.04 server failing is at my other location. That said, i'm very motivated, and happy to run the strace - i'll post here on the weekend.

@paul-theorem commented on GitHub (Jul 28, 2020): Yea, i can do that - sadly not until the weekend. I operate out of 2 locations - and the 20.04 server failing is at my other location. That said, i'm very motivated, and happy to run the strace - i'll post here on the weekend.

gitea-mirror commented

2026-05-05 05:57:36 -06:00

Author

Owner

@paul-theorem commented on GitHub (Aug 2, 2020):

I had to fiddle a bit to save the server config file (Barrier->save configuration) to get barriers to generate the error. But It did finally work. This is the command, and its ultimate output. The log file is attached:

$ strace /snap/barrier/83/usr/bin/barriers -f --no-tray --debug DEBUG --name outpost --enable-crypto --address :24800 -c /home/bemo/barrier.sgc &>/tmp/barriers-strace-badrip.log
Segmentation fault (core dumped)

This is the version currently running (I've tried stable and bleeding edge, same result):

$ /snap/barrier/83/usr/bin/barriers --version
barriers 2.3.2-snapshot
Protocol version 1.6
Copyright (C) 2018 Debauchee Open Source Group
Copyright (C) 2012-2016 Symless Ltd.
Copyright (C) 2008-2014 Nick Bolton
Copyright (C) 2002-2014 Chris Schoeneman

Let me know if there is anything else I can give you in terms of debug information.

barriers-strace-badrip.log

@paul-theorem commented on GitHub (Aug 2, 2020): I had to fiddle a bit to save the server config file (Barrier->save configuration) to get barriers to generate the error. But It did finally work. This is the command, and its ultimate output. The log file is attached: ``` $ strace /snap/barrier/83/usr/bin/barriers -f --no-tray --debug DEBUG --name outpost --enable-crypto --address :24800 -c /home/bemo/barrier.sgc &>/tmp/barriers-strace-badrip.log Segmentation fault (core dumped) ``` This is the version currently running (I've tried stable and bleeding edge, same result): ``` $ /snap/barrier/83/usr/bin/barriers --version barriers 2.3.2-snapshot Protocol version 1.6 Copyright (C) 2018 Debauchee Open Source Group Copyright (C) 2012-2016 Symless Ltd. Copyright (C) 2008-2014 Nick Bolton Copyright (C) 2002-2014 Chris Schoeneman ``` Let me know if there is anything else I can give you in terms of debug information. [barriers-strace-badrip.log](https://github.com/debauchee/barrier/files/5012257/barriers-strace-badrip.log)

gitea-mirror commented

2026-05-05 05:57:39 -06:00

Author

Owner

@hjcho616 commented on GitHub (Aug 7, 2020):

Not sure if it is the same issue, but I spent some time with gdb and the source code shared here and found that mine was failing due to ipv6 not being enabled in my system. It appears the connectivity between the machines are done through ipv6 only and the exception thrown is EAFNOSUPPORT, 97. The catched exception just deletes the socket, which wasn't created, causing segfault.

At some point of my linux usage ipv6 was recommended to be turned off from using some program... so it was in grub /etc/default/grub. Removing ipv6.disable=1 and update-grub and reboot it is now operational.

@hjcho616 commented on GitHub (Aug 7, 2020): Not sure if it is the same issue, but I spent some time with gdb and the source code shared here and found that mine was failing due to ipv6 not being enabled in my system. It appears the connectivity between the machines are done through ipv6 only and the exception thrown is EAFNOSUPPORT, 97. The catched exception just deletes the socket, which wasn't created, causing segfault. At some point of my linux usage ipv6 was recommended to be turned off from using some program... so it was in grub /etc/default/grub. Removing ipv6.disable=1 and update-grub and reboot it is now operational.

gitea-mirror commented

2026-05-05 05:57:40 -06:00

Author

Owner

@paul-theorem commented on GitHub (Sep 1, 2020):

Not sure if it is the same issue, but I spent some time with gdb and the source code shared here and found that mine was failing due to ipv6 not being enabled in my system. It appears the connectivity between the machines are done through ipv6 only and the exception thrown is EAFNOSUPPORT, 97. The catched exception just deletes the socket, which wasn't created, causing segfault.

At some point of my linux usage ipv6 was recommended to be turned off from using some program... so it was in grub /etc/default/grub. Removing ipv6.disable=1 and update-grub and reboot it is now operational.

This is interesting. There are many reasons to disable ipv6 for other reasons. Seems kinda strange for barrier to force ipv6. @shymega - any input here or further debugging from the above log or comment?

@paul-theorem commented on GitHub (Sep 1, 2020): > Not sure if it is the same issue, but I spent some time with gdb and the source code shared here and found that mine was failing due to ipv6 not being enabled in my system. It appears the connectivity between the machines are done through ipv6 only and the exception thrown is EAFNOSUPPORT, 97. The catched exception just deletes the socket, which wasn't created, causing segfault. > > At some point of my linux usage ipv6 was recommended to be turned off from using some program... so it was in grub /etc/default/grub. Removing ipv6.disable=1 and update-grub and reboot it is now operational. This is interesting. There are many reasons to disable ipv6 for other reasons. Seems kinda strange for barrier to _force_ ipv6. @shymega - any input here or further debugging from the above log or comment?

gitea-mirror commented

2026-05-05 05:57:42 -06:00

Author

Owner

@paul-theorem commented on GitHub (Sep 29, 2020):

I can confirm that ubuntu 20.04 only works (non segfault) when ipv6 is NOT disabled via grub as @hjcho616 notes.

@paul-theorem commented on GitHub (Sep 29, 2020): I can confirm that ubuntu 20.04 only works (non segfault) when ipv6 is NOT disabled via grub as @hjcho616 notes.

gitea-mirror commented

2026-05-05 05:57:44 -06:00

Author

Owner

@alexpdp7 commented on GitHub (Nov 26, 2020):

In case it helps anyone, running barriers (or barrierc) instead of using the barrier GUI wrapper doesn't seem to present the same issue, but that's a bit inconvenient.

@alexpdp7 commented on GitHub (Nov 26, 2020): In case it helps anyone, running `barriers` (or `barrierc`) instead of using the `barrier` GUI wrapper doesn't seem to present the same issue, but that's a bit inconvenient.

gitea-mirror commented

2026-05-05 05:57:48 -06:00

Author

Owner

@zonywhoop commented on GitHub (Dec 31, 2021):

Running into this same issue on Manjaro 21.2.0 using barrier from Snap. IPv6 in my instance is not fully disabled, but I also have several interfaces that do not have IPv6 and am using kvm and docker so bridge interfaces are also in play.

@zonywhoop commented on GitHub (Dec 31, 2021): Running into this same issue on Manjaro 21.2.0 using barrier from Snap. IPv6 in my instance is not fully disabled, but I also have several interfaces that do not have IPv6 and am using kvm and docker so bridge interfaces are also in play.

gitea-mirror referenced this issue

2026-05-05 07:57:08 -06:00

[PR #287] [MERGED] Windows installer fix #1593