Description of problem: When trying to find the dbus interfaces and methods for AVAHI using dbus-send resulted in this crash. Used the below command, dbus-send --system --print-reply --type=method_call --dest='org.freedesktop.Avahi' 'org/freedesktop/Avahi' org.freedesktop.DBus.Introspectable.Introspect Console log: dbus[10722]: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file ../../dbus/dbus-message.c line 1366. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Aborted (core dumped) Version-Release number of selected component: 1:dbus-1.12.0-1.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: dbus-send --system --print-reply --type=method_call --dest=org.freedesktop.Avahi org/freedesktop/Avahi org.freedesktop.DBus.Introspectable Introspect crash_function: _dbus_warn_check_failed executable: /usr/bin/dbus-send journald_cursor: s=f17e97f152d646839ef9eaaef54b0034;i=27ca2;b=0f6f77035c7f44b3970f6b0c509610cd;m=1768cc7574;t=56d58c62387db;x=174fb6988b8fd22e kernel: 4.16.11-200.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 529 Truncated backtrace: Thread no. 1 (3 frames) #3 _dbus_warn_check_failed at ../../dbus/dbus-internals.c:281 #4 _dbus_warn_return_if_fail at ../../dbus/dbus-internals.c:936 #5 dbus_message_new_method_call at ../../dbus/dbus-message.c:1366
Created attachment 1445395 [details] File: backtrace
Created attachment 1445396 [details] File: cgroup
Created attachment 1445397 [details] File: core_backtrace
Created attachment 1445398 [details] File: cpuinfo
Created attachment 1445399 [details] File: dso_list
Created attachment 1445400 [details] File: environ
Created attachment 1445401 [details] File: limits
Created attachment 1445402 [details] File: maps
Created attachment 1445403 [details] File: mountinfo
Created attachment 1445404 [details] File: open_fds
Created attachment 1445405 [details] File: proc_pid_status
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.