From: Max-FT <Max-FT@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Gajim fails to open with error "Namespace Soup not available"
Date: Mon, 06 Jul 2020 20:55:58 +0200 [thread overview]
Message-ID: <20200706185558.xeI0Mu3ovJ5a6b1GL37OMKi5CG0ZvMzWcZ-aFbV0KLM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23424@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
Closed issue by Max-FT on void-packages repository
https://github.com/void-linux/void-packages/issues/23424
Description:
# System
* xuname:
Void 5.7.7_1 x86_64 GenuineIntel uptodate rFFFF
* package:
gajim-1.2.0_1
### Expected behavior
The Application opens as expected
### Actual behavior
Application fails with
No translations found
Dirs searched: [PosixPath('/usr/local/share'), PosixPath('/usr/share')]
Traceback (most recent call last):
File "/bin/gajim", line 11, in <module>
load_entry_point('gajim==1.2.0', 'gui_scripts', 'gajim')()
File "/usr/lib/python3.8/site-packages/gajim/gajim.py", line 151, in main
_check_required_deps()
File "/usr/lib/python3.8/site-packages/gajim/gajim.py", line 46, in _check_required_deps
import nbxmpp
File "/usr/lib/python3.8/site-packages/nbxmpp/__init__.py", line 5, in <module>
gi.require_version('Soup', '2.4')
File "/usr/lib/python3.8/site-packages/gi/__init__.py", line 129, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Soup not available
### Steps to reproduce the behavior
Attempt to launch Gajim 1.2
next prev parent reply other threads:[~2020-07-06 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 18:44 [ISSUE] " Max-FT
2020-07-06 18:51 ` ericonr
2020-07-06 18:55 ` Max-FT
2020-07-06 18:55 ` Max-FT [this message]
2020-07-06 18:57 ` ericonr
2020-07-06 19:00 ` Max-FT
2021-01-21 17:55 ` ericonr
2021-01-21 18:11 ` mobinmob
2021-01-21 18:12 ` mobinmob
2021-01-21 18:44 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200706185558.xeI0Mu3ovJ5a6b1GL37OMKi5CG0ZvMzWcZ-aFbV0KLM@z \
--to=max-ft@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).