Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

Pages : 1

#1 Le 16/11/2023, à 13:30

chrislc

[Abandonné] Unrecoverable failure required component budgie-wm.desktop

Bonjour,

Suite à une tentative de récupérer du son disparu de ma sortie HDMI (vidéo ok)
première discussion ici

j'ai des problèmes de stabilité sur Ubuntu 22.04

principal@principal-Satellite-P300:~$ journalctl --no-pager -b -p err
nov. 16 11:07:14 principal-Satellite-P300 kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x1000 SErr 0x50000 action 0x0
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: cmd 60/08:60:00:08:00/00:00:00:00:00/40 tag 12 ncq dma 4096 in
                                                           res 41/40:08:00:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:07:14 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x8000 SErr 0x50000 action 0x0
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: cmd 60/08:78:00:08:00/00:00:00:00:00/40 tag 15 ncq dma 4096 in
                                                           res 41/40:08:00:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:07:14 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
nov. 16 11:07:14 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb, logical block 256, async page read
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x2000124 SErr 0x50000 action 0x0
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: cmd 60/08:10:00:08:00/00:00:00:00:00/40 tag 2 ncq dma 4096 in
                                                           res 41/40:08:00:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:07:14 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x7800 SErr 0x50000 action 0x0
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: cmd 60/08:58:00:08:00/00:00:00:00:00/40 tag 11 ncq dma 4096 in
                                                           res 41/40:08:00:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:07:14 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:07:14 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0
nov. 16 11:07:14 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 0, async page read
nov. 16 11:07:14 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 1, async page read
nov. 16 11:07:14 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 2, async page read
nov. 16 11:07:14 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 3, async page read
nov. 16 11:07:14 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 4, async page read
nov. 16 11:07:14 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 5, async page read
nov. 16 11:07:14 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 6, async page read
nov. 16 11:07:14 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 7, async page read
nov. 16 11:07:15 principal-Satellite-P300 systemd-udevd[394]: /etc/udev/rules.d/40-libsane.rules:26: GOTO="libsane_rules_end" has no matching label, ignoring
nov. 16 11:07:16 principal-Satellite-P300 systemd-udevd[394]: /etc/udev/rules.d/S99-2000S1.rules:26: GOTO="libsane_rules_end" has no matching label, ignoring
nov. 16 11:07:22 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x100000 SErr 0x50000 action 0x0
nov. 16 11:07:22 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:07:22 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:07:22 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:07:22 principal-Satellite-P300 kernel: ata5.00: cmd 60/08:a0:00:08:00/00:00:00:00:00/40 tag 20 ncq dma 4096 in
                                                           res 41/40:08:00:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:07:22 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:07:22 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:07:22 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
nov. 16 11:07:26 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x800000 SErr 0x50000 action 0x0
nov. 16 11:07:26 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:07:26 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:07:26 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:07:26 principal-Satellite-P300 kernel: ata5.00: cmd 60/08:b8:00:08:00/00:00:00:00:00/40 tag 23 ncq dma 4096 in
                                                           res 41/40:08:00:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:07:26 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:07:26 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:07:26 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
nov. 16 11:07:26 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb, logical block 256, async page read
nov. 16 11:07:30 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x40200080 SErr 0x50000 action 0x0
nov. 16 11:07:30 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:07:30 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:07:30 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:07:30 principal-Satellite-P300 kernel: ata5.00: cmd 60/08:a8:00:08:00/00:00:00:00:00/40 tag 21 ncq dma 4096 in
                                                           res 41/40:08:00:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:07:30 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:07:30 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:07:30 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
nov. 16 11:07:35 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x1cf8000 SErr 0x50000 action 0x0
nov. 16 11:07:35 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:07:35 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:07:35 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:07:35 principal-Satellite-P300 kernel: ata5.00: cmd 60/01:78:00:08:00/00:00:00:00:00/40 tag 15 ncq dma 512 in
                                                           res 41/40:01:00:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:07:35 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:07:35 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:07:35 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
nov. 16 11:07:35 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 0, async page read
nov. 16 11:07:43 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x7f00 SErr 0x50000 action 0x0
nov. 16 11:07:43 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:07:43 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:07:43 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:07:43 principal-Satellite-P300 kernel: ata5.00: cmd 60/01:60:03:08:00/00:00:00:00:00/40 tag 12 ncq dma 512 in
                                                           res 41/40:01:03:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:07:43 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:07:43 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:07:43 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2051 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
nov. 16 11:07:43 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 3, async page read
nov. 16 11:08:02 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x780000 SErr 0x50000 action 0x0
nov. 16 11:08:02 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:08:02 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:08:02 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:08:02 principal-Satellite-P300 kernel: ata5.00: cmd 60/01:98:04:08:00/00:00:00:00:00/40 tag 19 ncq dma 512 in
                                                           res 41/40:01:04:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:08:02 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:08:02 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:08:02 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2052 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
nov. 16 11:08:02 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 4, async page read
nov. 16 11:08:10 principal-Satellite-P300 kernel: ata5.00: exception Emask 0x0 SAct 0x1840000 SErr 0x50000 action 0x0
nov. 16 11:08:10 principal-Satellite-P300 kernel: ata5.00: irq_stat 0x40000008
nov. 16 11:08:10 principal-Satellite-P300 kernel: ata5: SError: { PHYRdyChg CommWake }
nov. 16 11:08:10 principal-Satellite-P300 kernel: ata5.00: failed command: READ FPDMA QUEUED
nov. 16 11:08:10 principal-Satellite-P300 kernel: ata5.00: cmd 60/01:90:07:08:00/00:00:00:00:00/40 tag 18 ncq dma 512 in
                                                           res 41/40:01:07:08:00/00:00:00:00:00/60 Emask 0x409 (media error) <F>
nov. 16 11:08:10 principal-Satellite-P300 kernel: ata5.00: status: { DRDY ERR }
nov. 16 11:08:10 principal-Satellite-P300 kernel: ata5.00: error: { UNC }
nov. 16 11:08:10 principal-Satellite-P300 kernel: blk_update_request: I/O error, dev sdb, sector 2055 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
nov. 16 11:08:10 principal-Satellite-P300 kernel: Buffer I/O error on dev sdb1, logical block 7, async page read
nov. 16 11:09:57 principal-Satellite-P300 systemd[2556]: /usr/lib/systemd/system-generators/friendly-recovery failed with exit status 1.
nov. 16 11:10:05 principal-Satellite-P300 avahi-daemon[2682]: chroot.c: open() failed: No such file or directory
nov. 16 11:10:10 principal-Satellite-P300 smartd[2668]: Device: /dev/sda [SAT], ATA error count increased from 0 to 4
nov. 16 11:10:10 principal-Satellite-P300 smartd[2668]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (183 bytes) to STDOUT/STDERR:
nov. 16 11:10:10 principal-Satellite-P300 smartd[2668]: /etc/smartmontools/run.d/10mail:
nov. 16 11:10:10 principal-Satellite-P300 smartd[2668]: Your system does not have /usr/bin/mail.  Install the mailx or mailutils package
nov. 16 11:10:10 principal-Satellite-P300 smartd[2668]: run-parts: /etc/smartmontools/run.d/10mail exited with return code 1
nov. 16 11:10:10 principal-Satellite-P300 smartd[2668]: Warning via /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit exit status: 256/1)
nov. 16 11:10:11 principal-Satellite-P300 smartd[2668]: Device: /dev/sdb [SAT], ATA error count increased from 0 to 3733
nov. 16 11:10:11 principal-Satellite-P300 smartd[2668]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (183 bytes) to STDOUT/STDERR:
nov. 16 11:10:11 principal-Satellite-P300 smartd[2668]: /etc/smartmontools/run.d/10mail:
nov. 16 11:10:11 principal-Satellite-P300 smartd[2668]: Your system does not have /usr/bin/mail.  Install the mailx or mailutils package
nov. 16 11:10:11 principal-Satellite-P300 smartd[2668]: run-parts: /etc/smartmontools/run.d/10mail exited with return code 1
nov. 16 11:10:11 principal-Satellite-P300 smartd[2668]: Warning via /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit exit status: 256/1)
nov. 16 11:11:04 principal-Satellite-P300 pulseaudio[4326]: 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.
nov. 16 11:12:26 principal-Satellite-P300 lightdm[7924]: gkr-pam: unable to locate daemon control file
nov. 16 11:12:26 principal-Satellite-P300 pulseaudio[4326]: Error opening PCM device front:0: Aucun fichier ou dossier de ce type
nov. 16 11:12:33 principal-Satellite-P300 gnome-session-binary[8328]: Unrecoverable failure in required component budgie-wm.desktop
nov. 16 11:12:52 principal-Satellite-P300 pulseaudio[8319]: 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.
nov. 16 11:20:50 principal-Satellite-P300 lightdm[9950]: gkr-pam: unable to locate daemon control file
nov. 16 11:20:56 principal-Satellite-P300 gnome-session-binary[9977]: Unrecoverable failure in required component budgie-wm.desktop
nov. 16 11:21:04 principal-Satellite-P300 pulseaudio[9968]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
nov. 16 11:40:12 principal-Satellite-P300 smartd[2668]: Device: /dev/sdb [SAT], 4 Currently unreadable (pending) sectors
nov. 16 11:40:13 principal-Satellite-P300 smartd[2668]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (183 bytes) to STDOUT/STDERR:
nov. 16 11:40:13 principal-Satellite-P300 smartd[2668]: /etc/smartmontools/run.d/10mail:
nov. 16 11:40:13 principal-Satellite-P300 smartd[2668]: Your system does not have /usr/bin/mail.  Install the mailx or mailutils package
nov. 16 11:40:13 principal-Satellite-P300 smartd[2668]: run-parts: /etc/smartmontools/run.d/10mail exited with return code 1
nov. 16 11:40:13 principal-Satellite-P300 smartd[2668]: Warning via /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit exit status: 256/1)

Merci pour votre aide

Dernière modification par chrislc (Le 22/11/2023, à 16:04)

Toshiba Satellite P300-1BB Intel Core 2 Duo P8400 - 2.26 GHz - 4096 Mo - DDR2-SDRAM
Serial ATA / 5400tr/mn / 250 Go  -  WebCam     1,3 Mpx - écran     17 " / 16:10 / 1440 x 900
ATI Mobility Radeon HD 3650 /  512 Mo ]
Ubuntu 22.04.3 LTS - Budgie 10.6.1 - 64 bits

Hors ligne

#2 Le 16/11/2023, à 19:21

inbox

Re : [Abandonné] Unrecoverable failure required component budgie-wm.desktop

Salut,

Peux-tu installer Smartmontools avec :

sudo apt-get install --no-install-recommends smartmontools

Puis récupérer les données Smart avec :

sudo smartctl -s on -a /dev/sdb

A+

Un problème résolu ? Indiquez le en modifiant le titre du sujet.

Hors ligne

#3 Le 16/11/2023, à 22:26

chrislc

Re : [Abandonné] Unrecoverable failure required component budgie-wm.desktop

Salut Inbox

merci pour ton message

voici les éléments 


principal@principal-Satellite-P300:~$ sudo smartctl -s on -a /dev/sdb
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-88-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MK..52GSX
Device Model:     TOSHIBA MK2552GSX
Serial Number:    68QOT1AOT
LU WWN Device Id: 5 000039 111b8707e
Firmware Version: LV010M
User Capacity:    250059350016 bytes [250 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 1.5 Gb/s
Local Time is:    Thu Nov 16 21:25:49 2023 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

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

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 118) minutes.
SCT capabilities: 	       (0x0039)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   099   099   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       1703
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       17603
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   039   039   000    Old_age   Always       -       24679
 10 Spin_Retry_Count        0x0033   253   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       12173
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       8
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       272
193 Load_Cycle_Count        0x0032   084   084   000    Old_age   Always       -       165888
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       36 (Min/Max 8/61)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       4
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       213
222 Loaded_Hours            0x0032   094   094   000    Old_age   Always       -       2592
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       326
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 3733 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 3733 occurred at disk power-on lifetime: 24669 hours (1027 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 92 07 08 00 60  Error: UNC at LBA = 0x00000807 = 2055

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 01 c0 05 08 00 40 00      00:01:48.413  READ FPDMA QUEUED
  60 01 b8 06 08 00 40 00      00:01:48.413  READ FPDMA QUEUED
  60 01 90 07 08 00 40 00      00:01:48.413  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:01:48.412  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      00:01:48.412  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 3732 occurred at disk power-on lifetime: 24669 hours (1027 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 9a 04 08 00 60  Error: UNC at LBA = 0x00000804 = 2052

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 01 b0 07 08 00 40 00      00:01:28.910  READ FPDMA QUEUED
  60 01 a8 06 08 00 40 00      00:01:28.910  READ FPDMA QUEUED
  60 01 a0 05 08 00 40 00      00:01:28.910  READ FPDMA QUEUED
  60 01 98 04 08 00 40 00      00:01:28.910  READ FPDMA QUEUED
  60 01 90 02 08 00 40 00      00:01:28.910  READ FPDMA QUEUED

Error 3731 occurred at disk power-on lifetime: 24669 hours (1027 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 62 03 08 00 60  Error: UNC at LBA = 0x00000803 = 2051

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 01 70 01 08 00 40 00      00:01:21.000  READ FPDMA QUEUED
  60 01 68 02 08 00 40 00      00:01:21.000  READ FPDMA QUEUED
  60 01 60 03 08 00 40 00      00:01:21.000  READ FPDMA QUEUED
  60 01 58 04 08 00 40 00      00:01:21.000  READ FPDMA QUEUED
  60 01 50 05 08 00 40 00      00:01:21.000  READ FPDMA QUEUED

Error 3730 occurred at disk power-on lifetime: 24669 hours (1027 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 7a 00 08 00 60  Error: UNC at LBA = 0x00000800 = 2048

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 68 30 88 8f 9c 40 00      00:01:16.890  READ FPDMA QUEUED
  60 80 28 00 8f 9c 40 00      00:01:16.890  READ FPDMA QUEUED
  60 f8 20 00 8e 9c 40 00      00:01:16.890  READ FPDMA QUEUED
  60 00 18 00 8c 9c 40 00      00:01:16.862  READ FPDMA QUEUED
  60 f8 10 08 ea 3a 40 00      00:01:16.854  READ FPDMA QUEUED

Error 3729 occurred at disk power-on lifetime: 24669 hours (1027 days + 21 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 41 aa 00 08 00 60  Error: UNC at LBA = 0x00000800 = 2048

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 08 40 f8 e7 3a 40 00      00:01:12.667  READ FPDMA QUEUED
  60 08 38 00 08 3b 40 00      00:01:12.650  READ FPDMA QUEUED
  60 08 30 00 f8 3a 40 00      00:01:12.638  READ FPDMA QUEUED
  60 08 28 00 f0 3a 40 00      00:01:12.626  READ FPDMA QUEUED
  60 08 20 00 ec 3a 40 00      00:01:12.619  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Dernière modification par chrislc (Le 16/11/2023, à 22:28)

Toshiba Satellite P300-1BB Intel Core 2 Duo P8400 - 2.26 GHz - 4096 Mo - DDR2-SDRAM
Serial ATA / 5400tr/mn / 250 Go  -  WebCam     1,3 Mpx - écran     17 " / 16:10 / 1440 x 900
ATI Mobility Radeon HD 3650 /  512 Mo ]
Ubuntu 22.04.3 LTS - Budgie 10.6.1 - 64 bits

Hors ligne

#4 Le 16/11/2023, à 22:48

inbox

Re : [Abandonné] Unrecoverable failure required component budgie-wm.desktop

Ton disque a subit quelques chocs :

191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       8
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       213

Il a quelques secteurs en attente de réallocation :

197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       4

Le secteur 2048 et suivants, pose problème, car il semble comporter une informations importante (fichier système ?) et le système n'arrive pas à réparer.
L'erreur suivante est inquiétante :

Buffer I/O error on dev sdb1, logical block 0, async page read

Ton disque a bien servi (24679 heures) :

  9 Power_On_Hours          0x0032   039   039   000    Old_age   Always       -       24679

Je pense que la tête de lecture/écriture a dû atterrir sur la surface du disque et a pris un coup ainsi que la surface du disque lui même.

Mais attend tout de même d'autres avis, si tu le souhaites.

Un problème résolu ? Indiquez le en modifiant le titre du sujet.

Hors ligne

#5 Le 16/11/2023, à 22:53

chrislc

Re : [Abandonné] Unrecoverable failure required component budgie-wm.desktop

ok
Tout aller bien jusqu'à ce que je suive la procédure pour forcer l'installation d'un pilote AMD/ATI
le choc ne doit pas être récent parce que l'appareil n'a pas bougé depuis pas mal de temps

Toshiba Satellite P300-1BB Intel Core 2 Duo P8400 - 2.26 GHz - 4096 Mo - DDR2-SDRAM
Serial ATA / 5400tr/mn / 250 Go  -  WebCam     1,3 Mpx - écran     17 " / 16:10 / 1440 x 900
ATI Mobility Radeon HD 3650 /  512 Mo ]
Ubuntu 22.04.3 LTS - Budgie 10.6.1 - 64 bits

Hors ligne

#6 Le 16/11/2023, à 23:52

inbox

Re : [Abandonné] Unrecoverable failure required component budgie-wm.desktop

Dans ce cas, ce peut n'être que de l'usure. L'installation d'un pilote/logiciel ne peut provoquer ce genre de problème matériel.

Un problème résolu ? Indiquez le en modifiant le titre du sujet.

Hors ligne

#7 Le 17/11/2023, à 15:20

chrislc

Re : [Abandonné] Unrecoverable failure required component budgie-wm.desktop

inbox a écrit :

Salut,

Peux-tu installer Smartmontools avec :

sudo apt-get install --no-install-recommends smartmontools

Puis récupérer les données Smart avec :

sudo smartctl -s on -a /dev/sdb

A+

En fait il semble que je sois sur /sda et non /sdb
J'ai 2 DD  et je vois maintenant que l'analyse a été fait sur le vieux Toshiba,
alors que j'en ai changé un il y a qq années et que c'est sur celui là que je tourne Hitachi

principal@principal-Satellite-P300:~$ sudo parted -l
[sudo] Mot de passe de principal : 
Modèle : ATA HGST HTS725032A7 (scsi)
Disque /dev/sda : 320GB
Taille des secteurs (logiques/physiques) : 512B/4096B
Table de partitions : msdos
Drapeaux de disque : 

Numéro  Début   Fin    Taille  Type      Système de fichiers  Drapeaux
 1      1049kB  538MB  537MB   primary   fat32                démarrage
 2      539MB   320GB  320GB   extended
 5      539MB   320GB  320GB   logical   ext4


Modèle : ATA TOSHIBA MK2552GS (scsi)
Disque /dev/sdb : 250GB
Taille des secteurs (logiques/physiques) : 512B/512B
Table de partitions : msdos
Drapeaux de disque : 

Numéro  Début   Fin    Taille  Type      Système de fichiers  Drapeaux
 1      1049kB  174GB  174GB   primary
 2      174GB   250GB  76,3GB  extended
 6      174GB   246GB  72,0GB  logical   ext4
 5      246GB   250GB  4288MB  logical   linux-swap(v1)

Il y a une grosse pause entre les deux DD, est-ce normal ?

je donne du coup l'analyse de ce dernier :

principal@principal-Satellite-P300:~$ sudo smartctl -s on -a /dev/sda
[sudo] Mot de passe de principal : 
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-88-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Hitachi/HGST Travelstar Z7K500
Device Model:     HGST HTS725032A7E630
Serial Number:    TF0400Y12PYXLT
LU WWN Device Id: 5 000cca 76ae62b20
Firmware Version: GHBOA420
User Capacity:    320072933376 bytes [320 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Fri Nov 17 14:12:04 2023 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.

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

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(   45) seconds.
Offline data collection
capabilities: 			 (0x5b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  71) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   235   235   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0012   094   094   000    Old_age   Always       -       9608
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   049   049   000    Old_age   Always       -       22485
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   095   095   000    Old_age   Always       -       9333
191 G-Sense_Error_Rate      0x000a   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   098   098   000    Old_age   Always       -       511
193 Load_Cycle_Count        0x0012   094   094   000    Old_age   Always       -       65609
194 Temperature_Celsius     0x0002   187   187   000    Old_age   Always       -       32 (Min/Max 8/53)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
223 Load_Retry_Count        0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 4
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 4 occurred at disk power-on lifetime: 3658 hours (152 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 00 e0 ff 03  Error: WP at LBA = 0x03ffe000 = 67100672

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 38 40 98 48 44 40 00      00:03:50.085  WRITE FPDMA QUEUED
  61 10 38 a8 6d 4b 40 00      00:03:50.085  WRITE FPDMA QUEUED
  60 08 30 00 e0 ff 40 00      00:03:49.643  READ FPDMA QUEUED
  60 08 28 f8 df ff 40 00      00:03:49.643  READ FPDMA QUEUED
  60 08 20 f0 df ff 40 00      00:03:49.643  READ FPDMA QUEUED

Error 3 occurred at disk power-on lifetime: 3658 hours (152 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 d8 00 e0 ff 03  Error: UNC at LBA = 0x03ffe000 = 67100672

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 c0 d8 e0 ff 40 00      00:03:46.582  READ FPDMA QUEUED
  60 00 b8 d8 df ff 40 00      00:03:46.566  READ FPDMA QUEUED
  60 00 b0 d8 de ff 40 00      00:03:46.564  READ FPDMA QUEUED
  60 00 a8 d8 dd ff 40 00      00:03:46.561  READ FPDMA QUEUED
  60 00 a0 d8 dc ff 40 00      00:03:46.559  READ FPDMA QUEUED

Error 2 occurred at disk power-on lifetime: 3360 hours (140 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 00 e0 ff 03  Error: WP at LBA = 0x03ffe000 = 67100672

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  61 68 b8 40 ca 46 40 00      05:35:06.407  WRITE FPDMA QUEUED
  60 08 b0 98 0a 44 40 00      05:35:06.407  READ FPDMA QUEUED
  60 08 a8 70 e0 ff 40 00      05:35:06.379  READ FPDMA QUEUED
  60 08 a0 68 e0 ff 40 00      05:35:06.379  READ FPDMA QUEUED
  60 08 98 60 e0 ff 40 00      05:35:06.379  READ FPDMA QUEUED

Error 1 occurred at disk power-on lifetime: 3360 hours (140 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 f8 00 e0 ff 03  Error: UNC at LBA = 0x03ffe000 = 67100672

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 88 f8 e0 ff 40 00      05:35:03.527  READ FPDMA QUEUED
  60 00 80 f8 df ff 40 00      05:35:03.524  READ FPDMA QUEUED
  60 00 78 f8 de ff 40 00      05:35:03.522  READ FPDMA QUEUED
  60 00 70 f8 dd ff 40 00      05:35:03.519  READ FPDMA QUEUED
  60 00 68 f8 dc ff 40 00      05:35:03.517  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Dernière modification par chrislc (Le 17/11/2023, à 15:38)

Toshiba Satellite P300-1BB Intel Core 2 Duo P8400 - 2.26 GHz - 4096 Mo - DDR2-SDRAM
Serial ATA / 5400tr/mn / 250 Go  -  WebCam     1,3 Mpx - écran     17 " / 16:10 / 1440 x 900
ATI Mobility Radeon HD 3650 /  512 Mo ]
Ubuntu 22.04.3 LTS - Budgie 10.6.1 - 64 bits

Hors ligne

#8 Le 17/11/2023, à 17:27

inbox

Re : [Abandonné] Unrecoverable failure required component budgie-wm.desktop

Sda ne comporte que d'anciennes (il y a 3658 heures, durée totale d'usage du disque 22485 heures) et peu importantes erreurs. Ont peut donc les ignorer. Par contre, il y a beaucoup d'erreurs signalées pour Sdb. Si ce dernier n'est plus utilisé, il faudrait le déconnecter et/ou l'enlever.

chrislc a écrit :

Il y a une grosse pause entre les deux DD, est-ce normal ?

Si tu veux parler d'un temps d'attente, c'est normal. C'est dû aux difficultés d'accès à Sdb.

Un problème résolu ? Indiquez le en modifiant le titre du sujet.

Hors ligne

#9 Le 17/11/2023, à 18:15

chrislc

Re : [Abandonné] Unrecoverable failure required component budgie-wm.desktop

Néanmoins je ne peux démarrer qu'avec le mode recovery actuellement
depuis que j'ai forcé l'installation du pilote

Je veux bien déconnecter sdb, je l'enlève carrément ?

Toshiba Satellite P300-1BB Intel Core 2 Duo P8400 - 2.26 GHz - 4096 Mo - DDR2-SDRAM
Serial ATA / 5400tr/mn / 250 Go  -  WebCam     1,3 Mpx - écran     17 " / 16:10 / 1440 x 900
ATI Mobility Radeon HD 3650 /  512 Mo ]
Ubuntu 22.04.3 LTS - Budgie 10.6.1 - 64 bits

Hors ligne

#10 Le 18/11/2023, à 01:31

inbox

Re : [Abandonné] Unrecoverable failure required component budgie-wm.desktop

Pour ce qui est de supprimer le pilote, je pense que tu peux retourner dans ton autre sujet. Je ne m'y connais pas pour supprimer un "run".

Un problème résolu ? Indiquez le en modifiant le titre du sujet.

Hors ligne

Pages : 1