So, if you launch the daemon then the client launch fine? In that case the daemon is not installed somewhere the client can find it.
1) Which prefix did you use for the client and the daemon? 2) Did you install the daemon? The client doesn't really launch the daemon directly. Rather it ask the system to provide it. If the system either doesn't reply or say "no", then the client wont try any further and close. If an error happen when launching the daemon, then there will be a messagebox and a console message. In scenario like the daemon is running with a different user, then the PID lockfile will be locked, then messy things happen, like permissions error when accessing the bus. I guess many of those case could be a lot more explicit than the vague error message or total lack of error message. Each of those need to be handled individually, rather than the "something went wrong before connecting" and "something went wrong while connecting" like it currently do. I will open an issue to improve those. ----- Original Message ----- From: "Robert Dyck" <[email protected]> To: "Emmanuel Lepage" <[email protected]> Cc: [email protected] Sent: Monday, July 21, 2014 8:49:26 PM Subject: Re: [SFLphone] Unable launch sflphone 1.4 I rebooted. If the client starts the daemon they are the same user, no? Nothing related is in the system tray. Video is on by default now if the configure script can be believed. If I manually start the daemon I can connect via dbus. If I manually start the daemon I can launch the client. Would the client not have to start the daemon before it can connect via dbus? On July 21, 2014 08:05:26 PM Emmanuel Lepage wrote: > Hi again, > > If sflphoned is launched using the same user as sflphone-client-kde, it > should start. So, if the sflphone-kde window does not show, check: > > 1) That it is not minimized in the systray > 2) That both sflphoned and sflphone-kde have video enabled (given your > previous questions/reports, I guess they have) 3) That d-feet and/or > qdbusviewer can access the daemon > 4) The problem is still there after a reboot* > 5) Add "dbus-launch" in front of both sflphoned and sflphone-client-kde > > If that still doesn't solve the problem, then it might be more serious. We > had issues like this twice before for both KDE and Gnome client. Some of > them were related to the initialization order causing some deadlocks > (freeze). For the KDE client, there is a compile option called > -DDISABLE_UNIQUE_APPLICATION=true . This helped in the past, but I am quite > sure all issues causing this have been fixed long ago. > > *In the past, there was a case where dbus itself was messed up by trying > to do invalid subscriptions. Reboot was the only option, restarting dbus > without restarting is not recommended as most services don't handle this > correctly. > > ----- Original Message ----- > From: "Robert Dyck" <[email protected]> > To: "Emmanuel Lepage" <[email protected]> > Cc: [email protected] > Sent: Monday, July 21, 2014 7:44:51 PM > Subject: Re: [SFLphone] Unable launch sflphone 1.4 > > Good call. It turns out that the daemon was running as root. By starting the > daemon as myself and then the client sflphone is launched. The error > message is still there except the bit about " probably crashed". Shall I > assume that the stuff about KGlobal::locale can be ignored? > > So now I see the communication error when I leave it to the client to start > the daemon. I'll try to familiarize myself with the dbus tools. > > On July 21, 2014 04:32:54 PM Emmanuel Lepage wrote:it > > > Hello Robert, > > > > Are you sure sflphone-client-kde and sflphoned are launched from the same > > user? Can get check in d-feet (GTK) or QDbusViewer (Qt, part of Qt dev > > tools) that sflphoned is accessible > > > > *you can try to execute the AconfigurationManager.getAccountList() method > > > > > > Regards, > > Emmanuel > > ----- Original Message ----- > > From: "Robert Dyck" <[email protected]> > > To: [email protected] > > Sent: Monday, July 21, 2014 4:24:26 PM > > Subject: [SFLphone] Unable launch sflphone 1.4 > > > > My system is Fedora 19 KDE spin. I compiled and installed sflphone 1.4 > > from > > the source tarball. There were no errors. Wiki could be freshened. > > > > I can start the daemon directly from /usr/lib64/sflphone/sflphoned. When I > > try to start the KDE client I get a very obscure error message. > > > > KGlobal::locale(): Warning your global KLocale is being recreated with a > > valid main component instead of a fake component, this usually means you > > tried to call i18n related functions before your main component was > > created. You should not do that since it most likely will not work > > sflphone-client-kde(16623): Communication problem with > > "sflphone-client-kde" , it probably crashed. > > Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did > > not receive a reply (timeout by message bus)" > > > > It does not matter whether the daemon is started in advance. > > > > I am anxious to try 1.4. Assistance appreciated. > > Rob > > > > _______________________________________________ > > SFLphone mailing list > > [email protected] > > http://lists.savoirfairelinux.net/mailman/listinfo/sflphone _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone
