Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:guides:faq [2010/05/12 20:09] jozee |
en:guides:faq [2019/01/30 15:37] hgt Shutdown via slim inserted |
||
---|---|---|---|
Line 5: | Line 5: | ||
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. | 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 ===== | ||
+ | * [[faq-login|Log-In Problems]] | ||
+ | * [[faq-slim|Shutdown via slim]] | ||
+ | * [[faq-terminal|Terminals (Copy/Paste etc.)]] | ||
- | ===== General Problems ===== | + | \\ |
- | * [[faq-login|Cannot Login to Desktop]] | + | |
- | * | + | ===== Package or Software ===== |
- | \ | + | |
- | ===== Package or Software Problems ===== | + | |
* [[faq-dependency| An Application Cannot Find Libraries/Files ]] | * [[faq-dependency| An Application Cannot Find Libraries/Files ]] | ||
- | * | + | * [[faq-programfailstorun | A Program Doesn't Run or Quits Unexpectedly ]] |
- | + | * [[faq-pkgconv | Can I install a package on SliTaz from another distribution? ]] | |
- | \ | + | |
- | === Cannot Login to Desktop === | + | |
- | + | ||
- | == Symptoms == | + | |
- | + | ||
- | * Slim, the SliTaz Login Manager, fails with the message: | + | |
- | <code> failed to execute login command </code> | + | |
- | + | ||
- | == 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: | + | |
- | <code> su root </code> | + | |
- | Change to the affected users /home directory: | + | |
- | <code> cd /home/USERNAME </code> | + | |
- | Set the shell options to allow the dot (.) to be included in file names: | + | |
- | <code> shopt -s dotglob </code> | + | |
- | Copy all files, recursively: | + | |
- | <code> cp -r /etc/skel/* /home/USERNAME </code> | + | |
- | Change ownership of all files and directories in the user's home to that of the affected user: | + | |
- | <code> chown -R USERNAME:USERGROUP /home/USERNAME/* </code> | + | |
- | Restore the shell options: | + | |
- | <code> shopt -u dotglob </code> | + | |
- | 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. | + | |
- | ---- | + | \\ |
+ | ===== Hardware ===== | ||
+ | * [[faq-mouse|Mouse]] | ||
- | === An Application Cannot Find Libraries/Files === | + | \\ |
- | == Symptoms == | + | ===== Questions Still Unanswered? ===== |
- | * When run in a Terminal, an application fails with the message: | + | No problem! We are happy to hear your question over at our [[http://forum.slitaz.org/|Support Forum]] -- or even the [[http://www.slitaz.org/en/mailing-list.html|Mailing List]] if it is a more lengthy discussion -- once you have looked through our [[http://doc.slitaz.org/en:start|documentation]]! |
- | <code> [name]: error while loading shared libraries: [library].so.*: cannot open shared object file: No such file or directory</code> | + | |
- | == Explanation == | + | Answering questions takes time however, to answer them well slightly longer. This time could be better spent for other necessary things, like improving SliTaz or writing documentation. |
- | 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. | + | ** Your first post should include the following things: ** |
- | == Solution == | + | * detailed information about your hardware |
+ | * e.g the manufacturer and model of your computer, motherboard or (even better) detailed chip information. The latter can be found by running the following command and uploading the generated //SysInfo.txt// file: | ||
+ | |||
+ | <code> | ||
+ | echo '=== PCI Devices: ===' >> SysInfo.txt && lspci >> SysInfo.txt && echo '=== USB Devices: ===' \ | ||
+ | >> SysInfo.txt && lsusb >> SysInfo.txt && echo '=== Kernel Modules: ===' >> SysInfo.txt && lsmod >> SysInfo.txt | ||
+ | </code> | ||
- | Check if the file required is available in another package. Use the package manager (TazPkg) to search for the file: | + | * precise information about your SliTaz installation: |
- | * start the package manager | + | * which version to you have? Stable or Cooking? |
- | * 'Recharge' the package lists, if necessary | + | * are you using the standard ISO or a specific flavor (XVESA, Lo-RAM etc.)? |
- | * click the "Search" tab | + | * is it installed on a HD or on an USB stick? |
- | * in the //Search// box, enter the file-name ([library].so) and click "Files" | + | * do you know which file-system you used? |
- | * 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: | + | * identify when your problem appeared: |
- | <code>tazpkg search-file //[library]//.so</code> | + | * was it just after installation or after an update? |
+ | * were there any changes to your normal usage pattern or configuration? | ||
- | ... and install the appropriate package with: | + | This should provide enough system information for help to be provided. |
- | <code> tazpkg get-install [package] </code> | + | |
- | If no packages are given, report this as a bug over at the [[http://labs.slitaz.org|Labs]] as it needs to be included, or the dependency removed during the build. | ||
---- | ---- |