Debian Debian-France Debian-Facile Debian-fr.org Debian-fr.xyz Debian ? Communautés

Debian-facile

Bienvenue sur Debian-Facile, site d'aide pour les nouveaux utilisateurs de Debian.

Vous n'êtes pas identifié(e).

#1 11-04-2021 17:34:42

robert2a
Membre
Distrib. : debian 11
(G)UI : Mate
Inscription : 15-11-2014

retour de apt-listchange sur 1260 paquets

Bonjour


apt-listchanges : nouveautés
----------------------------

apt (2.1.16) unstable; urgency=medium

  Automatically remove unused kernels on apt {dist,full}-upgrade. To revert
  to previous behavior, set APT::Get::AutomaticRemove::Kernels to false or
  pass --no-auto-remove to the command. apt-get remains unchanged.

  Packages files can now set the Phased-Update-Percentage field to restrict
  update rollout to a specified percentage of machines. Previously, this has
  only been available to users of Ubuntu's update-manager tool. See
  apt_preferences(5) for details and how to configure multiple systems to get
  the same updates. Phased updates are disabled in chroots for now to not
  break buildd-style setups.

 -- Julian Andres Klode <jak@debian.org>  Fri, 08 Jan 2021 22:01:50 +0100

compton (1-1) unstable; urgency=medium

  Compton is no longer being developed by the original author; the
  development continues as picom:

    https://github.com/yshui/picom

  Please consider switching over to picom.

  This package will likely not be included in the Debian releases following
  Bullseye.

 -- Andrej Shadura <andrewsh@debian.org>  Wed, 16 Dec 2020 16:07:30 +0100

exim4 (4.94-16) unstable; urgency=medium

  The configuration now enforces certificate verification against the
  system trust store on encrypted connections using the
  remote_smtp_smarthost transport (smarthost and satellite setups).
  Delivery will therefore fail if the host certificates are not verifyable
  and non TLS delivery is not available (e.g. because AUTH PLAIN is used).

:

glibc (2.31-5) unstable; urgency=medium

  Starting with glibc 2.31-5, the NIS and NIS+ name service modules
  libnss_nis.so.2.0.0 and libnss_nisplus.so.2.0.0 are not provided anymore by
  the libc6 package. People needing those modules have to install the
  libnss-nis and/or the libnss-nisplus packages, which are recommended by
  the libc6 package.

 -- Aurelien Jarno <aurel32@debian.org>  Tue, 01 Dec 2020 08:42:44 +0100

hddtemp (0.3-beta15-54) unstable; urgency=medium

  hddtemp has been dead upstream for many years and is therefore in a minimal
  maintenance mode. It will be shipped in the Debian Bullseye release, but
  will not be present in the Debian Bookworm release.

  Nowadays the 'drivetemp' kernel module is a better alternative. It uses the
  Linux Hardware Monitoring kernel API (hwmon), so the temperature is returned
  the same way and using the same tools as other sensors.

  Loading this module is as easy as creating a file in the /etc/modules-load.d
  directory:

    echo drivetemp > /etc/modules-load.d/drivetemp.conf

 -- Aurelien Jarno <aurel32@debian.org>  Tue, 02 Feb 2021 20:27:44 +0100

node-jquery (3.5.1+dfsg+~3.5.5-7) unstable; urgency=medium
 * Files pre-compressed with brotli compression now use suffix .brotli,
    to avoid clashing with ISO 639-1 language code for breton.

 -- Jonas Smedegaard <dr@jones.dk>  Tue, 12 Jan 2021 21:53:11 +0100

openssh (1:8.4p1-1) unstable; urgency=medium

  OpenSSH 8.4 includes a number of changes that may affect existing
  configurations:

   * ssh-keygen(1): the format of the attestation information optionally
     recorded when a FIDO key is generated has changed. It now includes the
     authenticator data needed to validate attestation signatures.

   * The API between OpenSSH and the FIDO token middleware has changed and
     the SSH_SK_VERSION_MAJOR version has been incremented as a result.
     Third-party middleware libraries must support the current API version
     (7) to work with OpenSSH 8.4.

 -- Colin Watson <cjwatson@debian.org>  Sun, 18 Oct 2020 12:07:48 +0100

systemd (247.2-2) unstable; urgency=medium

  systemd now defaults to the "unified" cgroup hierarchy (i.e. cgroupv2).
  This change reflects the fact that cgroupsv2 support has matured
  substantially in both systemd and in the kernel.
  All major container tools nowadays should support cgroupv2.
  If you run into problems with cgroupv2, you can switch back to the previous,
  hybrid setup by adding "systemd.unified_cgroup_hierarchy=false" to the
  kernel command line.
  You can read more about the benefits of cgroupv2 at
  https://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html

 -- Michael Biebl <biebl@debian.org>  Mon, 21 Dec 2020 18:40:10 +0100

systemd (247.2-1) unstable; urgency=medium

  KERNEL API INCOMPATIBILITY: Linux 4.14 introduced two new uevents
"bind" and "unbind" to the Linux device model. When this kernel
  change was made, systemd-udevd was only minimally updated to handle
  and propagate these new event types. The introduction of these new
  uevents (which are typically generated for USB devices and devices
  needing a firmware upload before being functional) resulted in a
  number of issues which we so far didn't address. We hoped the kernel
  maintainers would themselves address these issues in some form, but
  that did not happen. To handle them properly, many (if not most) udev
  rules files shipped in various packages need updating, and so do many
  programs that monitor or enumerate devices with libudev or sd-device,
  or otherwise process uevents. Please note that this incompatibility
  is not fault of systemd or udev, but caused by an incompatible kernel
  change that happened back in Linux 4.14, but is becoming more and
  more visible as the new uevents are generated by more kernel drivers.

  To learn more about the required udev rules changes please check the
  "CHANGES WITH 247" section of /usr/share/doc/systemd/NEWS.gz.

 -- Balint Reczey <rbalint@ubuntu.com>  Fri, 11 Dec 2020 18:22:42 +0100

unbound (1.11.0-1) unstable; urgency=medium

  The default Debian config file shipped in the unbound package has changed
  from using the "include:" directive to using the "include-toplevel:"
  directive in order to include the config file fragments in
  /etc/unbound/unbound.conf.d/*.conf into the unbound configuration.

  The "include-toplevel:" directive has been newly introduced in unbound
  1.11.0 and it requires that any included config file fragment begin its own
  clause (e.g., "server:").

  The existing "include:" directive that was used in previous Debian releases
  of the unbound package only performed textual inclusion, and it was possible
  to construct a set of config file fragments that depended on the presence or
  ordering of specific config file fragments in order to parse correctly. For
  instance, a config file fragment could have specified an option that can
  only appear in the "server:" clause, and rely on a previously included
  config file fragment to begin that clause. This behavior is no longer
  allowed by the use of the "include-toplevel:" directive because it is not
robust against config file fragments being added, removed, or reordered.

  If you are upgrading the unbound package and you have installed any config
  file fragments into /etc/unbound/unbound.conf.d/ you should check that each
  config file fragment begins its own clause (e.g., "server:") and update each
  config file fragment as necessary to be compatible with the behavior of the
  "include-toplevel:" directive.

  If needed, the previous behavior can be restored by changing the following
  line in /etc/unbound/unbound.conf:

      include-toplevel: "/etc/unbound/unbound.conf.d/*.conf"

  to its previous setting:

      include: "/etc/unbound/unbound.conf.d/*.conf"

 -- Robert Edmonds <edmonds@debian.org>  Sun, 09 Aug 2020 19:39:01 -0400

grep (3.6-1) unstable; urgency=low

  From upstream's NEWS:

  The GREP_OPTIONS environment variable no longer affects grep's behavior.
  The variable was declared obsolescent in grep 2.21 (2014), and since
  then any use had caused grep to issue a diagnostic.

 -- Santiago Ruano Rincón <santiago@debian.org>  Mon, 09 Nov 2020 10:57:22 +0100
 



j'avais un souci sur mon M2 nvme , je suppose a cause du noyau , des erreurs permanentes , a priori résolu , avec smartmontools .

en plus c'est écrit sur le ssd


Error Information (NVMe Log 0x01, 16 of 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS
  0         14     0  0x0007  0x4016  0x004            0     1     -
  1         13     0  0x0007  0x4016  0x004            0     1     -
  2         12     0  0x0008  0x4016  0x004            0     1     -
  3         11     0  0x0008  0x4016  0x004            0     1     -
  4         10     0  0x0008  0x4016  0x004            0     1     -
  5          9     0  0x0008  0x4016  0x004            0     1     -
  6          8     0  0x0008  0x4016  0x004            0     1     -
  7          7     0  0x0008  0x4016  0x004            0     1     -
  8          6     0  0x0008  0x4016  0x004            0     1     -
  9          5     0  0x0008  0x4016  0x004            0     1     -
 10          4     0  0x0008  0x4016  0x004            0     1     -
 11          3     0  0x0008  0x4016  0x004            0     1     -
 12          2     0  0x0008  0x4016  0x004            0     1     -
 13          1     0  0x0008  0x4016  0x004            0     1     -
 



je sais pas si possible de l' initialiser


=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        30 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    302801 [155 GB]
Data Units Written:                 2045849 [1,04 TB]
Host Read Commands:                 5631194
Host Write Commands:                14677913
Controller Busy Time:               99
Power Cycles:                       131
Power On Hours:                     273
Unsafe Shutdowns:                   51
Media and Data Integrity Errors:    0
Error Information Log Entries:      14
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               30 Celsius
Temperature Sensor 2:               37 Celsius
 



273 heures de fonctionnement pas vieux  roll


journalctl -r -p err
-- Journal begins at Sun 2021-04-11 17:19:39 CEST, ends at Sun 2021-04-11 17:35:21 CEST. --
avril 11 17:20:05 amdtr4 pulseaudio[1356]: Error opening PCM device front:0: Aucun fichier ou dossier de ce type
 

Dernière modification par robert2a (11-04-2021 17:38:37)

Hors ligne

Pied de page des forums