Linux Mint 21.3 Crash et nécessite un RESET

Postez ici toutes vos demandes d’assistance.
Répondre
Zoya
Messages : 4
Enregistré le : mer. 24 avr. 2024 20:55

Linux Mint 21.3 Crash et nécessite un RESET

Message par Zoya »

Bonjour,

De manière totalement aléatoire pendant l'utilisation, mon système crash et c'est particulièrement désagréable, surtout que je ne peux pas reprendre la main sur le système et je suis obligé de faire un redémarrage de l'ordinateur ...

J'ai cherché du côté carte graphique et température des composants mais je n'ai rien remarqué de particulier à signaler.

Par avance, merci à toutes les bonne âmes qui se pencheront sur ce problème.

Code : Tout sélectionner

System:
  Kernel: 5.15.0-105-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
    tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
    base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: ASUSTeK model: P8Z77-V LX2 v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 0501 date: 09/28/2012
CPU:
  Info: quad core model: Intel Core i5-3470 bits: 64 type: MCP smt: <unsupported> arch: Ivy Bridge
    rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 2382 high: 3142 min/max: 1600/3600 cores: 1: 1703 2: 2130 3: 3142 4: 2556
    bogomips: 25674
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: AMD Barts XT [Radeon HD 6870] driver: radeon v: kernel pcie: speed: 5 GT/s lanes: 16
    ports: active: HDMI-A-1 empty: DP-1, DP-2, DVI-D-1, DVI-I-1 bus-ID: 01:00.0 chip-ID: 1002:6738
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,radeon
    unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
  Monitor-1: HDMI-0 mapped: HDMI-A-1 model: LG (GoldStar) MP59G serial: <filter> res: 1920x1080
    hz: 60 dpi: 102 size: 480x270mm (18.9x10.6") diag: 551mm (21.7") modes: max: 1920x1080
    min: 720x400
  OpenGL: renderer: AMD BARTS (DRM 2.50.0 / 5.15.0-105-generic LLVM 15.0.7)
    v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASUSTeK P8Z77-V LX
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403
  Device-2: AMD Barts HDMI Audio [Radeon HD 6790/6850/6870 / 7720 OEM] driver: snd_hda_intel
    v: kernel pcie: speed: 5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 1002:aa88 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-105-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK P8 series
    driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 111.79 GiB used: 24.92 GiB (22.3%)
  ID-1: /dev/sda vendor: Kingston model: SH103S3120G size: 111.79 GiB speed: 3.0 Gb/s type: SSD
    serial: <filter> rev: BBF0 scheme: GPT
Partition:
  ID-1: / size: 108.98 GiB used: 24.91 GiB (22.9%) fs: ext4 dev: /dev/sda3
  ID-2: /boot/efi size: 512 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda2
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0 speed: 480 Mb/s
    chip-ID: 8087:0024 class-ID: 0900
  Hub-3: 2-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0 speed: 480 Mb/s
    chip-ID: 8087:0024 class-ID: 0900
  Device-1: 2-1.7:3 info: Dell Model L100 Keyboard type: Keyboard driver: hid-generic,usbhid
    interfaces: 1 rev: 1.1 speed: 1.5 Mb/s power: 70mA chip-ID: 413c:2105 class-ID: 0301
  Device-2: 2-1.8:4 info: MosArt USB Device type: Mouse driver: hid-generic,usbhid interfaces: 1
    rev: 1.1 speed: 12 Mb/s power: 98mA chip-ID: 062a:3688 class-ID: 0301
  Hub-5: 3-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-6: 4-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: radeon temp: 40.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2264 apt: 2253 flatpak: 11
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/Floorp.list
    1: deb [signed-by=/usr/share/keyrings/Floorp.gpg] https: //ppa.floorp.app/$(ARCH) ./
  No active apt repos in: /etc/apt/sources.list.d/amdgpu-proprietary.list
  Active apt repos in: /etc/apt/sources.list.d/amdgpu.list
    1: deb https: //repo.radeon.com/amdgpu/6.0.2/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https: //mirror.cyberbits.eu/linuxmint/packages virginia main upstream import backport
    2: deb http: //mirrors.ircam.fr/pub/ubuntu/archive jammy main restricted universe multiverse
    3: deb http: //mirrors.ircam.fr/pub/ubuntu/archive jammy-updates main restricted universe multiverse
    4: deb http: //mirrors.ircam.fr/pub/ubuntu/archive jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/rocm.list
    1: deb [arch=amd64] https: //repo.radeon.com/rocm/apt/6.0.2 focal main
Info:
  Processes: 235 Uptime: 7m wakeups: 0 Memory: 7.71 GiB used: 2.76 GiB (35.8%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon v: 6.0.4 inxi: 3.3.13
inxi -Gx

Code : Tout sélectionner

Graphics:
  Device-1: AMD Barts XT [Radeon HD 6870] driver: radeon v: kernel
    bus-ID: 01:00.0
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,radeon
    unloaded: fbdev,modesetting,vesa gpu: radeon resolution: 1920x1080~60Hz
  OpenGL: renderer: AMD BARTS (DRM 2.50.0 / 5.15.0-105-generic LLVM 15.0.7)
    v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes

Ma seule piste c'est le retour dmesg :

Code : Tout sélectionner

[    1.385993] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    1.386254] ata6.00: ATA-8: KINGSTON SH103S3120G, 506ABBF0, max UDMA/133
[    1.386663] ata6.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.395896] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
Pc : Fixe custom | Cinnamon 6.0.4 | quad core model: Intel Core i5-3470 | Linux Mint 21.3 Virginia | 6.5.0-28-generic x86_64 | 7.7 GiB | AMD Barts XT [Radeon HD 6870]

Avatar du membre
michLapprenti
Messages : 487
Enregistré le : sam. 20 août 2016 20:11

Re: Linux Mint 21.3 Crash et nécessite un RESET

Message par michLapprenti »

Bonjour Zoya

En notant "ACPI Error" dans recherche (fonction en haut à droite du forum)
possible piste :arrow: viewtopic.php?p=234456#p234456


Merci de faire ta signature :arrow: viewtopic.php?f=2&t=1514 pour que les Aidants puissent au mieux te répondre
Pc :Lenovo ThinkPad-W510 | Linux Mint 21.1 Vera | Xfce 4.16.0 | 5.15.0-71-generic x86_64 | dual core model: Intel Core i7 M 620 bits: 64 type: MT MCP | Memory: 7.63 GiB | NVIDIA GT216GLM [Quadro FX 880M] | disque dur: 465.2 go.

Avatar du membre
cyrille
Administrateur du site
Messages : 13037
Enregistré le : mar. 19 sept. 2017 08:49
Localisation : Nowhere
Contact :

Re: Linux Mint 21.3 Crash et nécessite un RESET

Message par cyrille »

As tu un second PC qui pourrait accéder à ce PC en SSH quand il crashe pour voir si ça vient du serveur X ou du système ?

Sinon que retourne

Code : Tout sélectionner

sudo dmesg | egrep 'fail|warn|error'
?séuqartéd sel ruoP / sécnoféd sel ruoP / sreiruréB sel ruoP / ?étéicos elleuQ

https://crust.ovh

Zoya
Messages : 4
Enregistré le : mer. 24 avr. 2024 20:55

Re: Linux Mint 21.3 Crash et nécessite un RESET

Message par Zoya »

Bonjour à tous et merci pour vos réponses,

Voici le retour de
sudo dmesg | egrep 'fail|warn|error'

Code : Tout sélectionner

