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.
Bug 1110451 - [abrt] nautilus-2.28.4-19.el6: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-2.28.4-19.el6: Process /usr/bin/nautilus was killed by signal...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gvfs
Version: 6.5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Ondrej Holy
QA Contact: Desktop QE
Jiri Herrmann
URL:
Whiteboard:
: 1180375 (view as bug list)
Depends On:
Blocks: 1075802 1172231 1271696
TreeView+ depends on / blocked
 
Reported: 2014-06-17 17:27 UTC by Piyush Bhoot
Modified: 2019-10-10 09:19 UTC (History)
8 users (show)

Fixed In Version: gvfs-1.4.3-26.el6
Doc Type: Release Note
Doc Text:
*gvfs* correctly checks if the metadata database has been loaded Prior to this update, the *gvfs* metadata daemon or client applications such as Nautilus terminated unexpectedly when uninitialized internal structures were used for corrupted or unreadable metadata databases. This update adds a missing check that verifies that the metadata database has been loaded properly. As a result, in the described circumstances, an error is returned instead of a crash occurring.
Clone Of:
Environment:
Last Closed: 2016-05-10 19:43:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Corrupted metadata files to help reproduce the bug. (1.18 KB, application/x-gzip)
2016-01-12 13:15 UTC, Bohdan Milar 		bmilar: review-
Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 598561 0 None None None Never
Red Hat Product Errata RHBA-2016:0755 0 normal SHIPPED_LIVE gvfs bug fix update 2016-05-10 22:32:20 UTC

Description Piyush Bhoot 2014-06-17 17:27:55 UTC 
Version-Release number of selected component (if applicable):
nautilus-2.28.4-19.el6

Truncated Backtrace:
gdb) bt
#0  journal_entry_is_key_type (journal=0x7f5c180239b0, path=<value optimized out>, key_callback=0x7f5c50002f90 <enum_keys_iter_key>, 
    path_callback=0x7f5c50000fa0 <enum_keys_iter_path>, user_data=0x7f5c3bffd840) at metatree.c:1221
#1  meta_journal_iterate (journal=0x7f5c180239b0, path=<value optimized out>, key_callback=0x7f5c50002f90 <enum_keys_iter_key>, 
    path_callback=0x7f5c50000fa0 <enum_keys_iter_path>, user_data=0x7f5c3bffd840) at metatree.c:1310
#2  0x00007f5c50002a88 in meta_tree_enumerate_keys (tree=0x7f5c18003af0, path=0x7f5c3400bb10 "/", 
    callback=0x7f5c4ffee7a0 <enumerate_keys_callback>, user_data=0x2bef8c0) at metatree.c:2132
#3  0x00007f5c4ffee73a in g_daemon_vfs_local_file_add_info (vfs=<value optimized out>, filename=<value optimized out>, device=16929, 
    matcher=0x7f5c3400d940, info=0x2bef8c0, cancellable=<value optimized out>, extra_data=0x7f5c3bffdab8, extra_data_free=0x7f5c3bffdac0)
    at gdaemonvfs.c:1141
#4  0x00000032c62a83ae in _g_local_file_info_get (basename=<value optimized out>, path=0x3052ad0 "/media/apm_f19_v4", 
    attribute_matcher=0x7f5c3400d940, flags=G_FILE_QUERY_INFO_NONE, parent_info=<value optimized out>, error=<value optimized out>)
    at glocalfileinfo.c:1731
#5  0x00000032c62a4078 in g_local_file_query_info (file=0x2b142e0, attributes=<value optimized out>, flags=G_FILE_QUERY_INFO_NONE, 
    cancellable=<value optimized out>, error=0x7f5c3bffdb18) at glocalfile.c:1186


Additional info:

abrt_version:   2.0.8
backtrace_rating: 0
cmdline:        nautilus --sm-client-id 10f41d376a413e773e138418330696669300000043370026 --sm-client-state-file /home/abenoit/.config/session-state/nautilus-1400867893.state
executable:     /usr/bin/nautilus
kernel:         2.6.32-431.17.1.el6.x86_64
last_occurrence: 1401303015
pid:            4152
pwd:            /home/abenoit
time:           Wed 28 May 2014 02:50:15 PM EDT
uid:            18176
Comment 2 Alexander Larsson 2015-10-08 12:05:15 UTC 
This is the well known gvfs metadata bug. We should try to backport all the fixes we did there.
Comment 3 Ondrej Holy 2015-10-09 12:18:04 UTC 
*** Bug 1180375 has been marked as a duplicate of this bug. ***
Comment 8 Bohdan Milar 2016-01-12 13:15:38 UTC 
Created attachment 1113946 [details]
Corrupted metadata files to help reproduce the bug.

Source: https://bugzilla.gnome.org/attachment.cgi?id=145523
Comment 9 Bohdan Milar 2016-01-12 14:01:51 UTC 
The attachment file was taken from http://bugzilla.gnome.org/show_bug.cgi?id=598561 and is used by the created test case https://tcms.engineering.redhat.com/case/516641/
Comment 10 Bohdan Milar 2016-03-07 15:24:35 UTC 
Tested on x86_64, i386, ppc64, s390x using the created test case.
Bug verified as fixed.
Comment 12 errata-xmlrpc 2016-05-10 19:43:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0755.html
Note You need to log in before you can comment on or make changes to this bug.