gwibber crashed with SIGSEGV

Bug #357000 reported by Tom Cameron
This bug report is a duplicate of:  Bug #345704: gwibber crashed with SIGSEGV. Edit Remove
4
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gwibber

Starting Gwibber after a reboot. Running all updated packages as of Apr. 7, 2009 at 08:51 EDT. Window opens without proper decorations or content, then crashes.

This system is using ActiveDirectory authentication with the new version of Likewise Open.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: fglrx
Package: gwibber 0.8-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_US.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-11-generic x86_64
UserGroups: adm admin cdrom dialout kvm lpadmin plugdev sambashare vboxusers

Revision history for this message
Tom Cameron (drdabbles) wrote :

After digging through the errors and a few other bugs, I've found the root cause. gnome-keyring-daemon refused to start, which appears to have been caused by corruption in my .gnupg directory. I simply created a backup of that directory, deleted the original, logged out, and logged back in. I was then able to import my personal keys, since I have backups of those as well.

visibility: private → public
tags: removed: need-amd64-retrace
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.