zed-industries / zed

Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
https://zed.dev
Other
50.3k stars 3.1k forks source link

Linux Wayland: "restore_on_startup" == "last_session" does not restore session #15959

Open nieware opened 3 months ago

nieware commented 3 months ago

Check for existing issues

Describe the bug / provide steps to reproduce it

When I run Zed, I am greeted with an empty window and an "Open recent project" button in the title bar. Even if I set "restore_on_startup" to "last_session", this still happens. This only started happening since I updated to the latest version (0.147.2).

Environment

Zed: v0.147.2 (Zed) OS: Linux Wayland ubuntu 22.04 Memory: 15.3 GiB Architecture: x86_64 GPU: Intel(R) Xe Graphics (TGL GT2) || Intel open-source Mesa driver || Mesa 23.2.1-1ubuntu3.1~22.04.2

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your Zed.log file to this issue.

Zed.log


JokaJukka commented 3 months ago

I can also confirm this issue.

Zed: v0.147.2 (Zed) Operating System: Arch Linux KDE Plasma Version: 6.1.3 Kernel Version: 6.6.44-3-lts (64-bit) Graphics Platform: Wayland Processors: 12 × 13th Gen Intel® Core™ i5-13420H Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LENOVO Product Name: 82XV System Version: LOQ 15IRH8

0xDEAD-C0DE commented 3 months ago

Good morning. The restore_on_startup = last_session has not been implemented for Wayland yet. Set "restore_on_startup" : "last_workspace" in your~/.config/zed/settings.ini` This worked for me.

Improved restoring of windows across restarts: the order of the windows is now also restored. That means windows that were in the foreground when Zed was quit will be in the foreground after restart. Supported on MacOS and Linux/X11, not yet on Linux/Wayland (https://github.com/zed-industries/zed/pull/15419).

apricotbucket28 commented 3 months ago

This has already been fixed in 0.148, see: