FS#57392 - [ring-daemon] Ring can't be started due to the daemon being unavailable

Attached to Project: Community Packages
Opened by Martin Roth (Captain_Rage) - Tuesday, 06 February 2018, 11:36 GMT
Last edited by Baptiste (zorun) - Wednesday, 07 February 2018, 21:14 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Baptiste (zorun)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I installed ring-gnome (pacman -S ring-gnome) and upon starting it an error message appears
"Ring Error - Unable to initialize. Make sure the Ring daemon (dring) is running. Error: @ - Close".


Additional info:
* package version(s)
community/ring-gnome 3:20180112.2.d0bda53-1 (ring)
* config and/or log files etc.
After starting ring.cx in the terminal:
"[user@Computer ~]$ ring.cx
** Message: Ring GNOME client version: 1.0.0
** Message: git ref: e9669d2871d79903de9a154545ebe59831ef1611
"Error : dring is not available, make sure it is running"

** (gnome-ring:2385): CRITICAL **: Error : dring is not available, make sure it is running
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged."

Steps to reproduce:
Install ring-gnome and try to start Ring and it will complain about the daemon being unavailable.
This task depends upon

Closed by  Baptiste (zorun)
Wednesday, 07 February 2018, 21:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  ring-daemon 2:20180203.1.15ad85f-1
Comment by Doug Newgard (Scimmia) - Tuesday, 06 February 2018, 16:56 GMT
Have you done any troubleshooting at all? Why isn't the daemon running?
Comment by Martin Roth (Captain_Rage) - Wednesday, 07 February 2018, 09:43 GMT
That is indeed the question. According to the Wiki the daemon should be started automatically by the Ring client. It doesn't. When running 'ring.cx -d':

"** (gnome-ring:23463): DEBUG: debug enabled
** Message: Ring GNOME client version: 1.0.0
** Message: git ref: e9669d2871d79903de9a154545ebe59831ef1611
** (gnome-ring:23463): DEBUG: enabling autostart
** (gnome-ring:23463): DEBUG: checking /usr/share/gnome-ring/gnome-ring.desktop
** (gnome-ring:23463): DEBUG: '/home/martin/.config/autostart/gnome-ring.desktop' is already a symlink to '/usr/share/gnome-ring/gnome-ring.desktop'
"Error : dring is not available, make sure it is running"

** (gnome-ring:23463): CRITICAL **: Error : dring is not available, make sure it is running
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged."

I checked that '/usr/share/gnome-ring/gnome-ring.desktop' exists on my system.
Upon using d-feet for debuggning, 'cx.ring.Ring - Activable: yes' shows up under 'Session Bus', but when clicking on it the following appears:
'DBUS Exception - cx.ring.Ring : g-dbus-quark: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process cx.ring.Ring exited with status 127 (25)'.

The 127 exit code seems to indicate that the command was not found or that there is a problem with the path.

pacman -Ql ring-daemon shows:

"ring-daemon /usr/
ring-daemon /usr/include/
ring-daemon /usr/include/dring/
ring-daemon /usr/include/dring/account_const.h
ring-daemon /usr/include/dring/call_const.h
ring-daemon /usr/include/dring/callmanager_interface.h
ring-daemon /usr/include/dring/configurationmanager_interface.h
ring-daemon /usr/include/dring/datatransfer_interface.h
ring-daemon /usr/include/dring/dring.h
ring-daemon /usr/include/dring/media_const.h
ring-daemon /usr/include/dring/presence_const.h
ring-daemon /usr/include/dring/presencemanager_interface.h
ring-daemon /usr/include/dring/security_const.h
ring-daemon /usr/include/dring/videomanager_interface.h
ring-daemon /usr/lib/
ring-daemon /usr/lib/libring.so
ring-daemon /usr/lib/libring.so.0
ring-daemon /usr/lib/libring.so.0.0.0
ring-daemon /usr/lib/ring/
ring-daemon /usr/lib/ring/dring
ring-daemon /usr/share/
ring-daemon /usr/share/dbus-1/
ring-daemon /usr/share/dbus-1/interfaces/
ring-daemon /usr/share/dbus-1/interfaces/cx.ring.Ring.CallManager.xml
ring-daemon /usr/share/dbus-1/interfaces/cx.ring.Ring.ConfigurationManager.xml
ring-daemon /usr/share/dbus-1/interfaces/cx.ring.Ring.Instance.xml
ring-daemon /usr/share/dbus-1/interfaces/cx.ring.Ring.PresenceManager.xml
ring-daemon /usr/share/dbus-1/interfaces/cx.ring.Ring.VideoManager.xml
ring-daemon /usr/share/dbus-1/services/
ring-daemon /usr/share/dbus-1/services/cx.ring.Ring.service
ring-daemon /usr/share/man/
ring-daemon /usr/share/man/man1/
ring-daemon /usr/share/man/man1/dring.1.gz
ring-daemon /usr/share/ring/
ring-daemon /usr/share/ring/ringtones/
ring-daemon /usr/share/ring/ringtones/default.wav
ring-daemon /usr/share/ring/ringtones/konga.ul"
Comment by Doug Newgard (Scimmia) - Wednesday, 07 February 2018, 17:38 GMT
So can the daemon run or is the the version/missing symbol issue that's come up on the forums?
Comment by Martin Roth (Captain_Rage) - Wednesday, 07 February 2018, 17:55 GMT
It's the same issue as described in the forum, yes: https://bbs.archlinux.org/viewtopic.php?id=233679. Ring doesn't start and complains that the daemon is unavailable. I don't know how to start the daemon explicitly, if such a possibilty exists, so I haven't been able to try that.
Since the issue is already described in the forum this might be a duplicate bug report.
Comment by Doug Newgard (Scimmia) - Wednesday, 07 February 2018, 18:12 GMT
  • Field changed: Summary (Ring can't be started due to the daemon being unavailable → [ring-daemon] Ring can't be started due to the daemon being unavailable)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Baptiste (zorun)
Baptiste, it appears that ring-daemon in Community needs opendht that's still in Community-Testing
Comment by Baptiste (zorun) - Wednesday, 07 February 2018, 20:50 GMT
Looks like a messed-up rebuild that happened while ring-daemon was in community-testing, probably yaml-cpp... I have just moved opendht to community, it should fix the issue.
Comment by Baptiste (zorun) - Wednesday, 07 February 2018, 21:14 GMT
Fixed for certain with with ring-daemon 2:20180203.1.15ad85f-1

Loading...