Bug 765931

Summary: [abrt] deluge-gtk-1.3.3-1.fc16: could not import bonobo.ui
Product: [Fedora] Fedora Reporter: Timo Skar <timoskar>
Component: delugeAssignee: Rahul Sundaram <metherid>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: calumlind, ggillies, igor.redhat, justinnoah, marek90, metherid
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:2faf2f7231d55384b36cebd173b04fe12bdd5ea7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-13 22:41:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: smolt_data none

Description Timo Skar 2011-12-09 17:45:45 UTC 
libreport version: 2.0.7
abrt_version:   2.0.6
cmdline:        /usr/bin/python /usr/bin/deluge-gtk
comment:        I got this error when I tried to connect to another instance of deluge, that is running on another server.
executable:     /usr/bin/deluge-gtk
kernel:         3.1.2-1.fc16.i686
reason:         could not import bonobo.ui
time:           fr. 09. des. 2011 kl. 18.08 +0100
uid:            1000
username:       timo

smolt_data:     Text file, 3215 bytes

backtrace:
:could not import bonobo.ui
:
:ImportError: could not import bonobo.ui
Comment 1 Timo Skar 2011-12-09 17:45:48 UTC 
Created attachment 544637 [details]
File: smolt_data
Comment 2 Marek Michał Mazur 2011-12-10 00:58:01 UTC 
Package: deluge-gtk-1.3.3-1.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment
-----
Starting Deluge.
Comment 3 igor.redhat@gmail.com 2011-12-12 19:00:04 UTC 
Package: deluge-gtk-1.3.3-1.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment
-----
This happened when starting deluge
Comment 4 Calum 2011-12-13 22:41:46 UTC 

*** This bug has been marked as a duplicate of bug 689836 ***