Description of problem: Idk I just logged in to my system after startup. Version-Release number of selected component: gnome-software-44.2-1.fc38 Additional info: reporter: libreport-2.17.10 type: CCpp reason: gnome-software killed by SIGSEGV journald_cursor: s=56ea0dc76f4f4682b3d347496b0eea7f;i=d0c24;b=d6d7f32bc81142cdb22bd0e21b554912;m=12703b5e6;t=5fe3a47d53959;x=471ae581daea4aff 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-3955.scope rootdir: / uid: 1000 kernel: 6.3.7-200.fc38.x86_64 package: gnome-software-44.2-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: gtk_css_value_unref comment: Idk I just logged in to my system after startup. Truncated backtrace: Thread no. 1 (19 frames) #0 gtk_css_value_unref at ../gtk/gtkcssvalue.c:179 #1 gtk_css_values_free at ../gtk/gtkcssstyle.c:791 #2 gtk_css_values_unref at ../gtk/gtkcssstyle.c:805 #3 gtk_css_style_finalize at ../gtk/gtkcssstyle.c:65 #6 gtk_css_node_style_cache_unref at ../gtk/gtkcssnodestylecache.c:64 #8 g_hash_table_remove_all_nodes at ../glib/ghash.c:709 #10 g_hash_table_unref at ../glib/ghash.c:1491 #11 gtk_css_node_style_cache_unref at ../gtk/gtkcssnodestylecache.c:66 #13 gtk_css_node_do_ensure_style at ../gtk/gtkcssnode.c:949 #14 gtk_css_node_ensure_style at ../gtk/gtkcssnode.c:998 #16 gtk_css_node_validate_internal at ../gtk/gtkcssnode.c:1320 #22 gtk_css_node_validate at ../gtk/gtkcssnode.c:1362 #24 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3883 #27 _gdk_frame_clock_emit_update at ../gdk/gdkframeclock.c:684 #28 gdk_frame_clock_paint_idle at ../gdk/gdkframeclockidle.c:557 #29 gdk_frame_clock_flush_idle at ../gdk/gdkframeclockidle.c:378 #33 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #34 g_main_context_iteration at ../glib/gmain.c:4343 #35 g_application_run at ../gio/gapplication.c:2573
Created attachment 1971145 [details] File: proc_pid_status
Created attachment 1971146 [details] File: maps
Created attachment 1971147 [details] File: limits
Created attachment 1971148 [details] File: environ
Created attachment 1971149 [details] File: open_fds
Created attachment 1971150 [details] File: mountinfo
Created attachment 1971151 [details] File: os_info
Created attachment 1971152 [details] File: cpuinfo
Created attachment 1971153 [details] File: core_backtrace
Created attachment 1971154 [details] File: exploitable
Created attachment 1971155 [details] File: dso_list
Created attachment 1971156 [details] File: var_log_messages
Created attachment 1971157 [details] File: backtrace
Thanks for a bug report. While the backtrace shows where the crash happens, it doesn't show why or what the crash caused. The crash happened deep in the gtk4 code, thus I'd move it there, but if it cannot be reproduced reliably, then I'm afraid diagnosing the cause of the crash is close to impossible. Also, the backtrace doesn't show any special activity in the other threads.
I clicked on new software information dialog, then accidentally clicked on an entry within the dialog. reporter: libreport-2.17.11 type: CCpp reason: gnome-software killed by SIGSEGV journald_cursor: s=b15b8113d94c40abaab49ada9b3044c6;i=318de3;b=f0c1a51b753e4e22b64aa4b05cb7b785;m=52ab9b9;t=5ffd191648728;x=38bf86f3b768dbe9 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-2978.scope rootdir: / uid: 1000 kernel: 6.3.11-200.fc38.x86_64 package: gnome-software-44.3-1.fc38 runlevel: N 5 dso_list: /usr/bin/gnome-software gnome-software-44.3-1.fc38.x86_64 (Fedora Project) 1688650291 backtrace_rating: 4 crash_function: gtk_css_value_unref comment: I clicked on new software information dialog, then accidentally clicked on an entry within the dialog.
Crashed when opening the details of one of the packages in the list of updates reporter: libreport-2.17.11 reason: gnome-software killed by SIGSEGV cmdline: /usr/bin/gnome-software --gapplication-service rootdir: / uid: 1000 type: CCpp package: gnome-software-44.4-1.fc38 runlevel: N 5 journald_cursor: s=a259751af99f4153924d9eb195192491;i=64c942;b=b04b17c7354a448280e46638887b5ddc;m=a96912d35;t=6065e4a16f9d3;x=a3b7cafb81996ea8 comment: Crashed when opening the details of one of the packages in the list of updates backtrace_rating: 4 crash_function: gtk_css_value_unref executable: /usr/bin/gnome-software kernel: 6.4.15-200.fc38.x86_64
*** Bug 2251745 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. 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 '39'. 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 39 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 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 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.