Template:Software Side Effects Fixes: Difference between revisions
No edit summary |
(as tested on 13.2.6, dconf has a binary copy of gsettings, the gconf is a shadow for prior versions) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
Stop the display manager. The remainder of these fixes must be typed into a virtual console, or a serial port. |
|||
sudo service olpc-dm stop |
|||
Delete the ".olpc-configured" files which tell olpc-configure it does not have to run again. This allows some of the files deleted below to be checked for and replaced. |
Delete the ".olpc-configured" files which tell olpc-configure it does not have to run again. This allows some of the files deleted below to be checked for and replaced. |
||
sudo rm - |
sudo rm -vf /.olpc-configured |
||
rm - |
rm -vf /home/olpc/.olpc-configured |
||
Destroy any saved network connections. Otherwise the cloned laptop cannot connect to the networks the original laptop used. |
Destroy any saved network connections. Otherwise the cloned laptop cannot connect to the networks the original laptop used. |
||
sudo rm - |
sudo rm -rvf /etc/NetworkManager/system-connections/* |
||
If SSH was enabled, destroy the SSH host key. Otherwise other systems in your network may report problems connecting to the laptops over SSH. |
If SSH was enabled, destroy the SSH host key. Otherwise other systems in your network may report problems connecting to the laptops over SSH. |
||
sudo rm - |
sudo rm -vf /etc/ssh/ssh_host_rsa_key{,.pub} |
||
Destroy the Sugar settings, forcing a first boot name prompt. Otherwise the cloned laptops won't be able to collaborate using activities, or the wrong names will be shown in Chat, |
Destroy the Sugar journal and settings, forcing a first boot name prompt. Otherwise the cloned laptops won't be able to collaborate using activities, or the wrong names will be shown in Chat, |
||
rm - |
rm -vrf /home/olpc/.sugar /home/olpc/.config/{g,d}conf /home/olpc/.local/share/telepathy |
||
Destroy the developer key request file. Otherwise the cloned laptops will apply for developer keys using the original laptop serial number and UUID. |
Destroy the developer key request file. Otherwise the cloned laptops will apply for developer keys using the original laptop serial number and UUID. |
||
rm - |
rm -vrf /home/.devkey.html |
||
If the laptop was ever registered with a school server, or you are not sure, clear the registration by destroying the GConf settings: |
|||
rm -rf /home/olpc/.config/gconf* |
|||
Destroy any saved volume settings, forcing defaults. Otherwise the cloned laptop may start with silent speakers or microphone. |
Destroy any saved volume settings, forcing defaults. Otherwise the cloned laptop may start with silent speakers or microphone. |
||
sudo rm - |
sudo rm -vf /etc/alsa/asound.state |
||
Immediately shutdown |
Immediately shutdown, to avoid asound.state being saved: |
||
sync && sudo poweroff -f |
sync && sudo poweroff -f |
||
Latest revision as of 03:32, 24 November 2015
Stop the display manager. The remainder of these fixes must be typed into a virtual console, or a serial port.
sudo service olpc-dm stop
Delete the ".olpc-configured" files which tell olpc-configure it does not have to run again. This allows some of the files deleted below to be checked for and replaced.
sudo rm -vf /.olpc-configured rm -vf /home/olpc/.olpc-configured
Destroy any saved network connections. Otherwise the cloned laptop cannot connect to the networks the original laptop used.
sudo rm -rvf /etc/NetworkManager/system-connections/*
If SSH was enabled, destroy the SSH host key. Otherwise other systems in your network may report problems connecting to the laptops over SSH.
sudo rm -vf /etc/ssh/ssh_host_rsa_key{,.pub}
Destroy the Sugar journal and settings, forcing a first boot name prompt. Otherwise the cloned laptops won't be able to collaborate using activities, or the wrong names will be shown in Chat,
rm -vrf /home/olpc/.sugar /home/olpc/.config/{g,d}conf /home/olpc/.local/share/telepathy
Destroy the developer key request file. Otherwise the cloned laptops will apply for developer keys using the original laptop serial number and UUID.
rm -vrf /home/.devkey.html
Destroy any saved volume settings, forcing defaults. Otherwise the cloned laptop may start with silent speakers or microphone.
sudo rm -vf /etc/alsa/asound.state
Immediately shutdown, to avoid asound.state being saved:
sync && sudo poweroff -f