Suddenly, my apps got closed, then system icons disappeared and then systemd messages appeared

[ruanvictordsc]

Ubuntu Version: 26.04 LTS

Desktop Environment: GNOME

Laptop: Dell Latitude 5300

Problem Description:

I was using Ubuntu normally. Suddenly, my applications closed by themselves, then system icons disappeared (like Wi-Fi, battery, Ubuntu, power icons) and then the screen showed a black background and white systemd messages. I didn’t take a photography or screenshot of the icons disappearing and apps closing.

[7615.734290] I/O error, dev loop6, sector 553592 op 0x0:(READ) flags 0x800 phys_seg 13 prio class 2
[7615.734395] SQUASHFS error: Failed to read block 0x10e4f3d4: -5
[7615.735047] I/0 error, dev loop6, sector 553592 op 0x0: (READ) flags 0x800 phys_seg 13 prio class 2
[7615.745015] SQUASHFS error: Failed to read block 0x10e4f3d4: -5
[7615.745177] I/O error, dev loop6, sector 553592 op 0x0: (READ) flags 0x800 phys_seg 13 prio class 2
[7615.745671] SQUASHFS error: Failed to read block 0x10e4f3d4: -5
[7615.807106] systemd[1]: systemd-udevd.service: Failed to spawn executor: Input/output error
[7615.809403] systemd[1]: Failed to start systemd-udevd.service - Rule-based Manager for Device Events and Files.
[7615.820248] systemd[1]: systemd-udevd.service: Failed to spawn executor: Input/output error
[7615.821659] systemd[1]: Failed to start systemd-udevd.service - Rule-based Manager for Device Events and Files.
[7615.829179] systemd[1]: systemd-udevd.service: Failed to spawn executor: Input/output error
[7615.830512] systemd[1]: Failed to start systemd-udevd.service - Rule-based Manager for Device Events and Files.
[7615.838868] systemd[1]: systemd-udevd.service: Failed to spawn executor: Input/output error
[7615.840255] systemd[1]: Failed to start systemd-udevd.service - Rule-based Manager for Device Events and Files.
[7615.855109] systemd[1]: systemd-udevd.service: Failed to spawn executor: Input/output error
[7615.856856] systemd[1]: Failed to start systemd-udevd.service - Rule-based Manager for Device Events and Files.
[7615.860242] systemd[1]: Failed to start systemd-udevd.service - Rule-based Manager for Device Events and Files.
[7632.403670] Read-error on swap-device (259:0:2237424)
[7632.403684] Read-error on swap-device (259:0:2237224)
[7632.403764] Read-error on swap-device (259:0:2237280)
[7632.403846] Read-error on swap-device (259:0:2237296)
[7632.404591] Read-error on swap-device (259:0:2237512)
[7632.404671] Read-error on swap-device (259:0:2237680)
[7632.406985] Read-error on swap-device (259:0:2206184)
[7632.462256] systemd[1]: user-runtime-dir@1000.service: Failed to spawn executor: Input/output error
[7633.074903] systemd[1]: Failed to add a watch for /var/cache/cups: Input/output error
[7633.076616] systemd[1]: Failed to start cups.path - CUPS Scheduler.
[7633.082562] systemd[1]: cups.service: Failed to spawn executor: Input/output error
[7633.084226] systemd[1]: Failed to start cups.service - CUPS Scheduler.
[7633.413120] systemd[1]: cups.service: Failed to spawn executor: Input/output error
[7633.414810] systemd[1]: Failed to start cups.service - CUPS Scheduler.
[7633.662968] systemd[1]: cups.service: Failed to spawn executor: Input/output error
[7633.665115] systemd[1]: Failed to start cups.service - CUPS Scheduler.
[7633.912037] systemd[1]: cups.service: Failed to spawn executor: Input/output error
[7633.913509] systemd[1]: Failed to start cups.service - CUPS Scheduler.
[7634.162066] systemd[1]: cups.service: Failed to spawn executor: Input/output error
[7634.163548] systemd[1]: Failed to start cups.service - CUPS Scheduler.
[7634.408461] systemd[1]: Failed to listen on cups.socket - CUPS Scheduler.
[7763.159230] systemd[1]: sysstat-collect.service: Failed to spawn executor: Input/output error
[7763.160579] systemd[1]: Failed to start sysstat-collect.service - system activity accounting tool.

What I’ve Tried: I forced shut down by pressing and holding my laptop’s Power button for 10 seconds. Then, I turned on my laptop and it came back to normal.

[peterwhite23]

Welcome to Ubuntu Discourse, @ruanvictordsc!

Those messages indicate some error in some snap, hence the SQUASHFS errors on loop devices and the “Read-error on swap-device” don’t look too good, either. Such I/O errors may indicate a failing disk/SSD or some loose connection.

You should check all your device connectors and connection cables, if you can, which may require opening the laptop.

[ruanvictordsc]

Thank you so much for answering my question.

[ruanvictordsc]

Here’s how the icons disappear

[peterwhite23]

Sorry, I cannot see much of what’s happening there, but I guess that’s to be expected without a screenshot of the state before this happens.

I also think you have a serious hardware issue; I/O errors are usually caused by some defect in the chain, hence my first suggestion. Even if all cables and connectors are in order, it may still be a defective storage device in dire need of replacement.