If you type d 5 (i.e. in the Soar interpreter window), which is the command to run Soar for 5 simulation cycles, called decision cycles, nothing really happens (this is also shown in Trace 1). When Soar is started up, it completely lacks any knowledge and just keeps noting this fact.
If you type just d and don't give a limit of decision cycles to run, Soar will run 1 decision cycle. If you type r -f or run Soar will run until it reaches a halt operation, either generated by a production or by the user. A halt is specified by pressing Control and C together (in the GUI click on the Stop button.
You should find the default rules and load them with the following command:
source simple.soar (or use the Soar Debugger menu or Soar's File menu). (This file is under share/soar/Demos/default/simple.soar)
(You should not need to change folders, but for general guidance see the "Folders and files" section of the notes on running Soar.)
Each asterisk that appears indicates that a rule was loaded successfully. Reset Soar using init-soar. Now when you run Soar ahead, it waits for something to happen (this is also shown in Trace 2).