Those interfaces were removed from upstream upower so relying on them is probably not the best idea now.
Thanks ZK On Thu, Mar 20, 2014 at 11:00 AM, Alberto Milone < [email protected]> wrote: > They are really two separate issue which, nonetheless, we're tracking in > LP: #1210077, and I think it makes sense to do so because the code to > handle resume is already in place in Unity (which is what this bug > report was about). > > It is true that one issue was in the nvidia driver (now fixed), however > the other issue is in Unity. The latter, though, is really Upower not > emitting the event on resume. This is why I suggested that we rely on > Logind instead. > > -- > You received this bug notification because you are a member of Canonical > Hardware Enablement Team, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/915265 > > Title: > [regression] Unity launcher on-screen corruption on resume from > suspend with nVidia proprietary driver > > To manage notifications about this bug go to: > https://bugs.launchpad.net/oem-priority/+bug/915265/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/915265 Title: [regression] Unity launcher on-screen corruption on resume from suspend with nVidia proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/915265/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
