#STARTX SCRIPT HOW TO#
#STARTX SCRIPT UPDATE#
#STARTX SCRIPT FULL#
#STARTX SCRIPT PASSWORD#
#STARTX SCRIPT PLUS#

#STARTX SCRIPT FULL#

Sorted out why, checking out 'man update-alternatives' is a good idea, knew some of the relevant cmds involved but couldn't remember the syntax anyway try ie: 'update-alternatives -display x-session-manager' it'll list out which graphical interfaces you can set as default x-session, here's where I messed up with installing fluxbox to x-session-manager, was in a hurry and probably did 'which fluxbox' at the time, which will show /usr/bin/fluxbox but that binary is meant to be used when fluxbox is acting as a window manager for another desktop, startfluxbox is meant to be used as a full stand-alone graphical session, 'which startfluxbox' will show the following. Had installed it to x-session as shown above but it wasn't running it's startup file etc. Okay here's the deal, recently was dorking with FB and thing didn't seem to be working.

#STARTX SCRIPT PLUS#

Plus I owe Fluxbox an apology some recent borkage was my error/Pebcak, though thing still comes up quite a bit short compared to Openbox imo.

#STARTX SCRIPT UPDATE#

Hey wanted to leave this with an important update and some additional info. After which the sucker should be up and running again.

If at some point in future you wish, re-enable the sucker with 'sudo systemctl enable lightdm' and you may also need to run 'sudo dpkg-reconfigure lightdm' too. Another would be to use 'sudo systemctl disable lightdm' to disable lightdm and keep it from automatically starting every time the system boots up. Couple options, remove the display manager from your OS, you can always reinstall it later if desired. For all this automagic-ness to work, you'll have to change that.

#STARTX SCRIPT PASSWORD#

You'll be met with a command-line login to enter the user and password you want to use.įinally, you likely already have a display manager running. Easy, peasy, just skip step 1 (or remove the directory/nf file. NOTE: Ok another scenario, the above is perfectly fine for a single user system but what about a multi-user one or one on which you want to be able to login more than one username. Once it's selected it'll launch as default x-session until something else is chosen. In the above, I'm installing something to the x-session-manager group of update-alternatives, in this case, fluxbox, /usr/bin/fluxbox is where fluxbox errrr, lives and I'm giving it a priority of 40 there. I couldn’t find out how that would help in my case.Code: Select all sudo update-alternatives -install /usr/bin/x-session-manager x-session-manager /usr/bin/startfluxbox 40 However, there is a unit named graphical.target though, but I assume that serves a different purpose altogether. I was unable to find any unit with the name rvice. I have looked through the list of units provided by the systemd. I have tried playing around with $DISPLAY variable and xhost command but no success. However, when the service is started there is some sort of error: Unable to init server: Could not connect: Connection refused : cannot open display: Manually the script is running fine and I can see the stream output. That script plays a live video stream from a camera.

#STARTX SCRIPT HOW TO#

I have been having a similar problem but I am not sure how to use the solution you suggested. The startx could even be set up as its own service, and if you don’t want the regular GUI login to run, then you could go to a default runlevel of “ multi-user.target”, and have your service trigger upon reaching multi-user.target (and perhaps even wait for rvice if needed).

The regular login manager could continue to be run on “ :0”, and the startx could purposely start somewhere this won’t collide with, e.g., “ :9”. This script is used to manually start X on a terminal, and simply runs as the user who ran the script. You might consider examining the “ startx” script. This does not actually log in a user, so I suspect that when rvice is reached there is no actual logged in X GUI session yet. If your X display is not running, or if the login menu is there and login is not truly complete, or if the logged in user differs from the user running the application, then using that $DISPLAY will fail or be refused.Īlso, rvice only guarantees a default TTY is running a login service. To emphasize something mentions, no X display will allow another user to remote display into it even if the $DISPLAY is otherwise correct.

Startx script