[gnome-user-docs] Updated session-debug.page

[Jana Svarova <jsvarova src gnome org>]

commit 881fbc857020b53a1251f34b9a25e356e3cff975
Author: Jana Svarova <jsvarova redhat com>
Date:   Tue Apr 2 18:02:29 2013 +0200

    Updated session-debug.page

 system-admin-guide/C/session-debug.page |   34 ++++++++++++++++++++++++------
 1 files changed, 27 insertions(+), 7 deletions(-)
---
diff --git a/system-admin-guide/C/session-debug.page b/system-admin-guide/C/session-debug.page
index b11abaf..739836e 100644
--- a/system-admin-guide/C/session-debug.page
+++ b/system-admin-guide/C/session-debug.page
@@ -11,18 +11,38 @@
       <years>2012</years>
     </credit>
 
+    <credit type="editor">
+      <name>Jana Svarova</name>
+      <email>jana svarova gmail com</email>
+      <years>2013</years>
+    </credit>
+
     <desc>What happened to <file>~/.xsession-errors</file>?</desc>
   </info>
 
   <title>Debugging session problems</title>
 
-  <comment>
-    <cite date="2012-07-24" href="mailto:mdhillca gmail com">Michael Hill</cite>
-    <p>Adapted from l-g-o SysAdminGuide page. Add link for XDG directories spec.</p>
-  </comment>
+<comment>
+  <cite date="2012-07-24" href="mailto:mdhillca gmail com">Michael Hill</cite>
+  <p>Adapted from l-g-o SysAdminGuide page. Add link for XDG directories 
+  spec.</p>
+</comment>
+
+  <p>If you want to find more information about a problem in a session or want 
+  to fix it, go directly to the <app>systemd</app>s journal, which stores 
+  log data in a binary format.</p>
 
-  <p>The <file>~/.xsession-errors</file> file was very handy for debugging
-   session problems. It is now located at <file>~/.cache/gdm/session.log</file>
-   to comply with the <em>XDG directories spec</em>.</p>
+<section id="session-log">
+  <title>Session.log no longer exists</title>
+  <p>Previously, the debugging information was stored in the session.log file. 
+  This file no longer exists on <app>systemd</app>-using systems. The content 
+  is now stored directly to the <app>systemd</app> journal. To get the logs 
+  back, you can use the <cmd>journalctl _UID=&lt;your-uid&gt;</cmd> command.</p>
+  <p>You can find more information on the <app>journalctl</app> man page: 
+  run <link xref="man:journalctl"><cmd>man journalctl</cmd></link> 
+  in the terminal or 
+  <link xref="http://www.freedesktop.org/software/systemd/man/journalctl.html";>
+  view the man page online</link>.</p>
+</section>
 
 </page>