dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75128] Artifacts
Date: Tue, 18 Feb 2014 21:52:38 +0000	[thread overview]
Message-ID: <bug-75128-502-MsZGf75Rsb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75128-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1348 bytes --]

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.

[-- Attachment #1.2: Type: text/html, Size: 2035 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-02-18 21:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18  1:51 [Bug 75128] New: Artifacts bugzilla-daemon
2014-02-18  3:36 ` [Bug 75128] Artifacts bugzilla-daemon
2014-02-18  4:34 ` bugzilla-daemon
2014-02-18  4:39 ` bugzilla-daemon
2014-02-18  7:43 ` bugzilla-daemon
2014-02-18 21:52 ` bugzilla-daemon [this message]
2014-04-16  7:04 ` bugzilla-daemon
2014-04-16  7:06 ` bugzilla-daemon
2014-04-16  7:07 ` bugzilla-daemon
2014-04-16  7:15 ` bugzilla-daemon
2014-05-25  2:09 ` bugzilla-daemon
2014-05-25  2:10 ` bugzilla-daemon
2014-05-25  2:12 ` bugzilla-daemon
2014-05-25  2:15 ` bugzilla-daemon
2014-05-25  2:23 ` bugzilla-daemon
2014-05-25  2:33 ` bugzilla-daemon
2014-05-27  3:49 ` bugzilla-daemon
2014-05-27  7:59 ` bugzilla-daemon
2014-05-27  9:57 ` bugzilla-daemon
2019-09-18 18:52 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-75128-502-MsZGf75Rsb@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox