Unlocking the phone over fullscreen app is very slow
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity8 (Ubuntu) |
Invalid
|
High
|
Gerry Boland | ||
Vivid |
Invalid
|
High
|
Gerry Boland |
Bug Description
Steps to repro:
* have a pass{code,
* start dialer
* lock the phone
* unlock the phone
Expected:
* nothing much, stuff unlocks fluently and all
Current:
* fade out of the lockscreen takes like 2-3s, dialer and panel seem to fight over fullscreen vs. maximized surface size
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity8 8.01+15.
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu10
Architecture: armhf
Date: Tue Nov 25 17:46:27 2014
InstallationDate: Installed on 2014-11-25 (0 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141125-020205)
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
summary: |
- Unlocking the phone over dialer is very slow + Unlocking the phone over fullscreen app is very slow |
tags: | added: vivid-stab-candidate |
tags: | removed: vivid-stab-candidate |
no longer affects: | unity8 (Ubuntu RTM) |
When locking phone with dialer in front, I see it tries to make itself fullscreen
qtmir.surfaces: MirSurfaceManag er::onSurfaceAt tributeChanged - surface= 0x1c36080 state=fullscreen :setFullscreen - session= qtmir:: Session( 0x1b2e608) fullscreen= true ger::onAppDataC hanged: Received "fullscreen" update
qtmir.sessions: Session:
qtmir.applications: ApplicationMana
and then on unlock of phone, it un-fullscreens itself
qtmir.sessions: Session: :setFullscreen - session= qtmir:: Session( 0x1b2e608) fullscreen= false ger::onAppDataC hanged: Received "fullscreen" update :updateMirSurfa ceSize surface = qtmir:: MirSurfaceItem (this = 0x20f9850 , name= "" , parent = 0x19c2078 , geometry = QRectF(0,0 768x1222) , z = 1 ) , old ( 768 , 1280 ) , new ( 768 , 1222 ) surface resized
qtmir.applications: ApplicationMana
qtmir.surfaces: MirSurfaceItem:
Is dialer fullscreening itself on lock?