gwibber crashed with SIGSEGV

Bug #454068 reported by Gregory
This bug report is a duplicate of:  Bug #434235: gwibber crashed with SIGSEGV. Edit Remove
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: gwibber

Had started Gwibber some time before, but not interacted with it. Brought up window, went to switch from "Home" to "Messages." Didn't switch, then window grayed out. Program crashed about a minute later.

ProblemType: Crash
Architecture: i386
Date: Sat Oct 17 09:19:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: gwibber 2.0.0~bzr466-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x4af70d9: cmpb $0x0,0x272(%eax)
 PC (0x04af70d9) ok
 source "$0x0" ok
 destination "0x272(%eax)" (0x5c400272) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
Title: gwibber crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Gregory (pouk-ledden) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:WebCore::DocumentLoader::stopLoading (this=0xb4cfc000,
WebCore::FrameLoader::stopAllLoaders (this=0xb57d2a28,
WebCore::FrameLoader::continueLoadAfterNavigationPolicy (
WebCore::FrameLoader::callContinueLoadAfterNavigationPolicy
WebCore::PolicyCheck::call (this=0xbfb8d084,

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

I tried to reproduce this issue in gwibber (2.0.0 bzr478) and works fine for me, Can you try to reproduce this issue in latest version of gwibber? Thanks!

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