bcooksley wrote:Just to clarify, the shared backend is something which is not KDE specific, and so it therefore cannot use KDE specific technology (which is what the D-Bus call I mentioned essentially is, as it is dependent on a certain KDE Daemon module being present). It is not directly developed nor under the control of KDE.

I do not know if it possible for KDE Telepathy to override the built in determinations made by the network systems in the shared backend unfortunately.

Even though you are probably right I will file a bug, perhaps someone can take it to the backend then. It is not wise to depend on a certain piece of software that it does not take much internet searching to find it can not (yet) correctly deal with all kinds of connections

In fact I have about 3 different 3G modems here (different networks) and all of them I have to use wvdial. There are x number of cheap chinese (mainly) modems out there and quite often "good old" wvdial is the only thing that actually works

It seems there is a way to disable the telepathy connection monitoring.

From a terminal type:

Code: Select all

dconf write /org/gnome/empathy/use-conn  false

(this disables the plugins in the backend that check connection state. Don't worry that it has gnome in the path)

then type:

Code: Select all

killall mission-control-5

(this will make it reload the config, it will automatically respawn)

You should only need to do this once.

If you have any network problems or spurious notifications make sure to mention that you made this change when filing bug reports.

david_edmundson wrote:It seems there is a way to disable the telepathy connection monitoring.

From a terminal type:

Code: Select all

dconf write /org/gnome/empathy/use-conn  false

(this disables the plugins in the backend that check connection state. Don't worry that it has gnome in the path)

then type:

Code: Select all

killall mission-control-5

(this will make it reload the config, it will automatically respawn)

You should only need to do this once.

If you have any network problems or spurious notifications make sure to mention that you made this change when filing bug reports.

this makes no change for me, telepathy still does not connect. Only workaround I have found: create a shared wifi connection, connect it and then telepathy thinks I am online and connects

As a followup: I did file a bug on this https://bugs.freedesktop.org/show_bug.cgi?id=62459 and got confirmed that the dependency on NetworkManager is there.

I have to question this, there is as an other example users of WICD that do not rely on NetworkManager though it may still be installed.

Anyhow, comment 3 https://bugs.freedesktop.org/show_bug.cgi?id=62459#c3 contains a workaround that I confirm works, namely issue command
gsettings set im.telepathy.MissionControl.FromEmpathy use-conn false

kde-telepathy then connects to the various accounts I have (4 of them) without problems.

The problem with this seems to be that kde-telepathy then loses the ability to note if the connection goes down... so it stays "online" regardless.

In other words the long term solution lies (I assume) in the suggestion in the comment to rewrite a piece of the underlying sourcecode

Awesome, thanks for letting us know!

mck182 wrote:Awesome, thanks for letting us know!

You are welcome, I appreciate the fact that you keep an eye on and actively participate in the forum! Also want to say that 0.6 is looking better and better from use of the daily Kubuntu PPA!

I assume you did some change to the code as I no longer have the problem with connecting and do not have to use the "workaround"?

No, it's because you've changed a config file above, you only need to do this once.

david_edmundson wrote:No, it's because you've changed a config file above, you only need to do this once.

OK cool! I assumed it was something I needed to do at every boot/login.

Hope that someone working on mission-control will find time later to revise the underlying code