X server isn't properly starting with startx, ends in error

Nigh Knight · 2022-03-10 06:53:20

Background

I restarted i3 using it's default restart command mod+shift+r, and suddenly I was existed out of my current session.
Background.

Attempts

I decided to run startx, to restart X, nothing. I decide to open use xinit to start the display, using xinit -- :1, nothing. I decided to update my system, nothing. I tried using an older version of xinit, nothing. I decided to reinstall xorg related packages and remove my configs and reinstall my display driver, that's xf86-video-amdgpu, but still, to no avail, it doesn't start.

I did make the attempt to change i3 & but it didn't make a difference.

Once in while sudo startx might allow me to start a session, but it would be in root, I wouldn't have my usual config, it would use the default config in /etc/i3/config, also while in i3 I would be able to exist with the default command. I tried to solve config file issue by using i3 -c [absolute path of i3 config] In my xinitrx, but it wouldn't start with sudo startx

If only I could find a way to start i3 using my normal config file I might have access to my desktop and make finding a solution more easier.

Was able to fix an auth problem, relating to the Xauthority, by removing an env varrible that sets it's location.

Files

Logs / std error

startx | xorg.log

sudo startx | xorg.log

xinit | xorg.log

sudo xinit | xorg.log

i3 config after killing with pkill

Config files

xinitrc

xserverrc

Last edited by Nigh Knight (2022-03-10 09:53:05)

jasonwryan · 2022-03-10 06:59:29

1. Remove the "Urgent" from your thread title. There isn't a priority service here.

2. The yellow highlighting is annoying, and makes your post hard to read. Stop it.

3. Stop randomly using sudo to "fix" things. Escalating privileges should be deliberate, not a hail mary, and especially when starting X

4. There is no exec line in your xinitrc.

Nigh Knight · 2022-03-10 07:18:31

4: I made the attempt of using exec i3 but it resulted in the same sort of error, still didn't allow me to start X without sudo

seth · 2022-03-10 07:30:31

The first Xorg log w/o sudo is fine, it just terminated immediately because you're forking i3 (same rule as for "sudo", don't randomly yank "&"s ito places)
If you truely lost the ability to run X11 w/o sudo now, that's probably because of permissions on the xuathority file, so fix that - nothing in your $HOME should belong to root.

Edit: otherwise post the actual error when failing to start X11 w/o sudo and after fixing your xinitrc

Last edited by seth (2022-03-10 07:31:12)

Nigh Knight · 2022-03-10 09:24:19

I handled Xauthority errors, by remove the env used to change the location of the file. Now it's in my $Home.

Updated error files in post

Last edited by Nigh Knight (2022-03-10 09:46:26)

seth · 2022-03-10 14:58:37

To paraphrase Jason:

No, you diidn't "handle" anything. It just shifted the brokeness one space to the right.

Fix the permissions on the authoriry file that you spolied w/ the mindless sudo invocation.

https://clbin.com/hvb0W still terminates immediately because https://0x0.st/oPKi.sh still has i3 forked.

Nigh Knight · 2022-03-14 22:44:13

Using the last reply, my home now contains the .Xauthority file, it has the following permissions

Also the reason I used sudo startx was because of the error: xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted) (startx error file, see above). I thought by offering it the sudo access it would enable the failed I/O ports(what is an I/O port?).

But it seemed like offering it caused the error Failed to connect to bus: No medium found (sudo startx error file, see above) which lead to the error dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead (sudo startx error file, see above).

How do you propose I get the I/O port to run successfully and the bus to property connect?

Trilby · 2022-03-14 23:22:12

That is not labeled as an error in the log file. What made you pull out that one random line out of thousands to focus on? I'm not sure if that's a concern at all, but it's not labeled as an error, and it's clearly not fatal as that X session ran successfully!

The dbus issue is (most likely) due to using sudo. There can be other causes of that error, but attempting to run X as root will cause an error like that. Don't do that.

So far there has been zero indication of any problem at all in this thread other than your xinitrc not being properly written to do what you want (and perhaps the self-inflicted problems due to attempting to use sudo).

Last edited by Trilby (2022-03-14 23:22:41)

Arch Linux

#1 2022-03-10 06:53:20