Differences between revisions 1 and 10 (spanning 9 versions)

nrec crashes right after starting it

Open a terminal window.
Click inside this window, type "nr" and press Enter. Carefully check, if there are any error messages in the output by scrolling up and down in the terminal window.
If an error with the message "Wrong subdevice type." appears, it is very likely, that the nrec configuration file has been corrupted. To resolve this issue, you first have to become super-user (Administrator) by typing
```
  sux
```
and pressing Enter in the terminal window (pressing Enter is now always necessary after typing). Type in the administrator password. Now the input prompt should display a "#" sign at the rightmost end. Show all the recent configuration file backups by typing
```
  ls -lart .nrec*
```
Choose one from a point of time (yesterday?), when nrec was correctly starting up (you may identify it by the file size) and copy it to the current configuration file:
```
  cp .nrec2008-11-11-11-11-11-111.cfg .nrec.cfg
```
That's all. Now you can close the terminal window and try to start nrec again.

-  ⇤ ← Revision 1 as of 2009-01-14 07:59:58 → 
  Size: 183
  Editor: hih-kn-2301-01
  Comment:
+   ← Revision 10 as of 2015-12-11 09:16:12 → ⇥
  Size: 1207
  Editor: FriedemannBunjes
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 7:
-... to be continued ...
+ * Open a terminal window. 
 * Click inside this window, type "nr" and press Enter. Carefully check, if there are any error messages in the output by scrolling up and down in the terminal window.
 * If an error with the message "Wrong subdevice type." appears, it is very likely, that the nrec configuration file has been corrupted. To resolve this issue, you first have to become super-user (Administrator) by typing
 {{{
  sux
 }}}
 and pressing Enter in the terminal window (pressing Enter is now always necessary after typing). Type in the administrator password. Now the input prompt should display a "#" sign at the rightmost end.

 Show all the recent configuration file backups by typing
 {{{
  ls -lart .nrec*
 }}}
 Choose one from a point of time (yesterday?), when nrec was correctly starting up (you may identify it by the file size) and copy it to the current configuration file:
 {{{
  cp .nrec2008-11-11-11-11-11-111.cfg .nrec.cfg
 }}}
 That's all. Now you can close the terminal window and try to start nrec again.