Bug 702879 - gnochm is not able to import gobject
Summary: gnochm is not able to import gobject
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnochm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Haïkel Guémar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-07 23:06 UTC by Francesco Tapparo
Modified: 2011-05-21 13:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-21 13:01:01 UTC
Type: ---


Attachments (Terms of Use)

Description Francesco Tapparo 2011-05-07 23:06:01 UTC
Description of problem:
gnochm won't start

Version-Release number of selected component (if applicable):
rawhide

How reproducible:


Steps to Reproduce:
1. download fedora nightly (as at sunday 8/5/2011)
2. start gnochm at the terminal
3.
  
Actual results:
gnochm stops with the following message
You do not have all of the required Python modules to run gnochm.
Check the gnochm README file for tips on how to fix this.
What follows is the error description highlighting the problematic module.

could not import gobject (could not find _PyGObject_API object)


Expected results:
gnochm should start and show its window

Additional info:
the package pygobject2.i686 is correctly installed. I also tried to install the devel package but it did not help.

Comment 1 Francesco Tapparo 2011-05-21 13:01:01 UTC
I updated the system right now and now gnochm start correctly, so the bug seems solved to me.
This is the list of updated packages in this resolutive update:

hplip-common-3.11.5-2.fc15.i686
hplip-libs-3.11.5-2.fc15.i686
gnome-keyring-3.0.2-1.fc15.i686
python-nose-1.0.0-3.fc15.noarch
python-smbc-1.0.11-1.fc15.i686
gnome-keyring-pam-3.0.2-1.fc15.i686
libsane-hpaio-3.11.5-2.fc15.i686
gnome-packagekit-3.0.0-5.fc15.i686
dash-0.5.6-4.fc15.i686
libgdata-0.8.1-1.fc15.i686


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