You are not logged in.
Good Day,
I have had a series of IPC client and broken pipe error resulting in sway crashing after opening alacritty terminal or firefox. Sometimes an initial command to Dmenu results in a crash. I have tried with and without GDM enabled and no observable change seems to happen. I am running a new HP OMEN 30L Desktop GT13 with a NVIDIA GeForce RTX 2060. Due to sway issues with Nvidia I am using nouveau modules only as shown below:
vim /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf
blacklist i2c_nvidia_gpuPrintout from neofetch
-` trentonknight@archALPHA
.o+` -----------------------
`ooo/ OS: Arch Linux x86_64
`+oooo: Host: OMEN 30L Desktop GT13-0xxx
`+oooooo: Kernel: 5.11.9-arch1-1
-+oooooo+: Uptime: 27 mins
`/:-:++oooo+: Packages: 1005 (pacman)
`/++++/+++++++: Shell: bash 5.1.4
`/++++++++++++++: Resolution: 2560x1080
`/+++ooooooooooooo/` WM: sway
./ooosssso++osssssso+` Theme: deepin-dark [GTK2/3]
.oossssso-````/ossssss+` Icons: Sea [GTK2/3]
-osssssso. :ssssssso. Terminal: alacritty
:osssssss/ osssso+++. CPU: AMD Ryzen 7 3700X (16) @ 3.600GHz
/ossssssss/ +ssssooo/- GPU: NVIDIA GeForce RTX 2060 Rev. A
`/ossssso+/:- -:/+osssso+- Memory: 1215MiB / 15974MiBI am able to run sway for long periods of time. Possible for days without an issue? Its only once I have performed a reboot and attempt to login using the sway command that it crashes. Normally after a few attempts it seemingly stabilizes.
trentonknight@archALPHA ~]$ lsmod | grep nouveau
nouveau 2367488 12
mxm_wmi 16384 1 nouveau
video 53248 1 nouveau
i2c_algo_bit 16384 1 nouveau
drm_ttm_helper 16384 1 nouveau
ttm 81920 2 drm_ttm_helper,nouveau
drm_kms_helper 282624 1 nouveau
wmi 36864 4 hp_wmi,wmi_bmof,mxm_wmi,nouveau
drm 569344 11 drm_kms_helper,drm_ttm_helper,ttm,nouveau
agpgart 40960 3 ttm,nouveau,drmThe below debug is being run from within sway.
trentonknight@archALPHA ~]$ sway --debug
00:00:00.000 [sway/main.c:326] Sway version 1.5.1
00:00:00.001 [sway/main.c:153] Linux archALPHA 5.11.9-arch1-1 #1 SMP PREEMPT Wed, 24 Mar 2021 18:53:54 +0000 x86_64 GNU/Linux
00:00:00.001 [sway/main.c:169] Contents of /etc/lsb-release:
00:00:00.001 [sway/main.c:153] LSB_VERSION=1.4
00:00:00.001 [sway/main.c:153] DISTRIB_ID=Arch
00:00:00.001 [sway/main.c:153] DISTRIB_RELEASE=rolling
00:00:00.001 [sway/main.c:153] DISTRIB_DESCRIPTION="Arch Linux"
00:00:00.001 [sway/main.c:169] Contents of /etc/os-release:
00:00:00.001 [sway/main.c:153] NAME="Arch Linux"
00:00:00.001 [sway/main.c:153] PRETTY_NAME="Arch Linux"
00:00:00.001 [sway/main.c:153] ID=arch
00:00:00.001 [sway/main.c:153] BUILD_ID=rolling
00:00:00.001 [sway/main.c:153] ANSI_COLOR="38;2;23;147;209"
00:00:00.001 [sway/main.c:153] HOME_URL="https://www.archlinux.org/"
00:00:00.001 [sway/main.c:153] DOCUMENTATION_URL="https://wiki.archlinux.org/"
00:00:00.001 [sway/main.c:153] SUPPORT_URL="https://bbs.archlinux.org/"
00:00:00.001 [sway/main.c:153] BUG_REPORT_URL="https://bugs.archlinux.org/"
00:00:00.001 [sway/main.c:153] LOGO=archlinux
00:00:00.001 [sway/main.c:141] LD_LIBRARY_PATH=(null)
00:00:00.001 [sway/main.c:141] LD_PRELOAD=(null)
00:00:00.001 [sway/main.c:141] PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
00:00:00.001 [sway/main.c:141] SWAYSOCK=/run/user/1000/sway-ipc.1000.962.sock
00:00:00.001 [sway/server.c:43] Preparing Wayland server initialization
00:00:00.001 [backend/wayland/backend.c:253] Creating wayland backendI have had the following errors so far. I apologize as some of the error is missing. Any guidance on pulling or creating proper sway or wayland logs would be appreciated:
date: write error: Broken pipe response0 (res 0x55de7b5d9070)sten 21 -listen 23 -wm 49e9500,00 "width": 0, "height": 0 }, "window": null, "urgent": false, "marks": [], "fullscreen_mode":1, modes": "floating_number".... "output": "HDMI-A-1"Although, it was not needed before I did set my output in the sway config due to the above error mentioning my monitor.
output HDMI-A-1 resolution 2560x1080 position 0,0Yes, I have xorg-xwayland installed
extra/xorg-xwayland 21.1.0-1 (xorg) [installed]Unfortunately, this is only one of a few error I have received. I will update this post and append the others. I appreciate any guidance anyone can offer on where to look first. I can run gnome, lxqt and gdm with zero issues or crashes. The following MarkDown file details my build on a HP OMEN 30L:
https://gitlab.com/trentonknight/custom … 0L_GT13.md
I actually went without the encryption and am using the standard linux kernel at this time to see if that affected sway in any way. It made no difference.
Last edited by trentonknight (2021-03-26 17:15:19)
Offline
I'm having similar issues with sway on Arch recently. After an update about a week ago my first login always crashes with wayland related errors. Subsequent login works. I removed GDM and used console login + sway manually and got the same issue so it's not the login/dm.
I have a bunch of apps configured to start, and I think one of them (or more) cause this. The interesting thing is it works the second time and any other time after. If I reboot first try causes a crash again.
Offline
Thank you almindor. That's comforting to know it was recent and not a permanent issue with Nvidia cards or modules. I did switch to sway-git from AUR and sway would not function at all. As you stated as of right now a second or third attempt strangely results in no issues? Hopefully, things get better before they get worse. I may need to post this on other sway related boards as well?
Offline
Thank you almindor. That's comforting to know it was recent and not a permanent issue with Nvidia cards or modules. I did switch to sway-git from AUR and sway would not function at all. As you stated as of right now a second or third attempt strangely results in no issues? Hopefully, things get better before they get worse. I may need to post this on other sway related boards as well?
I don't think this is nvidia specific either since I'm running on and AMD graphics card. It seems like either a sway bug or a [x]wayland issue.
Offline
almindor. OK, good information. That narrows it down to software most likely.
I don't think this is nvidia specific either since I'm running on and AMD graphics card. It seems like either a sway bug or a [x]wayland issue.
I have created a post on the Sway github Issues page as well here: https://github.com/swaywm/sway/issues/6142. Hopefully, we can get some underlying details from the developers. It would be interesting to see if other wayland windows managers are having similar issues. I have not seen anything as yet.
Offline
This issue appears to be with XWayland. Different Linux Distributions have had the exact same issue so this is NOT a Arch Linux issue, nor from what I can tell, an issue with the Sway windows manager. The temporary solution appears to wait a bit before launching XWayland type applications once entering sway. The Sway development members appear to be working at full speed. https://github.com/swaywm/sway/releases. I'm assuming one would need to install sway-git https://aur.archlinux.org/packages/sway-git/to retrieve the newest version on Arch Linux? I tried that today and sway would not even load at all, so I would wait on the AUR next update or build from source. Please see the response I received here from Simon Ser emersion https://github.com/emersion. The detailed Issue may be viewed here with several options for work around in the meantime: https://github.com/swaywm/sway/issues/6097. I have been able to run sway if I launch firefox first from Dmenu followed by my Alacritty terminal. Once that is accomplished sway does not appear to give me any issues. Not yet anyways.
Offline
I cannot reproduce your error, but from what I read in the linked gitgub issue, sway-git alone won't do it, you need wlroots-git, too.
so I would wait on the AUR next update or build from source.
Big misunderstanding: AUR packages with -git suffix will always fetch the latest sources, and using them means building from source.
Offline
I cannot reproduce your error, but from what I read in the linked gitgub issue, sway-git alone won't do it, you need wlroots-git, too.
so I would wait on the AUR next update or build from source.
Big misunderstanding: AUR packages with -git suffix will always fetch the latest sources, and using them means building from source.
That's great news regarding the GIT AUR packages. I was uncertain how those packages were maintained. When I used the latest git based sway-git AUR installation I did have to install several additional git based packages. I believe I was only missing three other packages, wlroots-git may have been included, and it compiled with no issues. Unfortunately, I then received strictly EGL errors and sway would not launch at all. I may try again today beginning with wlroots-git first. Thank you for your guidance Stefan.
Offline
Sorry for adding to such an old post, but i'm having this issue too. i can't get sway to run for more than 30 seconds. it freezes after like 10 seconds of typing in alacritty or immediately after trying to run dmenu. dmenu never opens it just freezes as soon as i press alt-d
I won't repost everything here but i did make a post here.
[nick@ProBook ~]$ neofetch
nick@ProBook
--------------------
OS: Arch Linux x86_64
Host: HP ProBook x360 440 G1
Kernel: 5.13.7-arch1-1
Uptime: 18 hours, 3 mins
Packages: 327 (pacman)
Shell: bash 5.1.8
Resolution: 1920x1080
Terminal: ly
CPU: Intel i5-7200U (4) @ 3.100GHz
GPU: Intel HD Graphics 620
Memory: 125MiB / 7843MiBThis was run from the shell btw so that's why it shows ly as the terminal and no wm.
Offline