[Solved] More than two minutes gap before Plasma appears after login

SanskritFritz · 2022-11-06 11:28:44

... and I really had high hopes with my other problem with nvidia solved, but sadly the gap is still there just as before.

SanskritFritz · 2022-11-20 18:08:50

I've tried greetd with agreety. There is no 2 mins gap in that setup, probably because the greeter simply uses startx.
I don't know what consequences this has but I'm still trying to solve this issue.

SanskritFritz · 2024-10-13 10:35:17

After the last Syu I noticed that the systemd messages at boot appear at native resolution on the screen, with the new nvidia driver. So I tried again after many months to start my beloved LightDM again and I'm pleased to report that the several minutes gap is gone for good.
So it was probably an nvidia problem, but of course I'm not sure of that. Anyway. If it counts, I mark this thread as solved, and sorry for the noise.

SimpleTechGuy · 2024-11-07 18:08:09

That's crazy, 2 years later the problem is fixed for you, but now the problem starts for me LOL.... Exactly the same issue, something is hanging for almost exactly 2 minutes after logging in with lightdm. No errors in the journal, nothing in dmesg. Assuming something to do with Nvidia and/or kernel update. I wonder if anyone else has noticed this?

@SansfritFritz, would you mind posting your specs for comparison?

OS: Arch Linux x86_64
Kernel: 6.11.6-arch1-1
Shell: bash 5.2.37
DE: Xfce 4.18
WM: Compiz
WM Theme: Materia
Theme: Materia-dark-compact [GTK2/3]
Icons: elementary [GTK2/3]
CPU: 12th Gen Intel i7-12700K (20) @ 5.300GHz
GPU: NVIDIA GeForce RTX 3060 Ti Lite Hash Rate

seth · 2024-11-07 19:04:24

What does your system journal look like?
SanskritFritz was/is using plasma, a common element would be nvidia but that's not very likely since lightdm and xfce4 would run on the same X11 server.

Do you get the problem w/ eg. openbox instead of compiz?

SimpleTechGuy · 2024-11-07 21:43:26

seth wrote:

What does your system journal look like?

Not comfortable posting the entire journal, but here is the split hang...
--

Nov 07 13:08:53 systemd[1]: user@972.service: Deactivated successfully.
Nov 07 13:08:53 systemd[1]: Stopped User Manager for UID 972.
Nov 07 13:08:53 systemd[1]: Stopping User Runtime Directory /run/user/972...
Nov 07 13:08:53 systemd[1]: run-user-972.mount: Deactivated successfully.
Nov 07 13:08:53 systemd[1]: user-runtime-dir@972.service: Deactivated successfully.
Nov 07 13:08:53 systemd[1]: Stopped User Runtime Directory /run/user/972.
Nov 07 13:08:53 systemd[1]: Removed slice User Slice of UID 972.
Nov 07 13:08:53 systemd[1]: user-972.slice: Consumed 918ms CPU time, 104.1M memory peak.
Nov 07 13:08:53 systemd-logind[2554]: Removed session 1.
Nov 07 13:09:00 systemd-timesyncd[2523]: Timed out waiting for reply from 
Nov 07 13:10:04 systemd-timesyncd[2523]: Contacted time server 
Nov 07 13:10:04 systemd-timesyncd[2523]: Initial clock synchronization to Thu 2024-11-07 13:10:05.241555 CST.
Nov 07 13:10:04 systemd[1]: Starting Daily man-db regeneration...
Nov 07 13:10:13 systemd[1]: man-db.service: Deactivated successfully.
Nov 07 13:10:13 systemd[1]: Finished Daily man-db regeneration.
Nov 07 13:10:13 systemd[1]: man-db.service: Consumed 7.761s CPU time, 162.5M memory peak.
Nov 07 13:10:57 systemd[2869]: Starting Virtual filesystem service...
Nov 07 13:10:57 systemd[2869]: Started Virtual filesystem service.
Nov 07 13:10:57 systemd[2869]: Starting Accessibility services bus...
Nov 07 13:10:57 systemd[2869]: Started Accessibility services bus.
Nov 07 13:10:57 dbus-broker-launch[3000]: Ready

