Logseq 0.10.12 desktop update crashes to white screen

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.

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)

1 Like

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

1 Like

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

Fair play on the report. Hope you get a fix :blush:

1 Like

Just a quick update, same issue with Obsidian.

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

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.

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

1 Like