V1.4.5 - Graph view does not render nodes - pixiejs shaders broken

[Isofruit]

Steps to reproduce

0. Have your Operating System be Arch Linux and Install the AppImage
1. Open the Sandbox Vault
2. Navigate to the graph view (either via CTRL + G or clicking on the graph view icon)

This also applies to showing local graphs.

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

Yes

Expected result

The graph view with nodes shown.

Actual result

The graph view (in the sense that I get shown the menu) but no nodes are shown.

Environment

Debug Info of my sandbox vault:

SYSTEM INFO:
	Obsidian version: v1.4.5
	Installer version: v1.4.5
	Operating system: #1 SMP PREEMPT_DYNAMIC Thu, 24 Aug 2023 00:38:14 +0000 6.4.12-arch1-1
	Login status: logged in
	Catalyst license: none
	Insider build toggle: off
	Live preview: on
	Legacy editor: off
	Base theme: dark
	Community theme: none
	Snippets enabled: 0
	Restricted mode: on

RECOMMENDATIONS:
	none

If I check for the browser version via user agent I get this string:

'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) obsidian/1.4.5 Chrome/114.0.5735.289 Electron/25.8.0 Safari/537.36'

So Chrome version 114.

---

Additional information

Opening the developer console shows the following error:

Stacktrace:

PixiJS Error: Could not initialize shader.
Wc @ pixi.min.js:306
Ha @ pixi.min.js:422
generateProgram @ pixi.min.js:492
bind @ pixi.min.js:492
_renderDirect @ pixi.min.js:1073
_render @ pixi.min.js:1073
render @ pixi.min.js:529
render @ pixi.min.js:529
render @ pixi.min.js:529
render @ pixi.min.js:529
render @ pixi.min.js:529
render @ pixi.min.js:1017
renderCallback @ app.js:1
requestAnimationFrame (async)
e.queueRender @ app.js:1
e.initGraphics @ app.js:1
e.onIframeLoad @ app.js:1
Node.setChildrenInPlace @ enhance.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
a @ app.js:1
load (async)
e @ app.js:1
t @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
a @ app.js:1
Promise.then (async)
l @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
t.setViewState @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
t.deserializeLayout @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
a @ app.js:1
Promise.then (async)
l @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
n @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
t.deserializeLayout @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
n @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
t.deserializeLayout @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
t.setLayout @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
a @ app.js:1
Promise.then (async)
l @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
t.loadLayout @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
a @ app.js:1
Promise.then (async)
l @ app.js:1
a @ app.js:1
Promise.then (async)
l @ app.js:1
a @ app.js:1
Promise.then (async)
l @ app.js:1
a @ app.js:1
Promise.then (async)
l @ app.js:1
a @ app.js:1
Promise.then (async)
l @ app.js:1
a @ app.js:1
Promise.then (async)
l @ app.js:1
s @ app.js:1
Promise.then (async)
l @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
e.initializeWithAdapter @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
e @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
(anonymous) @ app.js:1
v @ app.js:1
(anonymous) @ app.js:1

Note: I do not have this problem on my Ubuntu working machine.

Here the data of said “unbroken” Ubuntu machine:
Environment:

SYSTEM INFO:
      Obsidian version: v1.4.5
      Installer version: v1.3.5
      Operating system: #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17 15:17:25 UTC 2 5.19.0-35-generic
      Login status: logged in
      Catalyst license: none
      Insider build toggle: off
      Live preview: on
      Legacy editor: off
      Base theme: dark
      Community theme: none
      Snippets enabled: 0
      Restricted mode: on

RECOMMENDATIONS:
      none

UserAgent string

'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) obsidian/1.3.5 Chrome/112.0.5615.183 Electron/24.3.1 Safari/537.36'

So Chrome version 112.

Based on that I am strongly assuming that the “installer” version is what’s truly running on my Ubuntu machine at the moment and the reason it still works is that it hasn’t upgraded yet (?).

Is the problem the new Chrome version possibly?

[Isofruit]

I just fully updated my Ubuntu version (where it all worked before but I was assuming that was because it was running 1.3.5) with a reboot.

Now debug info displays Installer version: v1.4.5 an the graph view still works.
User Agent on said Ubuntu version shows:

'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) obsidian/1.4.5 Chrome/114.0.5735.289 Electron/25.8.0 Safari/537.36'

So the problem is not the browser version and possibly something specific to the combination of “Obsidian v1.4.5 + my machine” ?

The machine I am running is a Framework 13 if that helps anything.
This seems related to this issue on the pixiejs github, which describes the problem being the combination of Chrome version 114 + GPU drivers.

The weird thing this is the integrated CPU into intel’s 11th tigerlake motherboard. The Graphics are displayed as "Intel Xe Graphics (TGL GT2). I’m not sure what could be broken here or how one could even fix that as I don’t really have a dedicated driver package to update.

[Isofruit]

Given that there’s a non-zero chance this is a GPU driver/hardware issue I also opened a topic on the framework forum.
Maybe we can figure out over there (or somebody in here knows) how to upgrade the drivers on an integrated GPU because that is one area I am very much not knowledgeable on.

[Isofruit]

The solution turns out that I forgot I hadn’t installed the AppImage but via package manager - which I assumed was providing the appimage but I was wrong.
Under the AppImage it all works perfect.
Basically did a reinstall thusly >_>

I’m closing the issue and apparently I am silly.