Launching applications in linux

Ubuntu Documentation

Launch applications with the mouse

Move your mouse pointer to the Activities corner at the top left of the screen to show the Activities Overview .

Click the Show Applications icon that is shown at the bottom of the bar on the left-hand side of the screen.

A list of applications is shown. Click the application you want to run, for example, Help.

Launch applications with the keyboard

Open the Activities Overview by pressing the Super key.

Start typing the name of the application you want to launch. Searching for the application begins instantly.

Once the icon of the application is shown and selected, press Enter to launch the application.

More Information

• Getting started with GNOME — New to GNOME? Learn how to get around.

See Also

• Start applications — Launch apps from the Activities overview.

You can choose the displayed language by adding a language suffix to the web address so it ends with e.g. .html.en or .html.de.
If the web address has no language suffix, the preferred language specified in your web browser’s settings is used. For your convenience:
[ Change to English Language | Change to Browser’s Preferred Language ]

The material in this document is available under a free license, see Legal for details.
For information on contributing see the Ubuntu Documentation Team wiki page. To report errors in this documentation, file a bug.

Источник

Launching on Linux

To launch the application on Linux, do one of the following:

• Double-click the required icon on the Desktop.

• Open the Nuke application directory (by default, /usr/local/ Nuke 13.0v5 ) and double-click the required icon.

• Using a terminal, navigate to the Nuke application directory and enter:

• ./ Nuke 13.0 —studio to launch Nuke Studio .

• ./ Nuke 13.0 —nukex to launch NukeX .

• ./ Nuke 13.0 to launch Nuke .

• ./ Nuke 13.0 —indie to launch Nuke Studio in Indie mode.

Note: You can launch Nuke Studio using the —indie argument. See About Nuke Indie for more information.

• ./ Nuke 13.0 —hiero to launch Hiero .

• ./ Nuke 13.0 —player to launch HieroPlayer .

• ./ Nuke 13.0 —nukeassist to launch Nuke Assist .

Note: Nuke Assist licenses are only available as part of the NukeX or Nuke Studio package, and cannot be purchased separately. For more information, see About Nuke Assist.

If you already have a valid license, the interface appears. If you don’t have a license or haven’t installed one yet, proceed to Licensing on Linux.

High DPI Scaling

Nuke supports high definition displays, automatically scaling the interface using the operating system’s scaling settings. On Linux operating systems, scaling is currently set to off by default. Go to the Preferences Behaviors > UI Scaling sub-menu to manually set the scaling mode and scale per display, if required.

You can also enable automatic scaling by setting the QT_AUTO_SCREEN_SCALE_FACTOR environment variable to 1.

Note: Auto-scaling in some multi-screen setups causes the interface to scale incorrectly when moving from lower resolution screens to higher resolution screens. This is possibly a symptom of the way Qt calculates screen scale.
To avoid this issue, we recommend always placing your physical screens with the highest resolution on the far left-hand side of the setup.

Alternatively, you can set the screen scaling factor manually using the QT_SCALE_FACTOR environment variable to force scaling to 1, 1.5, or 2. The recommended scaling factor is 1.5.

In multi-monitor setups, you can manually scale the interface independently by screen using the QT_SCREEN_SCALE_FACTORS variable. Scaling uses the same recommended factors, separated by ; (semicolon). For example, QT_SCREEN_SCALE_FACTORS=»1.5;1″ where the first monitor is higher resolution than the second.

See Environment Variables for more information about setting environment variables.

Command Line Startup Options

If you choose to launch the application from a command line, you can append arguments to the command as follows:

Displays version and copyright information.

Displays the available arguments with examples.

Used with the -t option to run Nuke in terminal mode, but uses a Hiero license instead of the standard Nuke license. You can use this option to render headless Hiero exports in a similar way to headless Nuke renders.

Launch NukeX instead of standard Nuke .

Launch Nuke Studio instead of standard Nuke .

Launch Nuke Assist instead of standard Nuke .

Launch Nuke in Non-Commercial mode. See the notes farther down the page for more information.

Launch the application without displaying the splash screen or startup dialog.

Launch the application without loading any plug-ins, Export presets, and so on.

Nuke Studio only

Sets the location of any logfiles created. For example:

./ Nuke —studio —log-file /Desktop/log.txt

Sets the level of logging produced during operation. For example:

./ Nuke —studio —log-level warning

Log messages are output to screen unless you specify a
—log-file. There are four levels of detail, on a sliding scale from minimal to verbose:

Note: Setting the logging level to verbose can produce large log files when —log-file is specified.

Launch Nuke Studio and apply the specified workspace. Only the workspaces listed in the Workspace menu are valid, but this includes any custom workspaces you have saved as .xml files in your .nuke folder under:

See Loading Gizmos, NDK Plug-ins, and Python and Tcl Scripts for more information on locating your .nuke directory by operating system.

Launch Nuke Studio and open the project specified. The path to the project can be absolute or relative, such as:

Nuke .exe —studio C:\Users\mags\myProject.hrox

Nuke .exe —studio ..\..\mags\myProject.hrox

./Nuke —studio /tmp/myProject.hrox

./Nuke —studio ../../myProject.hrox

Specify the location of media to load on startup. You can import specific files or whole directories:

Nuke .exe —studio C:\Users\mags\Media1.mp4

Nuke .exe —studio C:\Users\mags\

./Nuke —studio /tmp/myfile.mov

./Nuke —studio /tmp/

—script file argv

Run the specified Python script on startup and pass the listed options to the script.

See Command Line Operations for more in-depth information on command line flags.

Nuke Analytics

In an effort to further improve quality and reliability, we ask you to allow us to collect usage statistics from the machines on which you license license Nuke , NukeX , Nuke Studio , Hiero , and HieroPlayer . This usage information also assists our Support team to resolve issues more quickly.

Note: The port number used to communicate with Foundry is 443, the same one used for uploading crash reports.

The first time you start an application, and on every major release, a dialog displays asking for permission for us to collect this information. You can enable or disable collection at any time in the Preferences under Behaviors > Startup.

Note: This information is only collected for interactive sessions. Running applications in terminal mode or under render licenses does not upload data to Foundry.

The following list shows the information we’ll collect, if you give us permission to do so:

Источник

6 Ways to Open a Ubuntu Application

Open your apps the most convenient way for you

In this guide, you will discover a number of different ways to open an application using Ubuntu. Some of them will be obvious and some of them less so.

Not all applications appear in the launcher, and not all of them appear in the Dash. Even if they do appear in the Dash, you might find it easier to open them in other ways.

You might want to make sure Ubuntu is updated so you don’t have any issues opening applications.

Use the Ubuntu Launcher to Open Applications

The Ubuntu Launcher is on the left side of the screen and contains icons for the most commonly used applications.

• You can open one of these applications simply by selecting it.
• Right-clicking​ on an icon often provides other options such as opening a new browser window or opening a new spreadsheet.

Search the Activities to Find an Application

If the application doesn’t appear in the launcher the second quickest way to find an application is to use the GNOME Activities menu.

1. Select Activities in the upper left corner of your screen.
2. Your screen will darken to display the Activities Overview. Here, you’ll see any applications that you have minimized, the other available workspaces, and a search.
3. Type the name of the application you want into the search. GNOME will show you both the apps installed on your system and the ones available for download.

For a more advanced approach of finding a program, or if you can’t find your application in the Activities search, check out our breakdown of how to use the ‘which’ command to find a program.

Browse the Applications Menu to Find an Application

If you just want to see which applications are on your computer or you know the type of application but not its name you can simply browse the GNOME applications menu.

1. To browse, select the Show Applications icon on the launcher or press the Super Key + A.
2. The GNOME applications menu will open up, displaying all the apps you have in your system in alphabetical order. At the bottom, you’ll find the option to toggle between All applications and your Frequent ones.
3. Select an app icon to launch it.

Use the Run Command to Open an Application

If you know the name of the application you can open it quite quickly in the following way:

1. Press Alt+F2 to bring up the run command window.
2. Enter the name of the application. If you enter the name of a correct application then an icon will appear.
3. You can run the application either by clicking on the icon or by pressing Return on the keyboard.

Use the Terminal to Run an Application

You can open an application by using the Linux terminal.

To open a terminal press Ctrl+Alt+T or follow this guide for more suggestions. If you know the program’s name you can simply type it into the terminal window. For example:

Of course, some applications aren’t graphical in nature. One example of this is apt-get, which is a command-line package manager.

When you get used to using apt-get you won’t want to use the graphical software manager anymore.

Use Keyboard Shortcuts to Open Applications

You can set up keyboard shortcuts to open applications with Ubuntu.

1. To do so, open the applications menu, and search for Settings.
2. Open the Settings app.
3. When the window opens, locate and press Devices in the left side menu.
4. Now, the menu will change to show device related options. Choose Keyboard Shortcuts.
5. The main body of the window will display a huge list of current keyboard shortcuts.
6. Scroll to the very bottom of the list, and select the Plus Sign (+) icon.
7. Another smaller window will pop up. Enter a Name for your shortcut. For the Command, you can usually use the name of the app. Sometimes, that’s different. You can search for the path to it with which . For example: which firefox
8. If you don’t know the name of the command at all, you can try:
   ls -lah /usr/bin | grep -i
9. Then, press Set Shortcut to input the key combination. Press the combination of keys that you want to assign the shortcut to on your keyboard. Then, press Add in the upper right of the window to create your shortcut

When the launcher has been created you can set the keyboard shortcut in the same way as the other launchers.

Источник

Launching Your Application (Linux / Unix)

On UNIX, it is possible to run an application either as a desktop application , or as a daemon process in the background. In the case of a daemon, the Wrapper needs to be able to be installed, removed, started, stopped, have its status queried, etc. Depending on whether the application has a GUI or is meant to be run in a command window also determines how it will be run.

• Command Based Script File — Provides a single shell script file which takes a command as a parameter to perform various actions on the Wrapper. Scripts like this are very common on UNIX systems.

• Standalone Binary — It is also possible to run the Wrapper binary directly. In most cases, this is done from a command line by providing additional parameters, but it is also possible to use a default configuration file to avoid this requirement.

Command Based Batch File

Set up the Scripts

The Wrapper is shipped with a shell script ( sh ), which can be used to reliably start and stop any Java application controlled by the Java Service Wrapper.

First, please copy the following shell script into the bin directory of your application (on older Wrapper versions, this file was named ‘sh.script.in’).

Rename the script file to reflect your application name. (Replace «MyApp» with the name of your application throughout this document.)

Script file:

Now open the script into an editor:

There are several variables at the top of the script that can be used to configure how the Wrapper should be launched. Each of them is preceded with a description explaining the usage and possible values. In most cases you can start using the default values, and then think about changing some variables when the need arises.

Since version 3.5.37, the shell script will look for a file with the same basename as the script, located in the same directory, and suffixed with a ‘.shconf’ extension. If such file exists it will be executed, making it possible to override any variable of the shell script. Should you need to customize a variable, it is a good practice to do it in the .shconf file and leave the script file to its original state. By doing so, any upgrade of the Wrapper will be easier as you would only need to replace the script without having to merge your modifications.

Example of replacing the file name:

Note that you will still need to replace the token in the ‘INIT INFO’ section at the top of the main script:

Among the variables of the shell script, you will most likely want to at least edit APP_NAME and APP_LONG_NAME to reflect that the script is being used to launch your application. If APP_NAME is not set it will default to the basename of the shell script, and if APP_LONG_NAME is not set it will default to the value of APP_NAME.

The script assumes that the wrapper executable is placed in the same directory, and that the wrapper.conf file is placed within a conf directory (one level up, ../conf/wrapper.conf ). If you wish to place either of these files somewhere else, the WRAPPER_CMD and WRAPPER_CONF variables will require appropriate modifications.

WARNING

Important! Before proceeding, please make sure that the script, the ‘.shconf’ file and the wrapper executable have their executable bit set.

The shell script ( sh ) will attempt to create a PID file in the /var/run directory. If the user used to launch the Wrapper does not have permission to write to this directory, then this will result in an error. An alternative that will work in most cases is to write the PID file to the same directory where the Wrapper executable is located. To make this change, edit the sh script and change the following line:

Running in a Console

Start the application:

The application can now be run by simply executing bin/myapp console . Because of the way the Wrapper script sets its current directory, it is not necessary to run this script from within the bin directory.

Example of script and shconf file names:

When running using the console command, output from the JVM will be visible in the console.

Stop the application:

