On first boot, clicking 'Login' causes sway to restart #58
Labels
question
Further information is requested
Comments
|
Could you post the ReGreet logs? They should be in |
|
I have the same issue. ReGreet logsMy config
/etc/greetd/config.toml[terminal]
vt = 1
[default_session]
#command = "env XKB_DEFAULT_LAYOUT=fr cage -m last -d -s -- regreet"
command = "sway --config /etc/greetd/sway-config -d 2> /tmp/regreet-sway$(date -Ins).log"
user = "greeter"/etc/greetd/regreet.toml[GTK]
# Whether to use the dark theme
application_prefer_dark_theme = true
# Cursor theme name
cursor_theme_name = "Catppuccin-Mocha-Dark-Cursors"
# Font name and size
font_name = "Noto Sans 11"
# Icon theme name
icon_theme_name = "Papirus"
# GTK theme name
theme_name = "catppuccin-mocha-lavender-standard+default"
[commands]
# The command used to reboot the system
reboot = [ "systemctl", "reboot" ]
# The command used to shut down the system
poweroff = [ "systemctl", "poweroff" ]/etc/greetd/sway-configset $mod Mod4
input type:keyboard xkb_numlock enable
input type:keyboard xkb_layout "fr"
include /etc/sway/config.d/*
bindsym $mod+Shift+c exec bash -c "swaymsg reload && notify-send --urgency=low 'Reload success' || notify-send --urgency=critical 'Reload fail'"
exec "regreet; swaymsg exit" |
|
Can confirm I encounter the same issue, same logs Logs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
okay so I'm running into a bit of a weird issue
basically when my computer boots for the first time (or reboots) and greetd starts and launches sway to display regreet, everything looks correct
however when I click the 'login' button the first time, it causes the entire login manager to appear to restart
the logs seem to reflect this:
what's extra strange is that it's only when i click the 'login' button: I can click the dropdown for my session, or edit the session, or edit the username, it all works fine.
i've tried with gtkgreet and it does not exhibit the same behavior
might anyone know what I should look at?
The text was updated successfully, but these errors were encountered: