Can't login to GUI

unixjedi · 2021-09-30 12:17:36

I am running i3 on a virtualized image of Arch. Everything was been working just fine until this morning. There are a couple of areas that I am somewhat weak. I don't really try to mess with systemd, I try to minimize messing with X11 or WM and a few other areas. I was trying to make user service under systemd. With the exception of making the unit file, timer and enable-linger, nothing else one done.

After I had enable and started my timer, I rebooted the VM. When I attempt to login, I get the attempt of X starting, and then I find myself back at the login prompt. I can use another tty to login, but I am not seeing where I am having an issue with the standard login. I have disabled the service, timer and linger, but still nothing it working. I have looked over the Xorg.0.log, but nothing really jumps out at me. My permissions are good across the board, so I am at a loss.

As I stated initially, there only thing I was doing was trying to get the service and timer working. So what is the process of getting back to normalcy?

kokoko3k · 2021-09-30 12:24:31

Sounds like Xorg started and exited because no more X clients running.
But, as you understand, you will have nothing else than conjectures as long as you don't provide logs.

unixjedi · 2021-09-30 12:33:07

kokoko3k wrote:

Sounds like Xorg started and exited because no more X clients running.
But, as you understand, you will have nothing else than conjectures as long as you don't provide logs.

I am working on providing the Xorg.0.log as I am typing. Is there any other logs I need to provide?

Trilby · 2021-09-30 12:33:18

~~Nothing will be able to jump out at us either if you don't post or link to that log.~~ (edit: this was cross posted with your last post).

Also please describe how you start X, and post any relevant startup files used (e.g., ~/.xinitrc if you use xinit or startx).

Last edited by Trilby (2021-09-30 12:35:25)

unixjedi · 2021-09-30 13:31:31

The following is my Xorg.0.log:

https://pastebin.com/ZkGUkBhU

and the following is my .xinitrc

https://pastebin.com/dNXWpJQH

seth · 2021-09-30 13:49:26

The xinitrc is broken (last link below) but I don't think that's the problem.
Since the X11 server terminates immediately, but cleanly, i3 probably crashes.

=> coredumpctl ?
Maybe there's also a message in the journal.

unixjedi · 2021-09-30 14:06:15

seth wrote:

The xinitrc is broken (last link below) but I don't think that's the problem.
Since the X11 server terminates immediately, but cleanly, i3 probably crashes.
=> coredumpctl ?
Maybe there's also a message in the journal.

I have seen the issue with i3status, but has failed over and over, but never enough to impede the starting of i3:

TIME                        PID  UID  GID SIG     COREFILE EXE                 SIZE
Mon 2021-06-07 08:30:31 CDT 274    0    0 SIGSEGV missing  /usr/bin/alsactl     n/a
Mon 2021-06-07 08:30:31 CDT 317    0    0 SIGSEGV missing  /usr/bin/alsactl     n/a
Mon 2021-06-07 10:59:55 CDT 297    0    0 SIGSEGV missing  /usr/bin/alsactl     n/a
Mon 2021-06-07 10:59:55 CDT 304    0    0 SIGSEGV missing  /usr/bin/alsactl     n/a
Sun 2021-06-20 23:17:41 CDT 409 1000 1000 SIGSEGV missing  /usr/bin/i3status    n/a
Tue 2021-06-29 01:54:06 CDT 415 1000 1000 SIGSEGV missing  /usr/bin/i3status    n/a
Mon 2021-09-13 10:26:43 CDT 384 1000 1000 SIGSEGV missing  /usr/bin/i3status    n/a
Fri 2021-09-17 03:46:58 CDT 395 1000 1000 SIGSEGV missing  /usr/bin/i3status    n/a
Wed 2021-09-22 09:56:25 CDT 378 1000 1000 SIGSEGV missing  /usr/bin/i3status    n/a
Mon 2021-09-27 23:35:14 CDT 386 1000 1000 SIGSEGV present  /usr/bin/i3status 230.5K
Tue 2021-09-28 10:04:09 CDT 398 1000 1000 SIGSEGV present  /usr/bin/i3status 230.1K

Last edited by unixjedi (2021-09-30 17:04:39)

seth · 2021-09-30 14:08:21

Please use code tags, https://bbs.archlinux.org/help.php#bbcode

Fix the xinitrc by including the relevant modules and replace "exec i3" w/ "exec urxvt" (or maybe "exec xterm") - can you then start the GUI?

Last edited by seth (2021-09-30 14:08:36)

unixjedi · 2021-09-30 14:43:46

seth wrote:

Please use code tags, https://bbs.archlinux.org/help.php#bbcode
Fix the xinitrc by including the relevant modules and replace "exec i3" w/ "exec urxvt" (or maybe "exec xterm") - can you then start the GUI?

I did change over to exec urxvt and the X server fired right up. So it would seem that the issue is potentially i3...

seth · 2021-09-30 15:07:11

You can try to start i3 from the interactive shell and see whether it yells an error at you.

unixjedi · 2021-09-30 15:51:20

seth wrote:

You can try to start i3 from the interactive shell and see whether it yells an error at you.

I tried that one, and it just kicks me out login prompt!!! I can't even get it to fire up in debug mode. I have to much config time in place to try to move another WM.

seth · 2021-09-30 15:52:58

Either it triggers the X11 server to crash or your ran "exec i3" in the terminal.
In case of the former, re-check your xog log.
In case of the latter: don't.

unixjedi · 2021-09-30 16:06:34

seth wrote:

