Hi!

I've just updated from nvidia-drivers-352.30 to 355.11, and after reboot
pidgin failed to start:

    pidgin: error while loading shared libraries:
    /usr/lib64/libGLdispatch.so.0: cannot make segment writable for
    relocation: Permission denied

and kernel log is:

    kern.alert: grsec: denied RWX mprotect of
    /usr/lib64/opengl/nvidia/lib/libGLdispatch.so.0 by /usr/bin/pidgin

I've temporary switched to `eselect opengl set xorg-x11` and was able to
start pidgin, but I wonder is there other way to work around this issue?
Problem is, I don't like to use `paxctl-ng -m /usr/bin/pidgin` because
pidgin is one of "these" apps - it process a lot of data from network, it
support a lot of protocols, does a lot of complex parsing…

And main question is: why the hell pidgin needs OpenGL? I don't have any
"visual" plugins for pidgin enabled, so at a glance it shouldn't use OpenGL.
And it was able to work without is before I've updated nvidia-drivers, so
maybe something is wrong with this nvidia-drivers version.
How to find out why pidgin needs this library at all?


P.S. I know using hardened on workstation with nvidia-drivers isn't
supported, that's why I'm asking here instead of opening bug report.

-- 
                        WBR, Alex.

Reply via email to