aboutsummaryrefslogtreecommitdiffstats
path: root/help
diff options
context:
space:
mode:
Diffstat (limited to 'help')
-rw-r--r--help/C/offline.page5
1 files changed, 2 insertions, 3 deletions
diff --git a/help/C/offline.page b/help/C/offline.page
index d22d48e034..26ba047428 100644
--- a/help/C/offline.page
+++ b/help/C/offline.page
@@ -7,7 +7,7 @@
<link type="guide" xref="index#common-other-problems"/>
<link type="seealso" xref="mail-working-offline" />
- <revision pkgversion="3.2.1" version="0.2" date="2012-02-18" status="final"/>
+ <revision pkgversion="3.2.1" version="0.3" date="2012-08-09" status="final"/>
<credit type="author">
<name its:translate="no">Brian Grohe</name>
<email its:translate="no">grohe43@gmail.com</email>
@@ -25,6 +25,5 @@
<p>If this is not the case and Evolution normally works but has suddenly stopped connecting, you may have unintentionally clicked on the connection icon in the lower left corner. When connected, the icon resembles a pair of sockets joined together. If the sockets are open, there is no connection (and the <gui style="button">Send/Receive</gui> button is grayed out). Click on the icon to change its state.</p>
-<p>If the problem persists and you are sure you have not clicked the icon, but you can still reach the network from other apps on your system (browsers, FTP, SSH, ping etc.) it may be that NetworkManager (NM) is not properly configured. Many Linux distributions now use NM to manage their connections, and if it is installed Evolution will use it to detect if the network is up. However NM can be installed but not properly configured, leaving the network working but not detectable by Evolution. (Note that other GNOME-based applications may also fail for the same reason.) The solution is to configure NM to manage your network interface. This is usually easy to do but is outside the scope of this document. For more information seek help from your distribution support forums, mailing lists etc.</p>
-
+<p>If the problem persists and you are sure you have not clicked the icon, but you can still reach the network from other apps on your system (browsers, FTP, SSH, ping etc.) it may be that NetworkManager (NM) is not properly configured. Many Linux distributions now use NM to manage their connections, and if it is installed Evolution will use it to detect if the network is up. However NM can be installed but not properly configured, leaving the network working but not detectable by Evolution. (Note that other GNOME-based applications may also fail for the same reason.) The solution is to configure NM to manage your network interface. This is usually easy to do but is outside the scope of this document. For more information please take a look at the <link href="ghelp:gnome-help#net">Desktop help</link> or seek help from your distribution support forums, mailing lists etc.</p>
</page>