Home » Support » Index of All Documentation » Wing IDE Reference Manual » Trouble-shooting Guide »

16.0. Trouble-shooting Failure to Start

If you are having trouble getting Wing to start at all, read through this section for information on diagnosing the problem.

On OS X, Wing requires that you install and launch an X11 Server before starting Wing IDE. If the launcher fails to start X11 or Wing, try starting X11 Server manually and then running wing3.1 from within the Wing IDE application folder (which can be entered using a terminal window in X11). See the OS X How-To for details.

On Windows, the user's temporary directory sometimes becomes full, which prevents Wing from starting. Check whether the directory contains more than 65,534 files. Some versions of Acrobat Reader will leave large numbers of lock files in this directory. These files are named Acrxxxx.tmp. Other applications may do this as well.

On Fedora Core 5 and other Linuxes with SELinux, Wing won't start because permissions are denied on one of the shared libraries needed by it. The solution is to go into bin/2.4/external/pyscintilla2 and issue the following command:

chcon -t texrel_shlib_t _scintilla.so

On Linux, in some cases, Wing will not run with its own private GTK installation because of incompatibilities with the system. To test this, run Wing with the --system-gtk command line option after making sure your Linux system has the GTK packages installed. If this works, you can set the Use System Gtk preference.

Note, however, that there are known problems running system-provided Qt emulation when using the system GTK option. Some of these themes contain bugs that can cause crashing. If you need to use the system GTK and experience crashes, we recommend using a theme other than a Qt theme.

On Linux, if Wing fails to start after the Use System Gtk preference has been set, use the --private-gtk command line option to get Wing running again so that the preference can be turned off.

To rule out problems with a project file or preferences, try renaming your User Settings Directory and restart Wing. If this works, you can copy over files from the renamed directory one at a time to isolate the problem -- or email support at wingware dot com for help.

Under a Windows terminal server, Wing may not be able to set up the environment variables it uses internally and will not start up. In this case, you can get Wing to start with the following commands:

set PYTHONOPTIMIZE=1
set PYTHONHOME=D:\Program Files\WingIDE\bin\PyCore
wing.exe

Alter PYTHONHOME according to the location at which you've installed Wing IDE.

In other cases, refer to Obtaining Diagnostic Output.