Mplayer segfault on Gutsy x86-64: preinit_libvo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mplayer (Ubuntu) |
Fix Released
|
Undecided
|
Mario Limonciello |
Bug Description
Mplayer worked perfectly on Feisty before I upgraded. I have tried doing a purge remove and then reinstalling mplayer. If I disable compiz and reboot it still occurs. I've tried different -vo's including x11 gl gl2 xv. I rebuild the ~/.gstreamer-0.10 directory in case there was something that was kept from my upgrade from Feisty.
Most importantly, mplayer will play my videos at first but if I start a new mplayer later in my gnome session this is when it will crash! When I reboot or restart X mplayer begins working again. It seems to be something with the screensaver.
Happens with every video. Using the Gutsy nvidia-new drivers. Running AMD64.
Someone else has the same problem here: http://
And one more thing ... I tried using Valgrind from the instructions at https:/
Terminal output:
$ mplayer -v options Monster\ -\ 30.avi
MPlayer 2:1.0~rc1-0ubuntu13 (C) 2000-2006 MPlayer Team
.......
Using built-in default codecs.conf.
.......
Clip info:
Software: VirtualDubMod 1.5.10.1 (build 2366/release)
get_path('sub/') -> '/home/
xscreensaver_
X11 opening display: :0.0
vo: X11 color mask: FFFFFF (R:FF0000 G:FF00 B:FF)
vo: X11 running at 1280x1024 with depth 24 and 32 bpp (":0.0" => local display)
[x11] Detected wm supports NetWM.
[x11] Detected wm supports FULLSCREEN state.
[x11] Detected wm supports ABOVE state.
[x11] Detected wm supports BELOW state.
[x11] Current fstype setting honours FULLSCREEN ABOVE BELOW X atoms
Disabling DPMS
DPMSDisable stat: 1aver window.
MPlayer interrupted by signal 11 in module: preinit_libvo
- MPlayer crashed by bad usage of CPU/FPU/RAM.
...... (edited out debug info) .....
vo: uninit ...
Changed in mplayer: | |
assignee: | nobody → superm1 |
status: | Confirmed → In Progress |
This bug also is the cause of the "slow startup" problem for mplayer it seems too (at least in my case). I've temporary resolved this problem by turning my screensaver off.