Fedora 30 and Insync 1.5.7.37371

[Bobses]

Hello,

Today I have made the upgrade to Fedora 30.

First of all, after repo sync I receive the following message (I have configured the repo as is indicated on your website):

Ignoring repositories: insync

Second, the Insync app doesn’t start.

$ insync start --no-daemon
MESA-LOADER: failed to open swrast (search paths /usr/lib64/dri)
libGL error: failed to load driver: swrast
Segmentation fault (core dumped)

If I run insync start, this is the output from the /var/log/messages file:

Apr 30 21:07:49 bobsesland audit[3880]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=3880 comm=“insync” exe="/usr/lib/insync/insync" sig=11 res=1
Apr 30 21:07:49 bobsesland kernel: insync[3880]: segfault at 38 ip 00007f89f561f814 sp 00007fff81c11b90 error 4 in ld-2.29.so[7f89f5614000+20000]
Apr 30 21:07:49 bobsesland kernel: Code: 04 49 83 fc 06 44 0f 44 c8 81 e6 ff 7f 00 00 45 89 8f 08 04 00 00 48 8d 04 76 4d 89 b7 00 04 00 00 4c 8d 04 c7 4d 85 c0 74 0f <41> 8b 48 08 b8 00 00 00 00 85 c9 4c 0f 44 c0 41 8b 3e 6a 00 48 8d
Apr 30 21:07:49 bobsesland systemd[1]: Started Process Core Dump (PID 3891/UID 0).
Apr 30 21:07:49 bobsesland audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=systemd-coredump@4-3891-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
Apr 30 21:07:49 bobsesland systemd-coredump[3892]: Process 3880 (insync) of user 1000 dumped core.#012#012Stack trace of thread 3880:#012#0 0x00007f89f561f814 _dl_relocate_object (ld-linux-x86-64.so.2)#012#1 0x00007f89f5626e9d dl_open_worker (ld-linux-x86-64.so.2)#012#2 0x00007f89f4f9abd9 dl_catch_exception (libc.so.6)#012#3 0x00007f89f562684e dl_open (ld-linux-x86-64.so.2)#012#4 0x00007f89f55b639a dlopen_doit (libdl.so.2)#012#5 0x00007f89f4f9abd9 dl_catch_exception (libc.so.6)#012#6 0x00007f89f4f9ac73 dl_catch_error (libc.so.6)#012#7 0x00007f89f55b6b09 dlerror_run (libdl.so.2)#012#8 0x00007f89f55b643a dlopen@@GLIBC_2.2.5 (libdl.so.2)#012#9 0x00007f89e3ea475e py_dl_open (ctypes.so)#012#10 0x00007f89f51907c2 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#11 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#12 0x00007f89f50df8be function_call (libpython2.7.so.1.0)#012#13 0x00007f89f50ca743 PyObject_Call (libpython2.7.so.1.0)#012#14 0x00007f89f50d2f76 instancemethod_call (libpython2.7.so.1.0)#012#15 0x00007f89f50ca743 PyObject_Call (libpython2.7.so.1.0)#012#16 0x00007f89f5111f57 slot_tp_init (libpython2.7.so.1.0)#012#17 0x00007f89f510ef94 type_call (libpython2.7.so.1.0)#012#18 0x00007f89f50ca743 PyObject_Call (libpython2.7.so.1.0)#012#19 0x00007f89f518c422 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#20 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#21 0x00007f89f5191629 PyEval_EvalCode (libpython2.7.so.1.0)#012#22 0x00007f89f51951c8 PyImport_ExecCodeModuleEx (libpython2.7.so.1.0)#012#23 0x00007f89f51a7804 zipimporter_load_module (libpython2.7.so.1.0)#012#24 0x00007f89f50ca743 PyObject_Call (libpython2.7.so.1.0)#012#25 0x00007f89f50ca6bd call_function_tail (libpython2.7.so.1.0)#012#26 0x00007f89f515aa0c PyObject_CallMethod (libpython2.7.so.1.0)#012#27 0x00007f89f519460d import_submodule (libpython2.7.so.1.0)#012#28 0x00007f89f51398a2 PyImport_ImportModuleLevel (libpython2.7.so.1.0)#012#29 0x00007f89f5127b98 builtin___import (libpython2.7.so.1.0)#012#30 0x00007f89f50ca743 PyObject_Call (libpython2.7.so.1.0)#012#31 0x00007f89f5187a37 PyEval_CallObjectWithKeywords (libpython2.7.so.1.0)#012#32 0x00007f89f5189ead PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#33 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#34 0x00007f89f5191629 PyEval_EvalCode (libpython2.7.so.1.0)#012#35 0x00007f89f51951c8 PyImport_ExecCodeModuleEx (libpython2.7.so.1.0)#012#36 0x00007f89f50b05a8 load_compiled_module (libpython2.7.so.1.0)#012#37 0x00007f89f519460d import_submodule (libpython2.7.so.1.0)#012#38 0x00007f89f5139d7e PyImport_ImportModuleLevel (libpython2.7.so.1.0)#012#39 0x00007f89f5127b98 builtin___import (libpython2.7.so.1.0)#012#40 0x00007f89f50ca743 PyObject_Call (libpython2.7.so.1.0)#012#41 0x00007f89f5187a37 PyEval_CallObjectWithKeywords (libpython2.7.so.1.0)#012#42 0x00007f89f5189ead PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#43 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#44 0x00007f89f5191629 PyEval_EvalCode (libpython2.7.so.1.0)#012#45 0x00007f89f51951c8 PyImport_ExecCodeModuleEx (libpython2.7.so.1.0)#012#46 0x00007f89f50b05a8 load_compiled_module (libpython2.7.so.1.0)#012#47 0x00007f89f519460d import_submodule (libpython2.7.so.1.0)#012#48 0x00007f89f5139d7e PyImport_ImportModuleLevel (libpython2.7.so.1.0)#012#49 0x00007f89f5127b98 builtin___import (libpython2.7.so.1.0)#012#50 0x00007f89f50ca743 PyObject_Call (libpython2.7.so.1.0)#012#51 0x00007f89f5187a37 PyEval_CallObjectWithKeywords (libpython2.7.so.1.0)#012#52 0x00007f89f5189ead PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#53 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#54 0x00007f89f518e403 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#55 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#56 0x00007f89f518e403 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#57 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#58 0x00007f89f5191629 PyEval_EvalCode (libpython2.7.so.1.0)#012#59 0x00007f89f518dae7 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#60 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#61 0x00007f89f5191629 PyEval_EvalCode (libpython2.7.so.1.0)#012#62 0x00007f89f518dae7 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#63 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#012Stack trace of thread 3889:#012#0 0x00007f89f4f56b3b __select (libc.so.6)#012#1 0x00007f89e74c54c3 time_sleep (time.so)#012#2 0x00007f89f51907c2 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#3 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#4 0x00007f89f518e403 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#5 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#6 0x00007f89f518e403 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#7 0x00007f89f518ed89 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#8 0x00007f89f518ed89 PyEval_EvalFrameEx (libpython2.7.so.1.0)#012#9 0x00007f89f5191418 PyEval_EvalCodeEx (libpython2.7.so.1.0)#012#10 0x00007f89f50df8be function_call (libpython2.7.so.1.0)#012#11 0x00007f89f50ca743 PyObject_Call (libpython2.7.so.1.0)#012#12 0x00007f89f50d2f76 instancemethod_call (libpython2.7.so.1.0)#012#13 0x00007f89f50ca743 PyObject_Call (libpython2.7.so.1.0)#012#14 0x00007f89f5187a37 PyEval_CallObjectWithKeywords (libpython2.7.so.1.0)#012#15 0x00007f89f519e4e2 t_bootstrap (libpython2.7.so.1.0)#012#16 0x00007f89f55c35a2 start_thread (libpthread.so.0)#012#17 0x00007f89f4f5f023 __clone (libc.so.6)#012#012Stack trace of thread 3888:#012#0 0x00007f89f4f542b7 __poll (libc.so.6)#012#1 0x00007f89e375d38a n/a (libxcb.so.1)#012#2 0x00007f89e375effa xcb_wait_for_event (libxcb.so.1)#012#3 0x00007f89dbfb82a9 _ZN15QXcbEventReader3runEv (libQt5XcbQpa.so.5)#012#4 0x00007f89e1bfd554 n/a (libQt5Core.so.5)#012#5 0x00007f89f55c35a2 start_thread (libpthread.so.0)#012#6 0x00007f89f4f5f023 __clone (libc.so.6)
Apr 30 21:07:49 bobsesland audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=‘unit=systemd-coredump@4-3891-0 comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
Apr 30 21:07:49 bobsesland systemd[1]: systemd-coredump@4-3891-0.service: Succeeded.
Apr 30 21:07:50 bobsesland abrt-server[3902]: Package ‘insync’ isn’t signed with proper key
Apr 30 21:07:50 bobsesland abrt-server[3902]: ‘post-create’ on ‘/var/spool/abrt/ccpp-2019-04-30-21:07:50.21280-3880’ exited with 1
Apr 30 21:07:50 bobsesland abrt-server[3902]: Deleting problem directory ‘/var/spool/abrt/ccpp-2019-04-30-21:07:50.21280-3880’

