You are not logged in.
TL;DR
Installed Qingy a while back, NVIDIA driver didn't like it, so I uninstalled it.
Since have long login delay on my account, new accounts are fine.
If I'm already logged in, this account is fine.
Full details:
Let's start from the top- My system was running great, and is still, as far as I can tell, running great.
On login, I have a 8-12 second delay on my Rojikku account.
This started happening after I attempted to install quingy (That was hell.)
I did all sorts of stuff attempting to get the qingy gui to work, and I never did.
I eventually undid everything, at least I believe I did, and uninstalled quingy.
I started the whole qingy search because I heard slim was abandoned, and qingy sounded cool.
I have since been using lightdm, which I thought was the problem.
In the process of going to fix this problem, I logged out completely and went to login to the tty, when I discovered I have the issue.
This issue WILL NOT happen if I am already logged in with my xsession started.
For example, I am on tty2 with this i3 session open. If I switch to tty3, my login will be instant.
If I close out of tty2, and login on any tty, it will take ten seconds or so.
If I attempt to login on a new account I just made, the login is instant.
I use the zsh shell. I assume everything outside of my shell is fairly irrelevant, though I have a couple user systemd processes.
I couldn't find the issue on Google, though I have a basic understanding of "Something that needs to see I'm logged in isn't seeing it until it reloads after about ten seconds". That could be completely wrong.
In case you're wondering, no, I didn't make any other major changes just before this started happening.
I run the nvidia driver, which wasn't very compatible with qingy.
My kernel is at 3.18.6-1-ARCH
I'm running off an SSD, 30GB partition, and I have 16GB of RAM.
My processor averages less than 20% load even when I'm doing a lot of stuff much more intensive than logging into a tty session.
I use the i3 window manager, for those curious, and have xinit setup to allow me to choose between it and xfce4. I have xfce4 installed so that I am not missing any major dependencies- or at least am less likely to be, as far as I can tell.
Last edited by Rojikku (2015-03-13 06:01:30)
Offline
Put set -x in your ~/.zprofile and see where it hangs
Last edited by Alad (2015-03-12 10:34:22)
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
In addition, what about the log/journal? Maybe there's a hint. Look at the end of the log after getting the delay...
Personal website: reboot.li
GitHub: github.com/rebootl
Offline
set -x was certainly interesting.
There's, by my timing, around a five or six second delay, before a rainbow falls from the sky. Then it becomes a shell. The fact that a rainbow of text flew in out of nowhere slightly distracted my ability to count time. Is there some way I can log this output so I can analyze it?
It's slightly too fast for me to see. By slightly, I mean a lot.
As for log/journal, I have no idea how to access that... I tried a few things, not getting anything.
Offline
As for log/journal, I have no idea how to access that... I tried a few things, not getting anything.
Offline
Thank you, jasonwryan.
This is the log from when I turned my computer on today to present.
Offline
Starting Random wallpaper with feh...
This looks wrong...
Offline
That's my custom system service. I don't know how to make it wait until X is actually started, though, X could have been started at that time.
Offline
It should be a user service, if at all...
Offline
It is a user service.
Offline
systemd-analyze --user blame
Without the user flag is helpful too.
It was a custom service I had written, apparently it had to complete before my shell loaded, for no apparent reason. That was my whole issue.
Offline