notmentaloutlaw

I was trying to reproduce this issue and I indeed experience sway crashing when using hardened_malloc. I started sway via gdb using ```shell $ gdb dbus-run-session --args /usr/bin/sway $ gdb...

I am actually building from source already as I am running gentoo. I am new to the whole debugging so I will have to find out first exactly how to...

For /etc/pam.d/swaylock I have this and it works fine. ```# # PAM configuration file for the swaylock screen locker. By default, it includes # the 'login' configuration file (see /etc/pam.d/login)...

What you could do is create a system service that sees the number of entries in faillock if its equal to 3 or greater than 3 it can run a...

Just for context my 99-usb-remove.rules in /etc/udev/rules.d/ is ``` ENV{DEVTYPE}=="usb_device", ACTION=="remove", SUBSYSTEM=="usb", ENV{idVendor}=="[redacted]", ENV{idProduct}=="[redacted]", RUN+="/path/to/script" ```

You can already do this just modify /etc/pam.d/swaylock just like you did with system-auth

Do you perhaps have a fix for 5.6? Unfortunately I am getting errors on my system

In order to setup dxvk in my wineprefix, which I created a brand new one just for yakuza-0 I did the following: ``` WINEPREFIX="/prefix/" WINEARCH="win64" WINEESYNC=1 WINEFSYNC=1 WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=2 DXVK_FRAME_RATE_LIMIT=145...

I just tried WINEDEBUG=+all and WINEDEBUG=+loaddll and I am getting no extra output other than what I said.

Maybe its due to the strip useflag in gentoo I will remove it and see if it provides a log. The thing is with +all I ran it without dxvk...