gwibber crashed with SIGILL

Bug #437932 reported by Lucky Jacobs
This bug report is a duplicate of:  Bug #437226: gwibber crashed with SIGILL. Edit Remove
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gwibber

When trying to get authentication from Facebook Gwibber freezes then crashes.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Sep 27 22:48:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: gwibber 2.0.0~bzr449-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
Signal: 4
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
Title: gwibber crashed with SIGILL
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Lucky Jacobs (lucky-jacobs) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
JSC::Interpreter::execute (this=0x1f8, program=0xbf926890,
JSC::evaluate (exec=0xb4e54ae4, scopeChain=@0xb4e54aa0,
WebCore::ScriptController::evaluate (this=0xb60e5388,
WebCore::FrameLoader::executeScript (this=0xb60e5128,

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
Revision history for this message
Alex Valavanis (valavanisalex) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 437226, so it 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. Feel free to continue to report any other bugs you may find.

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.