1010993 - On a 1.4 flame build logcat is continuously spammed with "connect failed with error 2 (No such file or directory)"

Status: RESOLVED FIXED

(Firefox OS Graveyard :: GonkIntegration, defect)

Description

[Kartikaya Gupta (email:[e-mail])]

Attachment: Backtrace

I built a local Flame build with the latest 1.4 code and when I run adb logcat it's just continuously spewing the following output:

I/I/O     ( 1067): connect failed with error 2 (No such file or directory)

I attached gdb and it appears to be coming from UnixSocketWatcher.cpp; see attached backtrace.

Comment 1

[Kartikaya Gupta (email:[e-mail])]

Attachment: Backtrace of task schedule site

This is the backtrace from where the task is getting scheduled.

Comment 2

[Kartikaya Gupta (email:[e-mail])]

Attachment: Backtrace of task schedule site for other task schedule site

And this is where the task in attachment 8423148 [details] is coming from. Basically there are two tasks that keep running each other forever in an infinite loop.

Comment 3

[Kartikaya Gupta (email:[e-mail])]

Core::IPC may be a more appropriate component.

Comment 4

[Sotaro Ikeda [:sotaro]]

I think it is gonk integration problem. It seems dup Bug 1008000 or Bug 1001327.

I locally applied Bug 1001327 to v1.4 flame and flashed by "./flash.sh". then I did not saw the log.

Comment 5

[Dave Hylands [:dhylands]]

If you push nfcd to /system/bin then it stops spamming.

So we either need to add nfcd to the build, or we need to have b2g not try to connect to nfcd

Comment 6

[Ken Chang[:kenkai]]

Dimi, lets disable NFC in Gecko instead of Gonk for 1.4.

Comment 7

[Dimi Lee [:dimi]]

As discussed in bug 1014485. This issue will be fixed by gonk by adding branch for flame device

Comment 8

[Ken Chang[:kenkai]]

Hi Vincent, It seems that you are working on this bug. If not, please reassign it.

Comment 9

[Faramarz Rashed]

sitting idle for 2wks now.  what's going on?

Comment 10

[Kai-Chih Hu [:khu]]

Thomas Tsai, looks like Vincent is on PTO. Can you help to provide some updates, or should we ask someone else to work on this? This bug has no any update for almost one month. Thank you!

Comment 11

[Vincent Liu[:vliu]]

Since the patch of bug 1014485 has landed, this bug can also be closed. Sorry for late response for this bug.