Pete, I didn't mean to give the impression of dumping it on your lap, but to ask if it made any sense to you either. :)
I agree with you that it's not likely to be a bug in libusermetrics itself. But this bug was usermetricsservice not being able to talk to libusermetricsoutput. I figured assigning to libusermetrics was closer to the real source of the problem than unity8 was.
I've looked into this, and thought I'd test the "frozen" angle. Adding a debug timer to libusermetricsoutput, it is definitely running while we're taking the photo and should be in a position to receive the signal.
I'm not sure why Mir would affect our ability to listen for the signal...
Pete, I didn't mean to give the impression of dumping it on your lap, but to ask if it made any sense to you either. :)
I agree with you that it's not likely to be a bug in libusermetrics itself. But this bug was usermetricsservice not being able to talk to libusermetricso utput. I figured assigning to libusermetrics was closer to the real source of the problem than unity8 was.
I've looked into this, and thought I'd test the "frozen" angle. Adding a debug timer to libusermetricso utput, it is definitely running while we're taking the photo and should be in a position to receive the signal.
I'm not sure why Mir would affect our ability to listen for the signal...