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.
Description of problem:
/usr/libexec/gvfsd-metadata is aborted frequently, a coredump is output.
(gdb) bt
#0 0x00000037fec32625 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00000037fec33e05 in abort () at abort.c:92
#2 0x0000003800467324 in g_assertion_message (domain=<value optimized out>,
file=<value optimized out>, line=<value optimized out>, func=
0x40b020 "meta_journal_add_entry", message=
0xad8a20 "assertion failed: (journal->journal_valid)") at gtestutils.c:1358
#3 0x00000038004678f0 in g_assertion_message_expr (domain=0x40ab95 "GVFS", file=
0x40adfd "metatree.c", line=1046, func=0x40b020 "meta_journal_add_entry",
expr=<value optimized out>) at gtestutils.c:1369
Currently, there is not the harm to a system.
Version-Release number of selected component (if applicable):
- kernel-2.6.32-504.3.3.el6.x86_64
- gvfs-1.4.3-18.el6
- glibc-2.12-1.149.el6
- glib2-2.28.8-4.el6
How reproducible:
Frequently
Steps to Reproduce:
No reproducer.
The customer said that abrtd reports coredump when a user log in.
Actual results:
gvfsd-metadata is aborted frequently.
Expected results:
gvfsd-metadata isn't aborted.
Additional info:
It is crashes probably, because metadata database is corrupted somehow. Try to remove or backup content of the ~/.local/share/gvfs-metadata/ directory. It should fix the problem.
To solve the issue properly we have to found what cause the database corruption. We need reproducer with empty gvfs-metadata directory. Please try to figure out what cause the crashes and provide full backtrace.
Description of problem: /usr/libexec/gvfsd-metadata is aborted frequently, a coredump is output. (gdb) bt #0 0x00000037fec32625 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x00000037fec33e05 in abort () at abort.c:92 #2 0x0000003800467324 in g_assertion_message (domain=<value optimized out>, file=<value optimized out>, line=<value optimized out>, func= 0x40b020 "meta_journal_add_entry", message= 0xad8a20 "assertion failed: (journal->journal_valid)") at gtestutils.c:1358 #3 0x00000038004678f0 in g_assertion_message_expr (domain=0x40ab95 "GVFS", file= 0x40adfd "metatree.c", line=1046, func=0x40b020 "meta_journal_add_entry", expr=<value optimized out>) at gtestutils.c:1369 Currently, there is not the harm to a system. Version-Release number of selected component (if applicable): - kernel-2.6.32-504.3.3.el6.x86_64 - gvfs-1.4.3-18.el6 - glibc-2.12-1.149.el6 - glib2-2.28.8-4.el6 How reproducible: Frequently Steps to Reproduce: No reproducer. The customer said that abrtd reports coredump when a user log in. Actual results: gvfsd-metadata is aborted frequently. Expected results: gvfsd-metadata isn't aborted. Additional info: