From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Jan <tona_kosmicznego_smiecia@interia.pl>
Cc: guix-devel@gnu.org
Subject: Re: Maintaining Jami #3
Date: Tue, 21 Jan 2020 11:12:10 +0100 [thread overview]
Message-ID: <87a76hjeyt.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20200120155324.00935fdc@kompiuter>
[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]
Jan <tona_kosmicznego_smiecia@interia.pl> writes:
> I didn't really answer your questions earlier, sorry.
>
> On Sun, 19 Jan 2020 10:20:51 +0100
> Pierre Neidhardt <mail@ambrevar.xyz> wrote:
>
>> Hi Jan,
>>
>> I tested the Jami package we have in upstream Guix:
>>
>> - It fails to start on my desktop, it only works on my laptop.
> What do you mean by desktop, is it even a difference for the OS and the
> application?
I have a desktop computer and a laptop. Both running a mostly identical
Guix system.
The hardware is different; in particular, the desktop does not have a
mic or a camera, if that matters.
>> - The client kept disconnecting. I could send a few text messages
>> here and there, but most of them didn't go through.
> For me it works, I test it in my local network though. The problem
> begins when you try communicating with someone behind a strong NAT,
> firewall or a badly configured network. Based on my previous experience
> I think that's normal - it have never worked well enough, because ISPs
> don't want you to have control over your networking - client-server
> applications work well, but p2p are broken. Often router firmware is
> buggy, outdated and malicious as nonfree software is.
I've tried between my laptop and an Android. Both were on the local network.
>> - I can receive calls, but when I click on the "pick up" button, Jami
>> crashes.
> Maybe its something hardware specific or depends on the client you call
> with - I have no problem answering calls made from Android.
>> In general, Jami crashed _a lot_. I wonder if it's upstream or if we
>> have something wrong with our package.
>>
>> Did you have a similar experience?
>> Does your work fix any of those issues?
>>
>
> I tested 20200115 version now, and it pretty much works the same.
> Anyway I fixed my private branch and can continue working, but see no
> point in waiting.
>
> What DE are you using? I could try it on my machine.
I run EXWM.
> If you run it on top of Wayland, then you should know Jami is
> currently broken on Wayland, they work on fixing it. Aaaand even if
> client-gnome will continue being broken like this, they're working on
> porting client-windows(Qt) to GNU/Linux and there's a possibility it
> won't be broken as well.
That'd be interesting.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-01-21 10:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 12:05 Maintaining Jami #3 Jan
2020-01-07 18:13 ` Jan
2020-01-18 23:47 ` Jan
2020-01-18 23:51 ` Jan
2020-01-18 23:55 ` Jan
2020-01-19 9:20 ` Pierre Neidhardt
2020-01-19 15:55 ` Jan
2020-01-20 14:53 ` Jan
2020-01-21 10:12 ` Pierre Neidhardt [this message]
2020-01-27 23:12 ` Jan
2020-02-06 21:41 ` Jan
2020-02-07 13:53 ` Pierre Neidhardt
2020-02-07 15:12 ` Jan
2020-02-07 17:17 ` Pierre Neidhardt
2020-02-07 22:34 ` Marius Bakke
2020-02-07 23:28 ` Jan
2020-02-08 1:39 ` Jan
-- strict thread matches above, loose matches on Subject: below --
2020-01-10 20:17 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=87a76hjeyt.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--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).