-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sway 1.10 segfault crash in workspace_add_floating #8500
Comments
For what it's worth: A few times yesterday I left the machine alone to see if I could reproduce the crash. So far, I was unable to reproduce this crash. However, I did see a similar symptom of black screens / no HDMI output after manually turning on the displays and moving mouse or pressing keys on the keyboard to wake up It turns out in that case, the HDMI displays were set as disabled by Sway. I'm not sure if this state was related to the crash, but it seems possible. Running: swaymsg -t get_outputs | \
jq --color-output '.[] | { name: .name, orientation: .orientation,
scale: .scale, scale_filter: .scale_filter,
current_workspace: .current_workspace, current_mode: .current_mode,
subpixel_hinting: .subpixel_hinting, current_workspace: .current_workspace,
pos: {x: .rect.x, y: .rect.y } }' | \
less -SMFRX Returned {
"name": "HDMI-A-4",
"orientation": null,
"scale": null,
"scale_filter": null,
"current_workspace": null,
"current_mode": null,
"subpixel_hinting": null,
"pos": {
"x": 0,
"y": 0
}
}
{
"name": "HDMI-A-5",
"orientation": null,
"scale": null,
"scale_filter": null,
"current_workspace": null,
"current_mode": null,
"subpixel_hinting": null,
"pos": {
"x": 0,
"y": 0
}
} In Dec 13 15:14:51 examplehost sway[2175]: reloading config
Dec 13 15:14:51 examplehost sway[2175]: applying profile 'hdtv-extended'
Dec 13 15:14:51 examplehost sway[2175]: applying profile output 'LG Electronics LG TV SSCR2 0x01010101' on connected head 'HDMI-A-4'
Dec 13 15:14:51 examplehost sway[2175]: applying profile output 'VIZIO, Inc M601d-A3/A3R 0x01010101' on connected head 'HDMI-A-5'
Dec 13 15:14:51 examplehost sway[2175]: running command 'swaymsg focus\ output\ \'VIZIO,\ Inc\ M601d-A3/A3R\ 0x01010101\',\ workspace\ 10,\ workspace\ number\ 10\ output\ \'VIZIO,\ Inc\ M601d-A3/A3R\ 0x01010101\''
Dec 13 15:14:51 examplehost sway[2175]: running command 'swaymsg focus\ output\ \'LG\ Electronics\ LG\ TV\ SSCR2\ 0x01010101\''
Dec 13 15:14:51 examplehost sway[2175]: configuration for profile 'hdtv-extended' applied
Dec 13 15:14:51 examplehost sway[656200]: [
Dec 13 15:14:51 examplehost sway[656200]: {
Dec 13 15:14:51 examplehost sway[656200]: "success": false,
Dec 13 15:14:51 examplehost sway[656200]: "parse_error": true,
Dec 13 15:14:51 examplehost sway[656200]: "error": "Can't run this command while there's no outputs connected."
Dec 13 15:14:51 examplehost sway[656200]: }
Dec 13 15:14:51 examplehost sway[656200]: ]
Dec 13 15:15:00 examplehost sway[2175]: reloading config
Dec 13 15:15:00 examplehost sway[2175]: applying profile 'hdtv-extended'
Dec 13 15:15:00 examplehost sway[2175]: applying profile output 'LG Electronics LG TV SSCR2 0x01010101' on connected head 'HDMI-A-4'
Dec 13 15:15:00 examplehost sway[2175]: applying profile output 'VIZIO, Inc M601d-A3/A3R 0x01010101' on connected head 'HDMI-A-5'
Dec 13 15:15:00 examplehost sway[2175]: running command 'swaymsg focus\ output\ \'VIZIO,\ Inc\ M601d-A3/A3R\ 0x01010101\',\ workspace\ 10,\ workspace\ number\ 10\ output\ \'VIZIO,\ Inc\ M601d-A3/A3R\ 0x01010101\''
Dec 13 15:15:00 examplehost sway[2175]: running command 'swaymsg focus\ output\ \'LG\ Electronics\ LG\ TV\ SSCR2\ 0x01010101\''
Dec 13 15:15:00 examplehost sway[2175]: configuration for profile 'hdtv-extended' applied
Dec 13 15:15:00 examplehost sway[656856]: [
Dec 13 15:15:00 examplehost sway[656856]: {
Dec 13 15:15:00 examplehost sway[656856]: "success": false,
Dec 13 15:15:00 examplehost sway[656856]: "parse_error": true,
Dec 13 15:15:00 examplehost sway[656856]: "error": "Can't run this command while there's no outputs connected."
Dec 13 15:15:00 examplehost sway[656856]: }
Dec 13 15:15:00 examplehost sway[656856]: ] So, I added this to This forces |
Just wanted to echo I have the same issue, it only started occuring when I started using kanshi to disable my laptop screen when plugged into monitor. It seems to occur shortly after disabling my laptop monitor, but not always. Usually I have to start sway a few times then eventually it stays working till unplugged or plugged back into monitor. My laptop screen is connected to intel IGPU over eDP and my monitor is over usb-C in DP alt mode. My guess is that the issue occurs when the output is disabled and the memory is freed, then sway tries to perform some action on that monitor like opening an application there. I'll see if I can provide more info later. Hopefully I can figure out a way to reliably repro. |
Sway Version:
sway version 1.10
on Manjaro Sway Edition December 2024unstable
branch (roughly equivalent to vanilla Arch Linux)extra/sway
package version1:1.10-1
Mon 28 Oct 2024 12:56:57 AM MDT
Robin Candau <antiz@archlinux.org>
Debug Log:
sway.log
Note: The full file was
4.3GiB
!!Due to this, I have been forced to remove most of the repeating lines described below
There were
54018360
instances of a repeating log line fromswaylock
:Count of original matching log lines & file size:
The filtering in the log file happened between these delimiters:
Due to the unusually large amount of log messages from
swaylock
, I suspect thatsway
crashed related to the following state:sway
/kanshi
saw them as disconnected or disabled at the time of crash)swaylock
was running and the screen was locked at the time of crashConfiguration File:
dotfiles
repo hereswaylock
running on both screens (configs)kanshi
managing display/output profiles (configs)Stack Trace:
debuginfod
via URL:https://debuginfod.archlinux.org
FULL:
export DEBUGINFOD_URLS='https://debuginfod.archlinux.org'; sudo -E coredumpctl debug 9708
andbt full
:Description:
Started up machine, logged into
sway
session (with debug logging, since I'm on Manjarounstable
)Used the machine for a while doing some web browsing, etc...
Left machine unattended
swayidle
usedswaylock
to lock the screen, then eventually turned off output (configs)Both HDMI displays went to sleep (low power standby or screen power off)
Came back later, turned on HDMI displays
Black screen!
Remotely SSH'ed into machine to view logs & troubleshoot what happened
Saw that
sway
process PID had crashed withSIGSEGV
:Found core dump for
sway
process PID withcoredumpctl list
, and abovesway.log
The text was updated successfully, but these errors were encountered: