Re: Bounce message including details for lots of people

2019-10-15 Thread Ken Moffat
On Tue, Oct 15, 2019 at 06:22:40PM -0700, Claus Assmann wrote: > On Wed, Oct 16, 2019, Ken Moffat wrote: > > I've received bounce messages (not unusual with my isp, they have > > "bounce messages" for mails going to this list? Those should go to > the envelope sender (xorg-boun...@lists.x.org),

Re: Bounce message including details for lots of people

2019-10-15 Thread Claus Assmann
On Wed, Oct 16, 2019, Ken Moffat wrote: > I've received bounce messages (not unusual with my isp, they have "bounce messages" for mails going to this list? Those should go to the envelope sender (xorg-boun...@lists.x.org), not some address in a header. Sounds like some broken software (geez, what

Bounce message including details for lots of people

2019-10-15 Thread Ken Moffat
I've received bounce messages (not unusual with my isp, they have severely broken commercial filters), but I was not expecting to see details of the *many* recipients who apparently bounced a message due to DMARC failures re a message from isp.net. ĸen -- Truth, in front of her huge walk-in

Re: Using Intel GPU "TearFree" option changes my detected screens / edid information

2019-10-15 Thread Chris Sorenson
I tested this on multiple machines and on both Debian 9 and 10 (with X11, not wayland). Is this a bug, or what is the explanation for this? Reply to both list an OP. I did a diff on those two xrandr outputs, there's a lot going on there. Intel is very wishy-washy about their graphics

Using Intel GPU "TearFree" option changes my detected screens / edid information

2019-10-15 Thread Seba Kerckhof
I was experiencing tearing on my Debian system. I read about the intel driver "TearFree" option and configured it as explained here: https://wiki.archlinux.org/index.php/Intel_graphics#Tearing While it does seem to help with the tearing, it changes my detected screens. By this I mean if I run

[ANNOUNCE] xf86-video-ati 19.1.0

2019-10-15 Thread Michel Dänzer
I'm pleased to announce the 19.1.0 release of xf86-video-ati, the Xorg driver for ATI/AMD Radeon GPUs supported by the radeon kernel driver. This release supports xserver versions 1.13-1.20. There are no big changes in this release, just fixes and other minor improvements. Thanks to everybody

[ANNOUNCE] xf86-video-ati 19.1.0

2019-10-15 Thread Michel Dänzer
I'm pleased to announce the 19.1.0 release of xf86-video-ati, the Xorg driver for ATI/AMD Radeon GPUs supported by the radeon kernel driver. This release supports xserver versions 1.13-1.20. There are no big changes in this release, just fixes and other minor improvements. Thanks to everybody

[Bug 112007] Broken powerplay table for Navi10 RX 5700XT.

2019-10-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=112007 Michel Dänzer changed: What|Removed |Added Assignee|xorg-driver-ati@lists.x.org |dri-devel@lists.freedesktop

[Bug 112007] Broken powerplay table for Navi10 RX 5700XT.

2019-10-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=112007 dobr...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 112007] Broken powerplay table for Navi10 RX 5700XT.

2019-10-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=112007 --- Comment #2 from dobr...@gmail.com --- Yes, thank you. That seems to fix powerplay issues. -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing list

[Bug 112007] Broken powerplay table for Navi10 RX 5700XT.

2019-10-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=112007 --- Comment #1 from Andrew Sheldon --- I've had this issue as well. You can workaround by reverting this commit: commit faa695c715e5c9203af824315127037499b33921 Author: Evan Quan Date: Mon Sep 2 12:37:23 2019 +0800 drm/amd/powerplay: