Closed
Bug 1149676
Opened 9 years ago
Closed 6 years ago
WiFi debugging not working on my Linux distribution
Categories
(Firefox OS Graveyard :: Developer Tools, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Jamie_, Unassigned)
References
(Blocks 1 open bug)
Details
On my linux distribution it seems that via wifi is not working. I am running on Ubuntu 14.10 64 bit with the Gnome display manager, and gnome 3 de and also running in the gnome repositories added in to the computer. I have a access to all of the standard Ubuntu repositories still. I have disabled the fire wall and checked the status of my ports using nmap and it says that all of 1000 ports checked are closed.
|
Reporter | |
Updated•9 years ago
|
Flags: needinfo?(jryans)
|
|
Reporter | |
Comment 1•9 years ago
|
||
I am on firefox nightly 40.0a1
Blocks: 1142741
Flags: needinfo?(jryans)
Summary: via wifi debugging not working on my Linux distribution → WiFi debugging not working on my Linux distribution
Try the following: 1. Start Firefox 2. Open WebIDE 3. Click the runtime button to show the runtime list 4. Run "netstat -lnup" from a terminal Attach the output here or link to a pastebin.
Flags: needinfo?(charja13)
|
|
Reporter | |
Comment 3•9 years ago
|
||
udp 0 0 127.0.1.1:53 0.0.0.0:* - udp 0 0 0.0.0.0:68 0.0.0.0:* - udp 0 0 192.168.1.2:123 0.0.0.0:* - udp 0 0 127.0.0.1:123 0.0.0.0:* - udp 0 0 0.0.0.0:123 0.0.0.0:* - udp 0 0 0.0.0.0:33869 0.0.0.0:* - udp 0 0 0.0.0.0:17500 0.0.0.0:* 3193/dropbox udp 0 0 0.0.0.0:5353 0.0.0.0:* - udp 0 0 127.0.0.1:50484 0.0.0.0:* 3121/skype udp 0 0 0.0.0.0:50625 0.0.0.0:* 22788/firefox-bin udp 0 0 0.0.0.0:52883 0.0.0.0:* - udp 0 0 0.0.0.0:26485 0.0.0.0:* 3121/skype udp6 0 0 fe80::5a94:6bff:fe8:123 :::* - udp6 0 0 ::1:123 :::* - udp6 0 0 :::123 :::* - udp6 0 0 :::36009 :::* - udp6 0 0 :::5353 :::* - udp6 0 0 :::11724 :::* -
Flags: needinfo?(charja13)
Hmm, okay. So, Firefox appears to listening on 50625 as expected. However, it seems to not receive a reply from the device. Is your Firefox OS device rooted? We could try some tests there if so.
Flags: needinfo?(charja13)
|
|
Reporter | |
Comment 5•9 years ago
|
||
no.... I can add a different boot image that is root if there is one I can get a hold of. Also would like to back up my stuff before doing so if possible.
Flags: needinfo?(charja13) → needinfo?(jryans)
|
|
Reporter | |
Comment 6•9 years ago
|
||
okay I know have a rooted image on it... what should i check for now jryans
So, let's enable the discovery log *on device* by setting the same pref you set in Firefox desktop. However, doing this with Firefox OS is a bit harder: 1. Connect with WebIDE 2. Open Device Preferences in WebIDE runtime menu * If this option is not available, you need "full DevTools access"[1] * Go to Runtime Info in WebIDE and "request higher privileges" 3. Look for "devtools.discovery.log" and enable it 4. Restart the device 5. With a USB cable connected, run "adb logcat | grep Gecko" in a terminal 6. Open WebIDE's runtime menu to trigger discovery Capture the terminal logs. Don't just paste them as a comment, as they could be somewhat long. I would suggest attaching to the bug. [1]: https://developer.mozilla.org/en-US/docs/Tools/WebIDE#Unrestricted_app_debugging_%28including_certified_apps.2C_main_process.2C_etc.%29
Flags: needinfo?(jryans)
|
|
Reporter | |
Comment 8•9 years ago
|
||
I/Gecko ( 208): Sending message to frozen Nuwa I/Gecko ( 208): UpdatePrompt: Forcing update check I/Gecko ( 208): *** AUS:SVC Checker: checkForUpdates, force: true I/Gecko ( 208): *** AUS:SVC getLocale - getting locale from file: resource://app/update.locale, locale: en-US I/Gecko ( 208): *** AUS:SVC Checker:getUpdateURL - update URL: https://aus4.mozilla.org/update/3/B2G/40.0a1/20150331010203/flame/en-US/nightly/Boot2Gecko%203.0.0.0-prerelease%20(SDK%2019)/default/default/update.xml?force=1 I/Gecko ( 208): *** AUS:SVC gCanCheckForUpdates - able to check for updates I/Gecko ( 208): *** AUS:SVC Checker:checkForUpdates - sending request to: https://aus4.mozilla.org/update/3/B2G/40.0a1/20150331010203/flame/en-US/nightly/Boot2Gecko%203.0.0.0-prerelease%20(SDK%2019)/default/default/update.xml?force=1 I/GeckoDump( 208): XXX FIXME : Got a mozContentEvent: force-update-check I/Gecko ( 208): *** AUS:SVC Checker:onError - request.status: 2152398864 I/Gecko ( 208): *** AUS:SVC getStatusTextFromCode - transfer error: Network is offline (go online), code: 2152398864 I/Gecko ( 208): UpdatePrompt: Setting gecko.updateStatus: retry-when-online I/Gecko ( 208): *** AUS:SVC Creating UpdateService I/Gecko ( 208): *** AUS:SVC UpdateService:onError - error during background update. error code: 111, status text: Network is offline (go online) I/Gecko ( 208): *** AUS:SVC UpdateService:_registerOnlineObserver - waiting for the network to be online, then forcing another check I/Gecko ( 1138): ###################################### forms.js loaded I/Gecko ( 1138): ############################### browserElementPanning.js loaded I/Gecko ( 1138): ######################## BrowserElementChildPreload.js loaded I/GeckoDump( 208): XXX FIXME : Got a mozContentEvent: remote-debugger-prompt not that long
Right, it does not seem like the device heard anything. Since you had to change to boot images, can you ensure: * The device is still on the same WiFi network as computer * DevTools via WiFi is still enabled When toggling DevTools via WiFi via logcat connected, you should get a message when it enables.
Flags: needinfo?(jryans)
|
|
Reporter | |
Comment 11•9 years ago
|
||
Yes, there is only one wifi network i have access to and i have check on the log cat and yes it is enabling. I/GeckoDump( 208): AdbController: Started WiFi debugger on 60204 I/Gecko ( 208): console.log: DISCOVERY: ADDING LOCAL SERVICE I/Gecko ( 208): at log (resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/discovery/discovery.js:69:undefined) I/Gecko ( 208): console.log: DISCOVERY: LISTEN FOR SCAN I/Gecko ( 208): at log (resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/discovery/discovery.js:69:undefined)
|
|
Reporter | |
Comment 13•9 years ago
|
||
i dont know if this seems odd... but it is listening on 50625 but in the web console it is says 50624
I dont know if those two are unrelated but due to the similarity and the use i thought it might...
"DISCOVERY: Send to 50624:
{
"device": "12592",
"services": {}
}"Right, two ports are actually used, 50624 and 50625, so that's expected. So far, it seems the device never hears anything from the computer, but the computer claims to have sent something. Are you able to try out this set up on a different WiFi network, such as a coffee shop or friend's house? Perhaps something about the WiFi network or router used is interfering?
Flags: needinfo?(jryans)
|
|
Reporter | |
Comment 15•9 years ago
|
||
do you think it would work to monitor the network with something like aircrack or something to see if the network is actually transferring it at all... I could monitor from there using wire shark... do you think that method will work to see if its getting caught up anywhere or not allowed to pass.
Flags: needinfo?(jryans)
|
|
Reporter | |
Comment 16•9 years ago
|
||
I dont have access at this time to another wifi network
At the moment, I can't think of more tests to perform. My best guess for now is that the router is blocking the packets from being transferred. I'll update the bug if I think of more ideas.
Flags: needinfo?(jryans)
|
||
Comment 18•9 years ago
|
||
I have the same problem. System is gentoo x64, firefox 39.0a2, device is Flame with nightly build. I have tried monitoring the phone as you suggested. Firefox does indeed listen on 50625, but I can not see any connection attempts in Flame's logs. I have adb addon helper logging enabled in firefox. There is an output when the phone is connected via cable, but nothing when it is disconnected and I click "Select Runtime" (which should trigger the discovery if I understand correctly). Maybe this can help you solve the issue.
|
|
||
Comment 19•9 years ago
|
||
I can confirm that this does NOT happen on windows 7 using the same configuration - firefox 39.0a2 and flame with the same build. Everything works there flawlessly. Therefore, I assume the bug is in (implementation of?) adb helper.
|
||
Comment 20•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•