[Bug 719769] Re: inspector's unity_running is not initialized

2014-07-25 Thread TreviƱo
** Changed in: unity (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719769 Title: inspector's unity_running is not initialized To manage notifications abo

[Bug 719769] Re: inspector's unity_running is not initialized

2014-01-11 Thread Adolfo Jayme
** No longer affects: libunity (Ubuntu Quantal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719769 Title: inspector's unity_running is not initialized To manage notifications about this bug go to

[Bug 719769] Re: inspector's unity_running is not initialized

2011-02-24 Thread Launchpad Bug Tracker
This bug was fixed in the package libunity - 3.4.6-0ubuntu1 --- libunity (3.4.6-0ubuntu1) natty; urgency=low * New upstream release. - libunity support gobject-introspected languages (LP: #709240) - inspector's unity_running is not initialized (LP: #719769) * debian/rules:

[Bug 719769] Re: inspector's unity_running is not initialized

2011-02-24 Thread Mikkel Kamstrup Erlandsen
** Changed in: unity Importance: Undecided => Medium ** Changed in: unity Status: New => Fix Released ** Changed in: unity Milestone: None => 3.4.6 ** Changed in: unity Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup) -- You received this bug notification becau

[Bug 719769] Re: inspector's unity_running is not initialized

2011-02-24 Thread Mikkel Kamstrup Erlandsen
** Changed in: libunity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719769 Title: inspector's unity_running is not initialized -- ubuntu-bugs mailing

[Bug 719769] Re: inspector's unity_running is not initialized

2011-02-24 Thread Mikkel Kamstrup Erlandsen
** Changed in: libunity Milestone: None => 3.4.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719769 Title: inspector's unity_running is not initialized -- ubuntu-bugs mailing list ubuntu-bug

[Bug 719769] Re: inspector's unity_running is not initialized

2011-02-23 Thread Launchpad Bug Tracker
** Branch linked: lp:libunity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719769 Title: inspector's unity_running is not initialized -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com http

[Bug 719769] Re: inspector's unity_running is not initialized

2011-02-23 Thread Mikkel Kamstrup Erlandsen
Fixed in r41 ** Changed in: libunity Importance: Undecided => Low ** Changed in: libunity Status: New => Fix Committed ** Changed in: libunity Assignee: (unassigned) => Mikkel Kamstrup Erlandsen (kamstrup) -- You received this bug notification because you are a member of Ubuntu

[Bug 719769] Re: inspector's unity_running is not initialized

2011-02-22 Thread Mikkel Kamstrup Erlandsen
The only sync call is get_bus() and that doesn't touch the bus in 99.% of the times you call it :-) I realize now, however, that my logic is flawed - I assumed that you can always just listen for "notify::unity-running", but that signal may have fired before you ever connect to it (say - if th

[Bug 719769] Re: inspector's unity_running is not initialized

2011-02-17 Thread Michael Terry
The inspector constructor already makes sync calls, so I didn't think that was a concern (though I agree it should be). It's more than just documentation. My understanding is that a client should be able to ask "is unity running?" and they can't right now. unity_running defaults to FALSE and only

[Bug 719769] Re: inspector's unity_running is not initialized

2011-02-17 Thread Mikkel Kamstrup Erlandsen
Well, that would require a sync dbus call. The idea is that you connect to the notify signal on that property to track updates. You need to do that anyway if you plan to make use of that value. So I guess the solution here is just documentation? -- You received this bug notification because you