Bug 2418164 - [abrt] nautilus: closure_atomic_get_flags(): nautilus killed by SIGSEGV
Summary: [abrt] nautilus: closure_atomic_get_flags(): nautilus killed by SIGSEGV
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 43
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:b89fa9ad97a3780a9529610ce7e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-12-01 23:36 UTC by Steve Barcomb
Modified: 2026-02-09 21:47 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-02-09 21:47:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: proc_pid_status (1.48 KB, text/plain)
2025-12-01 23:36 UTC, Steve Barcomb
no flags Details
File: maps (86.43 KB, text/plain)
2025-12-01 23:36 UTC, Steve Barcomb
no flags Details
File: limits (1.29 KB, text/plain)
2025-12-01 23:36 UTC, Steve Barcomb
no flags Details
File: environ (1.49 KB, text/plain)
2025-12-01 23:36 UTC, Steve Barcomb
no flags Details

Description Steve Barcomb 2025-12-01 23:36:27 UTC
Description of problem:
this happens very consistently when browsing a gvfs windows share

Version-Release number of selected component:
nautilus-49.1-5.fc43

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         nautilus killed by SIGSEGV
journald_cursor: s=4c3af01b930348adaacb880a0f9e176e;i=23483;b=1b112eaf37f5491d966836367ba08d6a;m=e5b4f71f;t=644ec6da27c7b;x=860131498bba2ffa
executable:     /usr/bin/nautilus
cmdline:        /usr/bin/nautilus -w
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-nautilus-58427.scope
rootdir:        /
uid:            1000
kernel:         6.17.8-300.fc43.x86_64
package:        nautilus-49.1-5.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: closure_atomic_get_flags
comment:        this happens very consistently when browsing a gvfs windows share

Truncated backtrace:
Thread no. 1 (23 frames)
 #0 closure_atomic_get_flags at ../gobject/gclosure.c:162
 #1 g_closure_remove_invalidate_notifier at ../gobject/gclosure.c:823
 #2 remove_invalid_closure_notify at ../gobject/gsignal.c:4068
 #4 signal_handler_disconnect_unlocked at ../gobject/gsignal.c:2696
 #5 g_signal_handler_disconnect at ../gobject/gsignal.c:2680
 #6 unbind_internal_locked at ../gobject/gbinding.c:315
 #7 weak_unbind at ../gobject/gbinding.c:416
 #8 g_object_weak_release_all at ../gobject/gobject.c:4065
 #9 g_object_real_dispose at ../gobject/gobject.c:1816
 #11 gtk_list_item_set_child at ../gtk/gtklistitem.c:387
 #13 gtk_signal_list_item_factory_teardown at ../gtk/gtksignallistitemfactory.c:145
 #14 gtk_list_factory_widget_teardown_factory at ../gtk/gtklistfactorywidget.c:139
 #15 gtk_list_factory_widget_clear_factory at ../gtk/gtklistfactorywidget.c:250
 #16 gtk_list_factory_widget_dispose at ../gtk/gtklistfactorywidget.c:259
 #18 maybe_unset_focus_and_default at ../gtk/gtkwindow.c:4922
 #19 after_paint at ../gtk/gtkwindow.c:4943
 #22 signal_emit_valist_unlocked at ../gobject/gsignal.c:3535
 #25 _gdk_frame_clock_emit_after_paint at ../gdk/gdkframeclock.c:749
 #26 gdk_frame_clock_paint_idle at ../gdk/gdkframeclockidle.c:643
 #29 g_main_context_dispatch_unlocked at ../glib/gmain.c:4425
 #30 g_main_context_iterate_unlocked at ../glib/gmain.c:4490
 #31 g_main_context_iteration at ../glib/gmain.c:4556
 #32 g_application_run at ../gio/gapplication.c:2741

Comment 1 Steve Barcomb 2025-12-01 23:36:31 UTC
Created attachment 2117019 [details]
File: proc_pid_status

Comment 2 Steve Barcomb 2025-12-01 23:36:32 UTC
Created attachment 2117020 [details]
File: maps

Comment 3 Steve Barcomb 2025-12-01 23:36:34 UTC
Created attachment 2117021 [details]
File: limits

Comment 4 Steve Barcomb 2025-12-01 23:36:35 UTC
Created attachment 2117022 [details]
File: environ

Comment 5 Fedora Admin user for bugzilla script actions 2025-12-01 23:36:36 UTC
Bug reports for this component on Red Hat Bugzilla are not actively monitored. Please consider reporting your issue directly to GNOME at https://gitlab.gnome.org/GNOME/ to improve the chances that your issue will be resolved. This issue should only be kept open if it:

1. Relates to Fedora packaging or integration with other Fedora components
2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions

If this issue isn't needed for either of these two reasons, please:

 * create an issue with GNOME
 * add a link to the GNOME issue here
 * close this issue as CLOSED/UPSTREAM

Thank you!

Comment 6 Steve Barcomb 2025-12-01 23:37:41 UTC
this happens very consistently when browsing a gvfs windows share


reporter:       libreport-2.17.15
type:           CCpp
reason:         nautilus killed by SIGSEGV
journald_cursor: s=4c3af01b930348adaacb880a0f9e176e;i=23483;b=1b112eaf37f5491d966836367ba08d6a;m=e5b4f71f;t=644ec6da27c7b;x=860131498bba2ffa
executable:     /usr/bin/nautilus
cmdline:        /usr/bin/nautilus -w
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-nautilus-58427.scope
rootdir:        /
uid:            1000
kernel:         6.17.8-300.fc43.x86_64
package:        nautilus-49.1-5.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: closure_atomic_get_flags
comment:        this happens very consistently when browsing a gvfs windows share

Comment 7 Steve Barcomb 2025-12-02 14:15:23 UTC
opened https://gitlab.gnome.org/GNOME/gtk/-/issues/7910

Comment 8 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-01-29 14:26:57 UTC
(In reply to Steve Barcomb from comment #7)

> opened https://gitlab.gnome.org/GNOME/gtk/-/issues/7910

Probably best to close this as UPSTREAM, and add that URI to the “Links” section, right?

---

(In reply to Steve Barcomb from comment #6)

> runlevel:       /bin/sh: line 1: runlevel: command not found

If of use, I've reported this at https://github.com/abrt/libreport/issues/827#issue-3870980082.


Note You need to log in before you can comment on or make changes to this bug.