Did someone make dbus work? When I run dbus-monitor, I see that a dbus-daemon process is created, but I get this error message:
Failed to open connection to session bus: Failed to get autolaunch address from launched dbus-daemon
any idea what do I miss to get it working?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
cd c:\python34\Lib\site-packages\gnome
dbus-daemon.exe --session
Here I can see a dbus-daemon process running.
I open a second command line interface
cd c:\python34\Lib\site-packages\gnome
dbus-monitor.exe
Here I see a second dbus-daemon process running and a dbus-monitor one for a few seconds, then I have this error printed:
"Failed to open connection to session bus: Failed to get autolaunch address from launched dbus-daemon"
The dbus-monitor process ends, but the dbus-daemon one keeps running. And a new one is created each time I try again to run dbus-monitor
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No I changed nothing in Python34\Lib\site-packages\gnome folder and subfolders. Is there something special to add to PATH except c:\Python34\Lib\site-packages\gnome ?
Is it normal that no environment variable is set when I run dbus-daemon?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
great ! running dbus-daemon and dbus-monitor with --address "autolaunch:scope=*user" works !
It also work if I simply change nonce-tcp: to autolaunch: in etc/dbus-1/session.conf
Thanks for the link!
now I have another question: What is the "gnome keyring" entry in your installer? only the lib to access the gnome keyring? Is there a way to launch a gnome-keyring daemon?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's the library version I think, which superseded by libsecret? I think the actual daemon is linux specific (unix-style credentials, etc). I'm not familiar at all about those though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not really, rather it's my lack of undersanding about keyring since I'm not using Linux. If I recall I start include it when compiling GCR/GCK which I thought to be related.
Is it really useless? If so, I'll remove them in the future.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
libgnome-keyring is a lib to access the gnome keyring daemon via D-Bus.
libsecret is a bit more global, it allows access to any secret service like gnome keyring or ksecretservice. But I'm not aware of any windows secret service. So IMHO those libs are not usefull under windows.
The 3 other you list, I can't tell anything, I never used them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
coming back to the subject: DBus.
I tried to create a small dbus service with the attached test_dbus.py. It works correctly under linux (I can run the test_dbus_client.py to talk to the service).
But under windows, the service creation fails. Python crashed on line sbus = dbus.SessionBus()
This same line works correctly if I don't do the DBusGMainLoop(set_as_default=True) line before, but in that case it crashes later.
I run it with gdb, I get that:
{{{
(gdb) run test_dbus.py
Starting program: C:\Python34\python.exe test_dbus.py [New Thread 284.0xbb0] [New Thread 284.0x39c] [Inferior 1 (process 284) exited with code 030000002027]
(gdb)
}}}
Ugh that dbus-python is.. hmm before I get my hand dirty... shouldn't you go with GDBus first or probably https://github.com/LEW21/pydbus? Just to be sure which the problem is I think dbus python is intended for PyGTK and sill have poor gi support.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did someone make dbus work? When I run dbus-monitor, I see that a dbus-daemon process is created, but I get this error message:
Failed to open connection to session bus: Failed to get autolaunch address from launched dbus-daemon
any idea what do I miss to get it working?
Works for me, can clarify how you launch the daemon?
I open a command line interface.
cd c:\python34\Lib\site-packages\gnome
dbus-daemon.exe --session
Here I can see a dbus-daemon process running.
I open a second command line interface
cd c:\python34\Lib\site-packages\gnome
dbus-monitor.exe
Here I see a second dbus-daemon process running and a dbus-monitor one for a few seconds, then I have this error printed:
"Failed to open connection to session bus: Failed to get autolaunch address from launched dbus-daemon"
The dbus-monitor process ends, but the dbus-daemon one keeps running. And a new one is created each time I try again to run dbus-monitor
Tried exactly that, but can't reproduce it
That's weird it shouldn't respawned like that, is there any modification made to dbus configuration files?
No I changed nothing in Python34\Lib\site-packages\gnome folder and subfolders. Is there something special to add to PATH except c:\Python34\Lib\site-packages\gnome ?
Is it normal that no environment variable is set when I run dbus-daemon?
Problem is the same with rev20
have you try it in VM?
Yes it's in a VM.
After installaing VirtualBOX, I can reproduce it both on real hardware and VM. Weird..
BTW this is better explanation http://lists.freedesktop.org/archives/dbus/2012-July/015203.html I may change it to one of that in the future.
great ! running dbus-daemon and dbus-monitor with --address "autolaunch:scope=*user" works !
It also work if I simply change nonce-tcp: to autolaunch: in etc/dbus-1/session.conf
Thanks for the link!
now I have another question: What is the "gnome keyring" entry in your installer? only the lib to access the gnome keyring? Is there a way to launch a gnome-keyring daemon?
That's the library version I think, which superseded by libsecret? I think the actual daemon is linux specific (unix-style credentials, etc). I'm not familiar at all about those though.
ok I use libscret indeed, but why compile it under windows if there is no daemon listening behind it? Do I miss something?
Not really, rather it's my lack of undersanding about keyring since I'm not using Linux. If I recall I start include it when compiling GCR/GCK which I thought to be related.
Is it really useless? If so, I'll remove them in the future.
OT: There are some other dbus related libraries that I dont know if those are linux specific
- accounts-glib
- appstream-glib
- dee
libgnome-keyring is a lib to access the gnome keyring daemon via D-Bus.
libsecret is a bit more global, it allows access to any secret service like gnome keyring or ksecretservice. But I'm not aware of any windows secret service. So IMHO those libs are not usefull under windows.
The 3 other you list, I can't tell anything, I never used them.
coming back to the subject: DBus.
I tried to create a small dbus service with the attached test_dbus.py. It works correctly under linux (I can run the test_dbus_client.py to talk to the service).
But under windows, the service creation fails. Python crashed on line sbus = dbus.SessionBus()
This same line works correctly if I don't do the DBusGMainLoop(set_as_default=True) line before, but in that case it crashes later.
I run it with gdb, I get that:
{{{
(gdb) run test_dbus.py
Starting program: C:\Python34\python.exe test_dbus.py
[New Thread 284.0xbb0]
[New Thread 284.0x39c]
[Inferior 1 (process 284) exited with code 030000002027]
(gdb)
}}}
Ugh that dbus-python is.. hmm before I get my hand dirty... shouldn't you go with GDBus first or probably https://github.com/LEW21/pydbus? Just to be sure which the problem is I think dbus python is intended for PyGTK and sill have poor gi support.
Yes I'd like to switch to GDBus, but unfortunatly it was not usable under python until 10 days ago:
https://bugzilla.gnome.org/show_bug.cgi?id=656325
Thanks for the link, I will try if that reviewed patch could applied to glib-2.32 or waiting for a bugfix release...