937498 - [Fugu][Buri][Gallery]cannot setup wallpaper for the first launch of Gallery

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Gallery, defect, P1)

Description

[Peipei Cheng (needinfo if you need my action)]

Test build:20131110004003
gecko: 8926376583fdd3711aaf75594fd4084306c5f02a
gaia: 3cc5e6ddec0656b3a6a197e989dabebee536c982

1.restart device or kill all process on device
2.Go to gallery.
2.Pick up a picture and click the share button
3.Choose Wallpaper.
  [issue] Nothing happens. Picture was not set as wallpaper
4.Send Gallery to backend, and then bring it to frontend
5. repeat 2 and 3. Wallpaper can be set.

Comment 1

[(Inactive after June) George Duan [:gduan] [:喬智]]

Depends on bug 934908 since we cannot enter pickView for second time,
I will test it later.

Comment 2

[Jason Smith [:jsmith]]

Does this reproduce on 1.2 or 1.3?

Comment 3

[James Zhang (Spreadtrum)]

v1.2

Comment 4

[Jason Smith [:jsmith]]

Okay - we should also check if this reproduces on 1.1

Comment 5

[J Zimbrick]

Unable to reproduce this issue on a Buri running 1.1, 1.2, or 1.3.

The wallpaper screen was brought up and I was able to assign the selected picture as a wallpaper on the first try each time when following the provided steps.

Are there additional steps not listed in the initial description?

Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20131119040204
Gaia: 4ecbc106a3fcf72cbd6dd8a43c46de7bacbedf20
Gecko: ba9ecdea3a90
Version: 28.0a1
Base Image: V1.2_20131115

Device: Buri v1.2 Mozilla RIL
BuildID: 20131119004006
Gaia: 9439907a255e04de4c33493fe03d6670c8256e2f
Gecko: fe2a7f0db27b
Version: 26.0
Base Image: V1.2_20131115

Device: Buri v1.1 Mozilla RIL
BuildID: 20131119041201
Gaia: b585b32441fafa67f2b4582db23be5f3a2afab21
Gecko: 7c3cfc0936ca
Version: 18.0
Base Image: V1.2_20131115

Comment 6

[Jason Smith [:jsmith]]

Not a blocker if doesn't reproduce on recent builds

Comment 7

[Peipei Cheng (needinfo if you need my action)]

I tried again. 
The same steps can reproduce this issue with build v1.2 build:20131110004003, but NOT on v1.2 build 20131119004006 and 20131118004001. So I think this might has been fixed.