I have no idea how to manage this situation, especially that the app worked well until the Fedora upgrade (Insync is the single app which doesn’t work after the upgrade).

Thanks.

[gbcox]

Same issue here after upgrade to Fedora 30.

[Mark_Glickman]

Same here - upgraded to Fedora 30 yesterday and can’t get insync to start. I sent a note to the support e-mail address in addition to posting in the forum.

[Mark_Glickman]

As a follow-up, I upgraded another computer to Fedora 30 from 29 and insync seems to work fine on that machine. So not sure what might have caused the problem on the one where insync fails to start.

[boxallw]

App runs for me. But I get an “ignoring repositories: insync” when updating.

[maxtorete]

Hi! Could you paste the output of this command please?

sudo dnf list extras

Maybe there is a needed package not installed in Fedora 30 by default.

[maxtorete]

I installed in a clean Fedora 30 installation and in a Fedora 29 upgraded to Fedora 30 machine, both are failing with MESA error.

[Mark_Glickman]

For the Fedora 30 machine where insync is working, or where it is not working? I assume the former, which I can do when I’m at work in a couple hours.

[maxtorete]

@Mark_Glickman in the working machine please. Maybe we could spot a dependency not satisfied in clean F30 installation, but you get it working with F29 packages.

[Mark_Glickman]

