- This topic has 43 replies, 6 voices, and was last updated May 13-7:05 am by zeh.
-
Posts
-
zeh
and here I just say thank you 🙂
and that what I said was basically that so far I lack the ability to learn beyond some more or less basics 🙂
tar attached
wildstar84
The fact that you got X to start up at all is a good sign. I’ve never had much luck in Antix w/startx. I just always use the default runlevel 5 which should start up X on it’s own. A cpl. more things to check
1) 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. files, etc.
2) Make sure your .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?).
3) Perhaps, reconfigure or reinstall slim, perhaps it’s config file (/etc/slim.conf) isn’t right?
4) If you have a .xinitrc file, perhapes check / rename it (to try not using it). 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.
Those are the only things I can think of for now.
Regards,
Jim
Hi Jim,
1)
/tmp in / (with plenty of space)
File properties, Permissions Tab:
Owner: root
Group: root
permissions rwx , rwx , rwx / –S2) /media/home/axTest/.Xauthority
File properties, Permissions Tab:
Owner: root
Group: root
permissions rw- , — , — / —3)
From slim.conf (before and after reinstallation)
default_path /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
default_xserver /usr/bin/X11/X
xserver_arguments -nolisten tcp4)
xinitrc
/media/rootaXTest/etc/X11/xinit/xinitrc
File properties, Permissions Tab:
Owner: root
Group: root
permissions rwx , r-x , r-x / —Restarted after having reinstalled slim. No difference:
blank screen, Ctrl+Alt-F1 gives me the system in text mode (before I said CLI, meaning the same – system in text mode). ‘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).Restarted again after having renamed xinitrc:
blank 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. I could launch apps from the terminal (root mode) – synaptic, spacefm, palemoon – which ran with some interface limitations (e. g., no window menu).
Restarted once again ater having renamed the file back to xinitrc – could start icewm with ‘sudo startx’ as before.Regards,
Zeh
Dave
Two notes that are antiX specific:
Xinitrc is not used in default antiX configuration. So relying on it will error out / be debian default package config with no extras.Second, startx defaults to .xinitrc which as previously stated is not used by default in antiX. Instead try something like
startx /usr/local/bin/desktop-session rox-icewm (or space-icewm, icewm, space-fluxbox etc)Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
Anonymous
Hi zeh,
wildstar84 wrote:
2) Make sure your .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?).and you wrote:
2) /media/home/axTest/.Xauthority File properties, Permissions Tab: Owner: root Group: root permissions rw- , — , — / —nothing in the users home folder should be owned by root … they should all be owned by the user.
both owner and group.Instead try something like
startx /usr/local/bin/desktop-session rox-icewm (or space-icewm, icewm, space-fluxbox etc)gives the same errors as just startx
nothing in the users home folder should be owned by root … they should all be owned by the user.
both owner and group.Something when wrong here then. Everything in my home folder is owned by root, both owner and group, I guess (didn’t check each and every file, but did check a few). I’ve suspected of a permissions problem from the beginning.
- This reply was modified 4 years ago by zeh.
Here’s a partial shot of my home folder.
note they say
dad dad
for my owner and group with none as root.as root you could try to use the “chown” command and recusively
change the permissions to your user. something like:chown -R axTest:axTest /media/home/axTestfrom the the command prompt and see if that helps.
Here’s a breakdown on the meaning of some of the permissions and chmod
use for further reading fromhttps://helpdeskgeek.com/linux-tips/understanding-linux-permissions-chmod-usage
and a pic from there I saved as a quick reference for me.
Thanks linuxdaddy!
“chown -R axTest:axTest /media/home/axTest” (actually “chown -R axTest:axTest /home/axTest”) did change the ownership of everything in my home folder.
After having checked if the change had been done, I rebooted.
Still got the blank screen. Ctrl+Alt+F1 as usual, and I get the system in text mode as usual.
Logged in and tried “startx” (so, without sudo) just to see what would happen. 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. The mouse didn’t work and I couldn’t open the menu by any other means (i.e. by the key bindings).
Hard shutdown and start again, this time using “startx /usr/local/bin/desktop-session icewm” as Dave said (again, no sudo anymore). And I got icewm in “antiX mode” (antiX background image), but… frozen as well. Mouse not working and couldn’t open the menu with any key binding.
So, it looks like we managed to get one more step forward, but without having reached the end of the line so far.
And now it doesn’t look like I have a permissions issue anymore. I may very well be wrong, though, since I don’t know what is causing the freezes.
EDIT:
“startx /usr/local/bin/desktop-session icewm” “startx /usr/local/bin/desktop-session rox-icewm” and “startx /usr/local/bin/desktop-session rox-fluxbox” all open the respective wm, frozen.“startx /usr/local/bin/desktop-session sapcefm-icewm” and “startx /usr/local/bin/desktop-session spacefm-fluxbox” do not open the wm, just return the prompt in the text mode session after printing some lines of text, the last of whose reads:
“waiting for X server to shutdown (II) Server terminated successfully (0). Closing log file.ession/logxinit: connection to X ser”It looks like the text in the line goes further but cannot be seen for getting out of the screen.
Noticed “log file.ession/logxinit” where the bit “ession” looks like a corruption of the word “session”.
- This reply was modified 4 years ago by zeh.
- This reply was modified 4 years ago by zeh.
- This reply was modified 4 years ago by zeh.
Noticed “log file.ession/logxinit” where the bit “ession” looks like a corruption of the word “session”.
yeah that is supposed to be session not ession you can rename it to be right
you cuold also try “Ctrl+Alt+F7” after you do “Ctrl+Alt+F1” to go back to graphics mode
and see if the desktop unfreezes.No luck this time.
On text mode (after the blank screen and entering “Ctrl+Alt+F1”) “Ctrl+Alt+F7” before entering starx /usr/…. just returns the blank screen.
On graphical mode (frozen) “Ctrl+Alt+F7” has no effect at all. The system remains totally frozen (except for the blinking conky minimized window on the panel – the concky is visible on the desktop – which I can’t do anything about)
And I couldn’t find any ‘file.ession’, ‘log file.ession’, ‘log file’ or ‘logxinit’ file so that I could rename it.Since there haven’t been any new ideas for a while and, as said before, I don’t depend on this system, I’ve just made a fresh reinstall.
Thank you to those who replied and tried to figure out what the problem could have been with my system.
- You must be logged in to reply to this topic.
