Bug#944880: libgl1-mesa-dri: Civilization6 regression with mesa 19.2.3-1 and Radeon RX580
Hi, it's not just Civ6, but all OpenGL drivers/apps which are affected. Known issue, and fixed in the Mesa 19.2.4 emergency release: https://lists.freedesktop.org/archives/mesa-dev/2019-November/223773.html https://gitlab.freedesktop.org/mesa/mesa/issues/2072 https://www.phoronix.com/scan.php?page=news_item&px=Mesa-19.2.4-Released Regards, David
Bug#522226: xserver-xorg-video-intel: screen briefly flashes/flickers a few times an hour
On Sat, Apr 04, 2009 at 08:13:52PM -0400, Sanjoy Mahajan wrote: I'm pretty certain that what you're seeing is already reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=17805 I just read through that thread. It looks similar but I'm not too sure. The reports there were of the whole display blanking for a (short) while. Mine doesn't go blank. Instead a portion of it jitters rapidly sideways, then recovers (all under 0.1 seconds). Seen out of the corner of the eye, it looks like a flash. I'm guessing that the exact behaviour is dependent on the display hardware. I've seen the same problem manifest itself in slightly different ways when I've had the same computer (with the same driver) hooked up to a couple of different TV's via HDMI. Some react like the HDMI cable had been physically disconnected and reconnected while at least one TV never showed any (visible) problems at all... I'll either wait for a new driver to make it into Debian unstable, or compile 2.5.1 + patch myself. Is it reasonable to try the version in 'experimental'? That seems like it would be a big change to the xorg file or package layout, so I was a bit worried about using those packages. I'm using the intel driver from the experimental repo on a system otherwise using unstable without any ill effects. The problem is that even the experimental version is too old (2.6.1). Upstream has had a large number of bug fixes since then (most importantly to me - XV tearing fixes and the sync fixes we're discussing right now), so I'm hoping a more recent version will appear in experimental or unstable soon. -- David Härdeman -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522226: xserver-xorg-video-intel: screen briefly flashes/flickers a few times an hour
I'm pretty certain that what you're seeing is already reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=17805 That particular bug is fixed in later versions of the intel driver. -- David Härdeman -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#420292: xserver-xorg-video-intel: gnome-screensaver blanks screen and does not display dialog after upgrade to 2.0.0-1
I have exactly the same problem (that the driver thinks something is connected to VGA output on my laptop and gnome-screensaver decides to show its dialogue on the VGA screen). As a workaround I added this line to xsession: xrandr --output VGA --off --output LVDS --auto And after that gnome-screensaver works again. Might be something to try until the driver is fixed. -- David Härdeman
Bug#392255: Seems to be a firefox problem
After looking at the corresponding beryl bug [1], it seems that this is in fact a Firefox bug [2] [3]. [1] http://bugs.beryl-project.org/ticket/9 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=368029 [3] https://bugzilla.mozilla.org/show_bug.cgi?id=215762 -- David Härdeman
Bug#392255: compiz: Firefox autoscroll cursor leaves trailing marks
Package: compiz Version: 0.0.13+git20060928-2 Severity: normal When using the middle-mouse-button to scroll feature in Firefox, the cursor leaves trailing marks behind as you scroll. This is the same bug as reported here: https://launchpad.net/bugs/58622 -- David Härdeman
Bug#347680: Xorg breaks acpid
The problem is made worse by the fact that /etc/logrotate.d/acpid contains: postrotate /etc/init.d/acpid restart >/dev/null at which point X will lose the acpid socket connection and grab the /proc/acpi/event node instead and acpid will fail to restart. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
