Ubuntu
update-manager package

update-manager crashed with RuntimeError in init(): Gtk couldn't be initialized

Bug #1142843 reported by Wanderson on 2013-03-03

This bug affects 8 people

Affects		Status	Importance	Assigned to	Milestone
	update-manager (Ubuntu)	Triaged	Medium	Unassigned

Bug Description

Crash in Ubuntu 13.04 Raring Ringtail

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: update-manager 1:0.183
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic x86_64
ApportVersion: 2.9-0ubuntu2
Architecture: amd64
Date: Sun Mar 3 18:02:18 2013
ExecutablePath: /usr/bin/update-manager
GsettingsChanges:
b'com.ubuntu.update-manager' b'first-run' b'false'
b'com.ubuntu.update-manager' b'launch-time' b'1357385430'
b'com.ubuntu.update-manager' b'show-details' b'true'
b'com.ubuntu.update-manager' b'window-height' b'363'
b'com.ubuntu.update-manager' b'window-width' b'640'
InstallationDate: Installed on 2012-10-30 (124 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/update-manager -c -d
PythonArgs: ['/usr/bin/update-manager', '-c', '-d']
SourcePackage: update-manager
Title: update-manager crashed with RuntimeError in __init__(): Gtk couldn't be initialized
UpgradeStatus: Upgraded to raring on 2013-02-27 (4 days ago)
UserGroups:

Tags:

Revision history for this message

Wanderson (ribeirws) wrote on 2013-03-03:

Aptdaemon.txt Edit (10.8 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt.txt Edit (2.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (13.7 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt.txt Edit (32.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt.txt Edit (78.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (109 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (42.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (767 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (435 bytes, text/plain; charset="utf-8")

Apport retracing service (apport) on 2013-03-03

tags:	removed: need-duplicate-check
Changed in update-manager (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Brian Murray (brian-murray) wrote on 2013-06-19:

This happened to me when I forgot I was ssh'ed into another system and tried to launch update-manager. Did you also happened to be connected via ssh?

information type:	Private → Public
Changed in update-manager (Ubuntu):
status:	New → Confirmed

Revision history for this message

Brian Murray (brian-murray) wrote on 2013-06-19:

There are approximately ~750 reports of this issue as seen at:

https://errors.ubuntu.com/bucket/?id=/usr/bin/update-manager:RuntimeError:/usr/bin/update-manager@114:__init__:__init__

Brian Murray (brian-murray) on 2013-06-26

Changed in update-manager (Ubuntu):
status:	Confirmed → Triaged

Apport retracing service (apport) on 2013-09-11

tags:

added: saucy

Revision history for this message

Jonathan (miareggeti) wrote on 2014-05-01:

It happened to me twice today.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntuupdate-manager package

update-manager crashed with RuntimeError in __init__(): Gtk couldn't be initialized

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
update-manager package

update-manager crashed with RuntimeError in init(): Gtk couldn't be initialized