FS#53623 - [mixxx] libGL error: No matching fbConfigs or visuals found

Attached to Project: Community Packages
Opened by hamelg (hamelg) - Sunday, 09 April 2017, 10:12 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 28 May 2017, 20:00 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Laurent Carlier (lordheavy)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Mixxx is broken.
When starting, it hangs at splash screen with these errors :

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Warning [Main]: X Error: BadValue (integer parameter out of range for operation) 2
Extension: 154 (Uknown extension)
Minor opcode: 3 (Unknown request)
Resource id: 0x0
Warning [Main]: X Error: GLXBadContext 169
Extension: 154 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x4e00014
Warning [Main]: X Error: 0 0
Extension: 154 (Uknown extension)
Minor opcode: 26 (Unknown request)
Resource id: 0x0
Warning [Main]: QGLTempContext: Unable to create GL context.

Additional info:
* package version(s)
community/mixxx 2.0.0-8

* config and/or log files etc.
I use nvidia drivers.
$ pacman -Qs nvidia
local/lib32-nvidia-340xx-utils 340.102-3
NVIDIA drivers utilities (32-bit)
local/libvdpau 1.1.1-2
Nvidia VDPAU library
local/nvidia-340xx 340.102-5
NVIDIA drivers for linux, 340xx legacy branch
local/nvidia-340xx-utils 340.102-8
NVIDIA drivers utilities


Steps to reproduce:
launch mixxx
This task depends upon

Closed by  Laurent Carlier (lordheavy)
Sunday, 28 May 2017, 20:00 GMT
Reason for closing:  Fixed
Additional comments about closing:  mixxx-2.0.0-11
Comment by Doug Newgard (Scimmia) - Monday, 10 April 2017, 14:45 GMT
Sounds like OpenGL is broken. What does glxinfo tell you?
Comment by hamelg (hamelg) - Monday, 10 April 2017, 16:47 GMT
My openGL is OK.
All other GL applications works fine (glxgears, kwin ...).
It seems related to libglvnd : if I remove /usr/lib/libGL.so.1, mixxx starts fine.
Comment by Darek (blablo) - Monday, 01 May 2017, 11:20 GMT
Please see  FS#53360 
Comment by hamelg (hamelg) - Monday, 01 May 2017, 11:58 GMT
No, it changes nothing.
The error is the same when forcing with LD_LIBRARY_PATH=/usr/lib/nvidia
Comment by Darek (blablo) - Monday, 01 May 2017, 12:57 GMT
If you are an experienced Arch user, then test this
https://gist.github.com/fafryd1125/16233c95b12a88a8a8a2f81a998a4865

1 build locally mesa (supports only nvidia/nouveau)
2 uninstall the mesa and libglvnd from the system (packages from the repository)
3 install new mesa (not mese-glvnd if you use nvidia 340/304)
4 run mixxx
Comment by Darek (blablo) - Monday, 01 May 2017, 13:44 GMT Comment by hamelg (hamelg) - Monday, 01 May 2017, 18:13 GMT
Do you say it's fixed in mesa 17.1.0 ?
Comment by Darek (blablo) - Monday, 01 May 2017, 18:48 GMT
Your solution is to uninstall libglvnd without pacman complaining that mesa package requires it.

>It seems related to libglvnd : if I remove /usr/lib/libGL.so.1, mixxx starts fine.

mesa-noglvnd https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mesa-noglvnd

As I mentioned in another bug report:
Nvidia 340/304 does not support glvnd. Users of these cards should not be forced to install the libglvnd package at all.
Comment by hamelg (hamelg) - Monday, 01 May 2017, 19:06 GMT
Thank you Darek for your help.
Is this issue known by the upstream project ?
I have searched some information at https://github.com/NVIDIA/libglvnd, but I found nothing.
All others GL applications works fine here and I encounter this issue only with mixxx.
What does lordheavy say about this issue ?
Comment by Darek (blablo) - Monday, 01 May 2017, 19:30 GMT
>Is this issue known by the upstream project ?
http://nvidia.custhelp.com/app/answers/detail/a_id/3142
Support for libglvnd will never be implemented.
>All others GL applications works fine here and I encounter this issue only with mixxx.
It seems that some applications have a problem with 00-nvidia.conf (ldconfig)
>What does lordheavy say about this issue ?
????:)
Comment by hamelg (hamelg) - Monday, 22 May 2017, 13:25 GMT
I found out what is wrong.
The issue comes from how the mixxx binary is linked.
It should not use rpath :
$ readelf -a /usr/bin/mixxx|grep -i rpath
0x000000000000000f (RPATH) Library rpath: [/usr/lib]
A immediate and simple workaround is to patch the binary with the chrpath utility :
chrpath -d /usr/bin/mixxx
Comment by hamelg (hamelg) - Monday, 22 May 2017, 16:21 GMT
I have just seen there is a mixxx update 2.0.0-10, but unfortunately the issue is still present.
Please, assign this report to the package maintainer.
Comment by Laurent Carlier (lordheavy) - Saturday, 27 May 2017, 07:55 GMT
Please test mixxx-2.0.0-11
Comment by hamelg (hamelg) - Sunday, 28 May 2017, 15:22 GMT
issue solved.
Thanks

Loading...