Yeah the problem seems to be that the specified applications were
relying entirely on NM for deciding the "network" status of the Linux
box, ...... but the dbus suggestion was inspired from a Lenny issue I
was looking at here , ...
http://debian.org/releases/lenny/i386/release-notes/ch-information.en.html#nis.
The NIS server in Lenny if not given the -no-dbus option relies on
NetworkManager for deciding whether the system is connected, I thought
it was a similar scenario and hence the suggestion, ...
Satish
On 2/15/09, steve <steve@xxxxxxxxxxxx> wrote:
Hi Satish,
Satish Eerpini wrote:
Hi everyone,
If this is a common problem because the NetworkManager is notifying
the system that no network interface is connected. Then is there no
way we can switch off the DBUS communication temporarily ??
If i understand the problem correctly, the issue is not that NM is notifying
the
system that none of the interfaces under its control are connected, but the
fact
that firefox and thunderbird, rely solely on NM to gather status of the
network
connection (even though there is a possibility that some interface is not
controlled by NM).
The workaround I mentioned fixes that assumption made by FF & TB.
cheers,
- steve
--
Linux Centric Marketplace: http://www.tuxcompatible.com
_______________________________________________
To unsubscribe, email ilugc-request@xxxxxxxxxxxxx with
"unsubscribe <password> <address>"
in the subject or body of the message.
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc