2011/4/12 Martin Klapetek <[email protected]>: > > On Apr 12, 2011 12:42 PM, "David Edmundson" <[email protected]> > wrote: >> >> >> >> On Tue, Apr 12, 2011 at 8:04 AM, Francesco Nwokeka >> <[email protected]> wrote: >>> >>> Hi guys, >>> I wanted to notify you about an error I've been getting this >>> morning and can't seem to solve >>> it. >>> This is what mission-control-5 tells me: >>> >>> mcd-WARNING **: Channel request /com/nokia/MissionControl/requests/r1 >>> failed, error: Handler no >>> longer available >>> >>> it can't handle any chats incoming or outgoing. Does anyone know why this >>> happens and how to solve >>> it? >>> >>> Francesco >> >> >> Turns out i'm an idiot who doesn't test properly. >> >> I recently modded the chat handler to be a KUniqueApplication, that broke >> everything. > > If we ever make the CL dbus activated, we must remember to change it there > as well. This also breakes debugging with KDevelop btw.
You can add --nofork to the command line arguments to prevent forking. This would also work with d-bus activation if you set --nofork in the .service file. However, I don't see any reason for the text ui to be a kuniqueapp, as well as I don't see any reason for the CL to be d-bus activated. _______________________________________________ KDE-Telepathy mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-telepathy
