gnome-mplayer crashed with SIGABRT in __GI___poll()

[Chenheting]

Gnome-Mplayer stoped and crashed during playing.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-mplayer 1.0.5-1
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Wed Feb 8 20:38:45 2012
ExecutablePath: /usr/bin/gnome-mplayer
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gnome-mplayer /home/username/Downloads/Madonna\ -\ Half\ Time\ Show\ (Super\ Bowl\ 2012)\ HD\ 720p.mp4
ProcEnviron:
 LANGUAGE=en_SG:en
 PATH=(custom, no user)
 LANG=en_SG.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-mplayer
StacktraceTop:
 poll () from /lib/i386-linux-gnu/libc.so.6
 g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
 gtk_main () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
Title: gnome-mplayer crashed with SIGABRT in poll()
UpgradeStatus: Upgraded to precise on 2012-01-27 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __GI___poll (fds=0x9b1ee00, nfds=9, timeout=40) at ../sysdeps/unix/sysv/linux/poll.c:87
 g_poll (fds=0x9b1ee00, nfds=9, timeout=40) at /build/buildd/glib2.0-2.31.16/./glib/gpoll.c:132
 g_main_context_poll (n_fds=9, fds=0x9b1ee00, timeout=<optimized out>, context=0x98c5638, priority=<optimized out>) at /build/buildd/glib2.0-2.31.16/./glib/gmain.c:3412
 g_main_context_iterate (dispatch=1, block=7276512, context=0x98c5638, self=<optimized out>) at /build/buildd/glib2.0-2.31.16/./glib/gmain.c:3113
 g_main_context_iterate (context=0x98c5638, block=7276512, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.31.16/./glib/gmain.c:3055

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastian Ramacher (s-ramacher)]

Please try 1.0.7-2 and report back if this is still an issue.

[Sebastian Ramacher (s-ramacher)]

Closing this now. Without further information, it doesn't make sense to keep this bug open any longer.