When updating i get Segmentation fault in fedora 41

Ask Fedora
1

what do i do to update

sudo dnf update
[sudo] password for
Updating and loading repositories:
Repositories loaded.
Package Arch Version Repository Size
Upgrading:
appstream-data noarch 41-11.fc41 updates 15.2 MiB
replacing appstream-data noarch 41-10.fc41 15.0 MiB
replacing appstream-data noarch 41-8.fc41 anaconda 14.4 MiB

Transaction Summary:
Upgrading: 1 package
Replacing: 2 packages

Total size of inbound packages is 15 MiB. Need to download 0 B.
After this operation, 14 MiB will be freed (install 15 MiB, remove 29 MiB).
Is this ok [y/N]: y
[1/1] appstream-data-0:41-11.fc41.noarch 100% | 0.0 B/s | 0.0 B | 00m00s

Already downloaded

[1/1] Total 100% | 0.0 B/s | 0.0 B | 00m00s
Running transaction
[1/5] Verify package files 100% | 34.0 B/s | 1.0 B | 00m00s
[2/5] Prepare transaction 100% | 28.0 B/s | 3.0 B | 00m00s
[3/5] Upgrading appstream-data-0:41-11.fc41.noarch 47% [========= ] | 23.8 MiB/s | 7.5 MiB | 00m00s

Segmentation fault

2

Check sudo dmesg | tail and coredumctl to what code actually segv’ed.
What do these commands report?

3

[ 9645.154005] sd 8:0:0:1: [sdc] Media removed, stopped polling
[ 9645.154880] sd 8:0:0:0: [sdb] Write Protect is off
[ 9645.154892] sd 8:0:0:0: [sdb] Mode Sense: 21 00 00 00
[ 9645.154911] sd 8:0:0:1: [sdc] Attached SCSI removable disk
[ 9645.155601] sd 8:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn’t support DPO or FUA
[ 9645.182717] sdb: sdb1
[ 9645.182956] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[ 9645.488971] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 9856.484537] sdb: detected capacity change from 249737216 to 0
[ 9863.882869] usb 2-4: USB disconnect, device number 3

coredumctl
bash: coredumctl: command not found…

5

that worked

thank you

2 Likes
6

Sorry my typo coredumpctl try that.
Also with the dmesg you must do it just after you see the error, so reproduce that error first.

