Summary: | media-libs/libepoxy with x11-drivers/nvidia-drivers-361.28 - nvidia-settings: segmentation fault in epoxy_glx_version () from /usr/lib64/libepoxy.so.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bas Nedermeijer <bas> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | jer |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Xorg.0.log |
Description
Bas Nedermeijer
2016-02-11 14:57:58 UTC
Created attachment 425252 [details]
Xorg.0.log
Please post your `emerge -vpq media-libs/libepoxy =x11-drivers/nvidia-drivers-361.28` output in a comment. (In reply to Jeroen Roovers from comment #2) > Please post your `emerge -vpq media-libs/libepoxy > =x11-drivers/nvidia-drivers-361.28` output in a comment. # emerge -vpq media-libs/libepoxy =x11-drivers/nvidia-drivers-361.28 [ebuild R ] media-libs/libepoxy-1.3.1 USE="{-test}" ABI_X86="32 (64) (-x32)" [ebuild R ] x11-drivers/nvidia-drivers-361.28 USE="X acpi driver gtk3 kms multilib static-libs tools uvm -pax_kernel" I'd be curious to see more information in the backtrace. Could you compile libepoxy with debugging symbols? That is, add -O0 -g3 to your CFLAGS and recompile it. (In reply to Matt Turner from comment #4) > I'd be curious to see more information in the backtrace. Could you compile > libepoxy with debugging symbols? That is, add -O0 -g3 to your CFLAGS and > recompile it. NEEDINFO. |