gwibber crashed with SIGSEGV in g_object_set_valist()

Bug #951749 reported by Sascha
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

1) Ubuntu 12.04 LTS Beta 1 (nightly build)

2) gwibber: Installiert: 3.3.91-0ubuntu2

3) I opened the gwibber main window, to look at the tweets, if gwibber again updates the stream.

4) The window opened and crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gwibber 3.3.91-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sat Mar 10 20:17:47 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gwibber
SegvAnalysis:
 Segfault happened at: 0x2e44a4: mov 0xc(%eax),%eax
 PC (0x002e44a4) 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: Upgraded to precise on 2012-03-10 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users

Revision history for this message
Sascha (skbierm-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #947928, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.