[Pkg-kde-commits] rev 1745 - branches/kde-3.4.0/packages/kdebase/debian

Christopher Martin chrsmrtn-guest at costa.debian.org
Thu Sep 8 16:33:04 UTC 2005


Author: chrsmrtn-guest
Date: 2005-09-08 16:33:03 +0000 (Thu, 08 Sep 2005)
New Revision: 1745

Modified:
   branches/kde-3.4.0/packages/kdebase/debian/kdm.NEWS
Log:
Update the kdm.NEWS. Hopefully this is more clear and readable.


Modified: branches/kde-3.4.0/packages/kdebase/debian/kdm.NEWS
===================================================================
--- branches/kde-3.4.0/packages/kdebase/debian/kdm.NEWS	2005-09-08 15:39:18 UTC (rev 1744)
+++ branches/kde-3.4.0/packages/kdebase/debian/kdm.NEWS	2005-09-08 16:33:03 UTC (rev 1745)
@@ -1,5 +1,7 @@
 kdebase (4:3.4.2-3) unstable; urgency=low
 
+  *** Changes to KDM conffiles:
+
   * Users upgrading KDM to a 3.4.x, from 3.3.x, will find that KDM no longer
     uses the /etc/kde3/kdm/Xservers file, if /etc/kde3/kdm/kdmrc has been
     updated to the version shipped with KDM 3.4.x. The package upgrade scripts
@@ -13,12 +15,14 @@
     all administrators accept the installation of the updated 3.4.x kdmrc file
     during the package upgrade. Many important changes to KDM's defaults have
     been made, and KDM is exceedingly bad at handling anything but the latest
-    kdmrc format, so the nuissance of re-customizing KDM will likely prove less
-    than the nuissance of dealing with a KDM that isn't working properly. If
-    you have already upgraded KDM to a 3.4.x package without accepting the new
-    kdmrc, purging and reinstalling the package should achieve the desired
+    kdmrc format, so the nuissance of re-customizing KDM will likely prove
+    less than the nuissance of dealing with a KDM that isn't working properly.
+    If you have already upgraded KDM to a 3.4.x package without accepting the
+    new kdmrc, purging and reinstalling the package should achieve the desired
     effect.
 
+  *** Changes to user login script handling:
+
   * Another important change that users upgrading from KDM 3.3.x may notice
     is that KDM's ability to source personal login scripts, long disabled, has
     been restored. The exact files sourced on login will depend on the user's
@@ -27,13 +31,18 @@
     is NOT spawning a login shell, but is merely mimicking the behaviour that
     popular shells would exhibit if they were login shells, by manually
     sourcing the customary login scripts. /etc/kde3/kdm/Xsession controls this
-    behaviour. The important downside of this approach is that KDM will
-    utterly fail to start a user's session if the newly sourced files contain
-    certain types of commands. For instance, trying to "exec" many binaries
-    will fail, if they expect an interactive shell. Thus if KDM is refusing to
-    start your session, try commenting out elements of the newly sourced login
-    scripts, and you may find the problem resolved.
- 
+    behaviour.
+
+  * The important downside of the above approach is that KDM will utterly fail
+    to start a user's session if the newly sourced files contain certain types
+    of commands. For instance, many commands will cause the login attempt to
+    fail because they expect an interactive shell, or because you are trying
+    to "exec" something that cannot provide an X session. For instance,
+    "exec ksmserver" will launch KDE, but "exec bash" will fail. Thus if you
+    are unsure why KDM is refusing to start your session, try commenting out
+    elements of the newly sourced login scripts, and you may find the problem
+    resolved.
+
  -- Debian Qt/KDE Maintainers <debian-qt-kde at lists.debian.org>  Thu,  8 Sep 2005 11:13:41 -0400
 
 kdebase (4:3.3.2-1) unstable; urgency=low




More information about the pkg-kde-commits mailing list