[krillin only] screen goes black immediately when pressing the Call button in dialer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
powerd |
In Progress
|
High
|
Michael Frey | ||
powerd (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
unity8 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity8 (Ubuntu RTM) |
Fix Released
|
High
|
Unassigned |
Bug Description
latest rtm image 84 on krillin
Have seen this problem for quite a while, but it is intermittent. Does not happen all the time, but I can get it to happen at least a few times per day
Steps to reproduce:
- open dialer
- type a number using the keypad
- press the call button
Expected results:
- screen stays on, live call view is made visible
Actual results:
- the screen goes immediately black
- pressing the power button shows the greeter/lockscreen as the call is not active yet
- the call continues to ring but you can't interact with it until you unlock the screen
This is causing Autopilot failures as well for the dialer as sometimes the screen goes black and can't be interacted with until unlocked.
Related branches
- PS Jenkins bot: Approve (continuous-integration)
- Ricardo Salveti (community): Needs Fixing
-
Diff: 15 lines (+6/-0)1 file modifiedsrc/powerd-sensors.cpp (+6/-0)
- Albert Astals Cid (community): Abstain
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Michael Terry: Approve
- Ricardo Salveti: Pending requested
-
Diff: 13 lines (+2/-1)1 file modifiedqml/Shell.qml (+2/-1)
tags: | added: rtm14 |
Changed in powerd: | |
importance: | Undecided → Critical |
Changed in powerd: | |
status: | New → In Progress |
assignee: | nobody → Michael Frey (mfrey) |
tags: | added: touch-2014-10-09 |
Changed in powerd: | |
status: | In Progress → Fix Committed |
Changed in powerd: | |
status: | Fix Committed → In Progress |
tags: |
added: touch-2014-10-23 removed: touch-2014-10-09 |
Changed in unity8 (Ubuntu RTM): | |
importance: | Undecided → High |
Changed in powerd: | |
importance: | Critical → High |
Changed in unity8 (Ubuntu): | |
status: | New → In Progress |
Changed in unity8 (Ubuntu RTM): | |
status: | New → In Progress |
This bug was fixed in the package unity8 - 8.01+15. 04.20141030~ rtm-0ubuntu1
--------------- 04.20141030~ rtm-0ubuntu1) 14.09; urgency=medium
unity8 (8.01+15.
[ Michael Terry ] Lockscreen
* Provide 'passphrase' as a field of Components.
* Fix a race between Qml loading and DBus registration that caused
problems when jenkins tried to unlock the phone.
* Set domain explicitly for the Dialogs component because the welcome
wizard wants to import it. (LP: #1381731)
* When greeter or lockscreen has focus, show active call panel. (LP:
#1378872)
[ Ted Gould ]
* Set the default OOM score for the dash (LP: #1379786)
[ Michał Sawicz ]
* Revert lp:~unity-team/unity8/flickables-speed-workaround to avoid
risk in RTM.
* Updated behaviour for zoomable image, workaround for sourcesize (LP:
#1333187)
[ Michael Frey ]
* Added a check for Proximity to determine if we show the lock screen.
(LP: #1378012)
[ Ying-Chun Liu ]
* Add non-interactive code into GenericScopeView. (LP: #1384441)
[ Mirco Müller ] lockscreen is shown. This fixes LP: #1378827. (LP: #1378827)
* Also use modal nature of snap-decision notifications when
greeter/
[ Michael Zanetti ]
* Make the launcher update on dconf changes (LP: #1376707)
* exit spread on background tap (LP: #1368261)
* Use an index instead of a scope id in DashCommunicator (LP:
#1376044)
[ Andrea Cimitan ]
* Updated behaviour for zoomable image, workaround for sourcesize (LP:
#1333187)
[ Daniel d'Andrada ]
* Make TouchGate synthesize QMouseEvents for mouse-based target items
* Don't specify a distanceThreshold as it conflicts with
hintDisplacment
-- Ubuntu daily release <email address hidden> Thu, 30 Oct 2014 21:43:42 +0000