Template:Software Side Effects Fixes

From OLPC
Revision as of 01:21, 24 November 2015 by Quozl (talk | contribs)
Jump to navigation Jump to search

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/gconf/desktop/sugar /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

If the laptop was ever registered with a school server, or you are not sure, clear the registration by destroying all the GConf settings:

rm -vrf /home/olpc/.config/gconf*

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