similar to: [ANNOUNCE] xorg-server 1.19.5

This is the first release candidate for xserver 1.20. Notable changes since 1.19 include: - RANDR 1.6, which enables leasing RANDR resources to a client for its exclusive use (e.g. head mounted displays) - Depth 30 support in glamor and the modesetting driver - A meson-based build system, parallel to autotools - Pageflipping support for PRIME output sinks - OutputClass device matching for

Ok, here's what I think we should release as 1.17. I plan on doing that in a few days (Monday? Tuesday?), unless there's some good reason not to. Let me know if there's some critical (i.e. crashing) fixes that I've missed somehow. And, again, I think we can run a shorter 1.18 cycle, given the pent-up list of fixes. Sorry for not getting this wrapped up sooner. Turns out that

While doing a security audit on a system I maintain, I stumbled upon an unvalidated use of a variable to compose an Originate request to the local Asterisk instance via AMI. Taking as an example an earlier exploit for FreePBX, I realized that this, combined with Application: System as an injected value, could allow arbitrary code execution. I am in the process of fixing all instances of this bug

Hi, I just had some issues with unvalidated certificates after the update of the mail/fetchmail port. The solution was to add the missing certificates manually, but that involved running the c_rehash script, that currently isn't installed. Of course, I could run it directly from src/crypto/openssl/tools/, but that isn't an option for users that don't have the source installed. So,

I am currently trying to get mcollective 2.2.4 up and running on RHEL 6 activeqm appears to be running and bound to the correct port, I see the server and client connections to the activemq box. However when I run mco ping all "seems to go well" except I get "No responses recieved" and above that I get the following log messages, debug 2013/05/29 17:02:12: activemq.rb:233:in

Changes with nginx 1.19.5 24 Nov 2020 *) Feature: the -e switch. *) Feature: the same source files can now be specified in different modules while building addon modules. *) Bugfix: SSL shutdown did not work when lingering close was used. *) Bugfix: "upstream sent frame for closed stream" errors might occur when

Изменения в nginx 1.19.5 24.11.2020 *) Добавление: ключ -e. *) Добавление: при сборке дополнительных модулей теперь можно указывать одни и те же исходные файлы в разных модулях. *) Исправление: SSL shutdown не работал при закрытии соединений с ожиданием дополнительных данных (lingering close). *) Исправление: при работе с

On Thu, Mar 29, 2018 at 04:00:04PM +0800, Jason Wang wrote: > Vq log_base is the userspace address of bitmap which has nothing to do > with IOTLB. So it needs to be validated unconditionally otherwise we > may try use 0 as log_base which may lead to pin pages that will lead > unexpected result (e.g trigger BUG_ON() in set_bit_to_user()). > > Fixes: 6b1e6cc7855b0 ("vhost:

On 8/2/20 2:47 AM, Alessandro Baggi wrote: > > Il 02/08/20 00:42, Mike McCarthy, W1NR ha scritto: >> It appears that it is affecting multiple distributions including Debian >> and Ubuntu so it looks like the grub2 team messed up. See >> >> https://www.zdnet.com/article/boothole-fixes-causing-boot-problems-across-multiple-linux-distros/ >> >> >> Mike

Some of you may recall that a few months ago I solicited advice and opinions on both R-help and R-sig-teaching about an "introduction to R" workshop I intended to present to a class of high school students enrolled in a 3-year longitudinal science research class. Much lively discussion ensued. Well, I did the workshop on 8 November, and thought I'd give some follow-up as to how it

> On Aug 2, 2020, at 9:14 AM, Gregory P. Ennis <PoMec at PoMec.Net> wrote: > > On 8/2/20 2:47 AM, Alessandro Baggi wrote: >> >> Il 02/08/20 00:42, Mike McCarthy, W1NR ha scritto: >>> It appears that it is affecting multiple distributions including Debian >>> and Ubuntu so it looks like the grub2 team messed up. See >>> >>>

On 8/2/20 2:47 AM, Alessandro Baggi wrote: > > Il 02/08/20 00:42, Mike McCarthy, W1NR ha scritto: > > It appears that it is affecting multiple distributions including Debian > > and Ubuntu so it looks like the grub2 team messed up. See > > > > https://www.zdnet.com/article/boothole-fixes-causing-boot-problems-across-multiple-linux-distros/ > > > > >

CentOS Errata and Enhancement Advisory 2018:2984 Upstream details at : https://access.redhat.com/errata/RHEA-2018:2984 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 4a9d8941e6cd3aa6466b1523f5070245e5dce2972268a5da22fc15fb20a06428 xorg-x11-server-1.19.5-5.1.el7_5.src.rpm

CentOS Errata and Security Advisory 2018:C001 Important x86_64: d7040381e9d05074c9220073c20eabe185ca6f133b0e8238f6afb250b28b566f xorg-x11-server-common-1.19.5-5.1.el7_5.0.1.x86_64.rpm ca56b7e4b160e55125ec6b1fa57c24cd2083edefa0ffd78c49bb4111ae053006 xorg-x11-server-devel-1.19.5-5.1.el7_5.0.1.i686.rpm 8c4ca5dc5588839730be5f34995f6f3b1f36c1bc335759fa936f4ddf79fd9dc7

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi Johnny, thank you for your answer. I always accepted release cycle of CentOS without any problem (maybe with EL8 but it is ok). I don't need SLA and I don't blame anyone for this, errors can occour. For example in this story, I applied blindly updates without check what and how so really I ran the command that brake my installation...and as I said no problem for this. You said:"

I've got a user with a legacy NVidia card. I've got kmod-nvidia. Last time I did an update, all I did was yum update --disableexcludes. This time, it fails, with Error: Package: nvidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 (@elrepo) Requires: xorg-x11-server-Xorg <= 1.19.99 Removing: xorg-x11-server-Xorg-1.19.5-5.el7.x86_64 (@base)

On Tue, 18 Dec 2018, mark wrote: > I've got a user with a legacy NVidia card. I've got kmod-nvidia. Last time > I did an update, all I did was yum update --disableexcludes. This time, it > fails, with > Error: Package: nvidia-x11-drv-304xx-304.135-1.el7.elrepo.x86_64 (@elrepo) > Requires: xorg-x11-server-Xorg <= 1.19.99 > Removing:

Hi all, I was trying to compile dfsan with wget. (Just enabling the dfsan feature, without actually making changes to the source code) Without dfsan, I am able to compile and run wget 1.19.5 (available at https://ftp.gnu.org/gnu/wget/wget-1.19.5.tar.gz). But when compiled with dfsan, it encountered a null pointer dereference error. Following an old post: