My desktop is crashing with some applications

Ask Fedora
,
1

Hello !
I have a problem with my Asus laptop i try to debug since weeks now, without success.
After a fresh reinstall, i can’t launch some apps (Bottles, Steam, Lutris, Heroic Game Launcher). I get a black screen and have to force shutdown with the power button. I don’t know where to look in the logs to find where does the problem come from.

  1. I already tried to launch Fedora in X-server mode (i’m in wayland), the same issue appear. I thought the problem came from flatpak, but the rpm packages of those apps crash too.
  2. I thought it could come from Electron apps, but it’s not really true, since some are working, others are not.
  3. Some errors and warnings about gtk are showing when trying to start steam from the command-line, i don’t know if this is relevant or just a side effect

Anybody have an idea of how to debug a topic like this one ? I’m starting to think the problem is hardware related…

2

Does journalctl have data for times past the black-screen failiure? Are the faiiures reproducible or random? Do the problems occur when running from a live USB?

Modern manufacturing is very reproducible, so if the problem is hardware related, others with the same hardware may have the same problem. Web searchs may find problem reports.

Consider the possibility of overheating and memory failures. Some laptop models have dust traps that degrade cooling. Searching for overheating problems for your model may be helpful. Laptops can have cooling issues after upgrading mass storage devices with higher capacity models that generate more heat.

To check for memory problems, use Memtest86+.

3

The problem is not random at all, the issue can be seen everytime i try to run one of those programs. I haven’t tried yet to launch one of these from a live USB, i should try this later this day.
I just made it happen again, and here’s what i gathered :

  1. After launching Bottles, my desktop freeze for 30 sec, then the program crash.
  2. After the freeze, my cursor is a white rectangle, and the icons from the gnome dropdown (the one to shutdown the computer or access the settings), are all missing
  3. Since i had my terminal opened, i tried to type journalctl, but nothing happend.
  4. Finally, my whole desktop crashed with the picture you’ll find in attachment.

After restart, i got into journalctl, and found this, which seems to be a gnome crash and may be the explanation for the missing icons / cursor.

déc. 23 14:10:55 mothlight audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=man-db-cache-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=s>
déc. 23 14:10:55 mothlight audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=man-db-cache-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=su>
déc. 23 14:10:55 mothlight systemd[1]: run-rac2757a56057485381972eb140f0871b.service: Deactivated successfully.
déc. 23 14:10:55 mothlight audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=run-rac2757a56057485381972eb140f0871b comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
déc. 23 14:10:56 mothlight PackageKit[1305]: get-updates transaction /850_edcbceeb from uid 1000 finished with success after 1911ms
déc. 23 14:10:58 mothlight PackageKit[1305]: get-details transaction /851_ebdbdbbd from uid 1000 finished with success after 1230ms
déc. 23 14:10:58 mothlight PackageKit[1305]: resolve transaction /852_ecaeebbc from uid 1000 finished with success after 2ms
déc. 23 14:10:58 mothlight PackageKit[1305]: search-file transaction /853_ceadecca from uid 1000 finished with success after 190ms
déc. 23 14:10:58 mothlight PackageKit[1305]: resolve transaction /854_aeeededc from uid 1000 finished with success after 5ms
déc. 23 14:10:58 mothlight PackageKit[1305]: get-update-detail transaction /855_aeaedbce from uid 1000 finished with success after 83ms
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-common
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-efi-ia32
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-efi-ia32-cdboot
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-efi-x64
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-efi-x64-cdboot
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-pc
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-pc-modules
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-tools
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-tools-efi
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-tools-extra
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for grub2-tools-minimal
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for ntfs-3g
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for ntfs-3g-libs
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for ntfsprogs
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for systemd
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for systemd-container
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for systemd-libs
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for systemd-libs
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for systemd-networkd
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for systemd-oomd-defaults
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for systemd-pam
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for systemd-resolved
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for systemd-udev
déc. 23 14:10:58 mothlight packagekitd[1305]: Failed to get cache filename for xorg-x11-drv-intel
déc. 23 14:10:58 mothlight PackageKit[1305]: get-details transaction /856_dcecbbdd from uid 1000 finished with success after 13ms
déc. 23 14:11:02 mothlight PackageKit[1305]: get-updates transaction /857_bddbaebc from uid 1000 finished with success after 130ms
-- Boot 1419362088b2445c81d22d383c8aeea4 --

déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.RP09._S0W], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.I2C1.TPL1], AE_NOT_FOUND (20220331/dswload2-162)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0010)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS05._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
déc. 23 15:47:38 mothlight kernel: ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
déc. 23 15:47:38 mothlight kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS06._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
déc. 23 15:47:38 mothlight kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)

I don’t think it’s a gnome problem though, i tried to install xfce and the same
crash happend.

250e07e976fbf4d6608c6b363729819a99447747.jpeg
250e07e976fbf4d6608c6b363729819a99447747.jpeg1920×1440 437 KB

4

From the photo, you certainly have a corrupt filesystem on nvme0n1p3. This could be a side effect of a crash or a failing drive.

