Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insync don't open again after config and close #244813

Closed
ajmasia opened this issue Jul 22, 2023 · 10 comments · Fixed by #251565
Closed

Insync don't open again after config and close #244813

ajmasia opened this issue Jul 22, 2023 · 10 comments · Fixed by #251565

Comments

@ajmasia
Copy link

ajmasia commented Jul 22, 2023

Describe the bug

I have installed the latest unstable version of Insync. I start it, configure my account, and the following happens:

  • No systry icon appears
  • When I close the Insync window and try to start it again, it does nothing
  • If I execute any command from the console, I get this message: Insync doesn't seem to be running. Start it first.

IMPORTANT: It's seems sync continue working but I can't show the Insync window.

Steps To Reproduce

Steps to reproduce the behavior:

  1. Install package
  2. Start package from Rofi
  3. Config account and all works
  4. Close Insync window
  5. Impossible show the Insync window again to view files or change config

Expected behavior

I should be able to reopen the Insync window and also use the commands from the console.

Logs

~ ✦ ➜ insync start --no-daemon --debug 0
QSystemTrayIcon::setVisible: No Icon set
INFO     2023-07-22 13:10:39,126 [mainlogs:_log_run:138] Core(app_version=3.8.6.50504, platform=Linux-x86_64-nixos/23.05) initialized
WARNING  2023-07-22 13:10:41,143 [base_events:_run_once:1782] Executing <Task finished coro=<SettingsMain._load_settings() done, defined at ideskcore/mainsettings.py:186> exception=DBLockedError('The database file is currently locked (SettingsDBInstaller).') created at ideskcore/mainsettings.py:160> took 2.009 seconds
INFO     2023-07-22 13:10:41,145 [core:init:31] DB is locked!
ERROR    2023-07-22 13:10:41,145 [platui_impl:display_notification:82] Cannot initialize notifications.
ERROR    2023-07-22 13:10:44,146 [base_events:default_exception_handler:1619] Task exception was never retrieved after 3.0 seconds
future: <Task finished coro=<SyncMain._start_syncing() done, defined at ideskcore/mainsync.py:199> exception=DBLockedError('The database file is currently locked (SettingsDBInstaller).') created at ideskcore/mainsync.py:185>
source_traceback: Object created at (most recent call last):
  File "threading.py", line 890, in _bootstrap
  File "threading.py", line 926, in _bootstrap_inner
  File "threading.py", line 870, in run
  File "ideskasync/coreloop.py", line 273, in run_loop
  File "asyncio/base_events.py", line 541, in run_forever
  File "asyncio/base_events.py", line 1778, in _run_once
  File "asyncio/events.py", line 88, in _run
  File "ideskcore/core.py", line 27, in init
  File "ideskcore/insync_core.py", line 17, in __init__
  File "ideskcore/mainsync.py", line 185, in __init__
Traceback (most recent call last):
  File "ideskdb/clientdb.py", line 149, in __init__
  File "ideskdb/clientdb.py", line 249, in execute
sqlite3.OperationalError: database is locked

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "ideskcore/core.py", line 28, in init
  File "ideskcore/mainbase.py", line 14, in init
  File "ideskcore/insync_core.py", line 58, in _init
  File "ideskcore/mainsync.py", line 196, in _init
  File "ideskcore/mainhttp.py", line 110, in _init
  File "ideskcore/mainsettings.py", line 164, in _init
  File "ideskcore/mainsync.py", line 200, in _start_syncing
  File "ideskcore/mainsettings.py", line 204, in _load_settings
  File "ideskcore/mainsettings.py", line 25, in __init__
  File "ideskdb/clientdb.py", line 197, in __init__
ideskdb.clientdb.DBLockedError: The database file is currently locked (SettingsDBInstaller).
INFO     2023-07-22 13:10:45,148 [app:quit:80] quitting
INFO     2023-07-22 13:10:45,150 [app:stop:75] core stopped
INFO     2023-07-22 13:10:45,150 [app:stop:77] clean exit

Notify maintainers

@hellwolf

Metadata

  • system: "x86_64-linux"
  • host os: Linux 6.1.34, NixOS, 23.05 (Stoat), 23.05.20230616.c7ff1b9
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.13.3
  • nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos
@ajmasia ajmasia changed the title Insync don't start after config and close Insync don't open again after config and close Jul 22, 2023
@ajmasia
Copy link
Author

ajmasia commented Jul 22, 2023

I discover more things about this:

  • It's seems the service is running!
  • The systry icon is invisble and stay there. When I click on the invisble char the Insync open
  • Any terminal command over Insync works

image

@hellwolf
Copy link
Contributor

Thanks for the report @ajmasia , I will be taking a look.

@OliverSchr
Copy link

I have the same.
and i tried with x11 and wayland, with plasma and gnome, and with configuration and with just closing the welcome screen.. Always the same. Freshly installed, you see the GUI exactly one Time.

@hellwolf
Copy link
Contributor

hellwolf commented Aug 13, 2023

Hey folks, it seems a hard nut to crack. I am scratching my head why this is happening. I have even looked into how buildFHSBubblwrap works.

Meanwhile, if you can get a system-tray plugin for your desktop environment, you may have the luck of being able to open the interface for you.

Until then, any help is welcome. I will keep digging another day!

@ajmasia
Copy link
Author

ajmasia commented Aug 15, 2023

From the system tray it opens, but since the icon is not painted you have to guess where the click is. Is there any way to launch the click action from the terminal?

Thanks @hellwolf for investigate it!

image

@hellwolf
Copy link
Contributor

hellwolf commented Aug 26, 2023

I should have fixed these reported problems in #251565:

  • When I close the Insync window and try to start it again, it does nothing
  • If I execute any command from the console, I get this message: Insync doesn't seem to be running. Start it first.

@hellwolf
Copy link
Contributor

I won't be able to fix the "No systry icon appears" issue still, it's a known bug and I suspect it's a defect in upstream closed source code.

@hellwolf
Copy link
Contributor

Expecting #251565 to be available next week ish for both 23.05 and unstable.

@hellwolf
Copy link
Contributor

Also backported to 23.05.

@hellwolf
Copy link
Contributor

hellwolf commented Apr 7, 2024

FYI: Also, a new package for nautilus users: #302422 please give a 👍 for faster merging!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants