[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#704211: [release-notes] [wheezy] issues: NM conflicts with wicd-daemon, Gnome3 now depends on NM



tags 704211 + patch
thanks

Patches attached for a proposed update for the release-notes concerning 
conflicts between NetworkManager and wicd-daemon (and possibly others).  These 
are based on release-notes svn revision 9694.

   issues-NM.dbk.diff    -> explains NM <-> wicd conflict and a workaround

   whats-new-NM.dbk.diff -> mentions some NetworkManager features
                            and points to conflict section if another
                            networking manager is desired.

These patches are separate so that the two sections can be updated 
independently of one-another.  I'm willing to keep these patches updated if 
changes to the wording are desired.

Thanks.

[Joost: not sure why, but I only saw your message in BTS just now and did not 
receive it in email.]

  -- Chris

--
Chris Knadle
Chris.Knadle@coredump.us
Description: update issues.dbk for conflicts between NetworkManager
  and other network management daemons, such as wicd-daemon
Author: Christopher Knadle <Chris.Knadle@coredump.us>
===================================================================
--- en/issues.dbk    (revision 9694)
+++ en/issues.dbk    (working copy)
@@ -106,21 +106,62 @@ the current Chromium releases for stable.
 
 <section id="gnome-desktop-changes">
 <title>GNOME desktop changes and support</title>
-<para>
-  By default, most accessibility tools are not enabled in the GNOME display
-  manager (gdm3).  In order to enable screen reading, zooming, or a visual
-  keyboard, the simplest way is to enable the <quote>shell</quote> greeter.
-</para>
+  <section>
+  <title>Accessibility</title>
+  <para>
+    By default, most accessibility tools are not enabled in the GNOME display
+    manager (gdm3).  In order to enable screen reading, zooming, or a visual
+    keyboard, the simplest way is to enable the <quote>shell</quote> greeter.
+  </para>
+  <para>
+    To do that, edit the <filename>/etc/gdm3/greeter.gsettings</filename> file,
+    and uncomment the following:
+  <programlisting>session-name='gdm-shell'</programlisting>
+    while commenting
+  <programlisting>session-name='gdm-fallback'</programlisting>
+    Note that it requires a compatible 3D graphics card — which is the reason
+    why it is not enabled by default.
+  </para>
+  </section>
+  <section id="network-manager-conflicts">
+  <title>NetworkManager</title>
+  <para>
+    The package chain in GNOME now Depends on
+    <systemitem role="package">network-manager</systemitem>.  At present,
+    <command>NetworkManager</command> can detect if a network interface is
+    managed by <command>ifupdown</command> to avoid conflicts with it, but
+    does not detect other networking manager programs such as
+    <command>wicd-daemon</command>. Problems and unexpected behavior can
+    result if two network manager daemons are managing the same interface
+    when attempting to make a networking connection.
+  </para>
+  <para>
+    For instance, if <command>wicd-daemon</command> and
+    <command>NetworkManager</command> are both running, attempting to use a
+    <command>wicd</command> client to make a connection will fail with a
+    counterintuitive error message:
+    <screen>Connection Failed: bad password</screen>
+    Attempting to use a <command>NetworkManager</command> client may likewise
+    fail with the message:
+    <screen>NetworkManager is not running.  Please start it.</screen>
+    The <systemitem role="package">network-manager</systemitem> package
+    cannot easily be removed due to it now being a GNOME dependency, but if
+    continuing to use another networking manager is desired, the
+    <command>NetworkManager</command> daemon may remain installed but be
+    permanently disabled in a way which is persistant through upgrades with
+    the following command:
+    <screen># update-rc.d network-manager disable</screen>
+    Also examine the contents of <filename>/etc/resolv.conf</filename>, which
+    is used to specify DNS servers for name resolution, as the contents of
+    this file are normally replaced by <command>NetworkManager</command>.
+  </para>
+  <para>
+    Further information is available in bugs
+    <ulink url="&url-bts;681834">#681834</ulink> and
+    <ulink url="&url-bts;688772">#688772</ulink>.
+  </para>
+  </section>
 
-<para>  
-  To do that, edit the <filename>/etc/gdm3/greeter.gsettings</filename> file,
-  and uncomment the following:
-<programlisting>session-name='gdm-shell'</programlisting>
-  while commenting
-<programlisting>session-name='gdm-fallback'</programlisting>
-  Note that it requires a compatible 3D graphics card — which is the reason
-  why it is not enabled by default.
-</para>
 </section>
 
 <section id="graphics" condition="fixme">
Description: update whats-new.dbk to mention NetworkManager and
  wicd-daemon, link to possible conflicts
Author: Christopher Knadle <Chris.Knadle@coredump.us>
===================================================================
--- en/whats-new.dbk    (revision 9694)
+++ en/whats-new.dbk    (working copy)
@@ -656,6 +656,19 @@ deb-src &url-debian-mirror-eg;/debian &releasename;-updates main contrib</progra
       features are now available in GDM 3.x.
     </para>
   </section>
+  <section>
+    <title>Network management</title>
+    <para>
+      GNOME now features online connectivity awareness with several
+      applications along with the GNOME shell using
+      <command>NetworkManager</command>, which features IPv6 compatibility and
+      network connection awareness for GNOME applications.  If you are
+      planning on using another network management daemon (such as
+      <command>wicd-daemon</command>), please see Section
+      <xref linkend="network-manager-conflicts"/> concerning possible
+      conflicts.
+    </para>
+  </section>
 
 </section>
 

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: