<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="urn:x-suse:xslt:profiling:docbook51-profile.xsl"
                 type="text/xml"
                 title="Profiling step"?>
<!DOCTYPE article
[
 <!ENTITY % myents SYSTEM "release-notes.ent" >
 %myents;
]>
<article xml:lang="en" xml:id="rnotes"
  xmlns="http://docbook.org/ns/docbook" version="5.1"
  xmlns:xi="http://www.w3.org/2001/XInclude"
  xmlns:xlink="http://www.w3.org/1999/xlink">
 <title>&rnotes;</title>
 <info>
  <releaseinfo>&rversion;</releaseinfo>
  <productname>&thisflavor;</productname>
  <!-- version doesn't make sense for TW
  <productnumber>&version;</productnumber>
  -->
  <date><?dbtimestamp format="Y-m-d"?></date>
  <abstract>
   <para>&thisflavor; is a free and Linux-based operating system for your
   PC, laptop or server. You can surf the web, manage your e-mails and
   photos, do office work, play videos or music and have a lot of fun!
   </para>
  </abstract>
  <dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">
   <dm:bugtracker>
    <dm:url>https://bugzilla.opensuse.org/enter_bug.cgi</dm:url>
    <dm:product>openSUSE Tumbleweed</dm:product>
    <dm:component>Release Notes</dm:component>
    <dm:assignee>sknorr@suse.com</dm:assignee>
   </dm:bugtracker>
  </dm:docmanager>
 </info>

 <para>
  The release notes are under constant development. To find out about the
  latest updates, see the online version at
  <link xlink:href="https://doc.opensuse.org/release-notes"/>. The English release
  notes are updated whenever need arises. Translated language versions can
  temporarily be incomplete.
 </para>

 <para>
  To report bugs against this release, use the &opensuse; Bugzilla. For more
  information, see
  <link xlink:href="https://en.opensuse.org/openSUSE:Submitting_bug_reports"/>.
 </para>


 <sect1 xml:id="installation">
  <title>Installation</title>

  <para/>

  <sect2 xml:id="sec.123.uefi">
   <title>UEFI&mdash;Unified Extensible Firmware Interface</title>
   <para>
    Prior to installing &osuse; on a system that boots using UEFI
    (Unified Extensible Firmware Interface), you are urgently advised to
    check for any firmware updates the hardware vendor recommends and,
    if available, to install such an update. A pre-installed Windows 8
    is a strong indication that your system boots using UEFI.
   </para>

   <para>
    <emphasis>Background:</emphasis> Some UEFI firmware has bugs that
    cause it to break if too much data gets written to the UEFI storage
    area. Nobody really knows how much "too much" is, though.  openSUSE
    minimizes the risk by not writing more than the bare minimum
    required to boot the OS.  The minimum means telling the UEFI
    firmware about the location of the openSUSE boot loader.  Upstream
    Linux Kernel features that use the UEFI storage area for storing
    boot and crash information (<literal>pstore</literal>) have been
    disabled by default. Nevertheless, it is recommended to install any
    firmware updates the hardware vendor recommends.
   </para>
  </sect2>


  <sect2 xml:id="sec.123.uefi-part">
   <!-- bnc#850056 -->
   <title>UEFI, GPT, and MS-DOS Partitions</title>
   <para>
    Together with the EFI/UEFI specification, a new style of
    partitioning arrived: GPT (GUID Partition Table). This new schema
    uses globally unique identifiers (128-bit values displayed in 32
    hexadecimal digits) to identify devices and partition types.
   </para>
   <para>
    Additionally, the UEFI specification also allows legacy MBR (MS-DOS)
    partitions. The Linux boot loaders (ELILO or GRUB2) try to
    automatically generate a GUID for those legacy partitions, and write
    them to the firmware. Such a GUID can change frequently, causing a
    rewrite in the firmware. A rewrite consist of two different
    operation: removing the old entry and creating a new entry that
    replaces the first one.
   </para>
   <para>
    Modern firmware has a garbage collector that collects deleted
    entries and frees the memory reserved for old entries. A problem
    arises when faulty firmware does not collect and free those entries;
    this may end up with a non-bootable system.
   </para>
   <para>
    The workaround is simple: convert the legacy MBR partition to the
    new GPT to avoid this problem completely.
   </para>
  </sect2>

 </sect1>

 <!--
 <sect1 xml:id="upgrade">
  <title>System Upgrade</title>
  <para></para>

 </sect1>
 -->

 <sect1 xml:id="general">
  <title>General</title>

  <sect2>
    <title>System with LUKS-Encrypted Partition Does Not Boot</title>
    <para>In some cases, Plymouth does not display the passphrase prompt
    properly. To fix this, add <literal>plymouth.enable=0</literal> to the
    kernel command line. See also
    <link xlink:href="https://bugzilla.opensuse.org/show_bug.cgi?id=966255"/>.
    </para>
  </sect2>

  <sect2 xml:id="sec.general.apparmor-restart">
   <!-- boo#1074097 -->
   <title><command>systemctl stop apparmor</command> Does Not Work</title>
   <para>
    In the past, there could be confusion over the difference between how the
    very similarly named <command>systemctl</command> subcommands
    <literal>reload</literal> and <literal>restart</literal> worked for
    AppArmor:
   </para>
   <itemizedlist>
    <listitem>
     <para>
      <command>systemctl reload apparmor</command> properly reloaded all
      AppArmor profiles. (It was and continues to be the recommended way of
      reloading AppArmor profiles.)
     </para>
    </listitem>
    <listitem>
     <para>
      <command>systemctl restart apparmor</command> meant that
      AppArmor would stop, thereby unloading all AppArmor profiles and then
      restart which left all existing processes unconfined. Only newly
      started processes would then be confined again.
     </para>
    </listitem>
   </itemizedlist>
   <para>
    Unfortunately, <systemitem>systemd</systemitem> does
    not provide a solution within its unit file format for the issue posed
    by the <literal>restart</literal> scenario.
   </para>
   <para>
    Starting with AppArmor 2.12, the command
    <command>systemctl stop apparmor</command> will not work.
    As a consequence, <command>systemctl restart apparmor</command> will now
    correctly reload AppArmor profiles.
   </para>
   <para>
    To unload all AppArmor profiles, use the new command
    <command>aa-teardown</command> instead which matches the previous
    behavior of <command>systemctl stop apparmor</command>.
   </para>
   <para>
    For more information, see
    <link xlink:href="https://bugzilla.opensuse.org/show_bug.cgi?id=996520"/>
    and
    <link xlink:href="https://bugzilla.opensuse.org/show_bug.cgi?id=853019"/>.
   </para>
  </sect2>

  <!-- boo#1059438, boo#1062550 -->
  <sect2 xml:id="sec.general.compose-key">
   <title>No Default Compose Key Combination</title>
   <para>
    In previous versions of &os;, the compose key combination
    allowed typing characters that were not part of the regular keyboard layout.
    For example, to produce <quote>å</quote>, you could press and release
    <keycombo><keycap function="shift"/><keycap>Right Ctrl</keycap></keycombo>
    and then press <keycap>a</keycap> twice.
   </para>
   <para>
    In &thisversion;, there is no longer a predefined compose key combination
    because
    <keycombo><keycap function="shift"/><keycap>Right Ctrl</keycap></keycombo>
    does not work as expected anymore.
   </para>
   <itemizedlist>
    <listitem>
     <para>
      To define a system-wide custom compose key combination, use the file
      <filename>/etc/X11/Xmodmap</filename> and look for the following lines:
     </para>
