gwibber crashed with SIGSEGV in gdk_window_enable_synchronized_configure()

Bug #763970 reported by Wuilmer Bolívar
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gwibber

Ubuntu 11.04

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber 3.0.0.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic-pae 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic-pae i686
Architecture: i386
Date: Sun Apr 17 14:54:25 2011
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 PATH=(custom, no user)
 LANG=
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x339d0d <gdk_window_enable_synchronized_configure+29>: mov 0xc(%edi),%esi
 PC (0x00339d0d) ok
 source "0xc(%edi)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 gdk_window_enable_synchronized_configure () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gwibber crashed with SIGSEGV in gdk_window_enable_synchronized_configure()
UpgradeStatus: Upgraded to natty on 2011-04-01 (16 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mythtv netdev plugdev sambashare tape users video voice

Revision history for this message
Wuilmer Bolívar (elwuilmer) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 IA__gdk_window_enable_synchronized_configure (window=0x0) at /build/buildd/gtk+2.0-2.24.4/gdk/x11/gdkwindow-x11.c:5448
 gtk_window_realize (widget=0x9cbc040) at /build/buildd/gtk+2.0-2.24.4/gtk/gtkwindow.c:4949
 g_cclosure_marshal_VOID__VOID (closure=0x9d5af38, return_value=0x0, n_param_values=1, param_values=0x9bf1678, invocation_hint=0xbfd03e60, marshal_data=0x1261920) at /build/buildd/glib2.0-2.28.5/./gobject/gmarshal.c:79
 g_type_class_meta_marshal (closure=0x9d5af38, return_value=0x0, n_param_values=1, param_values=0x9bf1678, invocation_hint=0xbfd03e60, marshal_data=0x74) at /build/buildd/glib2.0-2.28.5/./gobject/gclosure.c:878
 g_closure_invoke (closure=0x9d5af38, return_value=0x0, n_param_values=1, param_values=0x9bf1678, invocation_hint=0xbfd03e60) at /build/buildd/glib2.0-2.28.5/./gobject/gclosure.c:767

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Victor Vargas (kamus) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.

This will help us to find and resolve the problem.

Changed in gwibber (Ubuntu):
status: New → Incomplete
Revision history for this message
Wuilmer Bolívar (elwuilmer) wrote :

Sorry for the delay, the problem was solved with the new version

Revision history for this message
Victor Vargas (kamus) wrote :

Closed then, thanks.

Changed in gwibber (Ubuntu):
status: Incomplete → Invalid
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.