Logging in/logging out kills internet.

[ThatOneCalculator]

OS: Arch GNU/Linux WM: BSPWM

Issue: After logging out/logging back in on a session, the second login will kill my wifi connection. Rebooting "solves" the issue.

Reproducible: Every time.

Logout method: bspc quit

Version: Ly version v0.5.2.r1.g77f6958

[willww64]

Yes, other DM like sddm, gdm works well. I think it's a bug related to "session" handling. After first login the $XDG_SESSION_ID is 1, and loginctl show-session 1 output State=active. But after logout and login back, the $XDG_SESSION_ID is unset, loginctl show-session 1 output State=closing.

[ThatOneCalculator]

So what can I do to resolve it

[markstos]

I confirmed this after suspend/resume with Sway:

❯ loginctl show-session 1 | grep State
State=closing

I found the documentation for what "State=closing" means here:

user not logged in, and not lingering, but some processes are still around

That's clearly wrong, as I was logged when I ran the loginctl command.

As a workaround I was able to set the bluetooth.target systemd service to be restarted after a suspend/resume, which also fixes the issue.

[opossalite]

I have a similar issue on Arch with bspwm. I noticed after logging out and logging back in, I cannot shut down my system without a password, it requires a sudo password. The first time I log in, I can power down no problem. This is using both "shutdown now" and "systemctl poweroff". I ran the command @markstos mentioned above, and my system also says "State=closing" after logging out and logging back in again.

[markstos]

I eventually gave up on ly and just log directly into Sway from console login prompt now. This solved all problems related to running a display manager.

[AnErrupTion]

@ThatOneCalculator @markstos @opossalite Can you guys test if the issue is fixed with master, please?

[ThatOneCalculator]

Ah, I no longer use ly, as I now use a wayland compositor and gdm ^^;

[markstos]

I no longer use Ly either.