Disabling presence control when no network is available
Weng Xuetian
wengxt at gmail.com
Mon Dec 10 19:34:56 UTC 2012
On Mon, Dec 10, 2012 at 2:21 PM, David Edmundson <david at davidedmundson.co.uk
> wrote:
> On Mon, Dec 10, 2012 at 10:52 AM, Weng Xuetian <wengxt at gmail.com> wrote:
> >
> > On Mon, Dec 10, 2012 at 5:04 AM, Dan Vrátil <dvratil at redhat.com> wrote:
> >>
> >> On Sunday 09 of December 2012 19:01:38 Martin Klapetek wrote:
> >> > Hey all,
> >> >
> >> > me and David brainstormed the presence handling a bit and we came up
> >> > with
> >> > the idea of disabling the presence controls when you have no network.
> >> > This
> >> > way we can supress all errors when there is no network and prevent
> >> > situations when Tp gets stucked in a connecting state even if you have
> >> > no
> >> > network. I did small testing patch and here is how the contact list
> >> > would
> >> > look if you have no network:
> >> > http://dl.dropbox.com/u/6761102/presence_offline.png
> >> >
> >> > It watches Solid::Networking states and changes whenever Solid signals
> >> > network un/availability.
> >> >
> >> > The presence plasmoid would be changed in a similar way - presence
> >> > actions
> >> > would be replaced with "No network connection" and some actions
> disabled
> >> > accordingly ("Join chat room" etc).
> >> >
> >> > What do you think?
> >>
> >> Looks awesome!
> >>
> >> Is there a way to override the "No Network" status in case
> NetworkManager
> >> goes
> >> nuts?
> >>
> >> Dan
> >>
> > Yeah I also concern about this. There ARE some case if a network
> environment
> > only have "lo", but it use some other way to built a proxy with only "lo"
> > interface.
> >
> > For example,
> > Android phone, setup a proxy on the phone and redirect by adb (I know
> this
> > is a VERY rare case... but I have use it several times, don't argue why I
> > use this werid setup.. this is only for an example).
> >
> > So warn user about no network is good, but in some case it's still useful
> > make user can force the connection. Even proxy is not supported right
> now..
> >
> > _______________________________________________
> > KDE-Telepathy mailing list
> > KDE-Telepathy at kde.org
> > https://mail.kde.org/mailman/listinfo/kde-telepathy
> >
>
> In order to do that you would have to disable network manager (right?)
> if network manager is not running solid you will be in state unknown
> and not disconnected. At which point we won't show this.
>
> It's worth noting that mission-control-5 won't connect if NM is
> running and reports you as offline. So having the controls (this
> patch) won't actually help with anything.
> _______________________________________________
>
Well.. actually I didn't disable nm (it just running but no wireless, no
cable is plug-in).
Thanks for the info about mission-control-5, and yes.. this case is quite
rare.. I also doubt if any one really use network in this way..
So.. if people are using NM connection detect with mission-control, they
already trust NM will not... go wild .. no?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-telepathy/attachments/20121210/f934cb6b/attachment.html>
More information about the KDE-Telepathy
mailing list