jokeyrhyme
commented
8 months ago Okay, I tested this as a greeter, and it works just fine, no panics
When I was getting panics before, it was while trying to run it from a terminal inside a COSMIC session that was started by GDM (I cannot test this on Arch Linux without this PR, so I don't know if the PR caused this or if is was behaving like this without the PR)
I did try starting a GNOME session from cosmic-greeter and this bounces back to the greeter, with the following in the logs:
Nov 03 19:29:28 hostname gnome-session[5788]: gnome-session-binary[5788]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-session-t>
Nov 03 19:29:28 hostname gnome-session-binary[5788]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-session-tty@gnome.target not f>
Nov 03 19:29:28 hostname gnome-session[5788]: gnome-session-binary[5788]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
Nov 03 19:29:28 hostname gnome-session-binary[5788]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
Nov 03 19:29:28 hostname org.gnome.Shell.desktop[5822]: Failed to configure: Unsupported session type
Nov 03 19:29:28 hostname gnome-session[5788]: gnome-session-binary[5788]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1I assume this is nothing to do with this PR, given that I can confirm that cosmic-greeter functions perfectly well as a greeter for a COSMIC session
cargo checkandcargo build, so I assume all the other changes are related to transitive dependencies