1,847
edits
FAQ: Difference between revisions
Jump to navigation
Jump to search
→Common problems: Add "Octave does not start" section.
(Put section "Common problems" more to the top.) |
(→Common problems: Add "Octave does not start" section.) |
||
| Line 76: | Line 76: | ||
=Common problems= | = Common problems = | ||
== Octave does not start == | |||
The following steps have been the solution to several bug reports and help requests. Please try them before asking for further support. If nothing below helps, please give us the following information: | |||
* Operating system: e.g. [https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running '''Windows 10 (version 1909)'''] or '''Ubuntu 20.04''' | |||
* GNU Octave version: e.g. '''Version {{Release}}''' | |||
* Installation method: e.g. '''Downloaded and installed "octave-{{Release}}-w64-installer.exe" from https://www.octave.org/download.html''' | |||
=== MS Windows === | |||
* After upgrade the GUI does not open / shuts down immediately. | |||
** '''Solution:''' Delete the folder {{path|C:\Users\YOUR_USER_NAME\.config\octave}} | |||
* Missing/conflicting files. | |||
** '''Solution:''' Remove/Uninstall all existing Octave versions. Restart the system. Install GNU Octave again. | |||
* Permission errors. | |||
** '''Solution 1:''' Consult your malware detection (a.k.a. AntiVirus) software, if files are blocked. | |||
** '''Solution 2:''' Did you install Octave on a network-drive? Do you have the execution permissions? | |||
==I do not see any output of my script until it has finished?== | ==I do not see any output of my script until it has finished?== | ||
By default Octave is set to pass its screen output through a [https://en.wikipedia.org/wiki/Terminal_pager pager] (usually the default pager is "less") which allows things such as navigating through the output with arrow keys or searching for text or regular expressions within the output. The pager only displays the output after it's finished receiving it, so when it is active you'll not be able to see anything until your script has terminated. To change this behavior temporarily or permanently you may want to use one of the options described [ | By default Octave is set to pass its screen output through a [https://en.wikipedia.org/wiki/Terminal_pager pager] (usually the default pager is "less") which allows things such as navigating through the output with arrow keys or searching for text or regular expressions within the output. The pager only displays the output after it's finished receiving it, so when it is active you'll not be able to see anything until your script has terminated. To change this behavior temporarily or permanently you may want to use one of the options described [https://www.octave.org/doc/interpreter/Paging-Screen-Output.html in the manual]. | ||
==When I try plotting from a script, why am I not seeing anything?== | ==When I try plotting from a script, why am I not seeing anything?== | ||
| Line 88: | Line 106: | ||
A common solution is to put a {{manual|pause}} command at the end of your script. | A common solution is to put a {{manual|pause}} command at the end of your script. | ||
==How do I get sound input or output in Windows?== | ==How do I get sound input or output in MS Windows?== | ||
Sound input from a sound card and output to a sound card is fully supported since Octave 4.0.0 for all platforms. If you have problems with the [ | Sound input from a sound card and output to a sound card is fully supported since Octave 4.0.0 for all platforms. If you have problems with the [https://www.octave.org/doc/interpreter/Audio-Processing.html audio I/O functions] using Octave 4.0.0 or a newer version, please report them on the [http://bugs.octave.org bug tracker]. | ||
==I have problem X using the latest Octave version== | ==I have problem X using the latest Octave version== | ||
| Line 129: | Line 147: | ||
If Octave shows an error message about {{Codeline|invalid call to script .../close.m}} or {{Codeline|invalid use of of script .../close.m in index expression}}, it means that you have created a script called close.m that is overriding the built-in Octave function {{Codeline|close}}. Octave functions and scripts share the samem global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function. | If Octave shows an error message about {{Codeline|invalid call to script .../close.m}} or {{Codeline|invalid use of of script .../close.m in index expression}}, it means that you have created a script called close.m that is overriding the built-in Octave function {{Codeline|close}}. Octave functions and scripts share the samem global namespace. It is best to avoid creating your own scripts or functions that have the same name as an Octave function. | ||
=Licensing issues= | =Licensing issues= | ||