-
Notifications
You must be signed in to change notification settings - Fork 69
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
Error: No introspectable #222
Comments
I've discovered that this gtkDialog is actually being opened by Electron, due to an unhandled exception, so the dialog itself has nothing to do with node-dbus. However, if there's a way to test whether a given interface is accessible before trying to call it (causing this unhandled exception), I'd be really grateful to find out as this is crashing my application. |
I have the same error. I have fixed the permissions. Any idea on what we are doing wrong here? Here is the underlying error:
Here are the message and response:
|
Seems my issue is related to #183 |
Is there a way to stop node-dbus from trying to open a gtkDialog to display an error message?
I'm working on a kiosk application running on top of Ubuntu Core, which doesn't have a full desktop environment and trying to open this dialog just crashes the application. I'd like to be able to fail more gracefully and handle the error myself.
More specifically, if the application tries to call
systemBus.getInterface('org.freedesktop.NetworkManager', '/org/freedesktop/NetworkManager', 'org.freedesktop.NetworkManager', callback);
but the application doesn't have permission to access the network manager, then node-dbus fires an error saying "Error: No introspectable" and I see an error saying "GtkDialog mapped without a transient parent. This is discouraged." and my application fails to start. I'd to prevent that error from trying to open a GtkDialog and handle it myself.
The text was updated successfully, but these errors were encountered: