Hello Sudhakar Verma,
Thank you again for the support. I have run the smartctl command again, and
the response was the same.
Then, I ran sudo smartctl -x /dev/sda. Some errors meet.
The complete log is attached.

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0008  2            0  Device-to-host non-data FIS retries
0x0009  2            3  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            5  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
0x000f  2            0  R_ERR response for host-to-device data FIS, CRC
0x0012  2            0  R_ERR response for host-to-device non-data FIS, CRC
0x8000  4          618  Vendor specific


Em sex., 12 de jun. de 2026 às 02:25, Sudhakar Verma <
[email protected]> escreveu:

> Can you see that
>
> [39763.736556] ata1.00: status: { DRDY ERR }
> [39763.736564] ata1.00: error: { UNC }
> [39763.750578] ata1.00: configured for UDMA/133
> [39763.750817] sd 0:0:0:0: [sda] tag#21 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_OK cmd_age=3s
> [39763.750827] sd 0:0:0:0: [sda] tag#21 Sense Key : Medium Error [current]
> [39763.750835] sd 0:0:0:0: [sda] tag#21 Add. Sense: Unrecovered read error
> - auto reallocate failed
> [39763.750845] sd 0:0:0:0: [sda] tag#21 CDB: Read(10) 28 00 37 75 b0 80 00
> 00 08 00
> [39763.750851] I/O error, dev sda, sector 930459776 op 0x0:(READ) flags
> 0x800000 phys_seg 1 prio class 2
>
> something like this comes in dmesg when you run apt update?
>
> In the dmesg attached I can see a few instances of this
>
> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2155979
>
> Title:
>   Crash in ubuntu-manager. Fail in update it from the cache.
>
> Status in update-manager package in Ubuntu:
>   New
>
> Bug description:
>   I sent the logout from ubuntu-bug update-manager reported the bug
>   through the terminal.
>
>   (update-manager:164653): dconf-WARNING **: 19:34:25.409: failed to
>   commit changes to dconf: Falha ao executar processo filho “dbus-
>   launch” (Arquivo ou diretório inexistente)
>
>   (update-manager:164653): dconf-WARNING **: 19:34:25.409: failed to
>   commit changes to dconf: Falha ao executar processo filho “dbus-
>   launch” (Arquivo ou diretório inexistente)
>
>   (update-manager:164653): libunity-CRITICAL **: 19:34:25.421: file
>   unity-launcher.c: line 1646: unexpected error: Falha ao executar
>   processo filho “dbus-launch” (Arquivo ou diretório inexistente)
>   (g-exec-error-quark, 8)
>
>   (update-manager:164653): libunity-CRITICAL **: 19:34:25.421:
>   unity_launcher_entry_dbus_impl_construct: assertion 'conn != NULL'
>   failed
>
>   (update-manager:164653): libunity-CRITICAL **: 19:34:25.430:
> unity-inspector.vala:96: Unable to connect to session bus: Falha ao
> executar processo filho “dbus-launch” (Arquivo ou diretório inexistente)
>   warning: could not initiate dbus
>   Traceback (most recent call last):
>     File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py",
> line 257, in refresh_cache
>       self._check_oem_metapackages()
>       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
>     File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py",
> line 379, in _check_oem_metapackages
>       pkgs = UbuntuDrivers.detect.system_device_specific_metapackages(
>              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
>           apt_cache=self.cache._cache
>           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>       ).keys()
>       ^
>     File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line
> 949, in system_device_specific_metapackages
>       modalias_map = apt_cache_modalias_map(apt_cache)
>     File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line
> 302, in apt_cache_modalias_map
>       if not _check_video_abi_compat(apt_cache, package):
>              ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
>     File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line
> 215, in _check_video_abi_compat
>       depcache = apt_pkg.DepCache(apt_cache)
>   apt_pkg.Error: E:Erro de leitura - read (5: Erro de entrada/saída)
>
>   (update-manager:164653): GLib-GIO-CRITICAL **: 19:35:31.675:
> g_task_propagate_value: assertion 'task->result_set' failed
>   Traceback (most recent call last):
>     File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py",
> line 297, in cache_refreshed
>       task_returned, task_result = task.propagate_value()
>                                    ~~~~~~~~~~~~~~~~~~~~^^
>   TypeError: Invalid type
>
>   During handling of the above exception, another exception occurred:
>
>   Traceback (most recent call last):
>     File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py",
> line 310, in cache_refreshed
>       if e.matches(IO_ERR_QUARK, Gio.IOErrorEnum.FAILED):
>          ^^^^^^^^^
>   AttributeError: 'TypeError' object has no attribute 'matches'
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 26.04
>   Package: update-manager 1:26.04.5
>   ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0
>   Uname: Linux 7.0.0-22-generic x86_64
>   ApportVersion: 2.34.0-0ubuntu2
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Jun  8 19:39:05 2026
>   GsettingsChanges:
>    b'com.ubuntu.update-manager' b'first-run' b'false'
>    b'com.ubuntu.update-manager' b'launch-count' b'8'
>    b'com.ubuntu.update-manager' b'launch-time' b'int64 1780957983'
>   InstallationDate: Installed on 2026-05-25 (14 days ago)
>   InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64
> (20260423.1)
>   PackageArchitecture: all
>   ProcEnviron:
>    LANG=pt_BR.UTF-8
>    PATH=(custom, no user)
>    SHELL=/bin/bash
>    TERM=xterm-256color
>    XDG_RUNTIME_DIR=<set>
>   SourcePackage: update-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2155979/+subscriptions
>
>

-- 
##############################################
Prof. Dr. Sergio Ricardo de Lazaro
State University of Ponta Grossa
Campus Uvaranas - Ponta Grossa - PR - Brasil
Av. Carlos Cavalcanti, 4748 - CEP 84030-900
Phone: +55 42 3220 3731
Res. ID: http://www.researcherid.com/rid/C-4704-2018
ORCID: http://orcid.org/0000-0001-9753-7936
Publons: https://publons.com/a/1288887
###############################################


** Attachment added: "smart-analysis.log"
   
https://bugs.launchpad.net/bugs/2155979/+attachment/5977467/+files/smart-analysis.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2155979

Title:
  Crash in ubuntu-manager. Fail in update it from the cache.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2155979/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to