7 
coredumpctl
TIME                           PID  UID  GID SIG     COREFILE     EXE                               SIZE
Mon 2025-03-17 08:50:31 EDT   3243 1000 1000 SIGABRT present      /usr/bin/gnome-software          24.9M
Mon 2025-03-17 09:05:16 EDT   2749 1000 1000 SIGSEGV present      /usr/bin/gnome-software          86.3M
Mon 2025-03-17 09:23:51 EDT  21988 1000 1000 SIGSEGV present      /usr/bin/python3.11              29.1M
Mon 2025-03-17 17:01:48 EDT   2557 1000 1000 SIGSEGV present      /usr/bin/gnome-shell             18.4M
Mon 2025-03-17 23:56:45 EDT  32382 1000 1000 SIGSEGV present      /app/extra/chrome                26.9M
Tue 2025-03-18 17:14:28 EDT   2553 1000 1000 SIGSEGV present      /usr/bin/gnome-shell               17M
Wed 2025-03-19 10:50:24 EDT 422215    0    0 SIGABRT inaccessible /usr/libexec/packagekitd             -
Wed 2025-03-19 10:53:34 EDT   2823 1000 1000 SIGSEGV present      /usr/bin/gnome-software          30.5M
Thu 2025-03-20 00:28:47 EDT   3607 1000 1000 SIGABRT present      /usr/bin/Xwayland                 2.5M
Thu 2025-03-20 01:30:24 EDT   8115 1000 1000 SIGSEGV present      /app/extra/chrome                78.2M
Thu 2025-03-20 01:30:45 EDT  16569 1000 1000 SIGSEGV present      /app/extra/chrome                58.1M
Thu 2025-03-20 01:36:56 EDT  17927 1000 1000 SIGSEGV present      /app/extra/chrome                71.8M
Thu 2025-03-20 10:38:57 EDT   2578 1000 1000 SIGSEGV present      /usr/bin/gnome-shell             17.1M
Thu 2025-03-20 10:39:00 EDT   3570 1000 1000 SIGTRAP present      /app/extra/chrome               166.4M
Thu 2025-03-20 14:06:30 EDT   2569 1000 1000 SIGSEGV present      /usr/bin/gnome-shell             16.9M
Thu 2025-03-20 16:49:49 EDT   3665 1000 1000 SIGSEGV present      /app/extra/chrome                19.8M
Thu 2025-03-20 17:23:13 EDT   2623 1000 1000 SIGSEGV present      /usr/bin/gnome-shell             18.2M
Fri 2025-03-21 10:41:53 EDT  15343 1000 1000 SIGSEGV present      /app/extra/chrome                 9.7M
Fri 2025-03-21 10:41:54 EDT  14196 1000 1000 SIGSEGV present      /usr/bin/gnome-shell             16.9M
Sun 2025-03-23 13:59:46 EDT   4032 1000 1000 SIGSEGV present      /app/extra/chrome                26.6M
Sun 2025-03-23 13:59:51 EDT   3963 1000 1000 SIGABRT present      /usr/bin/Xwayland                 2.5M
Sun 2025-03-23 18:19:08 EDT 170691 1000 1000 SIGSEGV present      /app/extra/chrome                36.8M
Sun 2025-03-23 18:19:11 EDT 170645 1000 1000 SIGABRT present      /usr/bin/Xwayland                 2.5M
Mon 2025-03-24 11:51:41 EDT   3554 1000 1000 SIGSEGV present      /app/extra/chrome                  35M
Mon 2025-03-24 11:52:00 EDT   4626 1000 1000 SIGSEGV present      /app/extra/chrome                24.7M
Mon 2025-03-24 11:52:42 EDT   5305 1000 1000 SIGSEGV present      /app/extra/chrome                25.6M
Tue 2025-03-25 14:25:55 EDT   2827 1000 1000 SIGABRT present      /usr/bin/gnome-software          16.2M
Wed 2025-03-26 22:03:19 EDT   2835 1000 1000 SIGABRT present      /usr/bin/gnome-software            15M
Fri 2025-03-28 06:25:20 EDT 884694    0    0 SIGABRT inaccessible /usr/libexec/packagekitd             -
Fri 2025-03-28 15:22:59 EDT   2804 1000 1000 SIGILL  present      /usr/bin/gnome-software          15.4M
Fri 2025-03-28 15:23:56 EDT   4064    0    0 SIGSEGV none         /usr/bin/dnf5                        -
Fri 2025-03-28 15:48:07 EDT  18675    0    0 SIGSEGV none         /usr/bin/dnf5                        -
Fri 2025-03-28 17:59:46 EDT  72454 1000 1000 SIGSEGV present      /usr/libexec/tracker-miner-fs-3  31.8M
Fri 2025-03-28 18:00:05 EDT  88356 1000 1000 SIGSEGV present      /usr/libexec/tracker-miner-fs-3   6.9M
Fri 2025-03-28 18:00:22 EDT  88596 1000 1000 SIGSEGV present      /usr/libexec/tracker-miner-fs-3     7M
Fri 2025-03-28 18:00:38 EDT  88818 1000 1000 SIGSEGV present      /usr/libexec/tracker-miner-fs-3   6.7M
Sat 2025-03-29 01:15:19 EDT   3505 1000 1000 SIGSEGV present      /usr/bin/gnome-system-monitor       5M
Sat 2025-03-29 01:26:31 EDT  69169 1000 1000 SIGSEGV present      /usr/libexec/tracker-miner-fs-3 173.3M
Sat 2025-03-29 01:26:52 EDT  73619 1000 1000 SIGSEGV present      /usr/libexec/tracker-miner-fs-3    10M
Sat 2025-03-29 01:42:05 EDT  73798 1000 1000 SIGSEGV present      /usr/libexec/tracker-miner-fs-3 176.5M
Sat 2025-03-29 01:59:19 EDT   1733   42   42 SIGSEGV inaccessible /usr/bin/gnome-shell                 -
Sat 2025-03-29 01:59:30 EDT   1628    0    0 SIGTRAP inaccessible /usr/sbin/gdm                        -
Sat 2025-03-29 02:03:13 EDT   1809    0    0 SIGABRT inaccessible /usr/libexec/packagekitd             -
Sat 2025-03-29 11:26:46 EDT  11077 1000 1000 SIGILL  present      /usr/libexec/tracker-extract-3   61.4M
Sat 2025-03-29 11:27:32 EDT  11542 1000 1000 SIGSEGV present      /usr/libexec/tracker-extract-3   58.7M
Sat 2025-03-29 11:28:32 EDT  11963 1000 1000 SIGABRT present      /usr/libexec/tracker-extract-3   75.3M
Sat 2025-03-29 11:28:37 EDT  12575 1000 1000 SIGABRT present      /usr/libexec/tracker-extract-3   13.5M
Sat 2025-03-29 11:28:40 EDT  12720 1000 1000 SIGABRT present      /usr/libexec/tracker-extract-3    8.6M
Sat 2025-03-29 11:28:48 EDT  12816 1000 1000 SIGILL  present      /usr/libexec/tracker-extract-3   13.7M
Sat 2025-03-29 11:28:53 EDT  12968 1000 1000 SIGSEGV present      /usr/libexec/tracker-extract-3   14.4M
Sat 2025-03-29 11:28:55 EDT  13119 1000 1000 SIGILL  present      /usr/libexec/tracker-extract-3      7M
Sat 2025-03-29 11:28:57 EDT  13221 1000 1000 SIGSEGV present      /usr/libexec/tracker-extract-3    3.5M
lines 31-53/53 (END)
8

