From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 75128] Artifacts Date: Tue, 18 Feb 2014 21:52:38 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1755416955==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 93CCCFAC0E for ; Tue, 18 Feb 2014 13:52:38 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1755416955== Content-Type: multipart/alternative; boundary="1392760358.B3B2D0.23593"; charset="us-ascii" --1392760358.B3B2D0.23593 Date: Tue, 18 Feb 2014 21:52:38 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=75128 --- Comment #5 from publicface@bak.rr.com --- I've been able to fix ksnapshot (I didn't know how to force a reinstall - now I do). So since as I mentioned I already restarted kdm (and by inference, the X server) this problem can't be further explored at this time, what other tools/procedures should I be prepared with next time it happens? screenshot /var/log/Xorg.0.log dmesg xwininfo Anything else? For the record, the reason I reported it here is due to a discussion with someone else. And I quote: "I moved away from ATi/AMD altogether to nvidia because of the constant screen corruption issues on both the open source and proprietary drivers". Since changing cards isn't an option at this time, reporting the problem is a bit easier. It doesn't happen often, but it does happen every now and then. Me personally I'm not interested in blaming anyone or anything. I don't care where the bugs are, other than in terms of getting them fixed. Since restarting kdm is almost as extreme as rebooting, I would like to see a way to reset the screen without having the net effect of being logged out. I don't know if that's something that could be accomplished in the driver, or where exactly it could be done. -- You are receiving this mail because: You are the assignee for the bug. --1392760358.B3B2D0.23593 Date: Tue, 18 Feb 2014 21:52:38 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 5 on bug 75128 from 
I've been able to fix ksnapshot (I didn't know how to force a reinstall - now I
do).  

So since as I mentioned I already restarted kdm (and by inference, the X
server) this problem can't be further explored at this time, what other
tools/procedures should I be prepared with next time it happens?

screenshot
/var/log/Xorg.0.log
dmesg
xwininfo

Anything else?

For the record, the reason I reported it here is due to a discussion with
someone else.  And I quote: "I moved away from ATi/AMD altogether to nvidia
because of the constant screen corruption issues on both the open source and
proprietary drivers".

Since changing cards isn't an option at this time, reporting the problem is a
bit easier.  It doesn't happen often, but it does happen every now and then.

Me personally I'm not interested in blaming anyone or anything.  I don't care
where the bugs are, other than in terms of getting them fixed.  Since
restarting kdm is almost as extreme as rebooting, I would like to see a way to
reset the screen without having the net effect of being logged out.  I don't
know if that's something that could be accomplished in the driver, or where
exactly it could be done.

You are receiving this mail because:
  • You are the assignee for the bug.
--1392760358.B3B2D0.23593-- --===============1755416955== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1755416955==--