[bug#38211,0/9] Update Jami to 20111101

I believe this patchset to be mostly finished.
When I start Jami however, I get the tray icon but I cannot bring up the main interface, it does not show anything.

The console output is the following:


> (jami-gnome:4326): libnotify-WARNING **: 19:01:21.432: Failed to connect to proxy
>
> (jami-gnome:4326): Gtk-WARNING **: 19:01:21.432: Child name 'calls' not found in GtkStack
>
> (jami-gnome:4326): Gtk-CRITICAL **: 19:01:21.631: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
>
> (jami-gnome:4326): dconf-WARNING **: 19:01:21.653: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name ca.desrt.dconf was not provided by any .service files
>
> (jami-gnome:4326): dconf-WARNING **: 19:01:21.680: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name ca.desrt.dconf was not provided by any .service files
>
> (jami-gnome:4326): dconf-WARNING **: 19:01:21.680: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name ca.desrt.dconf was not provided by any .service files
>
> (jami-gnome:4326): dconf-WARNING **: 19:01:21.684: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name ca.desrt.dconf was not provided by any .service files
>
> (jami-gnome:4326): dconf-WARNING **: 19:01:21.684: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name ca.desrt.dconf was not provided by any .service files
> lookup name NOT FOUND: "" "35f9fe00a5e52f6c"
>
> (jami-gnome:4326): dconf-WARNING **: 19:01:21.701: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name ca.desrt.dconf was not provided by any .service files
> lookup name NOT FOUND: "" "35f9fe00a5e52f6c"
>
> (jami-gnome:4326): dconf-WARNING **: 19:01:21.701: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name ca.desrt.dconf was not provided by any .service files


Note that I have this issue with the non-update package as well, so I don't think this is related to the update in this patch.

Maybe because I'm on EXWM?  It used to work a couple months ago though.

We might have something broken in our GTK / GNOME / dconf.
Can anyone test if Jami works on GNOME?

Jan Wielkiewicz (3):
  gnu: Add resample.
  gnu: Add sobjectizer.
  gnu: opendht: Update to 2.0.0beta2.

Pierre Neidhardt (6):
  gnu: Add restinio.
  gnu: pjproject: Update to 2.9.
  gnu: jami: Update to 20191101.3.67671e7.
  gnu: pjproject-jami: Update to 2.9
  gnu: libring: Update to 20191101.
  gnu: jami: Fix wrapper.

 gnu/packages/audio.scm      | 24 ++++++++++
 gnu/packages/cpp.scm        | 32 ++++++++++++++
 gnu/packages/networking.scm | 79 +++++++++++++++++++++++++++++----
 gnu/packages/telephony.scm  | 87 +++++++++++++++++++++++--------------
 4 files changed, 180 insertions(+), 42 deletions(-)

>When I start Jami however, I get the tray icon but I cannot bring up
>the main interface, it does not show anything
> Maybe because I'm on EXWM?  It used to work a couple months ago
> though.
Works on my machine with XFCE, guix pulled, upgraded and reconfigured
yesterday.


Jan Wielkiewicz

Hi,

Patches 5 and 6 are missing in this patchset. I even checked the debbugs
web page for this bug at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38211 , but it isn't
there. Did you forget to send them?

Thanks,
Arun.

This is very strange.  In my Eshell history, patch 5 and 6 are part of
the command I've used to send patches from 3 to 9.  No clue why 2
patches would be missing in the middle.

Anyways, sending again.

Thanks for noticing!

> Anyways, sending again.

I still don't see the missing patches on the debbugs page for this
bug. Did you resend them?

> I believe this patchset to be mostly finished.

This patchset builds successfully. I am able to bring up the main jami
GUI. But, it tries to connect to the Jami daemon, fails and quits
immediately. I get a message box which says "Could not re-connect to the
Jami daemon (dring). Jami will now quit."

Am I missing something? Do I need to start dring somehow?

> Maybe because I'm on EXWM?  It used to work a couple months ago though.

I'm also on EXWM. I don't see any dconf errors in my console
output. Instead, I see the following.

** (jami-gnome:21234): WARNING **: 00:13:08.460: dring has possibly crashed, or has been killed... will wait 2.5 seconds and try to r
econnect                                                                                                                            

** (jami-gnome:21234): WARNING **: 00:13:10.977: Error : dring is not available, make sure it is running

** (jami-gnome:21234): WARNING **: 00:13:10.977: Error : dring is not available, make sure it is running

** (jami-gnome:21234): WARNING **: 00:13:10.977: could not reconnect to the daemon

This is great news!

You should start ring with ring.cx, _not_ gnome-ring.

If it still does not work, try launching dring:

/gnu/store/v9scpdy0zip94gsfl75zlw1alvgi6xkq-libring-20190319.4.a16a99f/lib/ring/dring -dcp

Now if it works for you I really wonder what's wrong with the GUI on my end...

> You should start ring with ring.cx, _not_ gnome-ring.
>
> If it still does not work, try launching dring:
>
> /gnu/store/v9scpdy0zip94gsfl75zlw1alvgi6xkq-libring-20190319.4.a16a99f/lib/ring/dring -dcp

It works for me now, but only after launching dring manually like you
said. Running ring.cx without starting dring failed.

Thank you very much for your work on jami! :-) Jami is of great
importance to the decentralized internet, and it's nice to have it in
Guix.

> Now if it works for you I really wonder what's wrong with the GUI on
> my end...

This is strange, but I think someone who actually understands dconf and
dbus should comment on this. I'm sorry, I don't know enough.

I'll merge the patch then, thanks for testing!

Merged.