How to debug an error in VLC for Chrome OS - google-chrome-app

I have a chrome app that mounts a filesystem in Chrome OS.
When I try to run a movie from that drive, I get the following error from VLC:
Playback error
VLC encountered an error with this media.
Please try refreshing the media library.
The location file:///data/data/org.chromium.arc/external/[Some_ID]/[File_Name] cannot be played.
I tried enabling logcat in the inspection window with:
plugin.shell('logcat');
but it didn't catch any errors.
How can I debug why this generic error has occurred in VLC?
Thanks!
UPDATE:
I can see the file using the following command:
plugin.shell("ls -l '/data/data/org.chromium.arc/external/[Some_ID]/[File_Name]'");
I get the following answer:
-------- 0 root gr0 0 Jan 01 02:00 /data/data/org.chromium.arc/external/[Some_ID]/[File_Name]

Related

unexpected system image feature string, emulator might not function correctly, please try updating the emulator

I Created an Emulator on Windows 10 without Installing Android Studio. But when I try to launch it, I get this error. Please help me. How can I fix this..?
C:\Users\This pc\AppData\Local\android\emulator>emulator -avd nexus
INFO | Android emulator version 31.2.10.0 (build_id 8420304) (CL:N/A)
WARNING | Crash service did not start
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
WARNING | cannot add library vulkan-1.dll: failed
WARNING | cannot add library vulkan-1.dll: failed
INFO | added library C:\Users\This pc\AppData\Local\android\emulator\lib64\vulkan\vulkan-1.dll
INFO | configAndStartRenderer: setting vsync to 60 hz
ERROR | Failed to open /qemu.conf, err: 2
Incompatible HAX module version 3,requires minimum version 4
No accelerator found.
C:\Users\This pc\AppData\Local\android\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: failed to initialize HAX: Invalid argument
Try this page: https://developer.android.com/studio/run/emulator-acceleration.
Judging from the line in your error "Incompatible HAX module..." you need an update.
In "Windows Features" I have Hyper-V unchecked, Virtual Machine Platform and Windows Hypervisor Platform checked.
Here's similar output from my machine where I have a working emulator set to x86 and api 30. My problem is getting my app running on api 31+ and 86_64.
INFO | configAndStartRenderer: setting vsync to 60 hz
INFO | added library vulkan-1.dll
ERROR | Failed to open /qemu.conf, err: 2
WHPX on Windows 10.0.22000 detected.
Windows Hypervisor Platform accelerator is operational

Android Emulator not running on M1

