unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jan <tona_kosmicznego_smiecia@interia.pl>
To: guix-devel@gnu.org
Subject: Jami: Bug source investigation
Date: Thu, 9 Apr 2020 01:20:19 +0200	[thread overview]
Message-ID: <20200409012019.3bf4c121@kompiuter> (raw)

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.

This issue is related to pjproject (https://www.pjsip.org/) - the
library implementing SIP, and patches Jami developers apply to it,
which can be found in ring-project/daemon/contrib/src/pjproject/.

I need help of someone experienced to investigate what is the
difference that makes our package crash, that doesn't occur on other
distributions. If we find out, we will hand it to Jami developers
so they can fix it.

Running daemon in the debugging mode:

/lib/ring/dring -pcd

Jami is built on debian 10, fedora 31, ubuntu 19.10 using GCC with
scripts written in python and bash located in ring-project/make-ring.py
and ring-project/scripts.

The source packages are available here:
https://dl.jami.net/release/tarballs/

And the binaries that don't suffer from the bug are here:
https://dl.jami.net/nightly/



Jan Wielkiewicz

             reply	other threads:[~2020-04-08 23:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 23:20 Jan [this message]
2020-04-13 21:21 ` Jami: Bug source investigation (help needed) Jan
2020-04-15 18:31 ` Jami: Bug source investigation Marius Bakke
2020-04-15 18:54   ` 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=20200409012019.3bf4c121@kompiuter \
    --to=tona_kosmicznego_smiecia@interia.pl \
    --cc=guix-devel@gnu.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.
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).