Any immutable distro would do I guess

The registery is much easier to break, much harder to debug and much harder to fix, UNIX config is more human-friendly, I’ll never mess with the registery again

Yes, it’s listed in lsusb output.

Here’s svlogtail output

2025-02-12T11:59:59.37471 kern.info: [ 8726.412768] usb 4-2: new full-speed USB device number 2 using uhci_hcd 2025-02-12T11:59:59.54085 kern.info: [ 8726.578922] usb 4-2: New USB device found, idVendor=045e, idProduct=0b12, bcdDevice= 5.09 2025-02-12T11:59:59.54125 kern.info: [ 8726.578957] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2025-02-12T11:59:59.54147 kern.info: [ 8726.578974] usb 4-2: Product: Controller 2025-02-12T11:59:59.54125 kern.info: [ 8726.578957] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2025-02-12T11:59:59.54147 kern.info: [ 8726.578974] usb 4-2: Product: Controller 2025-02-12T11:59:59.54164 kern.info: [ 8726.578986] usb 4-2: Manufacturer: Microsoft 2025-02-12T11:59:59.54191 kern.info: [ 8726.578997] usb 4-2: SerialNumber: 3039564C30313733323634323337 2025-02-12T11:59:59.54164 kern.info: [ 8726.578986] usb 4-2: Manufacturer: Microsoft 2025-02-12T11:59:59.54191 kern.info: [ 8726.578997] usb 4-2: SerialNumber: 3039564C30313733323634323337 2025-02-12T12:00:00.14687 user.info: Feb 12 15:00:00 mtp-probe: checking bus 4, device 2: “/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-2” 2025-02-12T12:00:00.15166 user.info: Feb 12 15:00:00 mtp-probe: bus: 4, device: 2 was not an MTP device 2025-02-12T12:00:00.58454 kern.warn: [ 8727.623272] xone_gip: loading out-of-tree module taints kernel. 2025-02-12T12:00:00.58477 kern.notice: [ 8727.623294] xone_gip: module verification failed: signature and/or required key missing - tainting kernel 2025-02-12T12:00:00.58454 kern.warn: [ 8727.623272] xone_gip: loading out-of-tree module taints kernel. 2025-02-12T12:00:00.58477 kern.notice: [ 8727.623294] xone_gip: module verification failed: signature and/or required key missing - tainting kernel 2025-02-12T12:00:00.58454 kern.warn: [ 8727.623272] xone_gip: loading out-of-tree module taints kernel. 2025-02-12T12:00:00.58477 kern.notice: [ 8727.623294] xone_gip: module verification failed: signature and/or required key missing - tainting kernel 2025-02-12T12:00:00.70751 kern.info: [ 8727.745802] usb 4-2: reset full-speed USB device number 2 using uhci_hcd 2025-02-12T12:00:00.86144 kern.info: [ 8727.896637] usbcore: registered new interface driver xone-wired 2025-02-12T12:00:00.88730 user.info: Feb 12 15:00:00 mtp-probe: checking bus 4, device 2: “/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-2” 2025-02-12T12:00:00.88984 user.info: Feb 12 15:00:00 mtp-probe: bus: 4, device: 2 was not an MTP device

Model 1914 (the one currently used with Series S/X) I’m trying to connect it using the usb port

How do I know which? I’m using whatever is default on void

Okay I made a mistake, there’s no js entry in /dev/input

The LED is off, which means the controller isn’t connected

The LED is off and I’ve tried retroarch and a game, retroarch detects the controller but takes no input, the game didn’t detect it at all

I’ve been trying exclusively a wired connection to dodgr Bluetooth issues, the controller is detected by the system (it’s creating a /dev/input/js0) and the controller vibrates on connecting but the LED is off and no input is received on the laptop’s side

Nope, xone ain’t doing it, it’s an Xbox series controller, but it could be related to my laptop hardware being extremely outdated idk, I should’ve tried it on a different distros, it works ootb on different machines running Arch and Pop

Reinstalled the xfce build, everything works well, except my controller tho

Both bash and fish are returning incorrect password upon trying to execute any command with sudo

It says incorrect password, I’m pretty sure it is entered correctly

I’ve tried

exec dbus-run-session -- startlxqt

Nothing changed

I also tried

exec lxqt-session

It ran a broken session with no panel, I tried to sudo from there but it also said incorrect password

I looked up void docs, the only recommended thing I found was enabling elogind :/

Not even close, Proton is a translation layer from Win32 API to whatever works similar for Linux, SDL just gives a higher level API of lower level stuff, like instead of using Xorg/Wayland directly, you get a nicer cross platform API that does the job well