You are not logged in.
Pages: 1
I tried a `startx openbox-session` and it gives me
```
X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
Build Operating System: Linux Arch Linux
Current Operating System: Linux arche 5.6.6-arch1-1 #1 SMP PREEMPT Tue, 21 Apr 2020 10:35:16 +0000 x86_64
Kernel command line: root=UUID=$UUID rw initrd=\initramfs-linux.img
Build Date: 30 March 2020 05:05:45AM
Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 26 01:21:18 2020
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error: Could not resolve keysym XF86FullScreen
Errors from xkbcomp are not fatal to the X server
xterm: Explicit shell already was /usr/bin/xterm
xterm: bad command line option "openbox-session"
usage: xterm [-/+132] [-C] [-Sccn] [-T string] [-/+ah] [-/+ai] [-/+aw]
[-b number] [-baudrate rate] [-/+bc] [-bcf milliseconds]
[-bcn milliseconds] [-bd color] [-/+bdc] [-bg color] [-bw number] [-/+cb]
[-cc classrange] [-/+cjk_width] [-class string] [-/+cm] [-/+cn] [-cr color]
[-/+cu] [-/+dc] [-display displayname] [-e command args ...] [-fa pattern]
[-fb fontname] [-/+fbb] [-/+fbx] [-fd pattern] [-fg color] [-fi fontname]
[-fn fontname] [-fs size] [-/+fullscreen] [-fw fontname] [-fwb fontname]
[-fx fontname] [%geom] [#geom] [-geometry geom] [-help] [-/+hm] [-/+hold]
[-iconic] [-/+ie] [-/+im] [-into windowId] [-/+itc] [-/+j] [-/+k8]
[-kt keyboardtype] [-/+l] [-/+lc] [-lcc path] [-leftbar] [-lf filename]
[-/+ls] [-/+maximized] [-/+mb] [-mc milliseconds] [-/+mesg] [-/+mk_width]
[-ms color] [-n string] [-name string] [-nb number] [-/+nul] [-/+pc]
[-/+pob] [-report-charclass] [-report-colors] [-report-fonts]
[-report-icons] [-report-xres] [-rightbar] [-/+rv] [-/+rvc] [-/+rw] [-/+s]
[-/+samename] [-/+sb] [-selbg color] [-selfg color] [-/+sf] [-sh number]
[-/+si] [-/+sk] [-sl number] [-/+sm] [-/+sp] [-/+t] [-ti termid]
[-title string] [-tm string] [-tn name] [-/+u8] [-/+uc] [-/+ulc] [-/+ulit]
[-/+ut] [-/+vb] [-version] [-/+wc] [-/+wf] [-xrm resourcestring]
[-ziconbeep percent]
Type xterm -help for a full description.
xinit: connection to X server lost
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
```
Last edited by vf (2020-04-26 13:25:02)
Offline
1. Please use code tags whe pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code
2. Paste your xinitrc
Offline
Offline
Comment the last 4 lines of your ~/.xinitrc and add a new line like this :
exec openbox-sessionLast edited by Lone_Wolf (2020-04-26 12:36:54)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
That should be the last 5 lines.
Though `startx openbox-session` should work and the xinitrc should be irrelevant when invoked that way. I say should as I've always found startx to be a buggy rats nest. If you ever want to go insane, try to read and understand it's code. Xinit itself isn't a whole lot better. They are both generally exceedingly reliable, but debugging their code when something does go wrong is a recipe for disaster.
Last edited by Trilby (2020-04-26 12:50:14)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
It works just fine
I have some questions: I used to like `exec xterm -geometry 80x66+0+0 -name login` because it prints out all executed programs logs. Do you know how to invoke that on purpose? (a command like `journalctl` but for that). And I have multiple screens resolutions so XTerm seems way too little with such DPI, but Alacritty changes his intern DPI automatically depending on what screens he is on, so is it possible to invoke that on an Alacritty terminal?
Isn't `startx` should setting some variable up? Because some services stills complain about cannot opening display
Last edited by vf (2020-04-26 13:23:21)
Offline
First, do these new questions have anything to do with this thread? If not, they should not be here, mark this thread as [SOLVED] and start a new one for your new question.
Second, I have no idea what you're new question is asking. The xterm command you quoted just opens a terminal running the default shell. You refer to printing out all executed programs logs, but this would not happen in that terminal unless you typed some command into that terminal. But whatever this command was, if it runs in a terminal, it could run in alacritty.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
This terminal that I talk you about has dissapeared as I commented out those 5 lines, thats why I suspect this line to be the one
Offline
Output of
type startx
type xinit?
Online
both in `/usr/bin`
Offline
I had more expected them to be soem sort of alias because your initial post only makes sense if you ran "startx xterm openbox-session" and something™ will have provided you w/ the dmesg, so probably some "xterm -e dmesg -w" that got passed openbox-session in addition.
So far error, expected behavior and xinitrc don't add up at all.
Online
Yeah maybe, not sure
Offline
Pages: 1