|
|
161.
|
|
|
This is often due to a faulty CD/DVD disk or drive. It may help to clean the CD/DVD, to burn the CD/DVD at a lower speed, or to clean the CD/DVD drive lens (cleaning kits are often available from electronics suppliers).
|
|
|
Type: error
Description
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubiquity.templates:104001
|
|
|
163.
|
|
|
This is often due to a faulty CD/DVD disk or drive, or a faulty hard disk. It may help to clean the CD/DVD, to burn the CD/DVD at a lower speed, to clean the CD/DVD drive lens (cleaning kits are often available from electronics suppliers), to check whether the hard disk is old and in need of replacement, or to move the system to a cooler environment.
|
|
|
Type: error
Description
This is used when we don't know whether the CD/DVD or the hard disk is at
fault.
Type: select
Description
This is used when there was an md5 mismatch during copying, meaning that
the source file and destination file are not equal.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubiquity.templates:106001 ../ubiquity.templates:107001
|
|
|
189.
|
|
|
This may be due to using an old installer image, or it may be due to a bug in some of the packages listed above. More details may be found in /var/log/syslog. The installer will try to continue anyway, but may fail at a later point, and will not be able to install or remove other packages (possibly including itself) from the installed system. You should first look for newer versions of your installer image, or failing that report the problem to your distributor.
|
|
|
Type: error
Description
Type: error
Description
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubiquity.templates:130001 ../ubiquity.templates:131001
|
|
|
196.
|
|
|
The installer needs to commit changes to partition tables, but cannot do so because partitions on the following mount points could not be unmounted:
|
|
|
Type: boolean
Description
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubiquity.templates:143001
|
|
|
212.
|
|
|
This will set up a system similar to a Primary Backend, however it will be configured to connect to an existing backend on the network.
|
|
|
Type: text
Description
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubiquity-frontend-mythbuntu.templates:11001
|
|
|
214.
|
|
|
A frontend only machine's main function is to receive media content from the backend and distribute it. This configuration requires an existing backend on the network.
|
|
|
Type: text
Description
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubiquity-frontend-mythbuntu.templates:13001
|
|
|
226.
|
|
|
The final steps of the installation require setting up your guide data and configuring the backend for the first time.
|
|
|
Type: text
Description
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubiquity-frontend-mythbuntu.templates:25001
|
|
|
227.
|
|
|
Click to open the Schedules Direct website
|
|
|
Type: text
Description
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubiquity-frontend-mythbuntu.templates:26001
|
|
|
228.
|
|
|
Users in North America will need to setup an account with Schedules Direct (SD). SD provides guide data for a nominal fee. Without SD, North American users may lose many of the scheduling features in MythTV.
|
|
|
Type: text
Description
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubiquity-frontend-mythbuntu.templates:27001
|
|
|
230.
|
|
|
After setting up your guide data source, you will need to launch MythTV-Setup to run the backend configuration for the first time. You will need to configure the first four sections, being sure to provide your guide data during the third.
|
|
|
Type: text
Description
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../ubiquity-frontend-mythbuntu.templates:29001
|
