Skip Menu |

This queue is for tickets about the Net-DBus CPAN distribution.

Report information
The Basics
Id: 47804
Status: rejected
Priority: 0/
Queue: Net-DBus

People
Owner: Nobody in particular
Requestors: IVANWILLS [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.33.6
Fixed in: (no value)



I have a new package (Event::ScreenSaver almost on CPAN). It trys to listen to org.gnome.ScreenSaver's ActiveChanged signal then runs the reactor. If the code using this module also uses Net::DBus and uses it before the reactor code in my module is run then the my codes $reactor->run method always returns immediately. I also can see that the object returned from Net::DBus->find is different the second time it is called (but that only seem to be the case when the two calls are in different files).
On Sun Jul 12 01:21:54 2009, IVANWILLS wrote: Show quoted text
> I have a new package (Event::ScreenSaver almost on CPAN). It trys to > listen to org.gnome.ScreenSaver's ActiveChanged signal then runs the > reactor. > > If the code using this module also uses Net::DBus and uses it before the > reactor code in my module is run then the my codes $reactor->run method > always returns immediately. > > I also can see that the object returned from Net::DBus->find is > different the second time it is called (but that only seem to be the > case when the two calls are in different files).
Are you saying that your code *and* the application using your code are both calling 'Net::DBus::Reactor->main->run' at the same time ? Or does the app code use the reactor for a while, then shut it down, and then your code later start it again ? By default there is one single reactor instance that is used to manage all dbus connections within a program, so it doesn't entirely make sense to have two different bits of code within the same program to both be running the reactor. If you could provide a short example code that demonstrates the problem that would be helpful
Closing since information requested was not provided. Feel free to re-open if you are still have this problem & can provide more information.