Ubuntu
gwibber package

gwibber crashed with SIGSEGV. Upon startup. No interaction

Bug #340113 reported by Allan Kristensen
92
This bug affects 15 people
Affects Status Importance Assigned to Milestone
Gwibber
Invalid
Undecided
Unassigned
gwibber (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gwibber

- Just installed Jaunty Alpha-5 fresh
- Update ran succesfully (approx 300 MB)
- Restarted (cold boot)
- Switched "System > Preferences > Appearance > Visual Effects" to "None"
- Added Gwibber PPA, using GUI (System > Administration > Software Sources). Got a warning regarding PUBLIC KEY. Ignored it
- Installed Gwibber, again using GUI (System > Administration > Synaptic Package Manager)
- Startet Gwibber, Applications > Internet > Gwibber Microblogging Client
- Main Gwibber window appeared, but with all white panels, with nothing in them
- Crashed

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 0.8-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_DK.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
 ?? () from /usr/lib/libwebkit-1.0.so.1
Title: gwibber crashed with SIGSEGV
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

See original description
Revision history for this message
Allan Kristensen (allanjorch) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:WTF::Vector<std::pair<KJS::Identifier, unsigned int>, 16u>::operator= (
ScopeNode (this=0xb4e8adc0, children=<value optimized out>,
FunctionBodyNode (this=0xb4e8adc0, children=0xb4e8ade8,
KJS::FunctionBodyNode::create (children=0xb4e85da0,
kjsyyparse (globalPtr=0xb6978fa0)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gwibber:
importance: Undecided → Medium
Dereck Wonnacott (dereck)
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
Omer Akram (om26er) wrote :

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

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gwibber (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Changed in gwibber (Ubuntu):
status: Incomplete → Invalid
Changed in gwibber:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.