Bug 1214126 - Remote GLX (libGLX_mesa.so) broken with FreeNX/X2Go
Summary: Remote GLX (libGLX_mesa.so) broken with FreeNX/X2Go
Status: RESOLVED INVALID
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Leap 15.5
Hardware: Other openSUSE Leap 15.5
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Gfx Bugs
QA Contact: Gfx Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-09 15:56 UTC by Kai Lappalainen
Modified: 2023-08-26 13:12 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Lappalainen 2023-08-09 15:56:28 UTC 
After remote login (FreeNX, X2Go) glxinfo, glxgears etc. show:

X Error of failed request:  GLXUnsupportedPrivateRequest
  Major opcode of failed request:  143 (GLX)
  Minor opcode of failed request:  17 (X_GLXVendorPrivateWithReply)
  Serial number of failed request:  27
  Current serial number in output stream:  27

Up to openSUSE 15.4 this was working fine.

Copying the libGLX_mesa.so.0.0.0 (incl. symlinks) and the symlink libGLX_indirect.so from openSUSE 15.4 to some directory and setting LD_LIBRARY_PATH in /etc/profile.d pointing to this directory, glxinfo and glxgears etc. work again.

This also affects some applications like Krita, KDE3 Kolourpaint and others, which refuse to start on an openSUSE 15.5 remote desktop but are working fine after the mentioned workaround (using 15.4 libs).
Comment 1 Stefan Dirsch 2023-08-26 13:12:54 UTC 
We do not support FreeNX/X2Go. I remember, that FreeNX needed special X libs. That could be the culprit here. We won't dig into this. Sorry.