[    1.316427] usb 2-1.8: device descriptor read/64, error -32
[    1.549079] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[    1.549935] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[    1.557736] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[    1.563737] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[    1.567732] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[    1.619609] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
[  117.958289] capability: warning: `gvfsd-admin' uses 32-bit capabilities (legacy support in use)
Depuis j'ai basculé sur un kernel plus récent mais j'ai eu un nouveau crash système avec besoin de redémarrer la machine au niveau hardware

puis j'ai mis à jour le bios de ma carte mère et depuis pour l'instant je n'ai plus de crash système.

J'ai tenté de couper acpi directement depuis le fichier GRUB mais ma carte graphique ne fonctionnait plus ... donc j'ai rétablis la configuration d'origine de GRUB et j'ai toujours les erreurs relative à ACPI dans mes logs mais j'ai l'impression que ça ne gêne pas le fonctionnement.

Je ne veux pas crier victoire trop tôt mais il semble que mettre à jour le BIOS à été la correction salvatrice du problème de crash inattendu avec nécessitez de redémarrage hardware.

Je vous tiens au courant !
Pc : Fixe custom | Cinnamon 6.0.4 | quad core model: Intel Core i5-3470 | Linux Mint 21.3 Virginia | 6.5.0-28-generic x86_64 | 7.7 GiB | AMD Barts XT [Radeon HD 6870]

Avatar du membre
cyrille
Administrateur du site
Messages : 13037
Enregistré le : mar. 19 sept. 2017 08:49
Localisation : Nowhere
Contact :

Re: Linux Mint 21.3 Crash et nécessite un RESET

Message par cyrille »

Cool dans ce cas
Bonne route sous Linux
?séuqartéd sel ruoP / sécnoféd sel ruoP / sreiruréB sel ruoP / ?étéicos elleuQ

https://crust.ovh

Zoya
Messages : 4
Enregistré le : mer. 24 avr. 2024 20:55

Re: Linux Mint 21.3 Crash et nécessite un RESET

Message par Zoya »

Arf me voilà de retour car je viens juste d'avoir un plantage ...

mon problème est toujours là mais j'ai aucune piste, mes seuls erreurs dans le log suivant ne semble pas provoquer la panne puisque hier elles apparaissaient aussi et pourtant je n'ai pas subi de plantage ...

J'ai l'impression que la panne se produit de manière totalement décorrélé des applications ou de l'utilisation. Je commence à me poser la question si ça ne pourrai pas venir du bloc alim ?

journalctl -p err..alert

Code : Tout sélectionner

avril 28 14:19:50 zoya-pc kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
avril 28 14:19:50 zoya-pc kernel: usb 2-1.8: device descriptor read/64, error -32
avril 28 14:19:50 zoya-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)
avril 28 14:19:50 zoya-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
avril 28 14:19:50 zoya-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)
avril 28 14:19:50 zoya-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
avril 28 14:19:50 zoya-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)
avril 28 14:19:50 zoya-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
avril 28 14:19:50 zoya-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)
avril 28 14:19:50 zoya-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
avril 28 14:19:50 zoya-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)
avril 28 14:19:50 zoya-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
avril 28 14:19:50 zoya-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20230331/psargs-330)
avril 28 14:19:50 zoya-pc kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20230331/psparse-529)
avril 28 14:19:50 zoya-pc kernel: ================================================================================
avril 28 14:19:50 zoya-pc kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-5nKPnc/linux-hwe-6.5-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43
avril 28 14:19:50 zoya-pc kernel: index 1 is out of range for type 'UCHAR [1]'
avril 28 14:19:50 zoya-pc kernel: ================================================================================
avril 28 14:20:00 zoya-pc systemd[1]: Failed to start casper-md5check Verify Live ISO checksums.
avril 28 14:20:20 zoya-pc pulseaudio[907]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote appli>
Pc : Fixe custom | Cinnamon 6.0.4 | quad core model: Intel Core i5-3470 | Linux Mint 21.3 Virginia | 6.5.0-28-generic x86_64 | 7.7 GiB | AMD Barts XT [Radeon HD 6870]

Zoya
Messages : 4
Enregistré le : mer. 24 avr. 2024 20:55

Re: Linux Mint 21.3 Crash et nécessite un RESET

Message par Zoya »

Et voici le cotenu de syslog au moment d'un crash système

Code : Tout sélectionner

Apr 28 20:58:57 zoya-pc dbus-daemon[711]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.network1.service': Unit dbus-org.freedesktop.network1.service not found.
Apr 28 20:58:57 zoya-pc networkd-dispatcher[854]: WARNING: systemd-networkd is not running, output will be incomplete.
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]: ERROR:Unknown state for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='n/a', administrative='unmanaged'): n/a
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]: Traceback (most recent call last):
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]:   File "/usr/bin/networkd-dispatcher", line 298, in trigger_all
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]:     self.handle_state(iface_name,
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]:   File "/usr/bin/networkd-dispatcher", line 348, in handle_state
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]:     raise UnknownState(operational_state)
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]: UnknownState: n/a
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='enp3s0', type='ether', operational='n/a', administrative='unmanaged'): n/a
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]: Traceback (most recent call last):
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]:   File "/usr/bin/networkd-dispatcher", line 298, in trigger_all
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]:     self.handle_state(iface_name,
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]:   File "/usr/bin/networkd-dispatcher", line 348, in handle_state
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]:     raise UnknownState(operational_state)
Apr 28 20:58:57 zoya-pc networkd-dispatcher[722]: UnknownState: n/a
Apr 28 20:58:57 zoya-pc systemd[1]: Started Dispatcher daemon for systemd-networkd.
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4703] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-bluetooth.so)
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4718] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-adsl.so)
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4721] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4721] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4722] manager: Networking is enabled by state file
Apr 28 20:58:57 zoya-pc dbus-daemon[711]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=712 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4751] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-settings-plugin-ifupdown.so")
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4752] settings: Loaded settings plugin: keyfile (internal)
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4753] ifupdown: management mode: unmanaged
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4753] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4753] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4753] ifupdown: interfaces file /etc/network/interfaces.d/* doesn't exist
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4753] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4794] dhcp-init: Using DHCP client 'internal'
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4796] device (lo): carrier: link connected
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4799] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4815] manager: (enp3s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4843] settings: (enp3s0): created default wired connection 'Connexion filaire 1'
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.4846] device (enp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 28 20:58:57 zoya-pc kernel: [   10.257939] RTL8211E Gigabit Ethernet r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)
Apr 28 20:58:57 zoya-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 28 20:58:57 zoya-pc dbus-daemon[711]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 28 20:58:57 zoya-pc systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 28 20:58:57 zoya-pc systemd[1]: Received SIGRTMIN+21 from PID 215 (plymouthd).
Apr 28 20:58:57 zoya-pc systemd[1]: Received SIGRTMIN+21 from PID 215 (plymouthd).
Apr 28 20:58:57 zoya-pc systemd[1]: Finished Hold until boot process finishes up.
Apr 28 20:58:57 zoya-pc systemd[1]: Starting Set console scheme...
Apr 28 20:58:57 zoya-pc systemd[1]: Started Light Display Manager.
Apr 28 20:58:57 zoya-pc systemd[1]: Finished Set console scheme.
Apr 28 20:58:57 zoya-pc systemd[1]: Created slice Slice /system/getty.
Apr 28 20:58:57 zoya-pc systemd[1]: Started Getty on tty1.
Apr 28 20:58:57 zoya-pc systemd[1]: Reached target Login Prompts.
Apr 28 20:58:57 zoya-pc systemd[1]: Started Modem Manager.
Apr 28 20:58:57 zoya-pc systemd[1]: Started Bluetooth management mechanism.
Apr 28 20:58:57 zoya-pc systemd[1]: Started Disk Manager.
Apr 28 20:58:57 zoya-pc udisksd[737]: Cleaning up mount point /media/zoya/ESD-USB (device 8:33 no longer exists)
Apr 28 20:58:57 zoya-pc udisksd[737]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Apr 28 20:58:57 zoya-pc systemd[1]: mintsystem.service: Deactivated successfully.
Apr 28 20:58:57 zoya-pc kernel: [   10.498768] r8169 0000:03:00.0 enp3s0: Link is Down
Apr 28 20:58:57 zoya-pc NetworkManager[712]: <info>  [1714330737.7328] modem-manager: ModemManager available
Apr 28 20:58:57 zoya-pc systemd[1]: e2scrub_reap.service: Deactivated successfully.
Apr 28 20:58:57 zoya-pc systemd[1]: Finished Remove Stale Online ext4 Metadata Check Snapshots.
Apr 28 20:58:58 zoya-pc avahi-daemon[708]: Server startup complete. Host name is zoya-pc.local. Local service cookie is 1969286132.
Apr 28 20:58:58 zoya-pc systemd[1]: Created slice User Slice of UID 1000.
Apr 28 20:58:58 zoya-pc systemd[1]: Starting User Runtime Directory /run/user/1000...
Apr 28 20:58:58 zoya-pc systemd[1]: Finished User Runtime Directory /run/user/1000.
Apr 28 20:58:58 zoya-pc systemd[1]: Starting User Manager for UID 1000...
Apr 28 20:58:58 zoya-pc systemd[898]: Queued start job for default target Main User Target.
Apr 28 20:58:58 zoya-pc systemd[898]: Created slice User Application Slice.
Apr 28 20:58:58 zoya-pc dbus-daemon[711]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=1000 pid=906 comm="/usr/bin/pipewire " label="unconfined")
Apr 28 20:58:58 zoya-pc systemd[898]: Created slice User Core Session Slice.
Apr 28 20:58:58 zoya-pc dbus-daemon[711]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Apr 28 20:58:58 zoya-pc systemd[898]: Reached target Paths.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Successfully called chroot.
Apr 28 20:58:58 zoya-pc systemd[898]: Reached target Timers.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Successfully dropped privileges.
Apr 28 20:58:58 zoya-pc systemd[898]: Starting D-Bus User Message Bus Socket...
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Successfully limited resources.
Apr 28 20:58:58 zoya-pc systemd[898]: Listening on GnuPG network certificate management daemon.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Running.
Apr 28 20:58:58 zoya-pc systemd[898]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Watchdog thread running.
Apr 28 20:58:58 zoya-pc systemd[898]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Canary thread running.
Apr 28 20:58:58 zoya-pc systemd[898]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Successfully made thread 906 of process 906 owned by '1000' high priority at nice level -11.
Apr 28 20:58:58 zoya-pc systemd[898]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Supervising 1 threads of 1 processes of 1 users.
Apr 28 20:58:58 zoya-pc systemd[898]: Listening on PipeWire Multimedia System Socket.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Successfully made thread 907 of process 907 owned by '1000' high priority at nice level -11.
Apr 28 20:58:58 zoya-pc systemd[898]: Listening on debconf communication socket.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Supervising 2 threads of 2 processes of 1 users.
Apr 28 20:58:58 zoya-pc systemd[898]: Listening on Sound System.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Supervising 2 threads of 2 processes of 1 users.
Apr 28 20:58:58 zoya-pc systemd[898]: Listening on Speech Dispatcher Socket.
Apr 28 20:58:58 zoya-pc systemd[898]: Listening on D-Bus User Message Bus Socket.
Apr 28 20:58:58 zoya-pc systemd[898]: Reached target Sockets.
Apr 28 20:58:58 zoya-pc systemd[898]: Reached target Basic System.
Apr 28 20:58:58 zoya-pc systemd[1]: Started User Manager for UID 1000.
Apr 28 20:58:58 zoya-pc systemd[898]: Started PipeWire Multimedia Service.
Apr 28 20:58:58 zoya-pc systemd[1]: Started Session c1 of User zoya.
Apr 28 20:58:58 zoya-pc systemd[898]: Starting Sound Service...
Apr 28 20:58:58 zoya-pc systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Apr 28 20:58:58 zoya-pc systemd[1]: Started RealtimeKit Scheduling Policy Service.
Apr 28 20:58:58 zoya-pc systemd[898]: Started D-Bus User Message Bus.
Apr 28 20:58:58 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] AppArmor D-Bus mediation is enabled
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Supervising 2 threads of 2 processes of 1 users.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Successfully made thread 930 of process 906 owned by '1000' RT at priority 20.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Supervising 3 threads of 2 processes of 1 users.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Supervising 3 threads of 2 processes of 1 users.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Successfully made thread 946 of process 907 owned by '1000' RT at priority 5.
Apr 28 20:58:58 zoya-pc rtkit-daemon[915]: Supervising 4 threads of 2 processes of 1 users.
Apr 28 20:58:59 zoya-pc rtkit-daemon[915]: Supervising 4 threads of 2 processes of 1 users.
Apr 28 20:58:59 zoya-pc rtkit-daemon[915]: Successfully made thread 1057 of process 907 owned by '1000' RT at priority 5.
Apr 28 20:58:59 zoya-pc rtkit-daemon[915]: Supervising 5 threads of 2 processes of 1 users.
Apr 28 20:58:59 zoya-pc dbus-daemon[711]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.33' (uid=1000 pid=907 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Apr 28 20:58:59 zoya-pc systemd[1]: Condition check resulted in Bluetooth service being skipped.
Apr 28 20:58:59 zoya-pc systemd[898]: Started Sound Service.
Apr 28 20:58:59 zoya-pc systemd[898]: Reached target Main User Target.
Apr 28 20:58:59 zoya-pc systemd[898]: Startup finished in 811ms.
Apr 28 20:58:59 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.15' (uid=1000 pid=1157 comm="csd-a11y-settings " label="unconfined")
Apr 28 20:58:59 zoya-pc systemd[898]: Starting User preferences database...
Apr 28 20:58:59 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'ca.desrt.dconf'
Apr 28 20:58:59 zoya-pc systemd[898]: Started User preferences database.
Apr 28 20:58:59 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.19' (uid=1000 pid=1163 comm="csd-clipboard " label="unconfined")
Apr 28 20:58:59 zoya-pc systemd[898]: Starting Virtual filesystem service...
Apr 28 20:58:59 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gtk.vfs.Daemon'
Apr 28 20:58:59 zoya-pc systemd[898]: Started Virtual filesystem service.
Apr 28 20:58:59 zoya-pc dbus-daemon[711]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.37' (uid=1000 pid=1171 comm="csd-media-keys " label="unconfined")
Apr 28 20:58:59 zoya-pc systemd[1]: Starting Daemon for power management...
Apr 28 20:58:59 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.26' (uid=1000 pid=1142 comm="csd-automount " label="unconfined")
Apr 28 20:58:59 zoya-pc systemd[898]: Starting Virtual filesystem service - disk device monitor...
Apr 28 20:58:59 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Apr 28 20:58:59 zoya-pc systemd[898]: Started Virtual filesystem service - disk device monitor.
Apr 28 20:58:59 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.26' (uid=1000 pid=1142 comm="csd-automount " label="unconfined")
Apr 28 20:59:00 zoya-pc dbus-daemon[711]: [system] Successfully activated service 'org.freedesktop.UPower'
Apr 28 20:59:00 zoya-pc systemd[1]: Started Daemon for power management.
Apr 28 20:59:00 zoya-pc systemd[898]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating service name='org.gnome.OnlineAccounts' requested by ':1.34' (uid=1000 pid=1268 comm="/usr/libexec/gvfs-goa-volume-monitor " label="unconfined")
Apr 28 20:59:00 zoya-pc ModemManager[833]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0': not supported by any plugin
Apr 28 20:59:00 zoya-pc goa-daemon[1273]: goa-daemon version 3.44.0 starting
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating service name='org.gnome.Identity' requested by ':1.35' (uid=1000 pid=1273 comm="/usr/libexec/goa-daemon " label="unconfined")
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gnome.OnlineAccounts'
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Apr 28 20:59:00 zoya-pc systemd[898]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Apr 28 20:59:00 zoya-pc dbus-daemon[711]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.43' (uid=1000 pid=1148 comm="csd-color " label="unconfined")
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gnome.Identity'
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.26' (uid=1000 pid=1142 comm="csd-automount " label="unconfined")
Apr 28 20:59:00 zoya-pc systemd[1]: Starting Manage, Install and Generate Color Profiles...
Apr 28 20:59:00 zoya-pc systemd[898]: Starting Virtual filesystem service - digital camera monitor...
Apr 28 20:59:00 zoya-pc dbus-daemon[711]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Apr 28 20:59:00 zoya-pc systemd[1]: Started Manage, Install and Generate Color Profiles.
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Apr 28 20:59:00 zoya-pc systemd[898]: Started Virtual filesystem service - digital camera monitor.
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.26' (uid=1000 pid=1142 comm="csd-automount " label="unconfined")
Apr 28 20:59:00 zoya-pc systemd[898]: Starting Virtual filesystem service - Apple File Conduit monitor...
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Apr 28 20:59:00 zoya-pc systemd[898]: Started Virtual filesystem service - Apple File Conduit monitor.
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.26' (uid=1000 pid=1142 comm="csd-automount " label="unconfined")
Apr 28 20:59:00 zoya-pc systemd[898]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Apr 28 20:59:00 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Apr 28 20:59:00 zoya-pc systemd[898]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Apr 28 20:59:01 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating service name='org.cinnamon.ScreenSaver' requested by ':1.7' (uid=1000 pid=908 comm="cinnamon-session --session cinnamon " label="unconfined")
Apr 28 20:59:01 zoya-pc NetworkManager[712]: <info>  [1714330741.7888] agent-manager: agent[6aa72bb60de48266,:1.55/org.freedesktop.nm-applet/1000]: agent registered
Apr 28 20:59:01 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.48' (uid=1000 pid=1369 comm="/usr/libexec/evolution-data-server/evolution-alarm" label="unconfined")
Apr 28 20:59:01 zoya-pc org.cinnamon.ScreenSaver[1362]: Loading AccountsService
Apr 28 20:59:01 zoya-pc org.cinnamon.ScreenSaver[1362]: Fractional scaling active: False
Apr 28 20:59:01 zoya-pc cinnamon-killer-daemon: Bound Cinnamon restart to <Control><Alt>Escape.
Apr 28 20:59:01 zoya-pc systemd[898]: Starting Evolution source registry...
Apr 28 20:59:01 zoya-pc org.cinnamon.ScreenSaver[1362]: Trying to connect to logind...
Apr 28 20:59:01 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.cinnamon.ScreenSaver'
Apr 28 20:59:01 zoya-pc org.cinnamon.ScreenSaver[1362]: Starting screensaver...
Apr 28 20:59:01 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gnome.evolution.dataserver.Sources5'
Apr 28 20:59:01 zoya-pc systemd[898]: Started Evolution source registry.
Apr 28 20:59:02 zoya-pc org.cinnamon.ScreenSaver[1362]: Cinnamon Screensaver support not found in current theme - adding some...
Apr 28 20:59:02 zoya-pc cinnamon-session[908]: WARNING: t+2.55104s: Detected that screensaver has appeared on the bus
Apr 28 20:59:02 zoya-pc org.cinnamon.ScreenSaver[1362]: AccountsService ready
Apr 28 20:59:02 zoya-pc org.cinnamon.ScreenSaver[1362]: Successfully using logind
Apr 28 20:59:02 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.48' (uid=1000 pid=1369 comm="/usr/libexec/evolution-data-server/evolution-alarm" label="unconfined")
Apr 28 20:59:02 zoya-pc systemd[898]: Starting Evolution calendar service...
Apr 28 20:59:02 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8'
Apr 28 20:59:02 zoya-pc systemd[898]: Started Evolution calendar service.
Apr 28 20:59:02 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook10' unit='evolution-addressbook-factory.service' requested by ':1.55' (uid=1000 pid=1426 comm="/usr/libexec/evolution-calendar-factory " label="unconfined")
Apr 28 20:59:02 zoya-pc systemd[898]: Starting Evolution address book service...
Apr 28 20:59:02 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating service name='org.cinnamon.CalendarServer' requested by ':1.41' (uid=1000 pid=1314 comm="cinnamon --replace " label="unconfined")
Apr 28 20:59:02 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10'
Apr 28 20:59:02 zoya-pc systemd[898]: Started Evolution address book service.
Apr 28 20:59:02 zoya-pc systemd[1]: dmesg.service: Deactivated successfully.
Apr 28 20:59:02 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.50' (uid=1000 pid=1368 comm="/usr/bin/python3 /usr/bin/blueman-applet " label="unconfined")
Apr 28 20:59:02 zoya-pc systemd[898]: Starting Bluetooth OBEX service...
Apr 28 20:59:02 zoya-pc obexd[1487]: OBEX daemon 5.64
Apr 28 20:59:02 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.bluez.obex'
Apr 28 20:59:02 zoya-pc systemd[898]: Started Bluetooth OBEX service.
Apr 28 20:59:02 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.cinnamon.CalendarServer'
Apr 28 20:59:03 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.45' (uid=1000 pid=1363 comm="nemo-desktop " label="unconfined")
Apr 28 20:59:03 zoya-pc systemd[898]: Starting Virtual filesystem metadata service...
Apr 28 20:59:03 zoya-pc dbus-daemon[926]: [session uid=1000 pid=926] Successfully activated service 'org.gtk.vfs.Metadata'
Apr 28 20:59:03 zoya-pc systemd[898]: Started Virtual filesystem metadata service.
Apr 28 20:59:03 zoya-pc NetworkManager[712]: <info>  [1714330743.7294] manager: startup complete
Apr 28 20:59:03 zoya-pc systemd[1]: Finished Network Manager Wait Online.
Apr 28 20:59:03 zoya-pc systemd[1]: Reached target Network is Online.
Apr 28 20:59:03 zoya-pc systemd[1]: Started Make remote CUPS printers available locally.
Apr 28 20:59:03 zoya-pc systemd[1]: Starting Tool to automatically collect and submit kernel crash signatures...
Apr 28 20:59:03 zoya-pc systemd[1]: kerneloops.service: Found left-over process 1529 (kerneloops) in control group while starting unit. Ignoring.
Apr 28 20:59:03 zoya-pc systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Apr 28 20:59:03 zoya-pc systemd[1]: Started Tool to automatically collect and submit kernel crash signatures.
Apr 28 20:59:03 zoya-pc systemd[1]: Reached target Multi-User System.
Apr 28 20:59:03 zoya-pc systemd[1]: Reached target Graphical Interface.
Apr 28 20:59:03 zoya-pc systemd[1]: Starting casper-md5check Verify Live ISO checksums...
Apr 28 20:59:03 zoya-pc systemd[1]: Starting Record Runlevel Change in UTMP...
Apr 28 20:59:03 zoya-pc casper-md5check[1532]: .fopen md5_file: No such file or directory
Apr 28 20:59:03 zoya-pc casper-md5check[1532]: Checking integrity, this may take some time (or try: fsck.mode=skip)
Apr 28 20:59:03 zoya-pc systemd[1]: casper-md5check.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 20:59:03 zoya-pc systemd[1]: casper-md5check.service: Failed with result 'exit-code'.
Apr 28 20:59:03 zoya-pc systemd[1]: Failed to start casper-md5check Verify Live ISO checksums.
Apr 28 20:59:03 zoya-pc systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Apr 28 20:59:03 zoya-pc systemd[1]: Finished Record Runlevel Change in UTMP.
Apr 28 20:59:03 zoya-pc systemd[1]: Startup finished in 6.697s (kernel) + 9.843s (userspace) = 16.540s.
Apr 28 20:59:07 zoya-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2577] device (enp3s0): carrier: link connected
Apr 28 20:59:11 zoya-pc kernel: [   24.026861] r8169 0000:03:00.0 enp3s0: Link is Up - 100Mbps/Full - flow control rx/tx
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2581] device (enp3s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2591] policy: auto-activating connection 'Connexion filaire 1' (626f001f-a04c-38f1-a409-39e28c639dda)
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2595] device (enp3s0): Activation: starting connection 'Connexion filaire 1' (626f001f-a04c-38f1-a409-39e28c639dda)
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2596] device (enp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2597] manager: NetworkManager state is now CONNECTING
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2598] device (enp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2603] device (enp3s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2608] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2661] dhcp4 (enp3s0): state changed new lease, address=192.168.0.17
Apr 28 20:59:11 zoya-pc avahi-daemon[708]: Joining mDNS multicast group on interface enp3s0.IPv4 with address 192.168.0.17.
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2673] device (enp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Apr 28 20:59:11 zoya-pc avahi-daemon[708]: New relevant interface enp3s0.IPv4 for mDNS.
Apr 28 20:59:11 zoya-pc dbus-daemon[711]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=712 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Apr 28 20:59:11 zoya-pc avahi-daemon[708]: Registering new address record for 192.168.0.17 on enp3s0.IPv4.
Apr 28 20:59:11 zoya-pc avahi-daemon[708]: Joining mDNS multicast group on interface enp3s0.IPv6 with address fe80::edfd:f826:4ebf:5af5.
Apr 28 20:59:11 zoya-pc avahi-daemon[708]: New relevant interface enp3s0.IPv6 for mDNS.
Apr 28 20:59:11 zoya-pc avahi-daemon[708]: Registering new address record for fe80::edfd:f826:4ebf:5af5 on enp3s0.*.
Apr 28 20:59:11 zoya-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 28 20:59:11 zoya-pc dbus-daemon[711]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Apr 28 20:59:11 zoya-pc systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2993] device (enp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2995] device (enp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2997] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.2999] manager: NetworkManager state is now CONNECTED_SITE
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.3000] policy: set 'Connexion filaire 1' (enp3s0) as default for IPv4 routing and DNS
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.3004] device (enp3s0): Activation: successful, device activated.
Apr 28 20:59:11 zoya-pc systemd-resolved[672]: enp3s0: Bus client set default route setting: yes
Apr 28 20:59:11 zoya-pc systemd-resolved[672]: enp3s0: Bus client set DNS server list to: 192.168.0.254
Apr 28 20:59:11 zoya-pc NetworkManager[712]: <info>  [1714330751.5322] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 28 20:59:12 zoya-pc NetworkManager[712]: <info>  [1714330752.5670] policy: set 'Connexion filaire 1' (enp3s0) as default for IPv6 routing and DNS
Apr 28 20:59:12 zoya-pc avahi-daemon[708]: Leaving mDNS multicast group on interface enp3s0.IPv6 with address fe80::edfd:f826:4ebf:5af5.
Apr 28 20:59:12 zoya-pc avahi-daemon[708]: Joining mDNS multicast group on interface enp3s0.IPv6 with address 2a01:e0a:b86:90d0:a037:be5f:dff7:21f3.
Apr 28 20:59:12 zoya-pc avahi-daemon[708]: Registering new address record for 2a01:e0a:b86:90d0:a037:be5f:dff7:21f3 on enp3s0.*.
Apr 28 20:59:12 zoya-pc avahi-daemon[708]: Withdrawing address record for fe80::edfd:f826:4ebf:5af5 on enp3s0.
Apr 28 20:59:12 zoya-pc systemd-resolved[672]: enp3s0: Bus client set DNS server list to: 192.168.0.254, fd0f:ee:b0::1
Apr 28 20:59:14 zoya-pc avahi-daemon[708]: Registering new address record for 2a01:e0a:b86:90d0:67e2:770b:7dd4:1ca5 on enp3s0.*.
Apr 28 20:59:21 zoya-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Apr 28 20:59:22 zoya-pc dbus-daemon[711]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.68' (uid=1000 pid=1660 comm="flatpak uninstall --unused -y " label="unconfined")
Apr 28 20:59:22 zoya-pc systemd[1]: Starting Locale Service...
Apr 28 20:59:22 zoya-pc dbus-daemon[711]: [system] Successfully activated service 'org.freedesktop.locale1'
Apr 28 20:59:22 zoya-pc systemd[1]: Started Locale Service.
Apr 28 20:59:22 zoya-pc org.cinnamon.CalendarServer[1477]: SET TIME: from 2024-04-01T00:00:00+02 to 2024-05-12T23:59:59+02
Apr 28 20:59:22 zoya-pc org.cinnamon.CalendarServer[1477]: Discovered calendar:  Dates de naissance et anniversaires
Apr 28 20:59:22 zoya-pc org.cinnamon.CalendarServer[1477]: Discovered calendar:  Personnel
Apr 28 20:59:22 zoya-pc org.cinnamon.CalendarServer[1477]: SET TIME: from 2024-04-01T00:00:00+02 to 2024-05-12T23:59:59+02
Apr 28 20:59:24 zoya-pc pulseaudio[907]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Apr 28 20:59:24 zoya-pc systemd[1]: systemd-fsckd.service: Deactivated successfully.
Apr 28 20:59:27 zoya-pc systemd-timesyncd[673]: Initial synchronization to time server [2620:2d:4000:1::40]:123 (ntp.ubuntu.com).
Apr 28 20:59:27 zoya-pc systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 28 20:59:27 zoya-pc systemd[1]: blueman-mechanism.service: Deactivated successfully.
Apr 28 20:59:32 zoya-pc cinnamon-session[908]: WARNING: t+32.55451s: Detected that screensaver has left the bus
Pc : Fixe custom | Cinnamon 6.0.4 | quad core model: Intel Core i5-3470 | Linux Mint 21.3 Virginia | 6.5.0-28-generic x86_64 | 7.7 GiB | AMD Barts XT [Radeon HD 6870]

Avatar du membre
tyrry
modérateur
Messages : 6029
Enregistré le : mar. 21 juil. 2015 07:42
Localisation : à l'ouest

Re: Linux Mint 21.3 Crash et nécessite un RESET

Message par tyrry »

Bonjour,
Pour une aide la plus efficace possible, merci de mettre la configuration de votre matériel dans la signature, comme demandé lors de votre inscription, pour cela Aide pour une signature technique
@+
LXDE Desktop résistance
Debian 12 Bookworm

Répondre