Hi,
Now that the new year has started, I can finally send out this posting.
I will like to see a new maintenance release of X Server 1.19 and even older
versions over the next two months.
Over the past month, I have finally poured in significant time resources to
figure out why Xfce desktop
On Wed, Jan 02, 2019 at 01:16:22PM +0100, Jens Harms wrote:
> imho both strings "XkbLayout" and "xkb_layout" are ?currently? used. i hope
> i'm using the right repo.
both are currently used, but why we switched from XkbLayout to xkb_layout
evades my memory. Possibly because at some point udev was
> Date: Wed, 2 Jan 2019 16:31:39 +0100
> From: Hanno Böck
>
> Hi,
>
> Trying to debug a crash (in gajim) I discovered that it was due to a
> stack buffer overread in gtk+/libX11.
>
> Digging down I am not entirely sure how to interpret it and whether
> it's libX11's or GTK's fault. Here's
FIX:There is an bug in xf86nameCompare, if you compare
a zero string with a non-zero string the result is inverted.
s1=zero string, s2 = non-zero string
this should return a value less than zero but the code returns 1.
-if (!s1 || *s1 == 0) {
-if (!s2 || *s2 == 0)
-return
Hi,
Trying to debug a crash (in gajim) I discovered that it was due to a
stack buffer overread in gtk+/libX11.
Digging down I am not entirely sure how to interpret it and whether
it's libX11's or GTK's fault. Here's what's going on:
Gtk+ calls XChangeProperty where the second last parameters
The xf86PostProbe would terminate with fatal error if both fb and pci
slots were claimed at the same time, so there is no point in trying.
The opposite logic already exists in xf86ClaimFbSlot - fb slots will
not be claimed if any pci slot was claimed.
This fixes issue when (autoconfigured) fbdev
imho both strings "XkbLayout" and "xkb_layout" are ?currently? used. i hope
i'm using the right repo.
Now i try to checkout what the crazy gnome desktop is doing to my keyboard
settings, maybe i switch back to fvwm2...
Cheers,
Jens
FYI:
