"Unexpected critical error occurred" on startup

Bugs and issues Linux
#1

I’m running opensuse 13.2 64-bit on two computers. Gnome is the main desktop on each. I can install insync 1.1 and 1.2 on one of the machines with no problems, but on the second computer I’ve never had luck getting it started. It installs fine using the rpm commands, but when I try insync start, I always receive the message “Unexpected critical error occurred. Will quit now” and that’s it.

Thoughts on what I should do to get this working? I’m not seeing any logs in /usr/lib/insync nor in /var/log, so I’m not sure where to begin. I’d just like insync to work on this machine like the other.

#2

@dmoss Please send us your crash logs and send it to support@insynchq.com with the link of this post. Thank you. :smile:

Please try running Insync through gdb to capture the backtrace when it crashes.

  • open a terminal
  • cd /usr/lib/insync
  • gdb --args ./insync start --no-daemon
#3

Please also send your logs. They are the files logs.db and out.txt located at ~/.config/Insync. You can compress them before sending to save space. Thanks.

#4

I have same problem… insync installed flawlessly on a laptop with ubuntu 14.04 but on a desktop with ubuntu 12.04 install fails. The destop used to run the free insync beta, but this has been removed.

Software center thought insync had been installed, got a window asking to start insync, then got a window with the “unexpected critcal error…” message.

Insync start did not get far enough to create ~.config. so no logs to report.

gdb not much help either:
willsd@willsd-OptiPlex-760:~$ cd /usr/lib/insync
willsd@willsd-OptiPlex-760:/usr/lib/insync$ gdb --args ./insync start --no-daemon
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Copyright © 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type “show copying”
and “show warranty” for details.
This GDB was configured as “i686-linux-gnu”.
For bug reporting instructions, please see:
http://bugs.launchpad.net/gdb-linaro/…
Reading symbols from /usr/lib/insync/insync…(no debugging symbols found)…done.
(gdb)
(gdb) quit

Suggestions?

#5

The same problem on MacOs Yosemite. Even on two different computers.

#6

@Steve_W

What is the output of insync start --no-daemon? Also please send your logs to support@insynchq.com for investigation. Refer here on how to find your logs.

#7

avid@linux-3gpt:~> insync start --no-daemon
CRITICAL:root:while creating Client object
Traceback (most recent call last):
File “ideskmain/client.py”, line 796, in client_gevent_runner
File “ideskutils/gevent_itc.py”, line 120, in wrapper
File “ideskutils/gevent_itc.py”, line 29, in wrapper
File “ideskmain/client.py”, line 82, in init
File “ideskmain/client.py”, line 519, in __load_config
File “ideskmain/clientconfig.py”, line 9, in init
File “ideskmain/clientconfig.py”, line 82, in _install_db
File “ideskdb/clientdb.py”, line 624, in install
File “ideskdb/clientdb.py”, line 638, in __migrate
File “ideskmain/configdb.py”, line 62, in _from_5
File “ideskdb/clientdb.py”, line 226, in execute
OperationalError: duplicate column name: read_only

#8

Seeing that there was a new version of insync available, I made sure that /usr/lib/insync was deleted as was ~/.config/Insync then I reinstalled. The installation went smoothly.

Perhaps the problem was in the ~/.config/Insync directory… the Insync beta was installed on this machine originally and worked fine, but wasn’t able to work after that.

#9

For those who experience this on Yosemite. I’ve resolved it by

  1. Cleaning my mac from the old version of Insync I have been using before. It seems there were some related older files remaining even when you install new insync version on top. In order to clean you mac from the old Insync files I used this free tool - http://freemacsoft.net/appcleaner/. Removed insync.
  2. restarted
  3. Installed the latest version of Insync with Yosemite support.
  4. Started Insync.

Now it seems to be working.

#10

Here is what I get on the ubuntu 12.04 desktop that does not run insync correctly (the critical error window still appears then vanishes in a few seconds):

willsd@willsd-OptiPlex-760:~$ insync start --no-daemon
CRITICAL:root:while creating Client object
Traceback (most recent call last):
File “ideskmain/client.py”, line 807, in client_gevent_runner
File “ideskutils/gevent_itc.py”, line 120, in wrapper
File “ideskutils/gevent_itc.py”, line 29, in wrapper
File “ideskmain/client.py”, line 83, in init
File “ideskmain/client.py”, line 527, in __load_config
File “ideskmain/clientconfig.py”, line 9, in init
File “ideskmain/clientconfig.py”, line 82, in _install_db
File “ideskdb/clientdb.py”, line 624, in install
File “ideskdb/clientdb.py”, line 638, in __migrate
File “ideskmain/configdb.py”, line 62, in _from_5
File “ideskdb/clientdb.py”, line 226, in execute
OperationalError: duplicate column name: read_only
willsd@willsd-OptiPlex-760:~$

#11

@dmoss Yes, there is an issue currently with upgrading from a beta version. We haven’t determined the cause yet though.

@Steve_W Have you tried deleting the ~/.config/Insync/dbs folder?

2 Likes
#12

Thanks, deleting Insync folder, worked to me (in my case it wasnt a problem).
I am using ElementaryOS freya (Ubuntu 14.04).

#13

This tip worked for me. Linux Mint 18 - 64 bit. Thanks!