While mplayer itself works fine with both hardened-gcc and PaX stack protection features, accessing the decoder plugins from Windows does not: Dec 15 13:48:21 peti PAX: terminating task: /usr/bin/mplayer(mplayer):8552, uid/euid: 1000/1000, PC: 301cf670, SP: 5b31095c Dec 15 13:48:21 peti PAX: bytes at PC: 53 56 57 bb 01 00 00 00 8b 7c 24 14 55 3b fb 75 2a 01 1d b4 This happened when I triet to play a VIVO file. The fix is to add mplayer to /etc/conf.d/chpax in order to have PaX disabled for it. Reproducible: Always Steps to Reproduce: 1. Activate PaX in the Linux kernel 2. mplay a .viv file
mplayer was already listed in the SEGMEXEC_EXEMPT of /etc/conf.d/chpax what flags does yours have/need? Here is exactly what mine looks like. PeMRxs ET_EXEC /usr/bin/gmplayer PeMRxs ET_EXEC /usr/bin/mplayer
Uh, is it? I'm running version 1.0_pre2, which is not the most current, and it doesn't seem to be registered in the chpax file here. (Yes, I had PaX activated and all tools installed when mplayer was emerged.) Perhaps an update is in order? Anyway, I disabled _all_ PaX features for mplayer, I didn't try to track down which particular feature causes the problem. Sorry.
Yes perhaps you need to update your chpax to get the latest revision of the /etc/conf.d/chpax file. Please try. emerge -C chpax rm /etc/{init,conf}.d/chpax emerge '>=sys-apps/chpax-0.5' chpax -z /usr/bin/mplayer ; # resets flags to default # Edit the /etc/conf.d/chpax file to your desires then /etc/init.d/chpax restart # Then report back success story so I can close bug. thanks..
I have chpax-0.5 installed already, and according to "/var/log/emerge.log", this version was installed right after the initial "emerge system". So there really isn't anything to update on my machine. :-) I'll be installing a new machine any time soon now, then I'll have an eye on this issue. Until then, just close the bug and assume everything is fine. I'll re-open in, in case I still have problems with mplayer.
Peter, It's very common for init/conf scripts to slightly change in portage without us needing to do a revision bump. This is what happened and why you dont have it. No big deal to me however. If you dont want to remerge then you dont have to. changing resolution to INVALID
OK, thanks for the clarification. I'll be re-installing over the hollidays anyway, to get to the 2.6.x kernel on my main machine, so I'll be using that opportunity test the ebuild. Until then, I don't want to mess too much with my machine, because I need it _running_ for the next couple of days. :-)
