Open Bug 1860512 Opened 2 years ago Updated 2 years ago

glxtest + VirtualGL depends on graphical console session

Categories

(Core :: Graphics, defect, P3)

Firefox 115
Unspecified
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: martin.kofahl, Unassigned)

Details

Steps to reproduce:

  • start a virtual x session under linux (here using NoMachine)
  • use a dedicated gpu (here Tesla M60)
  • use virtualgl 3.1

scenario 1)

  • switch host console to graphical display, e.g. tty7
  • run "vglrun glxtest" in the virtual x session
  • run "vglrun glxinfo -B" in the virtual x session

scenario 2)

  • switch host console to text output, e.g. tty1
  • run "vglrun glxtest" in the virtual x session
  • run "vglrun glxinfo -B" in the virtual x session

Actual results:

scenario 1)
gpu detected by glxtest and glxinfo

scenario 2)
not output from glxtest, exit code 1 but gpu detected by glxinfo

Expected results:

gpt is recognized regardless of the console session

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Graphics
Product: Firefox → Core

The severity field is not set for this bug.
:bhood, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(bhood)

Dropping into Triage for review.

Blocks: gfx-triage
Severity: -- → S3
Flags: needinfo?(bhood)
OS: Unspecified → Linux
Priority: -- → P3
Severity: S3 → S4
No longer blocks: gfx-triage

Martin, are you able to investigate and figure out where things are going wrong in glxtest?

Flags: needinfo?(martin.kofahl)

It depends. I could compile glxtest and add some debug output. Can you tell me the current source?

Flags: needinfo?(martin.kofahl)
You need to log in before you can comment on or make changes to this bug.