You are not logged in.
So I did the following command to install i3-gaps :
sudo pacman -S i3-gaps Next I copied my xinitrc config to home directory and made deleted last few lines:
sudo cp /etc/X11/xinit/xinitrc ~/.xinitrc
sudo nvim .xinitrcThe following is my final .xinitrc file:
#!/bin/sh
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f "$userresources" ]; then
xrdb -merge "$userresources"
fi
if [ -f "$usermodmap" ]; then
xmodmap "$usermodmap"
fi
# start some nice programs
if [ -d /etc/X11/xinit/xinitrc.d ] ; then
for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec i3Now i saved it and ran startx to recieve the following error:
xauth: (stdin):2: unknown command "9d3141e14cec6b6d61ced7ed5e93b795"
xauth: (stdin):2: unknown command "9d3141e14cec6b6d61ced7ed5e93b795"
/usr/lib/Xorg.wrap: Only console users are allowed to run the X server
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Couldn't get a file descriptor referring to the console.Now I don't know what to do next to fix this.
Last edited by pyrole (2022-07-15 22:57:41)
Offline
You used, indiscriminately, elevated privileges to edit ~/.xinitrc, so now it is likely owned by root.
Offline
The problem is he copied the file with elevated rights.
Editing a file owned by the user with sudo won't change the owner.
Offline
For future reference, this may help: https://wiki.archlinux.org/title/Help:R … er_or_root
(assuming you read the xinit article on the Wiki to get to this issue)
Last edited by vorvac (2022-07-11 22:33:35)
Offline
deleted
Last edited by pyrole (2022-07-12 20:15:56)
Offline
You used, indiscriminately, elevated privileges to edit ~/.xinitrc, so now it is likely owned by root.
I don't think so that was the issue, so I deleted the .xinitrc and redid the process without ever using sudo rights:
cp /etc/X11/xinit/xinitrc ~/.xinitrc
nvim .xinitrc
startxThe output remains:
xauth: (stdin):2: unknown command "9d3141e14cec6b6d61ced7ed5e93b795"
xauth: (stdin):2: unknown command "9d3141e14cec6b6d61ced7ed5e93b795"
/usr/lib/Xorg.wrap: Only console users are allowed to run the X server
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Couldn't get a file descriptor referring to the console.Offline
Just to clarify from the title -
Before this change to your .xinitrc, were you logging into XFCE through a display manager?
1. Have XFCE and i3 installed.
2. Boot into XFCE. Open XFCE's Session & Startup menu.
3. Under the Session tab, disable xfwm and xfdesktop.
4. Under the Application Autostart tab, add and enable i3
The above steps may work, have you tried any of them?
Also: https://wiki.archlinux.org/title/Xfce#U … ow_manager
Last edited by vorvac (2022-07-12 20:22:39)
Offline
Just to clarify from the title -
Before this change to your .xinitrc, were you logging into XFCE through a display manager?
Reddit wrote:1. Have XFCE and i3 installed.
2. Boot into XFCE. Open XFCE's Session & Startup menu.
3. Under the Session tab, disable xfwm and xfdesktop.
4. Under the Application Autostart tab, add and enable i3
The above steps may work, have you tried any of them?
Yes I have tried all of them when i disabled xfwm and xfdesktop and added i3, on reboot nothing loaded now i am trying to install i3 independently from xfce4, meaning I choose what i wanna boot into during login.
Still When i do startx it gives the errors i mention.
Offline
You're running startx from an X11 session - that's bonkers.
I choose what i wanna boot into during login
And how do you login? lightdm? Because your xinitrc doesn't implement a choice.
Offline
You're running startx from an X11 session - that's bonkers.
I choose what i wanna boot into during login
And how do you login? lightdm? Because your xinitrc doesn't implement a choice.
Yes sir I am using lightdm as my display manager and I didn't quiet understand what you meant by running startx form X11 session could you be so kind to explain why that is a bad idea?
Offline
You're logging into xfce via lightdm and then try to run startx from a VTE (xfce4-terminal, presumingly - but the specific VTE doesn't matter)
It's not a bad idea, but not possible - and kinda nonsense. You *have* started X11 at this point.
If you want to run i3 from there, "pkill xfwm4 && i3 &".
Alternatively select the i3 session in lightdm (won't run any xfce desktop/panel/… by default, though) - but I'd focus on vorvac's post and elaborate on what *exactly* you've actually done to replace the window manager.
Offline
You're logging into xfce via lightdm and then try to run startx from a VTE (xfce4-terminal, presumingly - but the specific VTE doesn't matter)
It's not a bad idea, but not possible - and kinda nonsense. You *have* started X11 at this point.
If you want to run i3 from there, "pkill xfwm4 && i3 &".
Alternatively select the i3 session in lightdm (won't run any xfce desktop/panel/… by default, though) - but I'd focus on vorvac's post and elaborate on what *exactly* you've actually done to replace the window manager.
Ok I think I understand what you explained, thanks.
Now what vorvoc said, I already followed that guide also each and every step, then rebooted to find that my lightdm only doesn't start, then after several unseccessfull attempts to fix this I reinstalled the xfwm4 and rebooted to be able to boot into lightdm and then into xfce4 and when I checked the autostart application menu the changes got reverted back to immediately form never.
Offline
Nothing in that article would prevent lightdm from starting.
Do you auto-login?
In general, see https://wiki.archlinux.org/title/LightD … TTY_output and https://wiki.archlinux.org/title/Kernel … _KMS_start
also each and every step
There're at least 4 variants to achieve this described in the article, nb. that "wm_name" is a placeholder, if you entered that verbatim (instead of i3) it will of course not work.
when I checked the autostart application menu the changes got reverted back to immediately form never.
google translate?
I've no idea what you're trying to say, but running xfwm4 and then autostarting "i3 --replace" is a rather clumsy approach anyway.
Offline
There're at least 4 variants to achieve this described in the article, nb. that "wm_name" is a placeholder, if you entered that verbatim (instead of i3) it will of course not work.
So I did not enter wm_name I understand we have to replace it with the name of appropriate wm...
Also I tried all the methods and none of them seemed to work, I removed all the configs after testing one approach and reinstalled the i3 packages set.
when I checked the autostart application menu the changes got reverted back to immediately form never.
google translate?
So in the guide there was a step in which we had to access the autostart applications gui setting menu and from that change "immediately" setting to "never" for xfwm and xfdesktop and then add the autostart for i3.
But after reboot this change was reverted.
Offline
Also I tried all the methods and none of them seemed to work
That's https://bbs.archlinux.org/viewtopic.php?id=57855
Your original description was that as consequnce lightdm didn't start, but that's not a possible outcome of *any* of the actions in the article.
So see the links I posted in #13 to secure the lightdm behavior, then *ONLY* run
xfconf-query -c xfce4-session -p /sessions/Failsafe/Client0_Command -t string -sa xfsettingsd
xfconf-query -c xfce4-session -p /sessions/Failsafe/Client1_Command -t string -sa i3Post any output you get from that (or that you didn't) - then reboot.
1. lightdm is supposed to start. Again: the above *CANNOT* impact that at all
2. try to login
3. report the outcome, if things fail, post a complete system journal for that boot (ctrl+alt+f3, sudo journalctl -b | curl -F 'file=@-' 0x0.st)
Ftr and later on you probably want to check
https://wiki.archlinux.org/title/Xfce#i … patibility
but that's currently not relevant.
Offline