SliTaz GNU/Linux official and community documentation wiki.
.png
Translations of this page:

This is an old revision of the document!


Frequently Asked Questions

Listed here are the most frequently asked questions from the user forums. Please check here to see if your problem has been fixed before starting a new forum thread.

These are organised into per-scenario groups - from system-level through to the desktop. Within each, a symptom describes a give-away identification of the problem; a widely-working solution is then outlined.


General Problems

Package or Software Problems

Cannot Login to Desktop

Symptoms
  • Slim, the SliTaz Login Manager, fails with the message:
 failed to execute login command 
Explanation

This is caused when files in the user's /home directory are not properly configured. The following files must exist, this can be verified with the ls -la command:

  • .Xdefaults
  • .xinitrc
  • something else?
Solution

You should copy the default files from the template located in the /etc/skel directory. This happens automatically when a new user is created with the SliTaz Control Box, but not when using the command-line utilities. Occasionally users experience these files being removed or modified/broken.

Switch to the root (super) user:

 su root 

Change to the affected users /home directory:

 cd /home/USERNAME 

Set the shell options to allow the dot (.) to be included in file names:

 shopt -s dotglob 

Copy all files, recursively:

 cp -r /etc/skel/* /home/USERNAME 

Change ownership of all files and directories in the user's home to that of the affected user:

 chown -R USERNAME:USERGROUP /home/USERNAME/* 

Restore the shell options:

 shopt -u dotglob 

The essential files should now be restored!


A Program Doesn't Run

A Program Quits Unexpectedly

Symptoms
  • Nothing happens when an application is run from the Launch menu.
  • An application quits without warning.
Explanation

One or more of problems may have caused this. Run the program in a Terminal to see any error messages the program may deliver.

Solution

Launch a Terminal (command line) and run the application by typing in its name. See the following FAQs on solving common problems.


An Application Cannot Find Libraries/Files

Symptoms
  • When run in a Terminal, an application fails with the message:
 [name]: error while loading shared libraries: [library].so.*: cannot open shared object file: No such file or directory
Explanation

The program is missing some files it needs to run. This is caused by the package information missing a reference to another, or not including the file.

Solution

Check if the file required is available in another package. Use the package manager (TazPkg) to search for the file:

  • start the package manager
  • 'Recharge' the package lists, if necessary
  • click the “Search” tab
  • in the Search box, enter the file-name ([library].so) and click “Files”
  • install the package (pick that with the closest name if there is more than one) by double-clicking the entry and clicking Install Package

Alternatively, run the following command from a terminal:

tazpkg search-file //[library]//.so

… and install the appropriate package with:

 tazpkg get-install [package] 

If no packages are given, report this as a bug over at the Labs as it needs to be included, or the dependency removed during the build.



Page Review Section
Quality Low
Review Major Updates FIXME
Priority High
Problems add a forum post link
OR add a lab issue tracker link
How to Improve Suggest briefly, e.g.,
Add link
Add new rows like this ;-)



 
en/guides/faq.1273687733.txt.gz · Last modified: 2010/07/08 17:16 (external edit)