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... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1234904 Title: [mir-only] infometric values are not updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1234904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
