Applications are the lifeblood of any desktop computer, but they are also packed with configuration options, different types of functionality, and other things that could possibly trip you up. This section covers some of the common application-oriented problems in Ubuntu.
When I Click the Close Window Icon, My Program Doesn’t Go Away
If your application seems to hang, and the window won’t go away, keep clicking the X icon. After a few seconds, a dialog box should appear indicating that the program has become inactive and asking if you want to close it.
If this does not work, you can use xkill to stop it. Press Alt-F2, type xkill, and press Enter. Your mouse cursor changes to a small skull and cross-bones. Click the offending application window, and it will finally be banished to that place where naughty applications wallow.
The Upgrade Notification Bubble Keeps Appearing, and I Want It to Stop
When your system detects new upgrades, a small bubble appears in the notification area. To switch this off, right-click the upgrades icon and deselect the Show Notifications option.
Extending the File Manager with Scripts
The file manager driving your Ubuntu desktop is called Nautilus. This comprehensive tool not only is packaged with features out of the box but also has the ability to be extended and improved with the use of special scripts.
A Nautilus script is just an executable shell script (usually using the default Ubuntu bash shell) that is placed in a special scripts directory so that the Nautilus graphical shell can find it. This is a really neat function of Nautilus because it allows you to extend the functionality of the file browser to do just about anything.
Scripts are invoked by selecting a file or group of files and right-clicking with the mouse to bring up a context menu. One of the options of this menu is the Scripts submenu, which allows you to select a script to invoke on the selected files.
Installing a Script
For a script to appear on the Scripts submenu, it must be placed in your scripts directory and be executable. If you place an executable script in your scripts directory, its name will not necessarily appear on the Scripts menu immediately. You first must visit the scripts directory with Nautilus by using the last option in the Scripts menu. Once the directory is visited, Nautilus will know about which scripts you have, and you will be able to use them. The current location of the scripts directory is .GNOME2/Nautilus-scripts in your home directory.
A Sample Nautilus Script
To get you started with Nautilus scripts, we look at an example script. This script pops up a window to ask for a folder location and then loads Nautilus at that location. It’s a simple example, but it shows you how to create a script and run it.
Open your favorite text editor, and type the following code into a new file:
#! /bin/bash # # GoTo script for Nautilus scripts # by ardchoille # This script is released under the GPL # February 20, 2006 # mylocation='zenity --entry --text="Enter the desired location:" --width=300 --title="Nautilus location"' Nautilus --no-desktop --browser $mylocation exit
Save the new file to your Nautilus scripts directory with the filename GoTo. (You can use any filename, really.) Now make the new script executable with this command:
foo@bar:~$ chmod a+x filename
Right-click in Nautilus, and choose Scripts > GoTo, and you will be presented with a dialog that asks for a valid path. After entering the path, click the OK button, and Nautilus will open with the specified path.
I Went to a Web Site in Firefox, and the Macromedia Flash Plug-in Is Missing
If you visit a Web site in Firefox and the Flash plug-in is required, a small bar appears indicating that you need to install an additional plug-in. To do this, click the Install Missing Plug-ins button, and follow the instructions. When the program has downloaded and installed the plug-in, restart Firefox, and you are all set.
Java Is Not Installed on My System
To run a Java application on your system or access a Java Web site in Firefox, you need to install the Java libraries first. To install the Java plug-in, go to Applications > Add/Remove Applications, and search for Java. Install the Sun Java Plug-in. This will also install the Sun Java Runtime libraries.
My E-Mail Doesn’t Work in Evolution
When you first run Evolution, it runs through the setup procedure to configure your e-mail address. To do this successfully, you need to have the following details available:
- Your type of e-mail server (such as POP or IMAP)
- Your mail server name (such as mail.server.com)
- Your mail account’s username and password
- Authentication type (typically password)
- Your outgoing mail server type (typically SMTP)
- Your outgoing mail server name
If you have configured your account and your e-mail doesn’t work, click Edit > Preferences, select the account from the list, and click the Edit button. Ensure that the settings are all correct. If you still cannot connect to your e-mail server, there is either a configuration problem or a network problem.
The latter problem would mean one of two things: Your computer is not connected to the network, or the mail server is not connected to the network. To test this, run the following command in a terminal:
foo@bar:~$ ping mail.server.com
Replace mail.server.com with the name of your mail server. The ping command sends a few pieces of information to the server to see if it responds. If it does respond, a series of lines will be displayed with a response time. If you get this, your network is running fine, and the problem is likely to be a configuration error.
A configuration error can be on either your computer or the mail server itself, with your computer being the far more likely candidate. You should get in touch with the person who runs the mail server and confirm that your settings are correct. Also check that the mail server is running fine. If the configuration error is on the mail server side, there is nothing you can do until it is corrected. In this case, ask the administrator to let you know when it is fixed.
When you find out the correct configuration settings, enter them into Evolution and try again.