You need to boot from good media, e.g., a Live USB.

First thing is to try to backup critical data Then try to repair the ext4 filesystem using fsck. This may allow a backup if it failed on the first attempt. You can install the nvme-cli and/or smartmontools package in the Live USB system to check the health of the nvme drive (nvme doen’t support some nvme drives, smartmon support for nvme is relatively new).

5

I tried to run fsck from a fedora live USB, and i discovered a problem :
I first ran lsblk, and this is the result :

[liveuser@localhost-live ~]$ lsblk -fe7 -o +size
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS   SIZE
sda  iso966 Jolie Fedora-WS-Live-37-1-7
                        2022-11-05-10-15-31-00                                           14.5G
├─sda1
│    iso966 Jolie Fedora-WS-Live-37-1-7
│                       2022-11-05-10-15-31-00                     0   100% /run/initramfs/live
│                                                                                         1.9G
├─sda2
│    vfat   FAT16 ANACONDA
│                       7268-1544                                                         9.9M
└─sda3
                                                                                          300K
zram0
                                                                            [SWAP]        7.6G
nvme0n1
                                                                                        476.9G
├─nvme0n1p1
│    vfat   FAT32       69F2-1B9A                                                         600M
├─nvme0n1p2
│    ext4   1.0         f886f176-28ee-4c4b-baaf-2019de08d063                                1G
├─nvme0n1p3
│    ext4   1.0         bc355de3-3466-40de-a329-e63307bee2e8                            467.3G
└─nvme0n1p4
     swap   1           b405075c-e38f-4bbc-b4f5-784aa1f3cf05                                8G

Then i ran fsck to check the first partition of the disk :

[liveuser@localhost-live ~]$ sudo fsck /dev/nvme0n1p1
fsck from util-linux 2.38.1
e2fsck 1.46.5 (30-Dec-2021)
fsck.ext2: No such file or directory while trying to open /dev/nvme0n1p1
Possibly non-existent device?

I checked again lsblk to see what happend, and the whole disk have disappeared :

[liveuser@localhost-live ~]$ lsblk -fe7 -o +size
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS   SIZE
sda  iso966 Jolie Fedora-WS-Live-37-1-7
                        2022-11-05-10-15-31-00                                           14.5G
├─sda1
│    iso966 Jolie Fedora-WS-Live-37-1-7
│                       2022-11-05-10-15-31-00                     0   100% /run/initramfs/live
│                                                                                         1.9G
├─sda2
│    vfat   FAT16 ANACONDA
│                       7268-1544                                                         9.9M
└─sda3
                                                                                          300K
zram0

Is my drive dead ?

6

Your experience (random filesystem errors followed by drive going missing) is typical of a failed drive. The drive vendor may have diagnostic tools, but a) the tools often require Windows and b) if you have any sensitive data on the drive. destroying the drive rather than seeking a warranty replacement (the potential cost of data falling into the wrong hands far exceeds the cost of a new drive) may be your best option.

You should also consider if the possibility of underlying issues such as overheating.

7

Ok ! I might buy a new one since those are not so expensive nowadays, thank you very much for your advices !

For the overheating, i don’t think it’s the problem, i encounter the problem even after a fresh start, in sec or so, not after using it for some time.

8

This was a major error.
The file system was FAT32 and you used fsck in ext2 mode. Potential for severe corruption of data on a drive exists when using the wrong mode especially if doing so with a mounted file system. Yes, I know you did not have it mounted, but the warning is still valid for other readers.

Please use the proper tools at the proper time.

9

I just changed the ssd drive, installed Fedora on it, and the problem is still here so i’m back to start.
I tried bottles in live usb and no problems happend. I still don’t find anything usefull in the logs, do you have any idea how to debug this further ?

10

Strange that it will install on the drive, but the system loses it after booting to the installed OS.

This is an nvme drive, so it has to be properly supported by both the bios & motherboard as well as the OS. We know the OS supports nvme so that leads us to the bios & motherboard.

Please check if there may be an updated bios for your motherboard. This may be the only issue. Also verify if the mfgr shows any updates for M.2 drives in the notes for the newer bios.

There also is some inconsistency in CPU support for some types of M.2 drives, though I would not suspect that since it seems to work well with the live media but not the installed OS. (newer kernels may exhibit weird behavior on those processors).

11

Strange, as running fsck would normally detect the type of file system and call the correct tool for checking it.

12

Note in his post above it was clearly calling the ext2 version. Thus my comment.

13

I thought of the Bios too, and flashed it with a newer version maybe two weeks ago, without better result for my problem.

14

That is what made it strange.

15

Was this a new nvme drive sourced from a reputable vendor with nothing previously installed?

Nvme connectors are fragile. You should visually inspect the connectors for bent contacts and corrosion with a magnifier.

I spent much of my working life at an oceanographic institution – salt air was hard on computers. Auto parts stores now sell “contact enhancer” that is used on connectors in modern computerized cars and sometimes fixes weird computer issues.

Have you been able to run the current memtest86+? Do you encounter problems running from a live USB drive?