--

Haven't tried openbox, but experiencing the same issue with compiz completely uninstalled and using default xfwm4. Also tried downgrading the kernel and using 560 and 555 nvidia drivers but no change. Also tried removing nvidia completely and using nouveau; no joy. And finally tried both nvidia-open and regular nvidia (which is what I was originally using)...

Kinda thinking I may have an issue with lightdm itself.

As a side note, I am using several other applications here (qemu/kvm, apparmor, firejail, nftables), also encrypted drives, but everything was great for a few months, until recent update (which happened while I was out of town for a few weeks), then got home to this lol...

mkinitcpio.conf (tried with and without ibt=off)

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

also have the following kernel options:

nvidia_drm.modeset=1 intel_pstate=no_hwp pcie_aspm=off rootfstype=ext4 intel_iommu=on iommu=pt

I have had NVreg_UsePageAttributeTable=1 disabled, but going to try with that turned on next. Most been focused on troubleshooting nvidia, haven't even started working on lightdm yet.

seth · 2024-11-07 21:54:40

It's waiting for your NTP synchronization - likely because of some network issues (or it just takes so long to setup the connection)

SimpleTechGuy · 2024-11-07 23:04:57

Sorry, forgot to mention; I thought about that too. tried disabling systemd-timesyncd, but got nada..

Nov 07 16:52:21 (sd-pam)[2825]: pam_unix(systemd-user:session): session closed for user lightdm
Nov 07 16:52:21 systemd[1]: user@972.service: Deactivated successfully.
Nov 07 16:52:21 systemd[1]: Stopped User Manager for UID 972.
Nov 07 16:52:21 systemd[1]: Stopping User Runtime Directory /run/user/972...
Nov 07 16:52:21 systemd[1]: run-user-972.mount: Deactivated successfully.
Nov 07 16:52:21 systemd[1]: user-runtime-dir@972.service: Deactivated successfully.
Nov 07 16:52:21 systemd[1]: Stopped User Runtime Directory /run/user/972.
Nov 07 16:52:21 systemd[1]: Removed slice User Slice of UID 972.
Nov 07 16:52:21 systemd[1]: user-972.slice: Consumed 940ms CPU time, 103.6M memory peak.
Nov 07 16:52:21 systemd-logind[2547]: Removed session 1.
Nov 07 16:54:24 systemd[2879]: Starting Virtual filesystem service...
Nov 07 16:54:25 systemd[2879]: Started Virtual filesystem service.
Nov 07 16:54:25 systemd[2879]: Starting Accessibility services bus...
Nov 07 16:54:25 systemd[2879]: Started Accessibility services bus.
Nov 07 16:54:25 dbus-broker-launch[2962]: Ready

Anyway, I think I might start a new post since I'm not using plasma, and since this one is 2 years old lol.. Just thought it was funny that I found this post in searching and it's almost exactly the same issue and the OP problem was fixed about the same time as mine started.. Feels like the OP and I just traded places. Hopefully this doesn't last 2 years for me. lol

seth · 2024-11-08 08:52:52

Does it take equally long to log into not-xfwm, but eg. openbox or icewm?
We'll at some point need way more log data (your login/session start typically happens before the lightdm session closes, any errors might be foreshadowed inbetween)

The journal does typically not contain sensitive data (possibly routable IPv6 addresses and sudo gets audited and logged) and you can obfuscate embarrassing one (like if your username reveals that you've a kink for squirrels what I will now assume but really don't care either )

SimpleTechGuy · 2024-11-08 15:42:00

lol, na, I keep the nsfw squirrel pics on another computer. Honestly more concerned about UUIDs, Mac Addresses, Serial Numbers, private IP address, etc. Really just don't trust ............, well you know. This is my daily driver, so I'm a little more careful about things like this.

Anyway, same issue with tiling wm's too.... Also tried disabling lightdm and using different DM's with no success. I had some custom config in the gtk-greeter, tried resetting that to default and nothing.

So far it seems unrelated or at least unspecific to nvidia drivers, Display Mangers, Window Managers.

seth · 2024-11-08 16:04:27

Drive/partition UUIDs are trackable (because they're UUIDs) if you post them in various places but don't tell anything else - they're random numbers generated to prevent ID collisions.
Your wlan AP yells its mac and SSID into the air and the information is useless outside the wifi range, your wifi NICs MAC is only valuable if you apply some MAC filter in your AP (and then also only in wifi range) there *might* be publically routable IPv6's in the journal but are typically not and I'm not sure what serial numbers you mean.

Obfuscate what you must (including your "ihumpsquirrels" username) but we'll *need* more context around the delay. At *least* starting w/ the actual login.

SanskritFritz · 2024-11-08 18:31:23

Try disabling and stopping Lightdm, and see if the problem persists with startx.
For me switching to another SDDM didn't help either.

SimpleTechGuy · 2024-11-09 00:31:38

hi @SanskritFritz, I actually tried that but kept getting an error when running startx with lightdm disabled.

The good news is that I finally figured out what the problem was for me, after 3 days lol.... Turns out the issue was/is being caused by opensnitch software. Not sure exactly what the problem is, but at least it has been narrowed down to this.

Thanks for all your help guys!

SimpleTechGuy · 2024-11-11 15:10:00

Determined further that the issue was directly related to an option in Opensnitch Nodes settings "Default action when the GUI is diconnected". I had it set to deny, which was blocking Localhost from doing something early in the boot process. Not sure what it was trying to do yet, but whatever it was getting blocked which in turn was blocking the opensnitch-ui from opening, which was causing some sort of loop.

SanskritFritz · 2024-11-11 16:09:25

Well, I don't even have Opensnitch installed, so your problem was very different from mine.
Having said that I'll check out Opensnitch, I didn't know about that so far and I like the idea.

SimpleTechGuy · 2024-11-11 16:18:17

SanskritFritz wrote:

Having said that I'll check out Opensnitch, I didn't know about that so far and I like the idea.

Definitely, I think everyone should use this software. It's really great to see which of your applications are reaching out to the internet and where they are going, with the added benefit of outbound protection against any potential infection on the computer. Honestly I'm surprised more people don't use it.

It can be a little frustrating to setup at first, especially if you don't have physical access to the computer, but once it's running, it's nice!

Arch Linux

#26 2022-11-06 11:28:44

Re: [Solved] More than two minutes gap before Plasma appears after login

#27 2022-11-20 18:08:50

Re: [Solved] More than two minutes gap before Plasma appears after login

#28 2024-10-13 10:35:17

Re: [Solved] More than two minutes gap before Plasma appears after login

#29 2024-11-07 18:08:09

Re: [Solved] More than two minutes gap before Plasma appears after login

#30 2024-11-07 19:04:24

Re: [Solved] More than two minutes gap before Plasma appears after login

#31 2024-11-07 21:43:26

Re: [Solved] More than two minutes gap before Plasma appears after login

#32 2024-11-07 21:54:40

Re: [Solved] More than two minutes gap before Plasma appears after login

#33 2024-11-07 23:04:57

Re: [Solved] More than two minutes gap before Plasma appears after login

#34 2024-11-08 08:52:52

Re: [Solved] More than two minutes gap before Plasma appears after login

#35 2024-11-08 15:42:00

Re: [Solved] More than two minutes gap before Plasma appears after login

#36 2024-11-08 16:04:27

Re: [Solved] More than two minutes gap before Plasma appears after login

#37 2024-11-08 18:31:23

Re: [Solved] More than two minutes gap before Plasma appears after login

#38 2024-11-09 00:31:38

Re: [Solved] More than two minutes gap before Plasma appears after login

#39 2024-11-11 15:10:00

Re: [Solved] More than two minutes gap before Plasma appears after login

#40 2024-11-11 16:09:25

Re: [Solved] More than two minutes gap before Plasma appears after login

#41 2024-11-11 16:18:17

Re: [Solved] More than two minutes gap before Plasma appears after login

Board footer