On Tue, 23 Jan 2024, Mark Hills wrote:
> On Tue, 23 Jan 2024, Jaimos Skriletz wrote:
>
> > On Tue, Jan 23, 2024 at 6:07 AM Mark Hills wrote:
> > >
> > > I'm experiencing rare (but annoying) whole X session crashes, since
> > > mid-2023.
> > >
&
On Tue, 23 Jan 2024, Jaimos Skriletz wrote:
> On Tue, Jan 23, 2024 at 6:07 AM Mark Hills wrote:
> >
> > I'm experiencing rare (but annoying) whole X session crashes, since
> > mid-2023.
> >
>
> There was a change in libX11 that caused fvwm crashes due to even
I'm experiencing rare (but annoying) whole X session crashes, since
mid-2023.
To my surprise it turns out to be FVWM exiting on SIGABRT.
I was able to make these crashes more likely by exercising Chromium
screen-scraping, Firefox playing YouTube, whilst iconifying a small
window. And do so
On Mon, 26 Jul 2021, Tom Horsley wrote:
> On Mon, 26 Jul 2021 10:15:08 +0100 (BST)
> Mark Hills wrote:
>
> > Is there some kind of X event that fvwm can respond to when a new USB
> > input device is plugged in?
>
> You could check out the silly program I wrote to ha
On Mon, 26 Jul 2021, Dominique Michel wrote:
> Le Mon, 26 Jul 2021 10:15:08 +0100 (BST),
> Mark Hills a écrit :
>
> > My keyboard and mouse are on a USB hub, powered on/off separately.
> > I'm tired of having to manually re-run a script every time I return
> > to wor
Is there some kind of X event that fvwm can respond to when a new USB
input device is plugged in?
Because I recently switched from using CorePointer/CoreKeyboard in the
xorg.conf, to the 'modern' hot plugging of X devices.
However, now the settings of keyboard and mouse return to the default
