> D-Bus python bindings are missing in this computer
> D-Bus capabilities of Gajim cannot be used
> Traceback (most recent call last):
>   File "gajim.py", line 289, in
>     import gtkexcepthook
>   File
> "/gnu/store/n9bspqi1dim0svkdklaii1rf7hhnhzgx-gajim-0.16.8/share/gajim/src/gtkexcepthook.py",
> line 31, in
>     import dialogs
>   File
> "/gnu/store/n9bspqi1dim0svkdklaii1rf7hhnhzgx-gajim-0.16.8/share/gajim/src/dialogs.py",
> line 48, in
>     import gtkspell
>   File
> "/gnu/store/n9bspqi1dim0svkdklaii1rf7hhnhzgx-gajim-0.16.8/share/gajim/src/gtkspell.py",
> line 43, in
>     libgtkspell = ctypes.cdll.LoadLibrary(libgtkspell_path)
>   File
> "/gnu/store/v7xx78g197xx3vg5gygqn0fjvv6b4i97-python-2.7.13/lib/python2.7/ctypes/__init__.py",
> line 440, in LoadLibrary
>     return self._dlltype(name)
>   File
> "/gnu/store/v7xx78g197xx3vg5gygqn0fjvv6b4i97-python-2.7.13/lib/python2.7/ctypes/__init__.py",
> line 362, in __init__
>     self._handle = _dlopen(self._name, mode)
> OSError: libgtkspell.so.0: cannot open shared object file: No such
> file or directory

Hm... It's already reported, see [1]. All in all, it's no longer a issue
specific to Trisquel, so it's better for the discussion to continue in
bug-guix mailing list ([2]) --- which is tied to [1].

Since you just downloaded/installed Guix, one way around this problem is
to make `guix pull' use a older version of the Guix repository, like
this:

--8<---------------cut here---------------start------------->8---
guix pull --commit="[A commit from Guix reposity before January 3rd, as seen in 
[1] ]"
--8<---------------cut here---------------end--------------->8---

However, this trick doesn't solve the issue itself. And there is no
guarantee that the commit selected will actually make Gajim work again,
you might have to select a commit from a date even earlier.

In cases where you use Guix for a given amount of time already in a
given computer, you can do `guix pull' normally (no need to do it again
if you just did it), then make use of `guix package' ability to do
roll-back and then use the `--do-not-upgrade' option of `guix package'
to select the problematic packages to be held in their working
versions. Again, this doesn't solve the issue itself.

[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29963 .

[2] https://lists.gnu.org/mailman/listinfo/bug-guix/ .

Reply via email to