GUI not launching/rendering on fresh fedora 29 installation


#1

Hi,

A fresh install on fedora linux 29 (version insync-1.5.7.37371-fc26.x86_64) fails to properly initialize the GUI. This is even before setting up any account or anything; really the very first (and all subsequent) attempts to run insync after the installation.

When running insync start, the main window of what should be the GUI begins to draw, but immediately begins a rapid flickering and only shows a white background during that. It’s impossible to interact with it.

If I run insync start --no-daemon I get this:

INFO     2019-04-03 12:09:07,147 [main__insync:main:105] insync version: 1.5.7.37371
INFO     2019-04-03 12:09:07,149 [main__insync:main:106] client created <ideskmain.client.Client object at 0x7f8
6c1ccd3d0>
INFO     2019-04-03 12:09:07,150 [unix_socket_server_portable:start:49] unix socket server thread start
INFO     2019-04-03 12:09:07,150 [main__insync:main:114] starting client
INFO     2019-04-03 12:09:07,156 [fswatch:_start:532] LinuxFSWatcher._start
INFO     2019-04-03 12:09:07,158 [fswatch:_pull_loop:267] Inotify loop enter
libpng warning: iCCP: known incorrect sRGB profile
[1:7:0403/120907.326081:ERROR:validation_errors.cc(87)] Invalid message: VALIDATION_ERROR_MESSAGE_HEADER_UNKNOWN_MET
HOD
[1:7:0403/120908.276250:ERROR:validation_errors.cc(87)] Invalid message: VALIDATION_ERROR_MESSAGE_HEADER_UNKNOWN_MET
HOD
[1:7:0403/120908.289694:ERROR:validation_errors.cc(87)] Invalid message: VALIDATION_ERROR_MESSAGE_HEADER_UNKNOWN_MET
HOD
[1:7:0403/120908.307447:ERROR:validation_errors.cc(87)] Invalid message: VALIDATION_ERROR_MESSAGE_HEADER_UNKNOWN_MET
HOD
[28110:28186:0403/120908.318946:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[28110:28186:0403/120908.333765:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[28110:28186:0403/120908.334097:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[28110:28186:0403/120908.334197:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[1:7:0403/120908.357468:ERROR:validation_errors.cc(87)] Invalid message: VALIDATION_ERROR_MESSAGE_HEADER_UNKNOWN_MET
HOD
[28110:28186:0403/120908.369087:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[28110:28186:0403/120908.370526:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[28110:28186:0403/120908.370660:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[28110:28186:0403/120908.370701:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[1:7:0403/120908.395946:ERROR:validation_errors.cc(87)] Invalid message: VALIDATION_ERROR_MESSAGE_HEADER_UNKNOWN_MET
HOD
[28110:28186:0403/120908.402998:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[28110:28186:0403/120908.417064:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[28110:28186:0403/120908.417119:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[28110:28186:0403/120908.417224:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service:
/usr/lib/insync/content_renderer.service
[1:7:0403/120908.446227:ERROR:validation_errors.cc(87)] Invalid message: VALIDATION_ERROR_MESSAGE_HEADER_UNKNOWN_MET
HOD

[ … endless repetition of the messages ERROR:service_manager_context.cc(252) and ERROR:validation_errors.cc(87) …]

^CINFO     2019-04-03 12:09:08,922 [platform_impl_portable:quit:164] calling quit in platform_impl
Exception in thread FM integrator:
Traceback (most recent call last):
 File “threading.py”, line 804, in __bootstrap_inner
 File “threading.py”, line 757, in run
 File “isyncd/linux/fm_integrator.py”, line 101, in install_fm_integration
 File “isyncd/linux/fm_integrator.py”, line 130, in integration_installable
 File “isyncd/linux/fm_integrator.py”, line 161, in get_default_fm
 File “isyncd/linux/fm_integrator.py”, line 185, in get_default_fm_kde
 File “subprocess.py”, line 223, in check_output
CalledProcessError: Command ‘/usr/bin/ktradertest  inode/directory  Application | grep DesktopEntryPath || :’ return
ed non-zero exit status -2

INFO     2019-04-03 12:09:08,934 [unix_socket_server_portable:stop:61] unix socket server thread stop
INFO     2019-04-03 12:09:08,936 [gdsyncer:stop:77] Stopping GD syncer…
INFO     2019-04-03 12:09:08,936 [fswatch:_stop:544] LinuxFSWatcher._stop
INFO     2019-04-03 12:09:08,937 [gdsyncer:stop:83] GD syncer stopped.
INFO     2019-04-03 12:09:08,984 [main__insync:on_exit:57] clean exit

This makes insync entirely unusable on my desktop since I know only how to setup accounts and syncing from the gui. Any clues or help debugging the underlying issue would be highly appreciated!


#2

Hi @Vitor_Pereira,

I’ve escalated this issue to our Linux team and will let you know once we’ve found something.

Thank you so much for the detailed report. <3


#3

Thanks, @najdc!

I’m looking forward for feedback on this over these days of the trial period since I would really like to be able to use insync across my linux devices.


#4

Hi @Vitor_Pereira,

In any case, I’ll be more than happy to extend your trial so you can test a little longer :heart: