823828 - Firefox OS just crashed notification is not dismissed after pressing "Report"

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[Marcia Knous [:marcia]]

Seen during end to end crash testing, unagi device using:

Gecko: c5fb80143cdf
Gaia: ccb9494855ef

STR:
1. Go into preferences to "Ask me when a crash occurs"
2. Send a adb kill command to the b2g process
3. Press the "Report" button at the bottom of the screen

Expected: The notification would be dismissed after pressing it
Actual: The notification remains and I have to shut off the screen for it to be dismissed

Comment 1

[Jason Smith [:jsmith]]

Small nit - flip the tracking flag and tef?

Comment 2

[:Margaret Leibovic]

Marcia, does the notification hang around forever, or does it eventually go away?

A few weeks ago I made a WIP patch for dismissing the notification immediately. It's here if anyone picks up this bug and wants to use it:
https://github.com/leibovic/gaia/commit/2ea8a2a7837c8a2ecbecf6afa7b4db6439b36c81

Comment 3

[Marcia Knous [:marcia]]

I will do a bit more testing of this today to check and see if it is still reproducible. John have you seen this during testing?

Comment 4

[Dietrich Ayala (:dietrich)]

Minusing, will take the patch on approval if well tested and near-zero risk. Marcia, please re-nom if investigation shows reproducible.

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Gecko  http://hg.mozilla.org/releases/mozilla-b2g18/rev/570a64393b8a
Gaia   d381947e8f066a5aaab17c4beeeec7f568627618
BuildID 20130117230201
Version 18.0
Unagi

I can't reproduce this specific issue off a fresh reboot.

The only time I got an issue where it caused me to have to force a reboot is when I had let the device sleep a long time before trying to kill the b2g.  Even then what I get instead is a black screen that didn't do anything prior to me rebooting the device.

Marcia could you try again please?  It might be some weird condition you hit prior to killing the process.  I'll try along the way again.

Comment 6

[Marcia Knous [:marcia]]

Tried reproducing this today on the latest nightly and was not able to.

Comment 7

[Lukas Blakk [:lsblakk] use ?needinfo]

Not tracking then, looks like this can be closed out if no longer reproducible.

Comment 8

[Deepa Subramanian]

When sending kill command to the device no notification report is received after performing step 1 and step 2 were performed. This happens during the lock screen too. 
This defect still repros on
Unagi Build ID: 20130508070204
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/66334a3bddcb
Gaia: 186d31782d8cadb296661a7d104bc28846d1dfb9

Comment 9

[Marcia Knous [:marcia]]

I just tested this and it WFM using the latest V1 train - you will get different results depending on what default crash setting you have set.

With "Ask me when a crash occurs", I am getting a notification. If you have "Always send," you will not get the report button.

If there is no notification being generated consistently (I don't see this currently), that should be filed as a separate bug as this bug was written about the notification being dismissed.


(In reply to Deepa Subramanian from comment #8)
> When sending kill command to the device no notification report is received
> after performing step 1 and step 2 were performed. This happens during the
> lock screen too. 
> This defect still repros on
> Unagi Build ID: 20130508070204
> Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/66334a3bddcb
> Gaia: 186d31782d8cadb296661a7d104bc28846d1dfb9

Comment 10

[Hubert Figuiere [:hub]]

Can't reproduce
And comment 9

Comment 11

[Hubert Figuiere [:hub]]

Actually i'm gonna reopen it. It seems that the touch event get passed to the dock as I ended up with the browser being launched instead (its icon is right where I tapped).

This is on master.

Comment 12

[BMO Automation]

Firefox OS is not being worked on