I don't think so, `inxi -Gx` says:

Graphics:
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Dell driver: i915
    v: kernel arch: Gen-13 bus-ID: 00:02.0
  Device-2: NVIDIA GA107GLM [RTX A500 Laptop GPU] vendor: Dell
    driver: nouveau v: kernel arch: Ampere bus-ID: 01:00.0
  Device-3: Sunplus Innovation Integrated_Webcam_FHD driver: uvcvideo
    type: USB bus-ID: 3-6:3
  Display: wayland server: X.Org v: 23.2.6 with: Xwayland v: 23.2.6
    compositor: gnome-shell v: 46.0 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1: 1920x1200~60Hz
    2: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,nouveau,swrast platforms:
    active: gbm,wayland,x11,surfaceless,device inactive: N/A
  API: OpenGL v: 4.6 compat-v: 4.3 vendor: intel mesa v: 24.0.5-1ubuntu1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (RPL-P)

However, I just noticed that I'm back to 24.0.9 (some automatic update I
must have missed), but this time, it works... partially. When I compile
the app in "dev" mode, it works now; but in "release" mode, it still
crashes with the same error. In principle, there's no fundamental
difference about them, it's just a live-reload feature that should be
completely irrelevant to the 3D graph.

Well, actually, after what you said and this behavior, I tried erasing
node_modules, etc, and then `~/.config/electron/*Cache`, and indeed, it
seems to have solved the issue! Thanks for the tips, we can close this
bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2074182

Title:
  libglx-mesa 24.0.9: shader issue in Electron three-based 3D graph

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On a laptop with Ubuntu 24.04, after updating from 24.0.5-1ubuntu1 to
  24.0.9-1ubuntu1 on the 2024-07-22, an Electron-based application,
  using a 3D graph based on three.js, stopped working properly. The
  Chromium developer tools indicated errors such as:

  ```
  node:internal/process/task_queues:140 THREE.WebGLProgram: Shader Error 0 - 
VALIDATE_STATUS false

  Material Name: 
  Material Type: MeshLambertMaterial

  Program Info Log: Location of variable pc_fragColor conflicts with another 
variable.
  ```

  And other related messages, such as shader issues, appeared as well.
  The graphs were no longer visible on the Electron component. When
  switching the node type to HTML-based node, it was visible, but the
  edges remained invisible. Node positioning and moving was unaffected,
  everything seemed normal except that the rendered graph was not
  visible.

  After downgrading back to 24.0.5, everything works normally once
  again.

  It is a Dell laptop with Intel Core i7-13800H and NVIDIA RTX A500.
  Trying to update its drivers did not help. Visiting
  https://threejs.org/docs/scenes/material-
  browser.html#MeshLambertMaterial with Chromium (to try and emulate the
  issue) did not produce any problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2074182/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to