Workaround for Insync not starting (segmentation fault) after Fedora 34 libxkbcommon update

Bugs and issues Linux
1

After libxkbcommon update in fedora 34, insync no longer starts

Error:
insync[16536]: segfault at cb32038 ip 00007f5c134c201d sp 00007ffc11a6a260 error 4 in libxkbcommon-x11.so.0.0.0[7f5c134c1000+4000]

This is the update that caused the issue:

https://bodhi.fedoraproject.org/updates/FEDORA-2021-83c8732861

It is currently in updates-testing repos, should be in stable soon.

I use Fedora 34 KDE.

WORKAROUND:

cd /usr/lib/insync

sudo mv libxkbcommon.so.0 libxkbcommon.so.0.bak

sudo ln -s /usr/lib64/libxkbcommon.so.0.0.0 ./libxkbcommon.so.0

then insync starts normally.

7 Likes
2

Same problem. Urgently waiting for a fix as I’d rather not make manual modifications to files that are managed by the OS’ package manager.

3

Hi @linuser :slight_smile: Thanks so much for sharing the workaround. I’ve raised this issue to our Linux team so we can work on deploying a fix.

4

Thanks for the workaround, @linuser.

The sooner this is fixed at Insync’s end, the better.

5

Thank you very much for sharing this. I spoke to support via chat, they do not know about it.

6

We really need Fedora 34 support fixed as soon as possible

7

Just to report same issue with OpenSuse Thumbleweed, Workaround fix the issue. Thanks @linuser

1 Like
8

Same here (Tumbleweed - fix).

9

Hi all-- our Linux team is working on the Fedora 34 build. I’ll update this thread as soon as the version is available.

Thank you!

1 Like
10

The same problem occurs on Manjaro 21.0.4, and yes - workaround fixed it.

1 Like
11

v3.3.10.40961 just came in through the InSync Fedora repo. Can confirm the issue is fixed.

I’m happy that the issue is now fixed, but I’m honestly a bit disappointed that the fix to an issue that broke the entire application took 2 weeks to be released. Not being able to use a file sync application for an entire 2 weeks (without making manual system modifications) is pretty bad.

I generally like the application and appreciate the work that is put into it, but I really hope issues like these can be prioritised more in future.

12

@RobinJ1995 If you did the workaround like a real linux user you wouldn’t of had to wait. :wink:

13

Hello everyone!! Please give this Fedora 34 build a try:
https://d2t3ff60b2tol4.cloudfront.net/builds/insync-3.3.10.40961-fc34.x86_64.rpm

Let me know how it goes by replying to this thread :slight_smile: Thank you!

14

@miamoran Confirmed fixed. Got the update from the repo yesterday.

Fedora 34 KDE

15

Unless you’re a Linux user with a full-time job that doesn’t have time to “fix” other developers’ applications, and to then possibly have to fix their own system later because they stupidly made manual modifications to libraries that were managed by the package manager :wink: When you pull tricks like these there’s always a good possibility that you end up causing problems down the line because your package manager realises the files it manages are not in the state it expects them to be in.

16

Works. Fedora 34 Gnome.

17

It’s a 3 line fix, so you are just lazy in my opinion. Dnf is smart enough to replace files.

18

I have installed insync-3.3.10.40961-fc34.x86_64 and can verify that it fixes the issue, and seems to work fine now on Fedora 34.

Thank you to the Insync team for fixing this!

1 Like
19

Im using Fedora 34. Download version 3.4 and still not working well. Thanks for the quick response and looking fordward to this issue to be corrected. :slight_smile:

20

@yerch82 Thank you for cross-posting! I have responded to the other thread :slight_smile: