Closed Bug 1063917 Opened 11 years ago Closed 11 years ago

cannot stat ‘../../../backup-flame/system/lib/libalsa-intf.so’

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: madrid.crespo, Unassigned)

Details

When I try to build B2G for the Flame device, extract_files.sh shows the following error: cannot stat ‘../../../backup-flame/system/lib/libalsa-intf.so’ This is the standard output: http://paste.ubuntu.com/8268827/ This is the error output: http://paste.ubuntu.com/8268828/ It seems that backup-flame/system/ only has one directory, "b2g". This means that extract_files.sh did not pulled the lib/ folder from the device. They exists in my device, this is what I get when I do "ls /system/": http://paste.ubuntu.com/8268861/ And this is /system/lib/ folder from my Flame: http://paste.ubuntu.com/8268864/ As you can see in the previous log, libalsa-intf.so exists (line 38). My screen is not locked and it never go off, so It is not an issue related to adb. Everytime I check that I have the proper permissions. So, extract_files.sh is failing, maybe it's a bug. One workaround is to pull all those files manually but it is REALLY painful. It would have too much sense. It may happens with other libs too. Would you know if there is any way to fix it?
When using extract-files.sh It seems to do it rightly: http://paste.ubuntu.com/8269031/ In line 941, libalsa-intf.so is pulled. So, why it does not work If I run ./build.sh?
Due to that extract_files.sh worked, I removed /backup-flame/ and tried to execute ./build.sh again. Standard output: http://paste.ubuntu.com/8269136/ Error output: http://paste.ubuntu.com/8269137/ Still can't pull it: cp: cannot stat ‘../../../backup-flame/system/lib/libalsa-intf.so’: No such file or directory
As [:gerard_majax] suggested me, I tried to run adb logcat meanwhile to see If something was killing adb. http://i.imgur.com/n429LXY.png And he was right, something is killing my adb connection: http://i.imgur.com/7HYZVrB.png However, I need to point out that the adb server is still running and it's accesible. Adb server is not being killed. In addition, my screen timeout is disabled and my usb cable is okay )I have replaced in that latest try). Is there any way to check what is killing my adb connection? And this is very interesting, why it does not happen when I run extract_files.sh?
There is no bug here. There may be multiple reasons why your adb connection gets killed, but I don't reproduce this.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
I noticed a similar bug, where 'adb pull' fails after the screen turns off. Maybe that's the problem. Try pulling while the screen is turned on.
Thomas, that is not a bug, that is a feature, It was inteded to block any adb connection if an evil hacker tries to plug an usb to a lonely mobile phone. The screen timeout was disabled in this case. I have noticed that It may only happens with the Flame, I have not seen that problem using the Keon (so far).
You need to log in before you can comment on or make changes to this bug.