Notas da versión
Notas da versión
  1. 1 Instalación
  2. 2 Xeral
  3. 3 Máis información e comentarios
openSUSE Tumbleweed

Notas da versión

openSUSE Tumbleweed é un sistema operativo libre baseado en Linux para o seu PC, portátil ou servidor. Pode navegar, xestionar os seus correos electrónicos e fotos, realizar o seu traballo de oficina, reproducir vídeos ou música, e divertirse!

: Jesús Bravo Álvarez, Manuel A. Vazquez, Leandro Regueiro, e Manuel A. Vázquez
Data de Publicación 2019-03-14 , 84.87.20190301.2742382
1 Instalación
2 Xeral
3 Máis información e comentarios

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

Para informar de erros desta versión, use o Bugzilla openSUSE. Consulte para máis información https://en.opensuse.org/openSUSE:Submitting_bug_reports.

1 Instalación

1.1 UEFI: Interface de Firmware Unificada Extensíbel

Antes de instalar openSUSE nun sistema que se inicia usando UEFI (Interface Unificada Extensíbel do Firmware), recoméndase comprobar se hai actualizacións do firmware que recomende o provedor de hardware e, de existiren, instalar esta actualización. Un Windows 8 preinstalado é un grande indicador de que o seu sistema iníciase usando UEFI.

Background: 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 (pstore) have been disabled by default. Nevertheless, it is recommended to install any firmware updates the hardware vendor recommends.

1.2 Particións UEFI, GPT e MS-DOS

Xunto coa especificación EFI/UEFI chegou un novo estilo de particionamento: GPT (GUID Partition Table). Este novo esquema usa identificadores únicos globais (valores de 128-bit mostrados coma 32 díxitos hexadecimais) para identificar dispositivos e tipos de particións.

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.

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.

The workaround is simple: convert the legacy MBR partition to the new GPT to avoid this problem completely.

2 Xeral

2.1 System with LUKS-Encrypted Partition Does Not Boot

In some cases, Plymouth does not display the passphrase prompt properly. To fix this, add plymouth.enable=0 to the kernel command line. See also https://bugzilla.opensuse.org/show_bug.cgi?id=966255.

2.2 systemctl stop apparmor non funciona

In the past, there could be confusion over the difference between how the very similarly named systemctl subcommands reload and restart worked for AppArmor:

  • systemctl reload apparmor properly reloaded all AppArmor profiles. (It was and continues to be the recommended way of reloading AppArmor profiles.)

  • systemctl restart apparmor 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.

Unfortunately, systemd does not provide a solution within its unit file format for the issue posed by the restart scenario.

Starting with AppArmor 2.12, the command systemctl stop apparmor will not work. As a consequence, systemctl restart apparmor will now correctly reload AppArmor profiles.

To unload all AppArmor profiles, use the new command aa-teardown instead which matches the previous behavior of systemctl stop apparmor.

For more information, see https://bugzilla.opensuse.org/show_bug.cgi?id=996520 and https://bugzilla.opensuse.org/show_bug.cgi?id=853019.

2.3 No Default Compose Key Combination

In previous versions of openSUSE, the compose key combination allowed typing characters that were not part of the regular keyboard layout. For example, to produce “å”, you could press and release Shift–Right Ctrl and then press a twice.

In openSUSE Tumbleweed, there is no longer a predefined compose key combination because Shift–Right Ctrl does not work as expected anymore.

  • Para definir unha combinación de teclas personalizadas para todo o sistema, use o ficheiro /etc/X11/Xmodmap e busque as seguintes liñas: 

    [...]
!! 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
[...]

    To uncomment the example code, remove the ! characters at the beginning of lines. However, note that the setup from Xmodmap will be overwritten if you are using setxkbmap.

  • To define a user-specific compose key combination, use your desktop's keyboard configuration tool or the command-line tool setxkbmap: 

    setxkbmap [...] -option compose:COMPOSE_KEY

    For the variable COMPOSE_KEY, use your preferred character, for example ralt, lwin, rwin, menu, rctl, or caps.

  • Alternatively, use an IBus input method that allows typing the characters you need without a Compose key.

3 Máis información e comentarios

  • Lea os documentos README dispoñíbeis no medio.

  • Consulte a información detallada dos cambios dun paquete en concreto a partires do seu RPM: 

    rpm --changelog -qp FILENAME.rpm

    Replace FILENAME with the name of the RPM.

  • Check the ChangeLog file in the top level of the medium for a chronological log of all changes made to the updated packages.

  • Encontre máis información no directorio docu no medio.

  • Para obter documentación adicional ou actualizada, consulte https://doc.opensuse.org/.

  • Para saber das últimas noticias de produtos, desde openSUSE, visite https://www.opensuse.org.

Copyright © SUSE LLC

Grazas por usar openSUSE.

O equipo de openSUSE.

© 2019 SUSE