Bug 2316835

Created attachment 2050723 [details]
File: proc_pid_status

Created attachment 2050724 [details]
File: maps

Created attachment 2050725 [details]
File: limits

Created attachment 2050726 [details]
File: environ

Created attachment 2050727 [details]
File: open_fds

Created attachment 2050728 [details]
File: mountinfo

Created attachment 2050729 [details]
File: os_info

Created attachment 2050730 [details]
File: cpuinfo

Created attachment 2050731 [details]
File: core_backtrace

Created attachment 2050732 [details]
File: exploitable

Created attachment 2050733 [details]
File: dso_list

Created attachment 2050734 [details]
File: backtrace

Thanks for a bug report. I think this is a variant of the bug #2266706. Do you have any idea how to reproduce this, please?

Unfortunately no. It happened immediately after boot when logging in.

So could be that some other service it depends on was not yet ready or returned different data?

I do not think so. The backtrace shows it's a "Changed" signal being delivered.

Anyway, I did re-read the backtrace and I see it also contains a thread with gs_appstream_gather_merge_data(). There are many crashes reported involving that function, gathered in the bug #2272232. It also crashes after start, thus maybe it's it, the problem only exhibiting in a different place. It can happen when there is involved memory corruption (things like use-after-free), which can overwrite "random" memory. Those are discovered only after the overwritten memory is accessed , which can be shortly after the overwrite happens or hours later, depending what the overwritten memory contained. Such are quite hard to reproduce due to this; it's the main reason why the bug is still opened.

Probably between the login screen and desktop. Otherwise before the login screen, which is then recovered in some way.


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-software killed by SIGSEGV
journald_cursor: s=2976431ac20b49a395dfc774c05561cb;i=156207;b=dfa575038a8f49c0b9564d8b41577237;m=304ec4c;t=62c489bc7cab7;x=f266f0145b7789d0
executable:     /usr/bin/gnome-software
cmdline:        /usr/bin/gnome-software --gapplication-service
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Software-3382.scope
rootdir:        /
uid:            1000
kernel:         6.12.9-200.fc41.x86_64
package:        gnome-software-47.4-1.fc41
runlevel:       N 5
backtrace_rating: 4
crash_function: g_type_check_instance
comment:        Probably between the login screen and desktop. Otherwise before the login screen, which is then recovered in some way.

Booted from cold, logged in, crash notification popped up.


reporter:       libreport-2.17.15
reason:         gnome-software killed by SIGSEGV
cgroup:         0::/user.slice/user-1001.slice/user/app.slice/app-gnome-org.gnome.Software-4440.scope
backtrace_rating: 4
crash_function: g_type_check_instance
uid:            1001
runlevel:       N 5
type:           CCpp
cmdline:        /usr/bin/gnome-software --gapplication-service
journald_cursor: s=19b58861720d40b99ba31485ba2c2a10;i=41fd09;b=06081fd108c4408aa538df714c1601d8;m=226326c;t=62db9c97dc0b2;x=1cc3df4ea278dee1
rootdir:        /
package:        gnome-software-47.4-1.fc41
comment:        Booted from cold, logged in, crash notification popped up.
kernel:         6.12.11-200.fc41.x86_64
executable:     /usr/bin/gnome-software

Updates ran and my pc rebooted


reporter:       libreport-2.17.15
rootdir:        /
executable:     /usr/bin/gnome-software
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.gnome.Software-3102.scope
journald_cursor: s=57297644e529427fad1d7fbda86db352;i=3fee3;b=7739ae2d98394fdeab82edc13b92800c;m=13241e5;t=62f98762b18da;x=846b3622a8d54e1
kernel:         6.13.5-200.fc41.x86_64
package:        gnome-software-47.4-1.fc41
runlevel:       N 5
reason:         gnome-software killed by SIGSEGV
backtrace_rating: 4
crash_function: g_type_check_instance
comment:        Updates ran and my pc rebooted
cmdline:        /usr/bin/gnome-software --gapplication-service
type:           CCpp
uid:            1000

after an update and then restart gnome-software automatically starts to show which updates have been applied, but it then crashed


reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-software killed by SIGSEGV
journald_cursor: s=7ca4b319df8c44f29a40b930de3c7939;i=45fa87;b=d4622f69eb4d4f02928117aa1af441aa;m=1617843;t=638aa98b62a42;x=aff4eb53a912014
executable:     /usr/bin/gnome-software
cmdline:        /usr/bin/gnome-software --gapplication-service
cgroup:         0::/user.slice/user-1001.slice/user/app.slice/app-gnome-org.gnome.Software-3307.scope
rootdir:        /
uid:            1001
kernel:         6.15.3-100.fc41.x86_64
package:        gnome-software-47.5-1.fc41
runlevel:       N 5
backtrace_rating: 4
crash_function: g_type_check_instance
comment:        after an update and then restart gnome-software automatically starts to show which updates have been applied, but it then crashed

This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.