Bug 742656 - nautilus dies with python ImportError from "gobject"
Summary: nautilus dies with python ImportError from "gobject"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-30 23:42 UTC by John Ellson
Modified: 2015-03-03 23:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 22:34:55 UTC
Type: ---


Attachments (Terms of Use)

Description John Ellson 2011-09-30 23:42:24 UTC
Description of problem:

ellson@halfpint:~> nautilus
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/gi/__init__.py", line 23, in <module>
    from ._gi import _API, Repository
ImportError: could not import gobject (error was: ImportError('When using gi.repository you must not import static modules like "gobject". Please change all occurrences of "import gobject" to "from gi.repository import GObject".',))
Traceback (most recent call last):
  File "/usr/share/nautilus-python/extensions/nautilus_terminal.py", line 48, in <module>
    from gi.repository import Nautilus, Gtk, Gdk, Vte, GLib
  File "/usr/lib64/python2.7/site-packages/gi/__init__.py", line 23, in <module>
    from ._gi import _API, Repository
ImportError: cannot import name _API
Segmentation fault


Version-Release number of selected component (if applicable):
nautilus-3.2.0-1.fc16.x86_64
pygobject3.x86_64 0:3.0.0-1.fc16
glib2-2.30.0-1.fc16.x86_64

How reproducible:
100%  

Steps to Reproduce:
1. nautilus
2.
3.
  
Actual results:
crash

Expected results:
desktop icons

Additional info:

Comment 1 John Ellson 2011-09-30 23:44:36 UTC
Changing "gobject" to "GObject" in gi/__init__.py as suggested, does seem to fix the problem.

Comment 2 John Ellson 2011-09-30 23:58:20 UTC
Ignore comment #1.  It sort of worked, once, but I still get error messages and it doesn't work on subsequent starts.   I've no idea what I'm doing with all this .py, .pyc, .pyo stuff.

Comment 3 John Ellson 2011-10-01 00:55:55 UTC
Never mind, it seems this bug has been fixed in:

      pygobject3-3.0.1-1.fc16.x86_64.rpm

from Koji.   Are you sure gnome3 is ready for fc16?

Comment 4 Fedora End Of Life 2013-01-16 17:44:42 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 22:34:58 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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