I edited this latest post and added the preformatted text tags so it appears as formatted on your screen. Please post text that you copy and paste that way so it remains much easier to read.

This is done by highlighting the pasted text then click the </> button on the toolbar of the text entry screen. You also can directly enter ``` on the line preceding the pasted text and on the line following the text to retain the on-screen formatting.

9

thank you jeff v

10

FYI I’m surprised that you have so many crashes on your system.

11

Me too. Segmentation faults should be addressed right away: a) if they are caused by a software problem, other users could be affected, and b) they can be a sign of failing hardware. The crash appears to have been corrupt data can be a symptom of failing hardware.

12

yeah? why do you say that

isnt it like that for everyone

hopefully its just software

ill find out if its my hardware in the future sometime probly not anytime soon

when i build me another computer

when i built the computer i had no way of testing each part to make sure it was fine

ill probly just buy another computer that should work
without problems untill i build another

then ill know if its hardware

or if its more software

13

Segmentation faults have only occurred 2 or 3 times in the last 10 years for me.
No, seg faults are not common for everyone.

14

No it is not like for most people. I have only sen 3 this year, a rate of 1/month.

15

i got a kernel panic

the other day

20250329_123145
20250329_1231451920Ă—1440 85.1 KB

Screenshot From 2025-03-30 21-32-00
Screenshot From 2025-03-30 21-32-00186Ă—127 25.3 KB

16

Home built computers can be tricky. It isn’t always easy to ensure that a) parts actually conform to advertised specs, and b) are suitable for purpose. It is tempting to reuse old cables, but (because “cables are evil”) careful builders use new cables.

Things you can try:

  • memory tests: They should be run for an extended period (e.g., over a weekend or multiple nights).
  • disconnect non-essential add-ons
  • check logs and core dumps: Problems with incorrect specs may produce error messages.
  • wiggle tests of cables
17

it was all new parts and cables

18

I was in windows 11 updated everything was stable and everything then updated and just kept crashing

So it is partly the software

19

Updates are generally more stressful than typical workloads, so hardware failures are more likely to be observed during and after updates.Also, hardware failure rates follow a “bathtub curve”: high infant mortality, a period of low failure rates, then increasing failure rates with old age.

We need data to understand why crashes occur.

1 Like
20

i try to report errors but i get problems everytime i try

21

i got another Segmentation fault

sudo rpm --rebuilddb
Illegal instruction