gwibber crashed with SIGSEGV

Bug #349474 reported by Tristan Greaves
This bug report is a duplicate of:  Bug #345704: gwibber crashed with SIGSEGV. Edit Remove
46
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Gwibber
New
Undecided
Unassigned
gwibber (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: gwibber

This crash occured on application startup after installation. The start window came up, but empty, and totally unresponsive. After a few seconds it crashed.

It ran correctly on second execution.

ProblemType: Crash
Architecture: amd64
Disassembly: 0x60000006:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: gwibber 0.8-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gwibber
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libwebkit-1.0.so.1
 ?? () from /usr/lib/libwebkit-1.0.so.1
 ?? () from /usr/lib/libwebkit-1.0.so.1
 ?? () from /usr/lib/libwebkit-1.0.so.1
Title: gwibber crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare vboxusers

Revision history for this message
Tristan Greaves (tristan-extricate) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
KJS::ParserRefCounted::deleteNewObjects ()
KJS::Parser::parse (this=0x7fc5bce215a0,
KJS::Parser::parse<KJS::ProgramNode> (this=
KJS::Interpreter::evaluate (exec=0x7fc5bcd65f78,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in gwibber:
importance: Undecided → Medium
visibility: private → public
Revision history for this message
Alexander Sack (asac) wrote :

pushing a bunch of ubuntu gwibber crashes upstream. If gwibber devs want us to just close them instead let me know (through identi.ca ;)?

Changed in gwibber (Ubuntu):
status: New → Triaged
Revision history for this message
Andy Duffell (andy-duffell) wrote :

Also seeing this same crash myself, except 100% reproducible. Blank window opens then crashes after a few seconds every time. I'm not able to get Gwibber 0.8-0ubuntu5 to run at all.

Command line output:

/usr/lib/python2.6/dist-packages/gwibber/microblog/support/facelib.py:47: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import md5
console message: @1: ReferenceError: Can't find variable: addMessages
console message: @22: ReferenceError: Can't find variable: setGtkConfig
console message: @1: ReferenceError: Can't find variable: setAccountConfig
console message: @1: ReferenceError: Can't find variable: addMessages
console message: @22: ReferenceError: Can't find variable: setGtkConfig
console message: @1: ReferenceError: Can't find variable: setAccountConfig
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.6/threading.py", line 525, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.6/threading.py", line 477, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 991, in process
    self.manage_indicator_items(view.message_store, tab_num=self.tabs.page_num(tab))
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 948, in manage_indicator_items
    if not self.is_gwibber_active():
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 945, in is_gwibber_active
    return self.window.xid == screen.get_active_window().get_xid()
AttributeError: 'NoneType' object has no attribute 'get_xid'

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.