Symbolic link needed in LMDE 64-bit

Open
#18 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux, python
Domain
operating-systems

Research direction

Start by reproducing nemo -q && nemo on a 64-bit LMDE system and inspect how the Python 2.7 shared library is located. Determine whether the missing /usr/lib64/libpython2.7.so.1.0 link belongs in the project or the distribution packaging; done means Nemo's Python extensions initialize without the manual symlink.

Written by the indexing model from the issue text.

Description

Was getting this error:

$ nemo -q && nemo
(nemo:14007): Nemo-Python-WARNING **: g_module_open libpython failed: /usr/lib64/libpython2.7.so.1.0: cannot open shared object file: No such file or directory
ImportError: could not import gobject (error was: '/usr/lib/libpyglib-gi-2.0-python2.7.so.0: undefined symbol: _Py_ZeroStruct')
(nemo:14007): Nemo-Python-WARNING **: pygobject initialization failed
(nemo:14007): Nemo-Python-WARNING **: nemo_python_init_python failed
(nemo:14013): Nemo-Python-WARNING **: g_module_open libpython failed: /usr/lib64/libpython2.7.so.1.0: cannot open shared object file: No such file or directory
ImportError: could not import gobject (error was: '/usr/lib/libpyglib-gi-2.0-python2.7.so.0: undefined symbol: _Py_ZeroStruct')
(nemo:14013): Nemo-Python-WARNING **: pygobject initialization failed
(nemo:14013): Nemo-Python-WARNING **: nemo_python_init_python failed

Needed to:

$ sudo mkdir -p /usr/lib64
$ sudo ln -s /usr/lib/libpython2.7.so.1.0 /usr/lib64/libpython2.7.so.1.0
Dominant language
C
Stars
486
Forks
172
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/nemo-extensions

All issues in linuxmint/nemo-extensions

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.