gnome-sound-recorder crashed with SIGSEGV in gsr_window_finalize()

[Carl Pedersen]

Testing ubuntu 12.04 rc1 on a fit-pc2.
gnome-media version 2.91.2-3ubuntu5
Closing the sound recorder with discard the record after an unsuccesful recording made it hang for some time.
A moment later the error report dialog showed up (the delay probably due to the speed of the cpu).

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-media 2.91.2-3ubuntu5
Uname: Linux 3.3.0-rc4-190212 i686
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Wed Feb 22 16:23:59 2012
ExecutablePath: /usr/bin/gnome-sound-recorder
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: gnome-sound-recorder
ProcEnviron:
 PATH=(custom, no user)
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8053f26: movl $0x0,0x14(%eax)
 PC (0x08053f26) ok
 source "$0x0" ok
 destination "0x14(%eax)" (0x00000014) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-media
StacktraceTop:
 ?? ()
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 gtk_main_do_event () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
Title: gnome-sound-recorder crashed with SIGSEGV in g_object_unref()
UpgradeStatus: Upgraded to precise on 2012-02-07 (15 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 gsr_window_finalize (object=0x8bf0040) at gsr-window.c:2635
 g_object_unref (_object=0x8bf0040) at /build/buildd/glib2.0-2.31.18/./gobject/gobject.c:3018
 gtk_main_do_event (event=0x8b43d20) at /build/buildd/gtk+3.0-3.3.16/./gtk/gtkmain.c:1598
 _gdk_event_emit (event=0x8b43d20) at /build/buildd/gtk+3.0-3.3.16/./gdk/gdkevents.c:71
 gdk_event_source_dispatch (source=0x898c9c8, callback=0, user_data=0x0) at /build/buildd/gtk+3.0-3.3.16/./gdk/x11/gdkeventsource.c:360

[Launchpad Janitor (janitor)]

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