282163 – wicd-client and emesene -- import gtk failed starting everytime

Bug 282163 - wicd-client and emesene -- import gtk failed starting everytime

Summary: wicd-client and emesene -- import gtk failed starting everytime

Status:	VERIFIED TEST-REQUEST

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:	SOLVED
Keywords:

Depends on:
Blocks:

Reported:	2009-08-21 06:34 UTC by Diego Flórez
Modified:	2009-08-22 02:55 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Diego Flórez 2009-08-21 06:34:28 UTC

wicd-client chashed at start,
when i try wicd-client, i get the next: 

$ wicd-client
Traceback (most recent call last):
  File "/usr/lib/wicd/wicd-client.py", line 38, in <module>
    import gtk
ImportError: No module named gtk


when i try wicd, i get:

# wicd
Traceback (most recent call last):
  File "/usr/lib/wicd/wicd-daemon.py", line 44, in <module>
    import gobject
ImportError: No module named gobject


Reproducible: Always




It's happened after did

emerge --newuse --deep --update world

Comment 1 Patrick Lauer gentoo-dev

2009-08-21 11:13:35 UTC

You did an incomplete python update.
Running python-updater should solve it, if that fails emerging pygobject and pygtk manually should.

Comment 2 Diego Flórez 2009-08-22 02:55:01 UTC

(In reply to comment #1)

> You did an incomplete python update.
> Running python-updater should solve it, if that fails emerging pygobject and
> pygtk manually should.


Perfect Patrick!!! Thanks for your help.

# emerge pygtk pygobject dbus-python 
has solved the whole problem.

I preferred do 
# unmerge pygtk pygobject dbus-python python-updater 
And then
# emerge --newuse --update --deep world