gwibber crashed with SIGSEGV

Bug #471480 reported by maty
This bug report is a duplicate of:  Bug #434235: gwibber crashed with SIGSEGV. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gwibber

The program didn't respond (the window was grey) and it clicked on it then it crashed.

ProblemType: Crash
Architecture: i386
Date: Mon Nov 2 19:35:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.0.0~bzr476-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x2f93752: movl $0x0,0xbbadbeef
 PC (0x02f93752) ok
 source "$0x0" ok
 destination "0xbbadbeef" (0xbbadbeef) 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
maty (kovacs-m) wrote :
visibility: private → public
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.