jami-client-gnome not connecting to daemon

jami-client-gnome not connecting to daemon

[nightowl]

I have been trying out the jami-client-gnome application.  I had this 
working between two computers, one running guixSD, but after I updated 
the guix distribution, I get an error when I start jami.  It says,

'could not re-connect to the jami daemon'

Then it quits.  The last couple of updates to guix seem to have changed 
a few things, for one I notice the gnome desktop manager is now used for 
the login.  I had some troubles with the network service not starting, 
but that seems ok now though I did not do anything in particular to 
address that.  I ask herd it's status and it says following services are 
stopped:

elogind
ntpd
term-auto
upower-daemon
user-homes

Though gnome desktop seems to be operating ok without these.  Is that 
ok, or could it be contributing to the problem with jami?

I also get a generic icon for jami in the menu but that has been the 
case ever since I installed it.  Should there be an icon for jami?

I am wondering how to get jami working again.

jami-client-gnome not connecting to daemon

[Chris Marusich]

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

Hi nightowl,

I'm replying to your email here:

https://lists.gnu.org/archive/html/help-guix/2019-04/msg00093.html

I encountered this myself just now.  It occurred after I installed Jami
to a stand-alone profile (e.g., "guix package -p
/home/marusich/.jami-profile -i jami-client-gnome").  I was able to work
around it by running:

/run/current-system/profile/bin/dbus-run-session /home/marusich/.jami-profile/bin/gnome-ring

I'm not sure why it didn't work out of the box.  The source code for the
package definition ("guix edit jami-client-gnome") suggests that the
daemon should be automatically started by DBUS.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: jami-client-gnome not connecting to daemon

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 196 bytes --]

Ha!  That's a good hunch.
So I suppose that ring.cx is only able to find the daemon if it's in the
PATH.

Is ~/.jami-profile/bin in your PATH?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]