ddcci-driver-linux VS sway

There is an out-of-tree kernel module that exposes the DDC-CI interface as a regular brightness control, so any laptop-oriented brightness control tool will work afterwards.

Those tools use the kernel backlight system, which doesn't support external monitors out of the box. It's the same with Xorg. You can get the ddcci-backlight driver: https://gitlab.com/ddcci-driver-linux/ddcci-driver-linux/

To add to this: if you install ddcci-driver-linux GNOME should be able to control your brightness again. This removes the need for any extensions, and it's what I've been using for my monitor for the last few years.

There is an out of tree kernel module doing just that (integrating ddc/ci, the control channel for external monitor*, with the backlight system). And someone is working on upstreaming it

This is kinda a self promotion but for the brightness issue https://gitlab.com/ddcci-driver-linux/ddcci-driver-linux may fix it. Or https://gitlab.com/YusufKhanAbdulHalim/ddcci-driver-linux/-/tree/master may fix it(if the first one doesnt work use the second one).

There is an unofficial Linux kernel module that allows userspace control of brightness (in a similar way to how laptop brightness is controllable):

https://gitlab.com/ddcci-driver-linux/ddcci-driver-linux

It used to be called `-my-next-gpu-wont-be-nvidia `

https://github.com/swaywm/sway/blob/3334d11adc926c0f6d86afc4...

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.