Leo Reporter
	Description • 11 years ago

1. Title : Cannot delete all logs in call log
2. Precondition : Connect multi call >> Switch call >> End all calls >> Enter call log
3. Tester's Action : Delete all logs
4. Detailed Symptom : Some logs remain
5. Expected : Can delete all logs
6. Reproducibility: Y
1) Frequency Rate : sometimes
7. Gaia Master/v1-train : Reproduced
8. Gaia Revision : 5cbb19e4bb78a7ad879fbe4b9a841e1c35714f5c
9 Personal email id : promise09th@gmail.com

	Tony Chung [:tchung]
	Comment 2 • 11 years ago

(In reply to Leo from comment #1)
> Created attachment 746722 [details]
> Cannot delete all logs

can you reproduce this again, this time try and record the logcat of the activity?  also, do you know the gecko changeset you have running on this?

	Leo Reporter
	Comment 3 • 11 years ago

Gecko revision : 950b402b6188bb2f3ce3176e620ed5249719d720

	Wayne Chang [:wchang]
	Comment 4 • 11 years ago

Hi Leo, can you let us know if the remaining call logs can never be deleted or do they get deleted when you attempt to 'delete all' again?

Hi Etienne, can you suggest someone to look at this issue? logs are attached.

	Leo Reporter
	Comment 5 • 11 years ago

I tried serveral times, Remaining logs can't be deleted again. 
Only logs can be deleted by "Factory reset"

	Alex Keybl [:akeybl]
	Comment 6 • 11 years ago

we suspect this is related to multi-calls, we'll need to find an assignee

	Etienne Segonzac (:etienne)
	Comment 7 • 11 years ago

The call log is being refactored (bug 847406, leo+ too).
We should test this again when it lands.

	Evan Tseng [:evanxd] Assignee
	Comment 10 • 11 years ago

Hi all,

You could see the log files "Root cause adb log" and "Root cause console log".

In the "Root cause console log" file, we could found out that
when user picked up a call and held a call, after ringed off one of these two calls and 
the handleEvent() function in handled_call.js was triggered with receiving the "connected" message.

So the connected() function of the HandledCall object was triggered for two times. And the bug was happend.

	Evan Tseng [:evanxd] Assignee
	Comment 11 • 11 years ago

I think is might be also a Gecko bug.

Bug I have a patch could fix the bug before the Gecko bug is resolved.

I think we could use the patch to fix this bug first, and create another bug for the Gecko issue.

How do you guys think?

	Evan Tseng [:evanxd] Assignee
	Comment 12 • 11 years ago

Hi Etienne,

Please help me review the patch.

Thanks. :)

	Tim Guan-tin Chien [:timdream] (please needinfo)
	Comment 13 • 11 years ago

(In reply to Evan Tseng [:evanxd] from comment #11)
> I think is might be also a Gecko bug.

Please file a bug if there is a bug. Thanks.

	Etienne Segonzac (:etienne)
	Comment 14 • 11 years ago

Comment on attachment 748400 [details]
Point to the GitHub pull request: https://github.com/mozilla-b2g/gaia/pull/9695

Well, the incoming and outgoing calls all go through this, so we can't do that.

That said, the underlying data backend changed and is currently in review.
So as I said in Comment 7 we should wait for the refactoring to land first.

	Evan Tseng [:evanxd] Assignee
	Comment 15 • 11 years ago

Hi Etienne,

I got it.

I made the patch because I found out a issue might be related with Gecko.

I'll wait for the refactoring to land first, and check this bug.

Thanks. :)

	Evan Tseng [:evanxd] Assignee
	Comment 16 • 11 years ago

Hi Etienne,

After the patch in Bug 847406 was landed, I tested this bug and I found out that the bug was also resolved.

So we could close this bug.

Thanks. :)