Either it triggers the X11 server to crash or your ran "exec i3" in the terminal.
In case of the former, re-check your xog log.
In case of the latter: don't.

The problem is that there is nothing that I have done that would change the start of i3. Prior to this debacle, I was working just fine, despite the fact that i3status seemed to have some issue. I started messing around with trying to make a systemd user service, tried to get the unit timer to work, and rebooted. There was no messing around with the the i3 config, any X11 crap or anything else, so I am at a loss.

seth · 2021-09-30 16:32:15

The problem is that decrying what the problem is won't get you ahead.

1. did you "exec i3"?
2. are there now errors in your Xorg log
3. does running i3 maybe actually terminate the session, ie. when you run "startx" and exit urxvt, you end at the console prompt, but if you run i3, you actually have to re-login?
In case of (3), you should elaborate on "messing around with trying to make a systemd user service"…

unixjedi · 2021-09-30 17:02:13

seth wrote:

The problem is that decrying what the problem is won't get you ahead.
1. did you "exec i3"?
2. are there now errors in your Xorg log
3. does running i3 maybe actually terminate the session, ie. when you run "startx" and exit urxvt, you end at the console prompt, but if you run i3, you actually have to re-login?
In case of (3), you should elaborate on "messing around with trying to make a systemd user service"…

1.) Using tty6, I entered the following:

~ > exec i3

The result was an immediate drop to the login prompt

2.) doing a diff between Xorg.0.log and Xorg.0.log.old and with minor changes (time information, etc), there was nothing blaring about the log.

3.) Using startx attempts to execute X, and then fails, but I am still in the session. As stated before, if I exec i3, that leads to a booting and back to login prompt.

No need to elaborate to deeply. I decided to create a service and a timer. The service called a simple script to sync to my taskd server. I created a unit timer as well. I wanted to use at a user service (systemctl --user enable foo.timer) located at ~./local/share/systemd/user. I was able to reboot and found that the timer was not working, so I removed and rebooted again. At this time, I ran into the issue of not executing i3 and dropping me back to login prompt.

Last edited by unixjedi (2021-09-30 17:03:18)

seth · 2021-09-30 17:06:47

"exec i3" will replace the current shell w/ i3. If "tty6" (likely) means some console, i3 will terminate w/ an error because it runs on and needs X11.
=> For interactive tests don't use "exec", it's pointless and inhibits the investigation. And: run it from urxvt.

Trilby · 2021-09-30 17:18:33

unixjedi wrote:

3.) Using startx attempts to execute X, and then fails, but I am still in the session. As stated before, if I exec i3, that leads to a booting and back to login prompt.

Then it clearly doesn't fail. But the key here is you are being asked to do this again, but without the "exec" before i3. From a tty, run 'startx' with your xinitrc as it currently is to start a terminal (e.g., urxvt). Then from that GUI terminal run 'i3', then report what message(s) it gives you in that same GUI terminal.

Last edited by Trilby (2021-09-30 17:19:18)

unixjedi · 2021-09-30 18:08:52

@seth, you are the MAN! I started to think more about what I was doing in setting up the systemd service, and thought about some of the changes that I made to try to get the timer file working! So I remember having to setup an environment variable DBUS_SESSION_BUS_ADDRESS in my .zshenv. While I was editing the file, I inadvertently deleted another environment variable XDG_RUNTIME_DIR and I used $USER instead of $UID. Oooppps! But because you made me think about making the unit service working, I read through all of my notes.

When I tried to start i3, it get telling me that the permissions were not right for /run/user/kcc. As soon as I saw the username instead of the UID, I had a ah-ha moment. I can change to the .zshenv, a re-boot and a login and life is once again good to go! Thanks for the time and to everyone else that I chimed in!

Last edited by unixjedi (2021-09-30 18:09:52)

seth · 2021-09-30 21:25:34

So I remember having to setup an environment variable DBUS_SESSION_BUS_ADDRESS in my .zshenv

I'm gonna say you wanted to fix your xinitrc and not hardcode that in your zshenv - unless you really know that and why you need to customize anything about it (and the XDG_RUNTIME_DIR which also sounds like it shouldn't be there doesn't support that case)

One of the major aspects of the mandatory xinitrc includes is to import those environments variables from the session.

Arch Linux

#1 2021-09-30 12:17:36

Can't login to GUI

#2 2021-09-30 12:24:31

Re: Can't login to GUI

#3 2021-09-30 12:33:07

Re: Can't login to GUI

#4 2021-09-30 12:33:18

Re: Can't login to GUI

#5 2021-09-30 13:31:31

Re: Can't login to GUI

#6 2021-09-30 13:49:26

Re: Can't login to GUI

#7 2021-09-30 14:06:15

Re: Can't login to GUI

#8 2021-09-30 14:08:21

Re: Can't login to GUI

#9 2021-09-30 14:43:46

Re: Can't login to GUI

#10 2021-09-30 15:07:11

Re: Can't login to GUI

#11 2021-09-30 15:51:20

Re: Can't login to GUI

#12 2021-09-30 15:52:58

Re: Can't login to GUI

#13 2021-09-30 16:06:34

Re: Can't login to GUI

#14 2021-09-30 16:32:15

Re: Can't login to GUI

#15 2021-09-30 17:02:13

Re: Can't login to GUI

#16 2021-09-30 17:06:47

Re: Can't login to GUI

#17 2021-09-30 17:18:33

Re: Can't login to GUI

#18 2021-09-30 18:08:52

Re: Can't login to GUI

#19 2021-09-30 21:25:34

Re: Can't login to GUI

Board footer