Remote inspector will no longer work in Fedora 30 because we have switched from dbus-daemon to dbus-broker, which does not (and will not ever) support D-Bus over TCP. The only application I'm aware of that does D-Bus over TCP is our remote inspector, and D-Bus over TCP was considered deprecated before we started using it, so WebKit should change rather than except dbus-broker to support this.
(In reply to Michael Catanzaro from comment #0) > Remote inspector will no longer work in Fedora 30 because we have switched > from dbus-daemon to dbus-broker, which does not (and will not ever) support > D-Bus over TCP. > > The only application I'm aware of that does D-Bus over TCP is our remote > inspector, and D-Bus over TCP was considered deprecated before we started > using it, so WebKit should change rather than except dbus-broker to support > this. How is this a problem? I have been using dbus-broker in my laptop since its first release (months) and haven't had any trouble so far and connecting to the remote inspector has worked just fine ¯\_(ツ)_/¯ Am I missing something?
I can think of two possibilities: If your laptop is not running dbus-daemon, maybe the remote computer running WebKit that you're connecting to is? The D-Bus library used by WebKit is itself not changing, of course (that's still GIO). It's also possible that WebKit doesn't use a message bus at all, in which case dbus-daemon/dbus-broker is not involved in the D-Bus connection in any way, and everything should still work. I didn't consider that possibility, but that's probably more likely tbh. If so, this should be closed as INVALID.
Remote inspector doesn't use dbus daemon, it's p2p.