Closed rrueger closed 1 year ago
Please provide a stack trace. You can do so by compiling from source, reproducing the crash and then running coredumpctl gdb
and then bt full
.
Here are some instructions to compile from source: https://github.com/swaywm/sway/wiki/Development-Setup#compiling-as-a-subproject
Of course. Thank you.
This was created using Archlinux
using the default sway
configurations. (No user config ~/.config/sway
or ~/.config/i3
).
To create the error, I started dunst (using dunst
) and then used systemctl suspend
. After waking from suspend, any activity causes sway
to segfault.
This error can be reproduced with mako
. However, for completeness I am also posting my ~/.config/dunst/dunstrc
It is worth noting, that I am using a Dell XPS 15 9510 with a discrete nvidia graphics card. That is why I must use --unsupported-gpu
. The graphics card is almost always disabled. My sway session runs on my intel cpu/gpu.
I had a similar issue on 2 machines, both running Slackware-current with sway compiled regularly from master. One Thinkpad T590 with an external screen plugged and my desktop PC (AMD 5600x with RX6600XT, 1 screen).
On the T590 sway has been crashing for quite a long time and the desktop only more recently. (A third machine, Thinkpad x270 never experienced this crash.)
I only got so far to notice that the crash occurred going out of idle, presumably when swayidle
issue the command swaymsg "output * power on"
.
I think this has been fixed by the last commit ( https://github.com/swaywm/sway/commit/8b4b65d66552d782d2c38a17756baf928b90e670 ), at least that's what I see in my cases.
I just reinstalled to test, and I am unfortunately still experiencing the same crashes with c08762901e9840d8dca008dcc8d0b5602602fd0a (one commit later).
Seems to have been fixed by now (20ffe545bab3fe518d8d1be00949943f7d39cfe0). Closing
1.9-dev-48d6eda3 (May 24 2023, branch 'master')
archlinux
Linux <hostname> 6.3.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 21 May 2023 16:15:22 +0000 x86_64 GNU/Linux
This is a somewhat peculiar issue, however I am able to successfully replicate it.
If either
dunst
andmako
)swaylock
when the computer is suspended, I get a core segmentation fault when resuming from suspend. The screen wakes, however if I do anything to cause the content to update, e.g. move the mouse, type my password for the locker, sway crashes.
However, if I remove the
include /etc/sway/config.d/50-systemd-user.conf
line from my sway config, the issue no longer appears. Regardless of locking/notifications. I isolated thatWAYLAND_DISPLAY
seems to cause the issues here.