sway: Sway 1.0-beta.1 freezes system on startup on void linux
- Sway Version:
sway version 1.0-beta.1 (Oct 29 2018, branch 'HEAD') - Debug Log: sway.log
- Configuration File: default
I compiled the latest release from github:
git clone https://github.com/swaywm/sway && cd sway
git checkout 1.0-beta.1
meson build
ninja -C build
sudo ninja -C build install
sudo chmod a+s /usr/local/bin/sway
Running sway causes the system to freeze.
SysRq does still work, however, which may mean that it is just crashing the graphics driver (I am not sure whether this is true, or how to test for it).
Extra info (I’m not sure whether any of this might be useful):
- I am running
void linuxwithmusl libc wlroots-develis installed withxbpsversionwlroots-devel-0.1_2- I have 2 GPU’s (amd and nvidia)
running with
WLR_DRM_DEVICEStocard0orcard1set causes the program to return having found no GPUs swaycard.log even though they are is/dev/dri
$ ls /dev/dri
by-path card0 card1 renderD128 renderD129
- cards are using
amdgpuandnouveaudrivers respectivelly
$ lspci -nnk
07:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:8c93]
Kernel driver in use: nouveau
Kernel modules: nouveau
09:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1002:67ef] (rev e5)
Subsystem: Gigabyte Technology Co., Ltd Device [1458:230a]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
installed xbps driver versions are mesa-ati-dri-18.2.3_1 and mesa-nouveau-dri-18.2.3_1
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 19 (8 by maintainers)
When you don’t have logind, sway needs root privileges to become DRM master. In this situation, we start as root, become DRM master and then drop privileges. However sometimes dropping root fails. Instead of running the whole compositor as root, we prefer to fail.
@catb0t thanks for the program, but unfortunatelly the output produced is still the same. In fact, I managed to reproduce the same issue with a piece of assembler code which only performed the mentioned setuid calls. I think this is a problem with my kernel and will report it to the
voiddevelopers.As for
sway, if I comment the last check out and recompile the code, it seems to work just fine. Therefore, I suggest to close this issue as the problem is beyond the scope ofsway.