Obsidian start time [quick fix] Hyprland/Arch NVIDIA

Just a small fix

11/18/20241 min read

Problem

I had a pretty annoying problem with start time of obsidian on my Arch/Hyperland.

To execute the obsidian app from AUR, FLatpak, and Github it would take a abnormal amount of time.

So I ran obsidian in the terminal and these are the messages.

└─[$] <> obsidian

2024-11-17 19:44:28 Loading main app package /usr/lib/obsidian/obsidian.asar

2024-11-17 19:44:28 Checking for update using Github

2024-11-17 19:44:29 Success.

2024-11-17 19:44:29 Latest version is 1.7.6

2024-11-17 19:44:29 App is up to date.

libva error: /usr/lib/dri/nvidia_drv_video.so init failed

[9396:1117/114459.132828:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

[9241:1117/114459.143457:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512

libva error: /usr/lib/dri/nvidia_drv_video.so init failed

^C[9396:1117/114529.328989:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

[9396:1117/114529.329024:ERROR:command_buffer_proxy_impl.cc(132)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

[9241:1117/114529.330110:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange.

[9241:1117/114529.338296:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=512

Notice how it tries to init the gpu then just fails, this is likely a problem with my own system and/or NVIDIA not obsidian

My solution

Since the problem is my GPU and I have a lot of DDR5 ram on this computer I have disabled the GPU on execute.

In my key-bind config for Hyprland I added the --disable-gpu flag to the exec command.

$notes = obsidian --disable-gpu

# exec notes

bind = $mainMod, O, exec, $notes

This has disabled obsidian even trying to “look” to init the GPU resulting in super fast start-up times

This is a quick fix as it likely highlights a problem with my system overall that I have yet to figure out and put time into.