*** This bug is a duplicate of bug 1236525 ***
https://bugs.launchpad.net/bugs/1236525
** Tags added: nexus4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1188504
Title:
Nexus4: Mir server
** Also affects: unity8 (Ubuntu Saucy)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1188504
Title:
Nexus4: Mir server dies when display goes to sleep
** Tags added: qa-touch rls-s-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1188504
Title:
Nexus4: Mir server dies when display goes to sleep (error posting
with fb device) and can no
** Changed in: mir
Assignee: (unassigned) = Kevin DuBois (kdub)
** Changed in: mir
Importance: High = Critical
** Changed in: mir
Milestone: None = phone-v1-freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
i just verified that at least under regular use
image 83 (channel devel-proposed)
blanking/waking works fine in either the time-out case or pressing the power
button to blank the screen.
I've rebooted, opened a variety of apps, seems no matter what I do, i cannot
reproduce the inability to wake
so cutting unity8 out of the loop altogether by using
mir_demo_standalone_render_to_fb, here's what I see
(from powerd-cli listen)
Received DisplayPowerStateChange: state=1 flags=0x04
root@ubuntu-phablet:/root# ./mir_demo_standalone_render_to_fb
renders ok for a while until the screen
powerd calls unity8 (via dbus) which calls mir to turn off the display.
If i cut unity8 out of the loop, then powerd and mir disagree on the fb
state more often because calls to change the state (originating from
powerd) don't update mir.
kgunn probably didn't see any problems (and users
closing to avoid confusion. this bug was due to an original problem
around lack of unblank support.
there is an architectural question of unblank causing issues in the case where
unity8 is stopped, e.g. under test
this bug is here https://bugs.launchpad.net/powerd/+bug/1236525
** Changed in:
*** This bug is a duplicate of bug 1236525 ***
https://bugs.launchpad.net/bugs/1236525
Since there wasn't actually a fix anywhere, I think this should be a
duplicate of the newly opened bug 1236525...
** Changed in: mir
Status: Fix Released = Triaged
** Changed in: unity8 (Ubuntu
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity8 (Ubuntu)
Status: New = Confirmed
** Changed in: unity8 (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
10 matches
Mail list logo
