Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was testing some modules for Slax - some Gparted modules and some requirements for it - adding and removing them.

But when I restarted OS, Slax Module Manager did not work anymore. When I try to install another module, a pop-up displays a message telling an error occurred in installation with no technical details.

When I put some modules in modules folder, they are installed but only after rebooting, but I'd like to test more modules installing and uninstalling them without restarting.

Is there any way to correct that issue in Module Manager without reinstalling Slax?

share|improve this question
Have you tried just restarting the module manager and slax? – soandos Jul 25 '11 at 14:07
So it shows up 'live' then disappears when you restart? Can you clarify "restarted OS Slax Module Manager" Do you mean when you restarted the OS? or the Slax Manager? – soandos Jul 25 '11 at 14:39
yeah. i'll put more punctuation marks :) "But when I restarted OS Slax Module Manager..." => "But when I restarted OS, Slax Module Manager..." – kokbira Jul 25 '11 at 14:47
Apologies. Is this what happens? You install the package, and dont see it until you restart the OS? – soandos Jul 25 '11 at 14:48
well, i'll try to be more clear: i installed 10 modules and then i uninstalled 9 modules. after that i turned off computer. some hours later, i turned on again and slax starts normally. when i try to install another module, i could not and a popup appears with a message saying that there were an error installing that module. i downloaded more modules, but i cannot install them too. i turned of/on computer some times but i cannot install modules anymore :( i saw later that copying modules to modules folder make them installed, but doing so i have to turn off and then on the computer... – kokbira Jul 25 '11 at 16:15
up vote 0 down vote accepted

Well, I find one solution, not the best one, but it avoids that kind of problem.


Add Slax modules saving them (the .LZM files) to /slax/modules folder.


When booting/rebooting Slax, .LZM files on /slax/modules folder are loaded as they were installed by clicking twice on it inside OS.


When operational system is "broken" (i.e., when it does not boot anymore or some "crazy" problems occurs in its use, like that reported error in Slax Module Manager), you can just delete /slax/changes folder and maintain your modules in /slax/modules folder. You will lost some SO customizations, but you will maintain your custom programs.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .