Comment 0 for bug 947928

Don't know what happened. I searched in the Dash for gedit by typing 'edi' hit ENTER and Gwibber showed up. I close Gwibber, re opened the Dash, verified that it shows gedit (it did) and pressed again ENTER to launch this time successfully gedit. After some seconds the Gwibber crash report appeared...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gwibber 3.3.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Tue Mar 6 13:04:48 2012
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120227)
ProcCmdline: gwibber
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x3b4dd4: mov 0xc(%eax),%eax
 PC (0x003b4dd4) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 g_object_set_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_set () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 gwibber_gtk_stream_view_tile_set_details () from /usr/lib/libgwibber-gtk.so.2
Title: gwibber crashed with SIGSEGV in g_object_set_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo