Logseq 0.10.12 desktop update crashes to white screen

Ken · June 2, 2025, 9:44am

I posted on the Github bug report, but Logseq desktop 0.10.12 crashes to a white screen after about 30 seconds, needing Terminal killall logseq to close the program.
My OS is Raspberry Pi 5 desktop which installed Logseq desktop previous perfectly with flatpak.

Thorah · June 2, 2025, 10:45pm

Sorry this isn’t a solution I’m afraid but in case the Devs see this (also to bump it anyway for you)

I’m running Android V13 and Windows 11 and I haven’t had any issues with the Markdown version at all. Are you using Markdown yourself or a different option?

Also maybe check the logs by pressing Ctrl+Shift+I (I think that’s the shortcut I’m typing this in bed because I can’t sleep)

Ken · June 4, 2025, 1:01pm

Bug reported, unable to find a small sample code though.

github.com/logseq/logseq

Logseq flashes to white screen after about 30 seconds

opened 11:41AM - 31 May 25 UTC

eiger3970

### Search first - [x] I searched and no similar issues were found ### What Ha…ppened? Logseq flashes white after about 30 seconds and freezes, requiring killall Logseq. ### Reproduce the Bug Open Logseq. ### Expected Behavior Logseq keeps the Dark mode green theme. ### Screenshots Not needed ### Desktop or Mobile Platform Information Raspberry Pi 5 Model B Rev 1.0, Debian GNU/Linux 12 (Bookworm). Logseq Version: 0.10.12 (both Flatpak and Snap versions). ### Additional Context Problem: Logseq flashes white after about 30 seconds and freezes, requiring killall Logseq. Error Messages: The full terminal output showing gbm_wrapper.cc and gl_surface_presentation_helper.cc errors (e.g., Failed to export buffer to dma_buf: No such file or directory (2)). Troubleshooting Steps Attempted: Full Flatpak reinstall of Logseq. flatpak update. Attempted flatpak run --env=ELECTRON_DISABLE_GPU=1 com.logseq.Logseq. Attempted flatpak run --env=XDG_SESSION_TYPE=x11 com.logseq.Logseq. Reinstallation of org.freedesktop.Platform.GL.default Flatpak runtimes. Confirmation of Flatpak permissions (devices=dri;). Attempted installation and use of the Snap version of Logseq. ### Are you willing to submit a PR? If you know how to fix the bug. - [ ] I'm willing to submit a PR (Thank you!)

Thorah · June 4, 2025, 5:09pm

You mean you didn’t send a screenshot. How incomplete of you .

Fair play on the report. Hope you get a fix

Ken · June 5, 2025, 5:43pm

Just a quick update, same issue with Obsidian.

Ken · June 6, 2025, 7:56am

Tried /boot/firmware/config.txt, adding a bottom line with:
gpu_mem=256
and also
gpu_mem_512
however same issue.

Ken · June 6, 2025, 8:11am

Also ran

sudo apt update
sudo apt full-upgrade -y

and same issue.
Reverted back to original /boot/firmware/config.txt and same issue for Logseq, however Obsidian no longer has the issue.

Ken · June 6, 2025, 2:11pm

Tried an older version of Obsidian 1.7 and works. Here’s some details, I’ll work on Logseq too.

Title: “Obsidian 1.8.10 (ARM64 AppImage) Freezes/Black Screens on Raspberry Pi 5, Regression from 1.7.7”
Hardware: Raspberry Pi 5 (mention RAM, e.g., 8GB).
Operating System: Raspberry Pi OS Bookworm (64-bit), clean reinstall performed.
Obsidian Versions: 1.8.10 (crashes), 1.7.7 (works).
Detailed Symptoms:
1.8.10: Launches, then turns black/white and freezes after ~30 seconds, with gbm_wrapper.cc, gl_surface_presentation_helper.cc, and Render frame was disposed errors.
1.7.7: Launches and is usable, but still shows gbm_wrapper.cc and gl_surface_presentation_helper.cc errors (which are not fatal in this version).
Troubleshooting Steps Taken (with concise results):
gpu_mem=512 in /boot/firmware/config.txt (confirmed set).
Launched 1.8.10 with --disable-gpu (still showed GBM errors, render frame disposed error).
Attempted to force X11 backend with export GDK_BACKEND=x11 (still showed GBM errors, render frame disposed error).
Confirmed lxsession installed but no X11 option at login.
Crucially: Performed a complete clean reinstall of Raspberry Pi OS Bookworm (64-bit), set gpu_mem=512, and the issue with 1.8.10 persists, while 1.7.7 works.

 rapi5  raspberrypi  ~  Downloads  $  cat /boot/firmware/config.txt
# For more options and information see
# http://rptl.io/configtxt
# Some settings may impact device functionality. See link above for details

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Additional overlays and parameters are documented
# /boot/firmware/overlays/README

# Automatically load overlays for detected cameras
camera_auto_detect=1

# Automatically load overlays for detected DSI displays
display_auto_detect=1

# Automatically load initramfs files, if found
auto_initramfs=1

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

# Run in 64-bit mode
arm_64bit=1

# Disable compensation for displays with overscan
disable_overscan=1

# Run as fast as firmware / board allows
arm_boost=1

[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.
otg_mode=1

[cm5]
dtoverlay=dwc2,dr_mode=host

[all]
dtparam=pciex1_gen=3

gpu_mem=512

TheCrig · October 26, 2025, 2:23am

Not sure how this got marked resolved. I still have this problem on Raspberry Pi 5 with latest 64-bit Raspberry Pi OS on logseq 0.10.14. Specifically: About 30 seconds after the desktop logseq starts, the window, including all the window manager decorations (frame, title bar, buttons, etc.) goes completely white. logseq 0.10.14 is unusable on Raspberry Pi (unless I missed something above).

Ken · October 27, 2025, 11:10am

This issue remains with the OP too (c’est moi), however the work around is still the best ‘fix’ hence I closed the post.