nautilus-python fails to load on 32- and 64-bit systems: g_module_open libpython failed: No such file or directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
RabbitVCS |
Unknown
|
Unknown
|
|||
nautilus-compare |
Won't Fix
|
Undecided
|
Unassigned | ||
nautilus-python |
Fix Released
|
Medium
|
|||
nautilus-python (Debian) |
Fix Released
|
Unknown
|
|||
nautilus-python (Ubuntu) |
Fix Released
|
Undecided
|
Barry Warsaw | ||
Raring |
Won't Fix
|
Undecided
|
Unassigned | ||
python-caja (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
thunarx-python (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I'm running Ubuntu 13.04 (Raring). To see the problem, do these steps on a 64-bit system:
1. Install the python-nautilus package.
2. Install any extension that uses nautilus-python, e.g. the rabbitvcs-nautilus package.
3. From a terminal window, run 'nautilus -q' to exit Nautilus, then run 'nautilus' to start it again.
You'll see this:
(nautilus:3810): Nautilus-
ImportError: could not import gobject (error was: '/usr/lib/
(nautilus:3810): Nautilus-
And of course then the extension will not work.
The problem is that nautilus-python is looking for libpython2.7.so in /usr/lib, but on this system it lives in /usr/lib/
Changed in nautilus-python: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in nautilus-python (Ubuntu Raring): | |
status: | New → Triaged |
Changed in nautilus-python (Debian): | |
status: | Unknown → Fix Released |
Changed in python-caja (Ubuntu Raring): | |
status: | Confirmed → Won't Fix |
Changed in nautilus-compare: | |
status: | New → Won't Fix |
no longer affects: | thunarx-python (Ubuntu Raring) |
no longer affects: | python-caja (Ubuntu Raring) |
Changed in nautilus-python: | |
status: | New → Fix Released |
When building from source, you can work around this by configuring like this:
$ ./configure PYTHON_ LIB_LOC= /usr/lib/ x86_64- linux-gnu