Bug 2260068

Summary: [abrt] nemo: g_slice_free_chain_with_offset(): nemo killed by SIGSEGV
Product: [Fedora] Fedora Reporter: ingo <ingobeh>
Component: gtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: epel-packagers-sig, gnome-sig, ingobeh, leigh123linux, mclasen, riehecky
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/bd2c6faf7f35449be097f4815d04b4113920b5d
Whiteboard: abrt_hash:4b300233f19964f15474481ac6a2d9009f523ba2;VARIANT_ID=cinnamon;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-27 22:45:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: environ
none
File: dso_list
none
File: exploitable
none
File: cpuinfo
none
File: open_fds
none
File: backtrace
none
File: os_info
none
File: maps
none
File: mountinfo
none
File: core_backtrace
none
File: proc_pid_status
none
File: limits none

Description ingo 2024-01-24 09:35:54 UTC 
Version-Release number of selected component:
nemo-6.0.2-1.fc39

Additional info:
reporter:       libreport-2.17.11
cmdline:        /usr/bin/nemo
package:        nemo-6.0.2-1.fc39
executable:     /usr/bin/nemo
journald_cursor: s=810efe36c8664877b7ead9fae6990a3d;i=8a094;b=7c2de9084dd24d6fba09ce1df91d16f3;m=1e3b462d1;t=60fadc39e8ba4;x=10667ccc877de716
rootdir:        /
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
backtrace_rating: 4
uid:            1000
crash_function: g_slice_free_chain_with_offset
type:           CCpp
kernel:         6.6.12-200.fc39.x86_64
runlevel:       N 5
reason:         nemo killed by SIGSEGV

Truncated backtrace:
Thread no. 0 (18 frames)
 #0 g_slice_free_chain_with_offset at ../glib/gslice.c:371
 #1 g_slist_free at ../glib/gslist.c:151
 #2 g_object_notify_queue_free at ../gobject/gobject.c:283
 #3 g_datalist_clear at ../glib/gdataset.c:277
 #6 init_randr13 at ../gdk/x11/gdkscreen-x11.c:926
 #7 init_multihead at ../gdk/x11/gdkscreen-x11.c:1058
 #8 process_monitors_change at ../gdk/x11/gdkscreen-x11.c:1211
 #9 _gdk_x11_screen_size_changed at ../gdk/x11/gdkscreen-x11.c:1250
 #10 gdk_x11_display_translate_event at ../gdk/x11/gdkdisplay-x11.c:1201
 #11 _gdk_x11_event_translator_translate at ../gdk/x11/gdkeventtranslator.c:51
 #12 gdk_event_source_translate_event at ../gdk/x11/gdkeventsource.c:243
 #13 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:341
 #14 gdk_display_get_event at ../gdk/gdkdisplay.c:442
 #15 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354
 #17 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284
 #18 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349
 #19 g_main_context_iteration at ../glib/gmain.c:4414
 #20 g_application_run at ../gio/gapplication.c:2577
Comment 1 ingo 2024-01-24 09:35:58 UTC 
Created attachment 2010061 [details]
File: environ
Comment 2 ingo 2024-01-24 09:36:00 UTC 
Created attachment 2010062 [details]
File: dso_list
Comment 3 ingo 2024-01-24 09:36:01 UTC 
Created attachment 2010063 [details]
File: exploitable
Comment 4 ingo 2024-01-24 09:36:03 UTC 
Created attachment 2010064 [details]
File: cpuinfo
Comment 5 ingo 2024-01-24 09:36:04 UTC 
Created attachment 2010065 [details]
File: open_fds
Comment 6 ingo 2024-01-24 09:36:06 UTC 
Created attachment 2010066 [details]
File: backtrace
Comment 7 ingo 2024-01-24 09:36:07 UTC 
Created attachment 2010068 [details]
File: os_info
Comment 8 ingo 2024-01-24 09:36:09 UTC 
Created attachment 2010070 [details]
File: maps
Comment 9 ingo 2024-01-24 09:36:10 UTC 
Created attachment 2010072 [details]
File: mountinfo
Comment 10 ingo 2024-01-24 09:36:12 UTC 
Created attachment 2010074 [details]
File: core_backtrace
Comment 11 ingo 2024-01-24 09:36:13 UTC 
Created attachment 2010076 [details]
File: proc_pid_status
Comment 12 ingo 2024-01-24 09:36:14 UTC 
Created attachment 2010078 [details]
File: limits
Comment 13 leigh scott 2024-01-24 10:34:18 UTC 
https://github.com/GNOME/gtk/commit/77ebdd85091833a7869ece48c3114fa6d9966321
Comment 14 Milan Crha 2024-01-24 12:25:53 UTC 
*** Bug 2260094 has been marked as a duplicate of this bug. ***
Comment 15 Aoife Moloney 2024-11-13 11:53:29 UTC 
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.
Comment 16 Aoife Moloney 2024-11-27 22:45:28 UTC 
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.