Problem replaying trace on Mesa 10.1.4

[io.github.apitrace at io7m.com]

Hello.

I am unable to replay the following trace:

  http://waste.io7m.com/2014/05/26/viewer.trace.0

$ glretrace -vvv viewer.trace.0
...
1 1927 glGetString(name = GL_SHADING_LANGUAGE_VERSION) = "1.30"
1 1928 glGetError() = GL_NO_ERROR
1 1929 glXMakeContextCurrent(dpy = 0x7f8a4400b040, draw = 0, read = 0, ctx = NULL) = True
1 1930 glXCreateContextAttribsARB(dpy = 0x7f8a4400b040, config = 0x7f8a44043de0, share_context = NULL, direct = True, attrib_list = {GLX_CONTEXT_MAJOR_VERSION_ARB, 4, GLX_CONTEXT_MINOR_VERSION_ARB, 4, GLX_RENDER_TYPE, 0x8014, GLX_CONTEXT_FLAGS_ARB, 0x0, GLX_CONTEXT_PROFILE_MASK_ARB, GLX_CONTEXT_CORE_PROFILE_BIT_ARB, 0}) = NULL
X Error of failed request:  GLXBadFBConfig
  Major opcode of failed request:  156 (GLX)
  Minor opcode of failed request:  34 ()
  Serial number of failed request:  45
  Current serial number in output stream:  44

$ glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.4
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.1.4
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:

$ uname -a
Linux viper 3.14.4-1-ARCH #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014 x86_64 GNU/Linux

$ X -version
X.Org X Server 1.15.1
Release Date: 2014-04-13
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.14.0-4-ARCH x86_64 
Current Operating System: Linux viper 3.14.4-1-ARCH #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014 x86_64
Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda3 ro vga=773 init=/usr/lib/systemd/systemd initrd=../initramfs-linux.img
Build Date: 14 April 2014  08:39:09AM
 
Current version of pixman: 0.32.4
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.

Any ideas why this has suddenly broken? I used apitrace a few months ago and didn't have these issues,
so this would seem to be reasonably recent breakage.

M