Setting Static IP creates tons of problems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mythbuntu |
Fix Released
|
Critical
|
Unassigned |
Bug Description
When you setup the machine with a static IP after the VNC server and MySQL server (for remote connections) are setup, both the VNC server and MySQL service no longer accept connections.
To reproduce: Install system and setup with VNC service and remote-frontend ability, and restart. After restart, exit the frontend, open the network config and setup for a static IP. Restart again or simply restart the networking to allow proper network connections. From now on, the system no longer accepts VNC connections (because it was listening to the old IP... one thought here: would a change in IP caused via DHCP result in the same problem?) and remote opperations such as MythWeb and a remote front-end no longer work either.
Changed in mythbuntu: | |
importance: | High → Critical |
status: | New → Confirmed |
Changed in mythbuntu: | |
status: | Confirmed → Fix Released |
Additional comment I forgot to include:
When you disable the MySQL service in an attempt to fix the solution, the mysql-server package is set to be removed. Oddly however, after this is completed, there is still a mysql-server package installed, and the backend is still functional, however the option in the MCC is now disabled (as in greyed out). At this point it has sofar been impossible to re-enable the MySQL option in the MCC, and it is unsure as to why the mysql-server package is listed to be removed, yet it is still there after the removal...