check-new-release-gtk crashed with RuntimeError in /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py: Gtk couldn't be initialized

Bug #828835 reported by Eliah Kagan
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I logged into a 3D Unity session on a Oneiric i386 system with update-manager 1:0.152.14 and was soon informed that the Update Manager had crashed.

I do not have any more information about this problem, except that a crash in oneconf occurred twice shortly thereafter, which I could not report due to outdated packages. I suspect the oneconf crash is unrelated to this crash in check-new-release-gtk.

This resembles, but is probably not the same bug as, bug 721421, bug 729387, bug 730569, and perhaps others. Bug 730569 is fixed; if this bug has a similar cause, perhaps it could be similarly fixed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: update-manager 1:0.152.14
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic i686
Architecture: i386
Date: Wed Aug 17 12:42:30 2011
ExecutablePath: /usr/lib/update-manager/check-new-release-gtk
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/update-manager/check-new-release-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/lib/update-manager/check-new-release-gtk']
SourcePackage: update-manager
Title: check-new-release-gtk crashed with RuntimeError in /usr/lib/python2.7/dist-packages/gi/overrides/Gtk.py: Gtk couldn't be initialized
UpgradeStatus: Upgraded to oneiric on 2011-06-18 (61 days ago)
UserGroups: adm admin dialout lpadmin plugdev sambashare

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
visibility: private → public
description: updated
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in update-manager (Ubuntu):
status: New → Confirmed
Changed in update-manager (Ubuntu):
importance: Undecided → Medium
Revision history for this message
dino99 (9d9) wrote :

This version has expired

Changed in update-manager (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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