2013-08-28, 14:51
Just for kicks I decided to set up a separate Intel system running on HD2500 (vs. HD4000 as previously tested on my main XBMC rig) and playing the problematic MKV file with VAAPI enabled.
This is also running in a "pure" Fluxbox session, which as expected made no difference from when running under the Cinnamon WM.
For the record, Fluxbox (and IceWM, XFCE4 et al.) does not play along nice with this multi-screen setup and consistently launches XBMC on the wrong output port and
the wrong refresh rate; even when force-feeding the same xrandr settings (and obviously using the same xorg.conf as before).
Nevertheless, the segmentation fault issue behaves the same regardless of running in a dual-output config or not, so it is not a showstopper
for debugging this problem.
XBMC debug log: http://pastebin.com/8gTZtq7y
GDB backtrace: http://pastebin.com/fRTgVTRd
Let me know if further output is needed. I can also provide a sample of the MKV file on Dropbox.
This is also running in a "pure" Fluxbox session, which as expected made no difference from when running under the Cinnamon WM.
For the record, Fluxbox (and IceWM, XFCE4 et al.) does not play along nice with this multi-screen setup and consistently launches XBMC on the wrong output port and
the wrong refresh rate; even when force-feeding the same xrandr settings (and obviously using the same xorg.conf as before).
Nevertheless, the segmentation fault issue behaves the same regardless of running in a dual-output config or not, so it is not a showstopper
for debugging this problem.
XBMC debug log: http://pastebin.com/8gTZtq7y
GDB backtrace: http://pastebin.com/fRTgVTRd
Let me know if further output is needed. I can also provide a sample of the MKV file on Dropbox.