Ubuntu
deluge package

deluge-gtk crashed with ImportError: could not import gio

Bug #507049 reported by norbert-bug on 2010-01-13

This bug report is a duplicate of: Bug #507046: deluge crashed with ImportError: could not import gio. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	deluge (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: deluge

pinio@piniobook:~$ lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04

pinio@piniobook:~$ apt-cache policy deluge-gtk
deluge-gtk:
  Zainstalowana: 1.2.0~rc5-1
  Kandydująca: 1.2.0~rc5-1
  Tabela wersji:
*** 1.2.0~rc5-1 0
        500 http://pl.archive.ubuntu.com lucid/universe Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
Date: Tue Jan 12 18:17:45 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/deluge-gtk
InterpreterPath: /usr/bin/python2.6
Package: deluge-gtk 1.2.0~rc5-1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/deluge-gtk
ProcEnviron:
SHELL=/bin/bash
LANG=pl_PL.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
PythonArgs: ['/usr/bin/deluge-gtk']
SourcePackage: deluge
Tags: lucid
Title: deluge-gtk crashed with ImportError: could not import gio
Traceback: ImportError: could not import gio
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video

Tags:

Revision history for this message

norbert-bug (dalmatyn) wrote on 2010-01-13:

Dependencies.txt Edit (3.9 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (17.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (805 bytes, text/plain; charset="utf-8")

visibility:

private → public

Apport retracing service (apport) on 2010-01-13

tags:

removed: need-duplicate-check

Revision history for this message

Charles Kerr (charlesk) wrote on 2010-01-30:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 507046, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.