Reminder: Debian package version sometimes starts with a digit followed by a column, like 1:7.3.1-2. The module's version may be different (The maintainers sometimes cherry-pick more recent and stable modules). If you want to learn more about Xorg releases/versions, see this blog.ĭebian version number follows upstream convention. For instance, Xorg 7.3 was shipped with Xserver version v1.4, xf86-input-evdev v1.1.5, xf86-video-intel v2.1.1, etc.
![startx command not found debian 9 startx command not found debian 9](https://1.bp.blogspot.com/-OH5y4SYGdj8/X8YgZsKfJlI/AAAAAAAANUE/X0e5DXOZfWgHoaWov9C7hU5Ov6TmhBPtgCLcBGAsYHQ/s1280/Screenshot_20201201_134904.png)
This release is composed of various modules which have their own version number (each module started at version "1.0" when Xorg 7.0 development cycle started).
![startx command not found debian 9 startx command not found debian 9](https://raspex.exton.se/wp-content/uploads/2015/04/rasparch-desktop-small-300x162.jpg)
Nowadays, Xorg is released with a version number (like 7.4). Xorg version numbering has changed since xorg 7.0. The current versions shipped in Debian are listed on : xorg, xserver-xorg-core.
#STARTX COMMAND NOT FOUND DEBIAN 9 CODE#
If like me you've installed im-switch then 80im-switch brings in a bunch of code to set up your language input.ĩ0consolekit adds consolekit startup stuff to STARTUP if it's needed.ĩ0x11-common_ssh-agent sets up ssh if needed. Line 262 or so (depending on what you have on your system) runs /usr/bin/xdg-user-dirs-update from the xdg-user-dirs package.ħ5dbus_dbus-launch adds the dbus command to STARTUP. If you've only got one window manager installed that's no problem of course. That's what you usually get from running plain 'startx' with no options or config files. If there's no file then the Debian alternatives system is asked for a candidate session manager, window manager or terminal emulator. This means that you can set your window manager (or other startup script like startxfce4) by writing it in ~/.xsession. First, it looks for ~/.xsession or ~/.Xsession and if there is one, that file gets set in the STARTUP variable to be run at the end of the script. Now, more interesting, the code from 50x11-common_determine-startup is where the window manager or desktop environment gets chosen. (You could also put that ERRFILE-truncating code here.) Things you want to apply on ttys too might better go in ~/.profile.
![startx command not found debian 9 startx command not found debian 9](https://i.pinimg.com/originals/1a/9b/f8/1a9bf82b28c37e8798848b9155def043.jpg)
Just remember that this file will only be read in X sessions. This is a good place to put your locale settings and environment variables. The next section came from 30x11-common_xresources and this is where the stuff in your ~/.Xresources will be added in, if you have one.Ĥ0x11-common_xsessionrc sources in your ~/.xsessionrc if you have one. Has_option() Īnyway, we can ignore the rest of that file (lines 130~181) because it only applies if an argument was sent. Ubuntu used to (and maybe still does) add some lines to /etc/X11/Xsession to keep. Quite useful sometimes, but verbose apps can fill that file up with dreck and bloat it out to a huge size over time. That file will collect all the standard output and standard error from apps launched in the X session if they don't have a terminal to talk to. xsession-errors file if it doesn't exist. These variables keep turning up later on and they're a pain to remember. USERXSESSIONRC=$HOME/.xsessionrc # can set locales and environment variables hereĪLTUSERXSESSION=$HOME/.Xsession # (can have capital X)ĮRRFILE=$HOME/.xsession-errors # all stdout & stderr from apps not on terminal goes here USERXSESSION=$HOME/.xsession # can set your window manager here SYSSESSIONDIR=/etc/X11/Xsession.d # startup stuff, some added by installed apps USRRESOURCES=$HOME/.Xresources # user X stuff - fonts etc (sometimes put in. # initialize variables for use by all session scripts
![startx command not found debian 9 startx command not found debian 9](https://i.pinimg.com/originals/6d/4d/37/6d4d37c60dd2c7cb8bc5679924712f73.gif)
Xauth -q -f "$xserverauthfile" /dev/null Īfter that's run there'll be a serverauth.********** file in /tmp.įinally, the whole point of startx is to run this: Trap "rm -f '$xserverauthfile'" HUP INT QUIT ILL TRAP KILL BUS TERM Xserverauthfile=`mktemp -tmpdir serverauth.XXXXXXXXXX` # create a file with auth information for the server. If hostname -version > /dev/null 2>&1 then # set up default Xauth info for this machine Here's the original thread this is copied from: There's a wealth of stuff there, much of it still relevant, worth a look round. Other users' posts will be added as quotes.ĮDIT: The CrunchBang forum seems to be readable again now. desktop files in /etc/xdg/autostart and ~/.config/autostart, not to mention window managers'/desktop environments' own autostart things, like ~/.config/openbox/autostart.įrom here on I'm not going to do any editing, just copy-paste my posts as they were. I don't think it's changed too much in 2017.Īll those X files still cause no end of confusion: which ones are used/ignored in which circumstances, which ones to use for what, etc.Īnd of course this omits all the xdg autostart. It's a bit long-winded and hands-on but it goes through the whole startx boot up procedure in Debian in 2012. Now the #! website is getting a bit unreliable, I'm going to copy/paste one of my threads in here, on a topic that still comes up.