Hot answers tagged telepathy
Empathy (the Instant Messaging client) uses Telepathy for protocol support. The telepathy-indicator is just the (sub-)indicator in the messaging indicator.
Removing telepathy-butterfly (complete removal in synaptic) did the trick for me - no need for reinstallation.
If chat is starting at login, you can open the settings window from the contacts list, go to the "General" section, and uncheck "Restore last presence on login". That doesn't disable the instant messaging icon in the panel (it just shows "offline" when it's not running). To get rid of the icon, right-click an empty space in the system tray (e.g. between ...
Telepathy is a framework for instant messaging. When you set up a chat account in the Online Accounts settings panel, you're setting up a login associated with Telepathy. Empathy is a frontend for Telepathy. That is, Empathy provides a user interface for interacting with the Telepathy system. If you wanted to, you could replace Empathy with another ...
First of all some introductory words as to what mission-control is: Mission Control implements [...] the Telepathy D-Bus specification, allowing clients like empathy to store account details, connect to accounts, request communication channels, and have channels dispatched to them. Source To disable the mission-control profile ...
I figured out how to do this (Ubuntu 12.10): Edit /usr/share/dbus-1/services/org.freedesktop.Telepathy.Client.KTp.TextUi.service to comment out (or remove) the link to ktp-text-ui and use Empathy instead. In the end, the service file will look like this: [D-BUS Service] Name=org.freedesktop.Telepathy.Client.KTp.TextUi # ...
It might be a little late but I just found out an easier method, in case anyone ever wonders in the future. Go to "System Settings -> Startup and Shutdown -> Background Services". In the lower box which is labeled "Startup Services" you will be able to check and uncheck services in the "Use" column. Uncheck "Accounts" if you want to disable the Instant ...
Do you want to paste this automatically or manually? If you just want to do it manually, you can do this: program_that_outputs_weather_info | xclip and then just paste using Ctrl-V.
It looks like Microsoft released a new version of Windows Live Messenger and made incompatible changes on the server side. There is a Launchpad bug here: https://bugs.edge.launchpad.net/ubuntu/+source/papyon/+bug/663670. It looks like there is a proposed update ready for testing (cfr. ...
Actually, I just answered that in the original question... ;-) It currently only works in one of the Jabber/XMPP protocol implementations that exist for Telepathy; the one in the telepathy-gabble plugin.
Temporary workaround: killall -9 empathy killall -9 /usr/lib/telepathy/mission-control-5 Then restart Empathy. It should work until it breaks again.
Did you try clicking "Chat" in the messaging menu (the little envelope icon next to the clock)? It should show the contacts list from where you can open any hidden message windows and change the settings concerning hiding and showing of windows.
To get empathy to properly exit by killing processes from the command line, you first need to kill telepathy and telepathy-butterfly processes, then kill the empathy process(es).
Until the official patch goes through, for those who cannot wait, type the following in a terminal (tested on Lucid and Maverick): gksudo gedit /usr/share/pyshared/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py Then find: gksudo gedit /usr/share/pyshared/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py ...
For some reason you need to create the directory .cache/dconf which isn't created.
I received the same message, but only if empathy is a start up application. If you deactivate empathy from starting at start up and activate it manually the problem seemed to go away. My feeling is that empathy is starting prior to telepathy being ready to accept its request.
There's a bug report on this issue here: https://bugs.launchpad.net/ubuntu/+source/ktp-text-ui/+bug/951104 There's a proposed solution on the last line, but I have to confess that I'm not entirely sure how to go about defining a preferred handler on dbus. (Since it's easy enough to remove the kde-telepathy packages without affecting the rest of KDE and I ...
Only top voted, non community-wiki answers of a minimum length are eligible