-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Openning a connection to a separate D-BUS bus #41
Comments
If you want to connect to a server that does not go through the D-Bus daemon, use the Ravel |
That does not seem to work out of the box:
Now this really looks like the problem that lead lrusak write this - and I noticed he also has another patch which seems to deal with another related issue.
Not sure why you're mentionning this, I'm not using any theading here. Also, don't you want to keep the ticket open for the segfault ? |
Although the README says we can create a ravel.Connection object, this is discouraged in the class' docstring.
The AT-SPI accessibility system uses a separate bus, which we can get eg. with:
This returns a string (well, a 1-element string list, which surprises the dbussy-noob in me) suitable for eg.
qdbus --bus ....
.Trying to use it with ravel, on Debian/testing (dbussy 1.3):
Given the ctypes in the backtrace it could be linked to #15, but that one is 100% reproducible.
The text was updated successfully, but these errors were encountered: