Closed
Bug 929285
Opened 11 years ago
Closed 11 years ago
[Gaia][System] after enable software home button and rebooting, app cannot be launched
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(blocking-b2g:koi+, b2g-v1.2 fixed)
People
(Reporter: gduan, Assigned: alive)
Details
(Keywords: regression, Whiteboard: [FT:System-Platform])
Attachments
(1 file)
Try on recent build 20131020040204 and flashed to latest gaia 595ee85a2d7f16b7. 1. device enable the software home button and reboot it 2. click one of the app Expect: launch the app -- KO Actual: App icon enlarged and disappear, but screen only remain the background of homescreen
Reporter | ||
Comment 1•11 years ago
|
||
I guess it may come from system app, so I tried to go back to 5a185523e3 and make reset-gaia, and found out it works normally. And also tried 6238e6f957, and it breaks. So, it's properly a regression between these two commit. https://github.com/mozilla-b2g/gaia/commits/master/apps/system
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → alive
Assignee | ||
Comment 2•11 years ago
|
||
Root cause: miss predefine appWindow size for software home button enabled.
Attachment #820312 -
Flags: review?(timdream)
Assignee | ||
Updated•11 years ago
|
blocking-b2g: --- → koi?
Keywords: regression
Updated•11 years ago
|
Whiteboard: [FT:System-Platform]
Updated•11 years ago
|
Attachment #820312 -
Flags: review?(timdream) → review+
Assignee | ||
Comment 3•11 years ago
|
||
https://github.com/mozilla-b2g/gaia/commit/cf2e63a44fbf095d3a7b5975919a1df19f610c8f
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 4•11 years ago
|
||
+'ing because this bug is going to break phones w/o hardware home buttons, e.g. Nexus. The patch is fairly simple too so if we cannot koi+ this I could a+ the patch instead.
blocking-b2g: koi? → koi+
Comment 5•11 years ago
|
||
I was not able to uplift this bug to v1.2. If this bug has dependencies which are not marked in this bug, please comment on this bug. If this bug depends on patches that aren't approved for v1.2, we need to re-evaluate the approval. Otherwise, if this is just a merge conflict, you might be able to resolve it with: git checkout v1.2 git cherry-pick -x -m1 cf2e63a44fbf095d3a7b5975919a1df19f610c8f <RESOLVE MERGE CONFLICTS> git commit
Flags: needinfo?(alive)
Comment 6•11 years ago
|
||
Uplifted cf2e63a44fbf095d3a7b5975919a1df19f610c8f to: v1.2: a87e04237d9fc1b26c70cf2baa72412250fb26d7
status-b2g-v1.2:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•