On open, application fails to render nearly all text. Ubuntu 24.04, Wayland, 0.10.14
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- electron, linux
- Domain
- desktop
Research direction
The payload only shows the launch log: the GPU process exits during initialization (viz_main_impl.cc, Chromium internals) on Ubuntu 24.04 under Wayland, and text fails to render. Start by reproducing on the same Ubuntu and Wayland setup and checking whether the GPU errors go away with Chromium's software-rendering or Ozone/Wayland flags. Done means the window renders text on Wayland, but the fix probably lies in the Electron launch configuration, which the payload does not show.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
On open, application fails to render nearly all text. First observed 2026-10-12. Ubuntu 24.04LTS, Logseq 0.10.14 (but also observed with 0.10.15).
Reproduce the Bug
eric@shiretoko:~/Downloads/Logseq-linux-x64-0.10.14/Logseq-linux-x64$ ./Logseq
(rsapi) init loggers
[442456:1012/191736.518382:ERROR:viz_main_impl.cc(185)] Exiting GPU process due to errors during initialization
19:17:36.685 › Logseq App(0.10.14) Starting...
19:17:36.691 › restore proxy settings {:type "system"}
19:17:36.692 › set proxy to {:type "system"}
[442677:1012/191736.976785:ERROR:viz_main_impl.cc(185)] Exiting GPU process due to errors during initialization
19:17:41.384 › :electron.handler/watch-dir {:path "/home/eric/.logseq/config"}
19:17:41.442 › :electron.handler/unwatch-dir {:path "/mnt/data0/Logseq/Health, medical, fitness"}
19:17:41.444 › :electron.handler/watch-dir {:path "/mnt/data0/Logseq/Health, medical, fitness"}
19:32:05.851 › :electron.handler/watch-dir {:path "/mnt/data0/Logseq/Travel"}
Expected Behavior
Window opens with text items rendered.
Screenshots
Files
No response
Browser, Desktop or Mobile Platform Information
No response
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
- Dominant language
- No language data
- Stars
- 29
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from logseq/db-test
-
Web build on a phone: the fold arrow of an h1/h2 block lies on its bullet, so tapping the bullet folds instead of zooming inPossibly taken @tiensonqin claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Page titles with `$$`, `$&`, `` $` `` or `$'` change when block refs are resolvedPossibly taken @RaphaelFakhri claimed this 19 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
`#Asset` label is not displayed on asset nodes when `Hide from Node` is disabledPossibly taken @tiensonqin claimed this 22 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Similar issues
-
help wanted roadmap tests
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug sharing & sync
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nonbili/meron#147 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day