Bug 47404

Summary:	Cannot use bustle with Remote tcp DBUS
Product:	Bustle	Reporter:	jaretouze-cedric
Component:	General	Assignee:	Will Thompson <will>
Status:	RESOLVED MOVED	QA Contact:
Severity:	major
Priority:	high	CC:	berfin.sert
Version:	unspecified
Hardware:	Other
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description jaretouze-cedric 2012-03-16 04:25:49 UTC

In version 0.2.5,

In a bash shell, doing :

export DBUS_SESSION_BUS_ADDRESS=tcp:host=<remote_device_IP>,port=1234

Then running bustle-monitor > file.txt

was loggin all dbus session traffic on my remote host (wich was configured to be accessible in remote)

Now in version 0.4

putting :

DBUS_SESSION_BUS_ADDRESS=tcp:host=10.12.74.140,port=1234
export DBUS_SESSION_BUS_ADDRESS

in the bustle.sh

launch bustle in the shell

Then in Bustle, Click New -> nothing happens and bustle is in frozen state. Need to Ctrl-C to exit.

Don't work also with bustle-pcap.

However I've got this log with new version of bustle :

(bustle-pcap:6511): GLib-GIO-WARNING **: Problems looking up entry in keyring: Error opening keyring `/home/<user>/.dbus-keyrings/org_freedesktop_general' for reading: Failed to open file '/home/<user>/.dbus-keyrings/org_freedesktop_general': No such file or directory

indeed I don't have this file "org_freedesktop_general".

Comment 1 Will Thompson 2012-06-21 09:03:31 UTC

Bustle just connects to the session bus using g_bus_get_sync (G_BUS_TYPE_SESSION, …). From looking at the GDBus source, setting DBUS_SESSION_BUS_ADDRESS and telling `bustle-pcap` to listen to the session bus should work—as should `gdbus`, for that matter.

  export DBUS_SESSION_BUS_ADDRESS=...
  gdbus monitor --session --dest com.example

or something.

In terms of monitoring over TCP from the UI, I think the right approach would be to add a menu item (File → Record from address…) which lets you paste in a bus address. This would then pass the address down to the C monitoring code, which would then use g_dbus_connection_new_for_address_sync() rather than g_bus_get_sync().

I'll try to prioritise this feature as and when I get a chance to hack on Bustle, though of course if anyone fancies having a crack at it that'd be great!

Comment 2 GitLab Migration User 2018-05-31 09:08:10 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/bustle/bustle/issues/10.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.