logseq / logseq/db-test

Desktop app crashes when opening a Library page imported from an OG graph (file-to-DB import)

Open
#1,170 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

A page hierarchy created in an OG graph is automatically imported as a Library when imported into the DB version (file-to-DB import). After the import, the Desktop app crashes immediately whenever the Library page — or any other non-leaf page of the Library hierarchy — is opened.

- App version: 2.0.1-alpha+nightly.20260908 (DB beta)
- Platform: Desktop (Linux)

Note: This does **not** happen when a similar structure is built manually in a new DB graph. Only imported hierarchies are affected.

### Reproduce the Bug

1. In an OG (file-based) graph, create a page with a hierarchy, e.g. `Country/Australia`
2. Import this graph into the DB version using file-to-DB import
3. The hierarchy is automatically imported as a Library
4. Open the Library page (or any other non-leaf page of the Library hierarchy, e.g. `Country` or `Library`)
5. The app crashes immediately

### Expected Behavior

Opening a Library page or any non-leaf page of an imported hierarchy should display the page normally, without crashing. Imported hierarchies should behave the same as hierarchies built manually in a DB graph.

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

- Version: 2.0.1-alpha+nightly.20260908
- Platform: Desktop (Linux)

### 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!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the crash on Desktop Linux using the documented file-to-DB import steps with a hierarchy such as Country/Australia. Compare opening imported non-leaf pages with an equivalent hierarchy created manually in a DB graph. Done means Library and other imported non-leaf pages open normally without crashing and the behavior matches manually built hierarchies.

Written by the indexing model from the issue text.

Assessment

Domain
database, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.