On Thu, Sep 11, 2025 at 1:17 PM Christoph Liebender <christ...@liebender.dev> wrote:
> On 9/11/25 15:25, Abel Abraham Camarillo Ojeda wrote: > > > > > > On Thu, Sep 11, 2025 at 4:58 AM Crystal Kolipe > > <kolip...@exoticsilicon.com <mailto:kolip...@exoticsilicon.com>> wrote: > > > > On Wed, Sep 10, 2025 at 04:22:15PM -0600, Abel Abraham Camarillo > > Ojeda wrote: > > > I have reported this since around 2 years ago, I don't think > > there's any > > > known solution/workaround. > > I know that, but I thought that after these years maybe somebody might > have a look again :) > > > > > Are you sure that it's the same bug? > > > > In your report, if I understand correctly, the issue only happens in > > X11. > > > > In Christoph's report, it happens if X11 is running, (via xenodm), > and > > the brightness is changed in any way, including from another VT using > > wsconsctl. > > I have to note here that I run wsconsctl in a terminal in X. I.e. I open > up my favorite terminal emulator, and just type doas wsconsctl ... > > > If you want to investigate it further, maybe try eliminating X11 and > see > > if the problem persists. Also, see whether there is a difference > > between > > starting X11 via xenodm and starting it manually from the console. > > > > > > You're right in my machine I can change brightness in VT with F5/F6 > > without lockups. > > Even if X11 is still running but 'hidden' via ctrl+alt+F1. > > > > In X11 I cannot change brightness without lockups via F5/F6 or > > xbacklight (I don't know other means) > > > > It seems to only happen in X11. Haven't tested without xenodm. (Can't > > test that today) > So, it happens if you change brightness outside of X11?
