this happened after an update for youtube plugin and a reboot, although i fail to see the connection
the plugin has been uninstalled since then but nothing changed
under system → system info → network eveything appears as busy ( mac address, ip address, etc)
same goes for summary, where operating system, system uptime and total uptime appear as busy
under myosmc → network , no wireless networks are available, and when i try to configure manually i get an “unhandled exception caught” - i need to access the logs to see exactly what happened, but i used to connect via the wi-fi network in order to get to them before, so i;m still trying to reach them from inside kodi
sorry i don’t yet have physical access to the logs, but here are two pics with errors which i think are relevant to my situation? https://imgur.com/a/mb7FeUL
Mmhhh, only idea I have is that for some reasons the connman wifi configuration got corrupt.
The problem is, you cannot delete the related directory with kodi’s file mgr since you need root-permissions for this.
Adhoc, I suggest
connect the Vero with a LAN cable to your network (no hdmi required)
figure out the new IP the device got on your router and use an appropriate terminal program like putty to ssh login to the Vero, user:osmc, password:osmc
remove the specfic directory: sudo rm -R /var/lib/connman/wifi_*
shutdown the Vero: sudo shutdown -h now … and wait a minute
place the Vero V to the previous location, connect the hdmi cable and power it on
From here the device should have no knowledge anymore about the wifi configuration and you should try to configure the wifi with MyOSMC within the GUI.
Plan B if the network access via cable is not possible for any reasons:
connect a USB keyboard to the Vero
in the GUI select power -> exit
immediately, when the desktop gets black or you see the blue splash screen, hit the escape key on the keyboard (doesn’t hurt to hit it several times); if it does not work at once, retry it several times restarting with power -> exit
from the login prompt, follow the steps already mentioned above
(be careful since the keyboard mapping might be wrong/strange)
revisiting this issue, any idea why this keeps happening? i seem to be needing to follow these steps every couple of days in order to get wireless working
@JimKnopf i also tried to connect to do the sudo rm -r wifi_* command via usb keyboard straight from vero, and although it did delete what it was supposed to, it still did not work
so i reconnected to it with an ethernet cable, tried to re-do the commands by ssh-ing into it - of course, there was nothing else to delete, and after plugging it back in its place with hdmi it worked. so maybe just connecting it via ethernet cable has something to do with it?
@habarnam The suggested method is only intended for the case that the problem occurs once and is not a recurring workaround!
Posting the individual Kodi log file doesn’t really help either; we usually need a log set with kernel logging, as you can read in all the current posts here.
Whatever went wrong with this YouTube update, based on your description I suggest you completely reinstall the device with the latest release from scratch.
You are also welcome to try uploading a current log set here again, in the hope that this will show the reason that something is corrupting your wifi configuration.
But this only make sense if you’re able to connect the box with an ethernet LAN cable to your router WITHOUT a reboot, after the wifi failed. Rebooting the Vero results in the loss of the kernel logs from interest. If you cannot prepare such data collection, better invest your time in a fresh installation of the box. Instructions for a debug log set follow:
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
