![]() And I got icewm in “antiX mode” (antiX background image), but… frozen as well. Hard shutdown and start again, this time using “startx /usr/local/bin/desktop-session icewm” as Dave said (again, no sudo anymore). The mouse didn’t work and I couldn’t open the menu by any other means (i.e. And what happened was icewm started as before when I used “sudo startx” (it started in “Debian mode” I guess - no background image), but… it got frozen. Logged in and tried “startx” (so, without sudo) just to see what would happen. Ctrl+Alt+F1 as usual, and I get the system in text mode as usual. “chown -R axTest:axTest /media/home/axTest” (actually “chown -R axTest:axTest /home/axTest”) did change the ownership of everything in my home folder.Īfter having checked if the change had been done, I rebooted. Restarted once again ater having renamed the file back to xinitrc – could start icewm with ‘sudo startx’ as before. I could launch apps from the terminal (root mode) – synaptic, spacefm, palemoon – which ran with some interface limitations (e. Restarted again after having renamed xinitrc:īlank screen, Ctrl+Alt-F1 gave me the system in text mode ‘sudo startx’ didn’t give me icewm, rather a black screen and a terminal. ‘startx’ produces errors and ‘sudo startx’ gives me icewm in root session (with a different menu, no background image, no access to fluxbox or JWM). No difference:īlank screen, Ctrl+Alt-F1 gives me the system in text mode (before I said CLI, meaning the same – system in text mode). Those are the only things I can think of for now.įrom nf (before and after reinstallation)ĭefault_path /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games I still think that starting up the normal way (no “startx”) and it drops you to a terminal login-prompt SHOULD put some useful error messages in /var/log/Xorg.0.log or slim.log or auth.log which should give some clue as to why X failed to start as user. xinitrc file, perhapes check / rename it (to try not using it). Xauthority file isn’t somehow owned by root, but by you (I’ve had root take ownership of it before, perhaps by running X as root, as you did?).ģ) Perhaps, reconfigure or reinstall slim, perhaps it’s config file (/etc/nf) isn’t right?Ĥ) If you have a. more things to checkġ) Where is /tmp set up – ramdisk, or in root (and it’s not full/has plenty of space)? Make sure it’s permissions 777 (so that X run as you can create temp. I just always use the default runlevel 5 which should start up X on it’s own. I’ve never had much luck in Antix w/startx. The fact that you got X to start up at all is a good sign.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |