[SFLphone] SFLphone stopped working

[Emmanuel Milou]

The general cause is that the daemon could not start properly, so when
the GNOME client tried to connect to it at startup, it couldn't.

You will have to provide further information if you want me to help you
more. Start the daemon in a terminal (/usr/lib/sflphone/sflphoned) to
see what's wrong and post the debug here. 

Thank you 


On Fri, 2009-10-23 at 12:13 -0700, Albixman wrote:
> Any idea about the reason of these kind of errors?
> Any suggestion?
> 
> ~$ sflphone-client-gnome
> SFLphone 0.9.6
> Copyright (c) 2005 2006 2007 2008 2009 Savoir-faire Linux Inc.
> This is free software.  You may redistribute copies of it under the terms of
> the GNU General Public License Version 3 <http://www.gnu.org/licenses/gpl.html>.
> There is NO WARRANTY, to the extent permitted by law.
> 
> [stdout] ERROR    org.sflphone.gtk - Failed to call register() on
> instanceProxy: Did not receive a reply. Possible causes include: the
> remote application did not send a reply, the message bus security
> policy blocked the reply, the reply timeout expired, or the network
> connection was broken.
> [stdout] ERROR    org.sflphone.gtk - Error while calling
> get_account_list: Did not receive a reply. Possible causes include:
> the remote application did not send a reply, the message bus security
> policy blocked the reply, the reply timeout expired, or the network
> connection was broken.
> [stdout] ERROR    org.sflphone.gtk - Failed to call get_codec_list()
> on ConfigurationManager: Did not receive a reply. Possible causes
> include: the remote application did not send a reply, the message bus
> security policy blocked the reply, the reply timeout expired, or the
> network connection was broken.
> [stdout] ERROR    org.sflphone.gtk - Failed to call
> get_active_codec_list() on ConfigurationManager: Activation of
> org.sflphone.SFLphone timed out
> [stdout] ERROR    org.sflphone.gtk - Failed to call
> get_codec_details() on ConfigurationManager: Did not receive a reply.
> Possible causes include: the remote application did not send a reply,
> the message bus security policy blocked the reply, the reply timeout
> expired, or the network connection was broken.
> Segmentation fault
> _______________________________________________
> SFLphone mailing list
> SFLphone at lists.savoirfairelinux.net
> http://lists.savoirfairelinux.net/mailman/listinfo/sflphone


-- 
Emmanuel Milou
Consultant en Logiciel Libre
Savoir-Faire Linux Inc.
emmanuel.milou at savoirfairelinux.com
514-276-5468 poste 136
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.savoirfairelinux.net/pipermail/sflphone/attachments/20091023/2f2236d4/attachment.pgp