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:
gvfs-1.16.4-7.el7

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/gvfs-udisks2-volume-monitor
crash_function: g_object_new_valist
executable:     /usr/libexec/gvfs-udisks2-volume-monitor
kernel:         3.10.0-123.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #7 g_object_new_valist at gobject.c:1836
 #8 g_initable_new_valist at ginitable.c:227
 #9 g_initable_new at ginitable.c:149
 #10 add_interfaces at gdbusobjectmanagerclient.c:1485
 #11 on_control_proxy_g_signal at gdbusobjectmanagerclient.c:1659
 #12 ffi_call_unix64 at /lib64/libffi.so.6
 #13 ffi_call at /lib64/libffi.so.6
 #14 g_cclosure_marshal_generic at gclosure.c:1454
 #19 on_signal_received at gdbusproxy.c:927
 #20 emit_signal_instance_in_idle_cb at gdbusconnection.c:3715

Created attachment 913194 [details]
File: backtrace

Created attachment 913195 [details]
File: cgroup

Created attachment 913196 [details]
File: core_backtrace

Created attachment 913197 [details]
File: dso_list

Created attachment 913198 [details]
File: environ

Created attachment 913199 [details]
File: limits

Created attachment 913200 [details]
File: maps

Created attachment 913201 [details]
File: open_fds

Created attachment 913202 [details]
File: proc_pid_status

Created attachment 913203 [details]
File: var_log_messages

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

Thanks for the bugreport. Hard to say what's wrong, because gvfs is missing in the stacktrace. Are you able to reproduce it?

(In reply to Ondrej Holy from comment #13)
> Thanks for the bugreport. Hard to say what's wrong, because gvfs is missing
> in the stacktrace. Are you able to reproduce it?

I don't recall I would see it again.

There are some crashes for Fedora 19 and CentOS 7 at https://retrace.fedoraproject.org/faf2/reports/4186/, but not for newer Fedoras. It seems like glib2 bug according the backtrace. Unfortunately I don't see any significant changes in the affected codes in gvfs/glib. It could be fixed by the planned rebase, because there aren't abrt reports for newer Fedoras. However closing this bug, because we don't have reproducer, nor any sufficient info to fix/verify this bug.