1.13.4: Linux Wayland starts with error

Help
,
1

Obsidian bug on Wayland in version 1.13.4-1

This bug spawned directly in this version I guess, because on version 1.12.7-3 everything is fine (checked with downgrading)

Steps to reproduce

  1. Install obsidian with latest official AppImage for Linux from obsidian website
  2. Start it

Did you follow the troubleshooting guide? [Y/N]

Yes

Expected result

Obsidian have no errors at startup and working on Wayland

Actual result

Obsidian starts with error about Wayland and starts in x11 (log below)
./Obsidian-1.13.4.AppImage
2026-08-02 06:57:39 Loaded updated app /home/qwerz/.config/obsidian/obsidian-1.13.4.asar
Fontconfig warning: We will not regenerate the cache because some cache files were generated by a newer version (0x2012001) of Fontconfig. Please regenerate the cache with the latest version of Fontconfig to avoid any unexpected behavior. (current version: 0x2011001)
2026-08-02 06:57:39 Checking for update using Github
[46838:0802/095739.751864:ERROR:ui/ozone/platform/wayland/gpu/wayland_surface_factory.cc:249] ‘–ozone-platform=wayland’ is not compatible with Vulkan. Consider switching to ‘–ozone-platform=x11’ or disabling Vulkan
2026-08-02 06:57:39 Success.
2026-08-02 06:57:39 Latest version is 1.13.4
2026-08-02 06:57:39 App is up to date.

Environment

SYSTEM INFO:
Obsidian version: 1.13.4
Installer version: 1.13.4
Operating system: #1 SMP PREEMPT_DYNAMIC Tue, 28 Jul 2026 13:49:51 +0000 7.1.5-arch1-2
Login status: not logged in
Language: en
Insider build toggle: off
Live preview: on
Base theme: dark
Community theme: Typewriter 2.3.3
Snippets enabled: 0
Restricted mode: off
Plugins installed: 1
Plugins enabled: 1
1: Remotely Save v0.5.25
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

Distro Name: Arch Linux
Distro Version: rolling
Desktop Environment: latest KDE
Installation method used: Appimage

Additional information

On version 1.12.7-3 everything is fine (checked with downgrading)

2

This seems to to be a problem with your specific system.

There was no prior version 1.12.7-3. I don’t know where you got that from.

3

I don’t think that there is a specific problems on my system. It’s clean install of Arch

Version 1.12.7.-3 is from Arch repos.
Anyway if I install 2 versions of obsidian (on screenshot) from GitHub the brand new one (1.13.14) have this problem and the old one (1.12.7) don’t.

I can try installing a WM with Ubuntu or whatever but I’m sure that update broke something no matter what system is.

image
image1569×943 130 KB

4

begin with clearing the Obsidian config/cache folder in your home.

5

if that helps, obsidian 1.13.4 on wayland on nixos works fine. can it be a problem with your installation method? can you try to install obsidian from the official repository via a command like sudo pacman -S obsidian? they have already updated the package

6

clearing cache and config folder didn’t help unfortunately

I tried any installation method including pacman and AppImage installation
maybe this is problem with electron?

7

it may be a problem with electron. did you update the system? maybe the wrapper for obsidian cannot find electron 43 or electron binary in the system is malfunctioning.

8

The only installation methods we support are the ones on our website. Please, do not complicate things with unauthorized/unsupported third-party redistribution.

9

I am reviewing this. It may be an electron/chrome problem under certain circumstances.

Which GPU(s) do you have? Which GPU driver/version do you use?

10

I’m not complicating anything with unofficial installing methods, I’m using official AppImage

System is fully updated and my GPU is Nvidia RTX 5060 with driver nvidia-open 610.43.03-9

11

I am reading again this BR, does the fact that there is this error on startup create any actual problem?

12

Actually only cosmetic problems like font rendering and this icon instead of normal one

image

13

That’s a different problem. For the Appimage, you need to update your .desktop file so that StartupWMClass=md.Obsidian

The Snap and Appimage have a built in correct .desktop file.

14

Updating .desktop file makes no change

And also there is no problems with 1.12.7 AppImage at all

The app starts not as it should since 1.13.4 version, this is a problem

15

I have not understood what the actual problem is aside from icon in the taskbar which is a different thing.

16

This is not a different thing

17

Again, the icon is a different problem.
I don’t know if you have any actual problem.
The error that you see about wayland and vulkan is a longstanding chromium support problem and it being worked on upstream.