Yes - I’ll share the list of extra packages when I’m at that machine later this morning.

[Mark_Glickman]

Here’s the list of extra packages on my Fedora 30 machine that has insync working:

Ignoring repositories: Dropbox, insync
Extra Packages
beignet.x86_64                                  1.3.2-5.fc29                   @fedora      
brscan-skey.x86_64                              0.2.4-1                        @System      
brscan4.x86_64                                  0.4.4-3                        @System      
clutter-gst2.x86_64                             2.0.18-5.fc28                  @fedora      
empathy.x86_64                                  1:3.12.14-7.fc29               @fedora      
ghostscript-fonts.noarch                        5.50-37.fc27                   @fedora      
insync.x86_64                                   1.5.7.37371-fc26               @insync      
jags4.x86_64                                    4.3.0-67.1                     @System      
kernel.x86_64                                   5.0.7-200.fc29                 @updates     
kernel.x86_64                                   5.0.9-200.fc29                 @updates     
kernel-core.x86_64                              5.0.7-200.fc29                 @updates     
kernel-core.x86_64                              5.0.9-200.fc29                 @updates     
kernel-debug-core.x86_64                        5.0.7-200.fc29                 @updates     
kernel-debug-core.x86_64                        5.0.9-200.fc29                 @updates     
kernel-debug-modules.x86_64                     5.0.7-200.fc29                 @updates     
kernel-debug-modules.x86_64                     5.0.9-200.fc29                 @updates     
kernel-debug-modules-extra.x86_64               5.0.7-200.fc29                 @updates     
kernel-debug-modules-extra.x86_64               5.0.9-200.fc29                 @updates     
kernel-modules.x86_64                           5.0.7-200.fc29                 @updates     
kernel-modules.x86_64                           5.0.9-200.fc29                 @updates     
libXevie.x86_64                                 1.0.3-14.fc27                  @fedora      
libgltf.x86_64                                  0.1.0-10.fc29                  @fedora      
libsilc.x86_64                                  1.1.10-14.fc23                 @System      
mfcl6800dwcupswrapper.i386                      3.2.0-1                        @System      
mfcl6800dwlpr.i386                              3.2.0-1                        @System      
mozjs24.x86_64                                  24.2.0-11.fc26                 @@commandline
pam_pkcs11.x86_64                               0.6.8-8.fc24                   @@commandline
python2-pygpgme.x86_64                          0.3-26.fc28                    @fedora      
recordmydesktop.x86_64                          0.3.8.1-19.fc27                @fedora      
rodent-icon-theme.noarch                        5.0-8.fc24                     @@commandline
rstudio.x86_64                                  1.1.463-1                      @System      
tabish-eeyek-fonts.noarch                       1.0-13.fc29                    @fedora   

Comparing these to the packages that were extras on my non-working machine, the ones on the working machine are the following 4:

rscan4.x86_64 0.4.4-3 @System
brscan-skey.x86_64 0.2.4-1 @System
mfcl6800dwcupswrapper.i386 3.2.0-1 @System
mfcl6800dwlpr.i386 3.2.0-1 @System

[Ray_Foss]

top that off with the repo insync is still not recognizing the existence of Fedora 30… despite being in beta for over a month and having been released nearly a week ago.

Failed to synchronize cache for repo 'insync'

[Vitor_Pereira]

Hi everyone,

I think this is more likely due to an outdated/incompatible library from the insync installation itself than a missing dependency when upgrading from f29 to f30.

I got the same problem after an upgrade from fedora 29 to 30 on a machine that has a Radeon graphics card:

$ lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX 
[Radeon HD 8490 / R5 235X OEM]

When I try to run it with “–no-daemon” to get further info to the terminal output, I get:

$ insync start --no-daemon 
libGL error: MESA-LOADER: failed to open r600 (search paths /usr/lib64/dri)
libGL error: failed to load driver: r600
libGL error: MESA-LOADER: failed to open r600 (search paths /usr/lib64/dri)
libGL error: failed to load driver: r600
libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib64/dri)
libGL error: failed to load driver: swrast
/usr/bin/insync: line 3:  4429 Segmentation fault      (core dumped) LC_TIME=C LD_LIBRARY_PATH=/usr/lib/insync ./insync "$@"

However, it runs fine in “headless” mode (no graphic UI, no graphic functionality):

$ insync start --headless --no-daemon
Qt WebEngine seems to be initialized from a plugin. Please set Qt::AA_ShareOpenGLContexts using QCoreApplication::setAttribute before constructing QGuiApplication.
INFO 2019-05-06 11:10:46,638 [main__insync:main:105] insync version: 1.5.7.37371
INFO 2019-05-06 11:10:46,639 [main__insync:main:106] client created <ideskmain.client.Client object at 0x7f8917577650>
INFO 2019-05-06 11:10:46,640 [unix_socket_server_portable:start:49] unix socket server thread start
INFO 2019-05-06 11:10:46,640 [main__insync:main:114] starting client
INFO 2019-05-06 11:10:46,644 [fswatch:_start:532] LinuxFSWatcher._start
INFO 2019-05-06 11:10:46,645 [fswatch:_pull_loop:267] Inotify loop enter
INFO 2019-05-06 11:10:46,651 [gdsyncer:sync_account:153] Syncing GDUser(id=, email=, name=).
INFO 2019-05-06 11:10:46,769 [fswatch:watch:550] watch origin:
INFO 2019-05-06 11:10:46,827 [client:__on_gd_account_added:891] GDUser(id=, email=, name=) (existing) is now being synced.

… and it syncs in the background just fine.

So, at least in my case, it is clearly related to the graphics drivers (on another computer with an Intel graphics card I got no problem on the same upgrade from fedora 29 to 30).

I suspect this might have to do with an outdated or no longer compatible library among the ones that are shipped with the insync installation and support its GUI (It’s the kind of thing that is common when an app ships its own “shared” libraries which must still interact with other versions of those libraries in the system)

It would be nice to have some feedback from the developers on how to solve this or further debug it, pleas!

[Vitor_Pereira]

To add more evidence to my previous post, I can see there’s no problem with my graphics drivers, for example by doing

$ glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: AMD CAICOS (DRM 2.50.0 / 5.0.11-300.fc30.x86_64, LLVM 8.0.0)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.3
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 19.0.3
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 19.0.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

However, if I run this from the insync installation folder, I have precisely the same error message as in my previous post:

$ cd /usr/lib/insync/

$ glxinfo | grep OpenGL
libGL error: MESA-LOADER: failed to open r600 (search paths /usr/lib64/dri)
libGL error: failed to load driver: r600
libGL error: MESA-LOADER: failed to open r600 (search paths /usr/lib64/dri)
libGL error: failed to load driver: r600
libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib64/dri)
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  60
  Current serial number in output stream:  59

With this, it seems pretty clear that it is an issue arising from the libraries shipped with insync not playing well anymore with those of the system they have to run on.

[Sebita]

I upgraded to fc30 from fc28.

[Bobses]

Still doesn’t work for me. This becomes annoying.

[nikki]

Hi everyone,

I’m really sorry for being quiet the past couple of days.

I just wanted to let you know that we’re working on a build for you guys. I’ll post the link as soon as it’s available.

Really sorry for any hassle this has caused

[Sebita]

After days “on hold” for no reason, I wanted to say something like Vitor said. InSync works as headless, pointing the problem to a GUI issue with drivers (I use an AMD card).
Now that InSync developers replied, I’m eagerly waiting for the new version

[Bobses]

I found a workaround: I reinstalled the Nvidia driver and the Insync app seems to work, but the Insync repo is still ignored.

I’m waiting for the new version too.

[artu72]

I confirm these issues. Notabily, It seems that is a specific problem with F30 and AMD graphics hardware. I’m waiting for new version too.