Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in or
create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision |
Your text |
Line 100: |
Line 100: |
|
| |
|
| 3 Restart the NetworkManager service <pre>$ /sbin/service NetworkManager restart</pre> | | 3 Restart the NetworkManager service <pre>$ /sbin/service NetworkManager restart</pre> |
|
| |
| ===== Forcing Anaconda to Fail =====
| |
|
| |
| While errors (referred to as tracebacks) during installation are not uncommon during the development cycle. If you need to force the installation program to fail in order to test the SaveToBugzilla functionality, the easiest way is to boot with the following command-line option:
| |
|
| |
| <pre>updates=http://jlaska.fedorapeople.org/traceback.img</pre>
| |
|
| |
| This will cause the installation program to fail after clicking "Next" for the first time. This will present an error dialog which you can use to test [[Anaconda/Features/SaveToBugzilla|SaveToBugzilla]]
| |
|
| |
|
| ==== Exploratory Testing ==== | | ==== Exploratory Testing ==== |