All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 56405] New: Distorted graphics on Radeon HD 6620G
Date: Thu, 25 Oct 2012 17:37:25 +0000	[thread overview]
Message-ID: <bug-56405-502@http.bugs.freedesktop.org/> (raw)


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

https://bugs.freedesktop.org/show_bug.cgi?id=56405

          Priority: medium
            Bug ID: 56405
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Distorted graphics on Radeon HD 6620G
          Severity: critical
    Classification: Unclassified
                OS: Linux (All)
          Reporter: mdrslmr@t-online.de
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: Drivers/DRI/Radeon
           Product: Mesa

Created attachment 69083
  --> https://bugs.freedesktop.org/attachment.cgi?id=69083&action=edit
Distorted graphics

On my dell vostro laptop I get distorted graphics. I use Gnome3 shell.

See attached screen shot.

The kernel used is 3.6.3-1-ARCH.   

I found the problem is apparent with the versions 9.0-1 of ati-dri and
libgl and is not seen when I downgrade to the versions:

ati-dri-8.0.4-3-x86_64.pkg.tar.xz
libgl-8.0.4-3-x86_64.pkg.tar.xz

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2447 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

             reply	other threads:[~2012-10-25 17:37 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25 17:37 bugzilla-daemon [this message]
2012-10-25 17:48 ` [Bug 56405] Distorted graphics on Radeon HD 6620G bugzilla-daemon
2012-10-25 18:57 ` bugzilla-daemon
2012-10-26 18:47 ` bugzilla-daemon
2012-10-26 18:49 ` bugzilla-daemon
2012-10-26 19:02 ` bugzilla-daemon
2012-10-26 19:18 ` bugzilla-daemon
2012-10-26 20:39 ` bugzilla-daemon
2012-10-28 21:46 ` bugzilla-daemon
2012-11-01 17:16 ` bugzilla-daemon
2012-11-02 12:06 ` bugzilla-daemon
2012-11-03  4:58 ` bugzilla-daemon
2012-11-03 18:38 ` bugzilla-daemon
2012-11-03 18:39 ` bugzilla-daemon
2012-11-06 10:00 ` bugzilla-daemon
2012-11-06 20:51 ` bugzilla-daemon
2012-11-07  9:22 ` bugzilla-daemon
2012-11-09 18:28 ` bugzilla-daemon
2012-11-09 19:43 ` bugzilla-daemon
2012-11-09 19:48 ` bugzilla-daemon
2012-11-12 16:40 ` bugzilla-daemon
2012-11-19 20:06 ` bugzilla-daemon
2012-11-19 21:30 ` bugzilla-daemon
2012-11-20  8:34 ` bugzilla-daemon
2012-11-20 18:18 ` bugzilla-daemon
2012-11-20 18:19 ` bugzilla-daemon
2012-11-20 18:43 ` bugzilla-daemon
2012-11-20 19:14 ` bugzilla-daemon
2012-11-20 19:21 ` bugzilla-daemon
2012-11-20 19:27 ` bugzilla-daemon
2012-11-20 19:33 ` bugzilla-daemon
2012-11-20 19:38 ` bugzilla-daemon
2012-11-21  7:29 ` bugzilla-daemon
2012-11-21 10:58 ` bugzilla-daemon
2012-11-22 20:02 ` bugzilla-daemon
2012-11-22 20:04 ` bugzilla-daemon
2012-11-24 13:02 ` bugzilla-daemon
2012-11-26  3:08 ` bugzilla-daemon
2012-11-26 19:51 ` bugzilla-daemon
2012-11-26 19:55 ` bugzilla-daemon
2012-12-01  9:37 ` bugzilla-daemon
2012-12-01 14:11 ` bugzilla-daemon
2012-12-10 17:42 ` bugzilla-daemon
2012-12-10 18:09 ` bugzilla-daemon
2012-12-10 18:25 ` bugzilla-daemon
2012-12-10 18:46 ` bugzilla-daemon
2012-12-10 19:22 ` bugzilla-daemon
2012-12-11  6:12 ` bugzilla-daemon
2012-12-12 14:16 ` bugzilla-daemon
2012-12-12 14:19 ` bugzilla-daemon
2012-12-13  8:38 ` bugzilla-daemon
2012-12-13 14:17 ` bugzilla-daemon
2012-12-22  0:52 ` bugzilla-daemon
2012-12-22  9:19 ` bugzilla-daemon
2012-12-24 20:27 ` bugzilla-daemon
2012-12-24 21:40 ` bugzilla-daemon
2013-01-04 17:58 ` bugzilla-daemon
2013-02-19  1:45 ` bugzilla-daemon
2013-02-19  1:46 ` bugzilla-daemon
2013-02-19  1:48 ` 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-56405-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.