Hi!
On Sat, Sep 19, 2015 at 02:06:45AM +0300, Alex Efros wrote:
> And it was able to work without is before I've updated nvidia-drivers, so
> maybe something is wrong with this nvidia-drivers version.
This issue also affect many other apps, for example:
$ xxkb
xxkb: error while loading s
On 19 Sep 2015 at 2:06, Alex Efros wrote:
> 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 -
Hi!
On Sat, Sep 19, 2015 at 04:14:17PM +0200, PaX Team wrote:
> 3e3ef95fd0351495d400147b994b1978
> /usr/lib64/opengl/nvidia/lib/libGLdispatch.so.0
This lib in 355.11 on my system have same MD5.
Looks like previous (352.41) nvidia-drivers doesn't have this lib.
> so try "readelf -edW /usr/lib64
On 19 Sep 2015 at 17:45, Alex Efros wrote:
> > so try "readelf -edW /usr/lib64/opengl/nvidia/lib/libGLdispatch.so.0"
> > and post its output.
>
> Section Headers:
> [Nr] Name TypeAddress OffSize ES
> Flg Lk Inf Al
> [10] wtext PROGBITS
Hi!
On Sat, Sep 19, 2015 at 05:50:20PM +0200, PaX Team wrote:
> so there're two things left to do:
> 1. enable ELFRELOCS in your kernel config (and keep MPROTECT enforced
>on all binaries)
Done. This works. I don't really like it, but let it be, at least for now.
At a glance only difference
On 19 Sep 2015 at 20:24, Alex Efros wrote:
> On Sat, Sep 19, 2015 at 05:50:20PM +0200, PaX Team wrote:
> > so there're two things left to do:
> > 1. enable ELFRELOCS in your kernel config (and keep MPROTECT enforced
> >on all binaries)
>
> Done. This works. I don't really like it, but let it
Hi!
On Sat, Sep 19, 2015 at 09:33:15PM +0200, PaX Team wrote:
> did you see only a single log per executable or two? i'm asking it
> because this method of runtime codegen would produce two messages
> (and the grsec log message is actually wrong as it's not a denial
> but rather the opposite, spen
Hi!
On Sat, Sep 19, 2015 at 09:33:15PM +0200, PaX Team wrote:
> > > 1. enable ELFRELOCS in your kernel config (and keep MPROTECT enforced
> > >on all binaries)
> > Done. This works. I don't really like it, but let it be, at least for now.
> well, disabling MPROTECT is much worse, this way you
On 19 Sep 2015 at 22:40, Alex Efros wrote:
> Hi!
>
> On Sat, Sep 19, 2015 at 09:33:15PM +0200, PaX Team wrote:
> > > > 1. enable ELFRELOCS in your kernel config (and keep MPROTECT enforced
> > > >on all binaries)
> > > Done. This works. I don't really like it, but let it be, at least for now.