I cannot start the android emulator V30.9.4
I got this error message:
INFO | Android emulator version 30.9.4.0 (build_id 7759208) (CL:N/A)
WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
WARNING | cannot add library /Users/-/Library/Android/sdkPreview/emulator/qemu/darwin-aarch64/lib64/vulkan/libvulkan.dylib: failed
WARNING | cannot add library /Users/-/Library/Android/sdkPreview/emulator/lib64/vulkan/libvulkan.dylib: failed
ERROR | EglOsGlLibrary: Could not open GL library libGLESv2.dylib [dlopen(libGLESv2.dylib, 0x0002): tried: '/Users/-/Library/Android/sdkPreview/emulator/lib64/qt/lib/libGLESv2.dylib' (no such file), '/Users/-/Library/Android/sdkPreview/emulator/lib64/gles_swiftshader/libGLESv2.dylib' (code signature]
ERROR | EglOsEglDispatcher: Could not open EGL library libEGL.dylib [dlopen(libEGL.dylib, 0x0002): tried: '/Users/-/Library/Android/sdkPreview/emulator/lib64/qt/lib/libEGL.dylib' (no such file), '/Users/-/Library/Android/sdkPreview/emulator/lib64/gles_swiftshader/libEGL.dylib' (code signature in <5C3A]
It works with sudo privilege.
Try to use the host system's OpenGL driver:
cd $ANDROID_SDK_ROOT/emulator
./emulator -avd <Pixel_4_API_29> -gpu host
Then go to Emulator Settings -> Settings -> Advanced.
Select OpenGL ES renderer "Autodetect based on host".
Save & restart.
P.S. Get list of avds:
./emulator -list-avds
https://developer.android.com/studio/run/emulator-acceleration#command-gpu

Unity WebGL build error in NON-development mode only

I'm using Unity 2017.3.03f free personal edition, I've an application in unity that works normally in desktop and android platforms. However, When it's built for WebGL release (unchecked "development build" option") it gives this error in browser during loading splash screen:
> An error occurred running the Unity content on this page. See your browser JavaScript console for more info. The error was:
uncaught exception: abort(-1) at jsStackTrace (webgl-11B.asm.framework.unityweb:2:27460)
stackTrace (webgl-11B.asm.framework.unityweb:2:27631)
abort (webgl-11B.asm.framework.unityweb:4:33732)
_il2cpp_gc_disable (webgl-11B.asm.framework.unityweb:2:204426)
scripting_gc_disable() [vNc] (webgl-11B.asm.code.unityweb:10:1)
_main [eNc] (webgl-11B.asm.code.unityweb:10:1)
callMain (webgl-11B.asm.framework.unityweb:4:32097)
doRun (webgl-11B.asm.framework.unityweb:4:32800)
_String_Join_m2050845953 [run] (webgl-11B.asm.framework.unityweb:4:32986)
runCaller (webgl-11B.asm.framework.unityweb:4:31614)
removeRunDependency (webgl-11B.asm.framework.unityweb:2:34407)
processDataJob#file:.../Build/UnityLoader.js:1:17079
I've tried to enable the development option and apply the steps of this article:
https://community.gamedev.tv/t/webgl-debugging/54948
to enable debugging symbols and disable stripping code engine to see the errors in browser console. But the Development version works without error, but when I return to release build "unchecking the development option" again, the same error appears.
and the log of browser console contains the following message:
> IndexedDB is not available. Data will not persist in cache and PlayerPrefs will not be saved.
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:124
unreachable code after return statement[Learn More]
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:4519
missing function: il2cpp_gc_disable
UnityLoader.js:1:8039
-1
UnityLoader.js:1:8002
-1
UnityLoader.js:1:8039
Use of the motion sensor is deprecated.
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:54097
Use of the orientation sensor is deprecated.
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:54097
uncaught exception: abort(-1) at jsStackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27460
stackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27631
abort#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:33732
_il2cpp_gc_disable#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:204426
vNc#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:10:1
eNc#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:10:1
callMain#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:32097
doRun#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:32800
run#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:32986
runCaller#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:31614
removeRunDependency#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:34407
processDataJob.../UnityLoader.js:1:17079
If this abort() is unexpected, build with -s ASSERTIONS=1 which can give more information.
154
UnityLoader.js:1:8002
154
UnityLoader.js:1:8039
uncaught exception: abort(154) at jsStackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27460
stackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27631
abort#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:33732
Vxq#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:32:1
y7c#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:23:1
ynq#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:32:1
handlerFunc#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:57395
jsEventHandler#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:53935
why does this error happen? is it because of using unity free edition, or because the application reads some text file from Resources folder at loading?
thanks in advance.

Metadata.framework error while running root in jupyter

I am running a code in jupyter notebook (here is the code for reference):
import ROOT as root
f = root.TFile("160721_0828.root")
for event in f.tree.events:
print (1)
It should be a simple code, looping through a file. But when I run it, the kernel crushes and I have to restart everything. I also get in terminal many errors of this kind:
2016-08-08 18:25:20.439 atos[99872:272f] Metadata.framework [Error]: couldn't get the client port
0x0000000100000cc4 in start (in python) + 52
before the program crushes. I am using a Mac, version 10.9.5. What could be the cause?
Perhaps your Spotlight indexing is disabled and necessary metadata is inaccessible.
Try to turn Spotlight indexing On and the error message:
"Metadata.framework [Error]: couldn't get the client port"
disappears and kernel will be stable.

Should I worry about DDMS console log messages "Can't bind to local nnnn for debugger"?

I'm new to Android programming (and Eclipse IDE and Android emulator). I've got Hello World and some of Notepad working, but I'm still constantly getting quite a few DDMS console log messages (shown below) about not being able to bind locals for debugger.
[2010-05-29 21:03:16 - ddms] Can't bind to local 8601 for debugger
[2010-05-29 21:05:26 - Device] Failed to delete temporary package: device (emulator-5556) request rejected: device not found
[2010-05-29 21:06:47 - ddms] Can't bind to local 8600 for debugger
[2010-05-29 21:07:05 - ddms] Can't bind to local 8601 for debugger
[2010-05-29 21:07:05 - ddms] Can't bind to local 8602 for debugger
And so on. Is this a problem? Can I get rid of these messages somehow?
In Eclipse, goto
1) Windows->Preference
2) Expand Android menu in the side of the Preference Window.
3) Now select DDMS from it.
4) Then Set the Base local debugger port to "8601" and enable "Use ADBHOST" checkbox and the ABDHOST value should be "127.0.0.1".
5) Click apply and ok.
6) Now you have to restart your ADB, for this you have to login as root user(Assuming linux user) and navigate to Platfrom tools folder of your Android SDK. Then execute,
./adb kill-server
./adb start-server
You will be able to see the message "Daemon started Successfully" . If not repeat step 6 once again until you see the success message.
You can get rid of the the messages by adding following to your hosts file:
127.0.0.1 localhost
ps. hosts file can be found from c:\windows\system32\drivers\etc\hosts
or if you are on linux /etc/hosts
In my situation the problem has been solved by a uninstalling all Java 7. The debugger is now working again!