Created attachment 300351 [details] Output of "emerge --info" mplayer from recent ebuilds (1.0_rc4_p20120105, 1.0_rc4_p20120109, 1.0_rc4_p20120128) crashes when trying to use keyboard controls, like LEFT, RIGHT, UP, DOWN, o, and several others: Player interrupted by signal 4 in module: filter_video - MPlayer crashed by an 'Illegal Instruction'. It usually happens when you run it on a CPU different than the one it was compiled/optimized for. Verify this! - MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash. - MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, please read DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and won't help unless you provide this information when reporting a possible bug.
please attach a backtrace as described in: http://www.gentoo.org/proj/en/qa/backtraces.xml and reopen, thanks!
Created attachment 300757 [details] backtrace.log
I think I have found the problem: mplayer was compiled with the use flag "3dnowext" and the cpu is an Intel core i7, giving an incompatibility. Recompiling mplayer without the "3dnowext" use flag fix the problem.
(In reply to comment #3) > I think I have found the problem: mplayer was compiled with the use flag > "3dnowext" and the cpu is an Intel core i7, giving an incompatibility. > > Recompiling mplayer without the "3dnowext" use flag fix the problem. closing as invalid then ;)
Interestingly, versions of mplayer prior to 1.0_rc4_p20120105 does not crash when compiled and run with the "3dnowext" use flag on a computer with a core i7 processor!
(In reply to comment #5) > Interestingly, versions of mplayer prior to 1.0_rc4_p20120105 does not crash > when compiled and run with the "3dnowext" use flag on a computer with a core i7 > processor! thats probably because i removed the babysitting that was done in previous ebuilds :) before, it ran a check on the running cpu to determine whether to build and use said extensions or not; now, if you enable it, you get it.