My Wheezy system is headed for End Of Life May 2018, and I want to get a replacement system installed and ready to go by that time. True, I don't boot to a terminal, but I'm just testing and evaluating now. But for now I installed lightdm, and X and Openbox load and work fine after logging in. I've had similar"problems" happen before. I mentioned in another reply that this startx problem could be a VirtualBox glitch. It's likely that the problem boils down to some of those files having the wrong ownership or permissions. I made no changes other than configuring to boot to console (startx still wasnt working) and back to GUI and back to console (and now it works). It generates a copious list of all system calls which will show all the files that are being accessed. Another approach is to run Xorg with the strace command. Having similar systems that work may make debugging easier. My hope is that maybe most of this can be fixed with a well-placed chown -R or chmod -R command. To enable x at startup time you can use: sudo systemctl enable graphical.target -force sudo systemctl set-default graphical.target.
I personally use startx instead of a display manager and what you want is in accord with the antiX"lean and mean" motto. systemctl get-default permit to see what target is set for the startup either multi-user.target or graphical.target. And to be as"light' and fast as possible.
#Ubuntu startx not working install
I don't want to install a display manager as I want the system to boot to a standard terminal and not X as many times I only need a terminal. Traditional Desktops which I abandoned about 6 years ago are such leviathans and CPU gluttons, and no more useful than a good window manager and a single panel. I've tested Stretch in VirtualBox under numerous configurations - systemd init, sysv and runit inits with and without systemd components - installed the same way as I did Antix and never experienced any startx problems. My thinking now is this startx failure is an Antix 17 Beta glitch and not an upstream Debian Stretch or xorg problem. Although, I don't think the bug report applies (and it's a year old), but I'll read it more thoroughly later. Thanks for your quick response, advice and the bug link. You can probably explore this further but it might be faster/easier to install slim or lightdm or some other display manager that you can start as an init.d service. I think the problem is upstream with Debian and/or X.org and/or. Code: Select all sudo chmod u+x /usr/bin/Xorgīut that didn't change anything.
0 kommentar(er)
