Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Version-Release number of selected component:
nautilus-3.8.2-8.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        nautilus --new-window /home/djasa/Pictures
crash_function: nautilus_bookmark_connect_file
executable:     /usr/bin/nautilus
kernel:         3.10.0-175.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            16189

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 nautilus_bookmark_connect_file
 #5 nautilus_bookmark_constructed
 #6 g_object_new_internal at gobject.c:1763
 #7 g_object_new_valist at gobject.c:1980
 #9 nautilus_bookmark_new
 #10 view_begin_loading_cb
 #15 finish_loading_if_all_metadata_loaded
 #16 metadata_for_directory_as_file_ready_callback
 #17 call_ready_callbacks_at_idle
 #18 ??

Potential duplicate: bug 1149780

Created attachment 946898 [details]
File: backtrace

Created attachment 946899 [details]
File: cgroup

Created attachment 946900 [details]
File: core_backtrace

Created attachment 946901 [details]
File: dso_list

Created attachment 946902 [details]
File: environ

Created attachment 946903 [details]
File: limits

Created attachment 946904 [details]
File: maps

Created attachment 946905 [details]
File: open_fds

Created attachment 946906 [details]
File: proc_pid_status

Created attachment 946907 [details]
File: var_log_messages

Created attachment 946908 [details]
File: binary

Created attachment 946909 [details]
File: sosreport.tar.xz

Another user experienced a similar problem:

Crashed on mounting an archive

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: nautilus_bookmark_connect_file
executable:     /usr/bin/nautilus
kernel:         3.10.0-229.el7.x86_64
package:        nautilus-3.14.2-1.el7
reason:         nautilus killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

This looks to have been recently fixed upstream:

https://git.gnome.org/browse/nautilus/commit/?id=9429c94f354460e7bcc2a9063b98f3a904e6a358

It should be straightforward to backport the patch.

After closer investigation, this looks like a duplicate of an existing bug.

*** This bug has been marked as a duplicate of bug 1115338 ***