The application can be terminated by pressing CTRL-C in the console (command window). This will cause the Wrapper to shut down the application cleanly.

Standard Daemon scripts:

As you will see if you omit a command, the scripts shipped with the Wrapper are fairly standard daemon scripts. They accept console , start , stop , restart , status , and dump commands.

• The start , stop , and restart commands are common to most daemon scripts and are used to control the Wrapper and its application as a daemon process.
• The status command can be used to find out whether or not the Wrapper is currently running.
• The console command will launch the Wrapper in the current shell, making it possible to kill the application with CTRL-C .
• The final command, dump , will send a » kill -3 » signal to the Wrapper, causing the JVM to do a full thread dump.

Running as a Daemon Process

The application can be run as a detached daemon process by executing the script using the start command.

Command and Output Example:

When running using the start command , the output from the JVM will only be visible by viewing the wrapper.log file using tail -f wrapper.log .

Because the application is running as a detached process, it cannot be terminated using CTRL-C and will continue to run even if the console is closed.

To stop the application, rerun the script using the stop command .

Command and Output Example:

Installing the Application to Start on Reboot

Introduced in the Wrapper version 3.4.0, the shell script provides an unified way to install the Wrapper as a Daemon through different platforms (Linux distributions or other Unix systems), allowing your application to automatically start on a system boot or reboot.

Command and Output Example:

During the installation step, the script will automatically detect the OS (Linux distributions or other Unix platforms), then figure out which service management tools (such as Systemd, Upstart, Initd) are present. Whenever several service managements are available, the most advanced one will be chosen. For example, on Linux, systemd is preferred to upstart, which itself is preferred to initd. This default behavior has been introduced in version 3.5.31 and can be changed by editing the following line located near the top of the script:

For example, if you want to force using initd over Systemd or Upstart, you may use the following:

Note that the daemon needs to be reinstalled for the change on SERVICE_MANAGEMENT_TOOL to take effect.

As the script installs itself into your OS, it is necessary to run the install (and uninstall) commands as a root user!

For FreeBSD and MacOSX users, or when using Systemd or Upstart on Linux, the install command will create a default configuration file that describes how the operating system service management will handle the script during the boot process.

It is possible to customize this step just by placing the configuration file into the bin directory:

For example, if the script is called » testwrapper » it would look for » testwrapper.plist » on MacOSX, » testwrapper.install » on FreeBSD or Upstart, and » testwrapper.service » on Systemd.

If you wish to uninstall/remove the Wrapper from the system initialization, run the script (as a root user!) with passing the action parameter » remove «. This will first stop the running Wrapper application and finally clean itself from initialization.

Output Example:

Installing older versions of the Wrapper prior to 3.4.0 has to be done manually. If your platform is not included, please read over those that have been included and adapt as necessary. Please post what you come up with to the wrapper-user@lists.sourceforge.net mailing list and we will be more than happy to include them in the next release.

Standalone Binary

As an alternative to using the scripts shipped with the Java Service Wrapper, you may choose to launch the Wrapper directly.

Wrapper Usage

If the wrapper executable is launched without any parameters or with a » -? «, the following usage output will be displayed.

Output Example:

Run the Wrapper in a Shell

To run the Wrapper in a shell, please use the -c command , followed by the path to the wrapper.conf file. The location of the wrapper.conf file can be absolute or relative. If a relative path is used, the path is always relative to the location of the wrapper file, not the current directory.

Output Example:

Starting the Application as a Daemon Process

To launch the application as a daemon process using the command line, please add wrapper.daemonize=TRUE after the path to the wrapper.conf file. However, using the Shell Script is recommended.

Command Example:

Reference: Launching your application with the Wrapper

Источник

Читайте также:  Подключить гугл диск как сетевой диск windows 10

Оцените статью

Вам также может понравиться

Windows или Linux: Что лучше выбрать?

Есть много причин выбирать между Windows и Linux, но

Файл владелец изменить linux

Команда Chown в Linux Chown Command in Linux (File

Установка шлюза по умолчанию linux

Настройка сети вручную Содержание Краткое описание

Чем разбить диск для linux

ИТ База знаний Курс по Asterisk Полезно — Узнать IP —

• Правообладателям
• Политика конфиденциальности
• Контакты

Command Example: