From: Marius Bakke <mbakke@fastmail.com>
To: Jan <tona_kosmicznego_smiecia@interia.pl>, guix-devel@gnu.org
Subject: Re: Jami: Bug source investigation
Date: Wed, 15 Apr 2020 20:31:01 +0200 [thread overview]
Message-ID: <87blnsiot6.fsf@devup.no> (raw)
In-Reply-To: <20200409012019.3bf4c121@kompiuter>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
Jan <tona_kosmicznego_smiecia@interia.pl> writes:
> Hello,
>
> so I tested Jami on core-updates and it didn't fix the bug
> (https://git.jami.net/savoirfairelinux/jami-packaging/issues/63)
>
> Here's my work up to now, it is on wip-jami branch:
> https://gitlab.com/kromka_chleba/jami-package-and-other-things-for-guix/-/tree/wip-jami
> https://gitlab.com/kromka_chleba/jami-package-and-other-things-for-guix.git
>
> What happens is when making an audio call and then pressing the red
> "disconnect" button, Jami daemon (dring) stops with the following
> message:
>
> dring: ../src/pjsip-ua/sip_inv.c:246: pjsip_inv_dec_ref: Assertion `inv
> && inv->ref_cnt' failed.
It looks like this problem was fixed a while back:
https://trac.pjsip.org/repos/ticket/2240
https://github.com/pjsip/pjproject/commit/d5a9caf6aac077c157fa6b20c770385c2355973d
Have you tried updating pjproject to 2.10?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-04-15 18:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 23:20 Jami: Bug source investigation Jan
2020-04-13 21:21 ` Jami: Bug source investigation (help needed) Jan
2020-04-15 18:31 ` Marius Bakke [this message]
2020-04-15 18:54 ` Jami: Bug source investigation Jan
2020-04-16 8:16 ` Pierre Neidhardt
2020-04-16 11:57 ` Jan
2020-04-17 0:53 ` Jan
2020-05-03 7:54 ` Pierre Neidhardt
2020-05-03 14:05 ` Jan
2020-05-03 14:17 ` Pierre Neidhardt
2020-05-03 14:50 ` Jan
2020-05-03 15:26 ` Pierre Neidhardt
2020-05-03 15:28 ` sirgazil
2020-05-03 16:11 ` Jan
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blnsiot6.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=tona_kosmicznego_smiecia@interia.pl \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).