The only way to start sway on my computer is to remove ~/.config/sway/config and uses the system default /etc/sway/config. Otherwise, it would either print 'failed to create display', or display some garbage on my screen. Have to downgrade to 1.5 for now.
I run a custom config... A `diff -u` between the broken and working config would be helpful to see.
Here's the diff: 6a7,8 > xwayland enable > 10c12 < set $mod Mod4 --- > set $mod Mod1 17c19 < set $term alacritty --- > set $term foot 21c23,24 < set $menu dmenu_path | dmenu | xargs swaymsg exec -- --- > #set $menu bemenu-run > set $menu bemenu-run --no-exec | xargs swaymsg exec systemd-cat -- 26c29 < output * bg /usr/share/backgrounds/sway/Sway_Wallpaper_Blue_1920x1080.png fill --- > output * bg ~/Pictures/LabMemWordline_HD_WallpaperBG.png fill 45a49,52 > exec swayidle -w \ > timeout 300 'swaylock -f -c 000000' \ > timeout 600 'swaymsg "output * dpms off"' resume 'swaymsg "output * dpms on"' \ > before-sleep 'swaylock -f -c 000000' 83a91,92 > bindsym $mod+ctrl+Shift+l exec swaylock -f -c 000000 > 198a208,226 > bindsym XF86MonBrightnessDown exec sudo light -U 2 > bindsym XF86MonBrightnessUp exec sudo light -A 4 > > bindsym XF86AudioRaiseVolume exec pactl set-sink-volume @DEFAULT_SINK@ +5% > bindsym XF86AudioLowerVolume exec pactl set-sink-volume @DEFAULT_SINK@ -5% > > # > # Screen capture > # > set $ps1 Print > set $ps2 Control+Print > set $ps3 Alt+Print > set $ps4 Alt+Control+Print > > bindsym $ps1 exec grim - | wl-copy > bindsym $ps2 exec grim -g "$(slurp)" - | wl-copy > bindsym $ps3 exec grim Pictures/Screenshot/ps_$(date +"%Y%m%d%H%M%S").png > bindsym $ps4 exec grim -g "$(slurp)" Pictures/Screenshot/ps_$(date +"%Y%m%d%H%M%S").png > 208c236,238 < status_command while date +'%Y-%m-%d %l:%M:%S %p'; do sleep 1; done --- > #status_command exec while echo; do sleep 1; done > #status_command exec tee /tmp/swaystatus-input | swaystatus ~/.config/sway/swaystatus_config.json 2>/tmp/swaystatus_stderr > status_command exec swaystatus ~/.config/sway/swaystatus_config.json 2>/tmp/swaystatus_stderr
Hmm, I'm not seeing anything obvious. I'd start, one line at a time, to make the files identical. Then once the config works, make the last change that seemed to 'fix' it to your original config file and test to make sure the change was the fix.
I tried, but it doesn't help much. Even with all these different comment out and status_command set to `while echo; do sleep 1; done`, sway still couldn't start.
(In reply to Jiahao_XU from comment #4) > I tried, but it doesn't help much. > > Even with all these different comment out and status_command set to `while > echo; do sleep 1; done`, sway still couldn't start. Have you resolved this? I am inclined to close the bug as the default config shipped with it works.
I have asked this problem on [here](https://github.com/swaywm/sway/issues/6408) and getted my reply: > The nouveau issues should be fixed with wlroots 0.14.1.
Sorry the comment was cut off, the replybwas: > The nouveau issues should be fixed with wlroots 0.14.1
