Logseq freezes entire Ubuntu gui when /upload an asset. Graph on Insync-synced folder.

[afrigeri]

What happened?

Working on a DriveSyncFiles shared graph (Insync locally synced, files are ok and network connection too), freezes Ubuntu gui when /upload an asset. Need to restart all X11 or reboot the machine.

Reproduce the Bug

1. Open a graph on DriveSyncFiles shared folder (using Insync)
2. work on the graph
3. /upload an asset - the file window is shown but all the Ubuntu GUI is freezed and no interaction is possible

Expected Behavior

the asset should be uploadable.

if the graph is moved to a local directory - behavior is as expeced.expected

Screenshots

No response

Desktop Platform Information

Distributor ID: Ubuntu
Description: Ubuntu 21.10
Release: 21.10
Codename: impish

also tried with Ubuntu LTS - same behavior

Mobile Platform Information

No response

Additional Context

No response

[cnrpman]

Can you capture anything from the Console in devtools?

[afrigeri]

Hi @cnrpman - Logseq newbie here. Can you please tell me how to trace the error in the Console devtools? The UI freezes with the Desktop App. When starting Logseq from the Chrome browser with the devtools opened, I do not have the /upload asset command available (which I have in the desktop app).

[cnrpman]

@afrigeri
Are you using Windows?
You may press alt to activate the menu bar, then choose View / Toggle Devloper Tools from it

[afrigeri]

@cnrpman Ah! I'm on Ubuntu but the alt trick works, and I get the Dev tools console on. The problem now is that since the UI freezes as soon as the file folder opens, I'm not able to see what the console is telling us.

Is there a way to redirect the console output to a text file so that after the reboot we can investigate the log?

[cnrpman]

@afrigeri To confirm, the whole ubuntu desktop is freezed and no console captured?
What's the version of Logseq?

Something similar to this?
#3202

[afrigeri]

@afrigeri To confirm, the whole ubuntu desktop is freezed and no console captured?

whole ubuntu desktop - the mouse moves but no interaction with the existing environment. OS is not freezed, I can reach it via ssh.

What's the version of Logseq?

0.6.6

Something similar to this? #3202

mmmhh, don't think so - no errors appear in the console before the freeze.

[tdido]

I have a similar case in my Debian Sid with i3, Logseq v0.7.2.

• If I click on the "Upload an asset" option from the dropdown using the mouse, then I can't click on anything in the file browsing window. I can however navigate and close the window using the keyboard.
• If I use the keyboard instead to select the option from the dropdown, I can use the window normally even with the mouse.

Attaching a short video showing the behaviour.

logseq_bug_5113.mp4

[AllanChain]

Maybe a duplicate of #2994?

[afrigeri]

I confirm same behavior reported by @tdido with v0.7.6 on Ubuntu 22.04 LTS. Now I can upload the asset by navigating the file window with the arrow keys, but when the file selection window is on, I cannot interact anymore with the Gnome GUI.

[cnrpman]

Sounds upstream issue

[orkolorko]

I confirm same behaviour, Logseq captures the cursor from Gnome (xkill is not able to get the cursor from Logseq)

[bdklahn]

Same behavior on KDE Plasma (OpenSUSE Tumbleweed).

Everything is frozen, and the only thing I seem to be able to do is log out via Ctrl-Alt-Delete key combo, and wait for the timer to count down and activate the default option.

So it does seem maybe related to GUI mouse interaction, since I can't even move and click to select logout (nor shutdown, etc.).

[Bad3r]

I am unable to reproduce this issue. As cnprman mentioned, this looks like an upstream issue, not related to logseq.
If you are still encountering this issue. Please feel free to re-open