From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Packaging Jami progress Date: Fri, 03 Jan 2020 07:35:01 +0100 Message-ID: <87sgkx2gkq.fsf@elephly.net> References: <20191215211230.66fea79e@interia.pl> <875zihclep.fsf@elephly.net> <20191222002815.4db8e9ca@interia.pl> <87d0cgpzqo.fsf@elephly.net> <20191223204317.3069e8ba@kompiuter> <20191225023416.0b36b90c@kompiuter> <20191227195731.6b869970@interia.pl> <20191227224639.5b7d1e74@interia.pl> <8736d4kcue.fsf@ambrevar.xyz> <20191228125745.606222a5@kompiuter> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:50967) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1inGzx-0008Jc-4x for guix-devel@gnu.org; Fri, 03 Jan 2020 02:03:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1inGzw-0006eZ-1E for guix-devel@gnu.org; Fri, 03 Jan 2020 02:03:53 -0500 Received: from sender4-of-o51.zoho.com ([136.143.188.51]:21105) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1inGzv-0006aZ-Oj for guix-devel@gnu.org; Fri, 03 Jan 2020 02:03:51 -0500 In-reply-to: <20191228125745.606222a5@kompiuter> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Jan Cc: guix-devel@gnu.org Jan writes: > On Sat, 28 Dec 2019 10:40:09 +0100 > Pierre Neidhardt wrote: > >> This is indeed your problem, I suspect that something broke the >> wrapper somehow. >> Can you share your patch set again? I can have a look. > I didn't really break anything - it works when launching Jami normally > or using the ring.cx script or the jami-gnome script manually. ring.cx > starts both the daemon and the client using "jami-gnome", jami-gnome is > also a script, which exports the path and then starts > ".jami-gnome-real". Jami works during normal use, but I couldn't debug > like this, because by passing only ".jami-gnome-real" which is a > binary, to gdb, the needed path wasn't exported. You can run =E2=80=9Cgdb --args /bin/sh /path/to/wrapper=E2=80=9D and then = "set follow-fork-mode child" in gdb. -- Ricardo