<screen>[...]
!! Third example: Change right Control key to Compose key.
!! To do Compose Character, press this key and afterwards two
!! characters (e.g. `a' and `^' to get 342).
!remove  Control  = Control_R
!keysym Control_R = Multi_key
!add     Control  = Control_R
[...]</screen>
     <para>
      To uncomment the example code, remove the
      <literal>!</literal> characters at the beginning of lines. However,
      note that the setup from <filename>Xmodmap</filename> will be
      overwritten if you are using <command>setxkbmap</command>.
     </para>
    </listitem>
    <listitem>
     <para>
      To define a user-specific compose key combination, use your desktop's
      keyboard configuration tool or the command-line tool
      <command>setxkbmap</command>:
     </para>
     <screen>
setxkbmap <replaceable>[...]</replaceable> -option compose:<replaceable>COMPOSE_KEY</replaceable>
     </screen>
     <para>
      For the variable <replaceable>COMPOSE_KEY</replaceable>, use your
      preferred character, for example
      <literal>ralt</literal>, <literal>lwin</literal>,
      <literal>rwin</literal>, <literal>menu</literal>,
      <literal>rctl</literal>, or <literal>caps</literal>.
     </para>
    </listitem>
    <listitem>
     <para>
      Alternatively, use an IBus input method that allows typing the
      characters you need without a Compose key.
     </para>
    </listitem>
   </itemizedlist>
  </sect2>

 </sect1>

 <!-- <sect1 xml:id="technical">
  <title>Technical</title>
  <para/>
 </sect1> -->

 <!--
 <sect1 xml:id="misc" remap="Misc">
  <title>Miscellaneous</title>

 </sect1>
 -->

 <sect1 xml:id="feedback">
  <title>More Information and Feedback</title>
  <itemizedlist>
   <listitem>
    <para>
     Read the <filename>README</filename> documents on the medium.
    </para>
   </listitem>
   <listitem>
    <para>
     View a detailed changelog information about a particular package from its
     RPM:
    </para>
    <screen>rpm --changelog -qp <replaceable>FILENAME</replaceable>.rpm</screen>
    <para>
     Replace <replaceable>FILENAME</replaceable> with the name of the RPM.
    </para>
   </listitem>
   <listitem>
    <para>
     Check the <filename>ChangeLog</filename> file in the top level of the
     medium for a chronological log of all changes made to the updated packages.
    </para>
   </listitem>
   <listitem>
    <para>
     Find more information in the <filename>docu</filename> directory on the
     medium.
    </para>
   </listitem>
   <listitem>
    <para>
     For additional or updated documentation, see
     <link xlink:href="https://doc.opensuse.org/"/>.
    </para>
   </listitem>
   <listitem>
    <para>
     For the latest product news, from &opensuse;, visit
     <link xlink:href="https://www.opensuse.org"/>.
    </para>
   </listitem>
  </itemizedlist>

  <para>
   Copyright © <?dbtimestamp format="Y" ?> SUSE LLC
  </para>

  <para>
   Thanks for using &opensuse;.
  </para>
  <para>
   The &opensuse; Team.
  </para>
 </sect1>

</article>
