Bug#856499: marked as done (Xorg crash when rotation or other transform used)
Your message dated Mon, 13 Mar 2017 13:45:01 -0600
with message-id <fd6bef70e28510e5fde8fae3821f6371@lixil.net>
and subject line 856499-done
has caused the Debian Bug report #856499,
regarding Xorg crash when rotation or other transform used
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
856499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856499
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-core
Version: 2:1.19.1-4
Severity: important
Tags: upstream
I'm experiencing random and frequent X crashes on the current stretch
version of Xorg. They occur for me using a laptop with external monitors
which are rotated. After some searching, this is a confirmed and fixed
issue with upstream. I'm filing it as important since it won't affect
everyone (only those using transforms such as rotation), but would
request consideration for it being flagged as serious to enable
incorporation of the fix into stretch, since it's far from an isolated
usage pattern.
The upstream bugzilla is below, as well as the original Fedora report
that spawned the upstream fix.
https://bugs.freedesktop.org/show_bug.cgi?id=99358
https://bugzilla.redhat.com/show_bug.cgi?id=1384486
Commit fixes
https://cgit.freedesktop.org/xorg/xserver/commit/?id=7198a6d4e74f684cb383b3e0f70dd2bae405e6e7
https://cgit.freedesktop.org/xorg/xserver/commit/?id=cfddd919cce4178baba07959e5e862d02e166522
https://cgit.freedesktop.org/xorg/xserver/commit/?id=3eb964e25243056dd998f52d3b00171b71c89189
Thanks,
Joel Johnson
--- End Message ---
--- Begin Message ---
Version: 2:1.19.2-1
The update to the 1.19.2 release includes the changes referenced in this
request. I'm therefore tagging the version and marking the bug as done.
Joel
--- End Message ---
Reply to: