Crash (SIGTRAP) on Linux when enabling native window title bar in 2.0.2

未关闭
#1,485 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
electron, linux
领域
desktop

调研方向

Start by reproducing the crash on Logseq 2.0.2 on Linux with the native title bar option enabled, then trace the setting change and window recreation path in the Electron app. The report provides no source files or tests to start from, so first locate that path and inspect the crash around window teardown. Done means confirming the cause and ensuring the window restarts with the native title bar or the app requests a restart.

由索引模型根据 Issue 内容生成。

描述

Describe the bug
Logseq 2.0.2 crashes (SIGTRAP) when enabling the "native window title bar" option on Linux and confirming the dialog.

To reproduce

  1. Start Logseq 2.0.2 on Linux (Arch, Hyprland/Wayland, AppImage via the AUR logseq-appimage package).
  2. Go to Settings and enable "Enable the native window title bar on Windows and Linux".
  3. Confirm the prompt.
  4. The app dies instead of restarting its window.

Expected behavior
The window is recreated with the native title bar (or the app asks for a restart).

Actual behavior
The main process aborts. The setting is saved (configs.edn contains {:window/native-titlebar? true}, written in the same second as the crash), and the next launch works with the native title bar.

Crash details

  • Signal: SIGTRAP, si_code: SI_KERNEL, main thread (single-threaded core)
  • Kernel log: traps: logseq[...] trap int3 ip:55d0b7525fbb sp:7ffe078e2ee0 error:0 in logseq[74d7fbb,55d0b26cc000+9a69000]
  • Offset in binary: logseq + 0x74d8fbb, called from +0x327a246, +0x327860c, +0x3278a59, +0x2ae03b1
  • This looks like a deliberate abort (int3 / fatal check) rather than a segfault. The binary is stripped, so I could not symbolize frames.
  • main.log for that run has no "window-all-closed" / quit line, so it did not exit cleanly.
  • Same-second writes at crash time: configs.edn, window-state.json, DIPS, and the graph's search/db.sqlite, which looks like the window teardown path.

Environment

  • Logseq 2.0.2 (AppImage, Electron-based)
  • Arch Linux, kernel 7.2.8, Hyprland (Wayland)
  • Fresh install, first run after switching from 0.10.15; graph was the Demo graph

Happy to test again or provide more details if useful.

主要语言
没有语言数据
星标
29
派生
2
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

logseq/db-test 的其他 Issue

查看 logseq/db-test 的全部 Issue

相似的 Issue

更多 Desktop Dev Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。