dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69062] New: Corrupted visuals in Gnome3 (A6-4400M)
Date: Sat, 07 Sep 2013 01:42:29 +0000	[thread overview]
Message-ID: <bug-69062-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 69062
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Corrupted visuals in Gnome3 (A6-4400M)
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: lrn1986@gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: DRI CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 85385
  --> https://bugs.freedesktop.org/attachment.cgi?id=85385&action=edit
Corrupted shell

On boot gdm3 looks fine (displays a list of users).
When i choose a user from the list, the animation plays out - and that's when
the corruption starts (missing text and missing graphics).
I can still log in by typing the password.
Once logged in, gnome shell looks fine at first. Opening the Activities screen
might cause minor corruption (for example, hovering over icons on the left
panel might show corrupted selection rectangle fadein). Typing in the
Activities screen _always_ causes major corruption in visuals.
Only Gnome shell (top bar, Activities, window switcher) is affected.
Applications continue to be drawn correctly.

Gnome shell reset (Alt+F2, r) cleans up corruption from the shell (completely
or almost completely), but it quickly returns.

Tried changing radeon.gartsize on boot - no difference.

No errors on Xorg.log
No errors in dmesg

This is a regression (things used to work ~half a year ago)

Versions:
 *Gnome3
  3.8
  Debian sid/experimental

 *kernel:
  git://people.freedesktop.org/~airlied/linux
  86a7e1224a68511d3a1ae0b7e11581b9d37723ae
  (also tried older kernels, as far as 3.8rc4 - same thing, this doesn't seem
to be kernel-dependent)

 *drm
  git://anongit.freedesktop.org/git/mesa/drm
  d18cd0c7ccf88c9f6585aaa3cc57f0f064d7310b

 *mesa
  git://anongit.freedesktop.org/git/mesa/mesa
  505fad04f10eee1efdfcd8986b4d484b49d39986

 *xorg (radeon driver, xserver, and its dependencies)
  git
  latest versions on 06.09.2013

A screenshot is attached.

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

[-- Attachment #1.2: Type: text/html, Size: 3578 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:[~2013-09-07  1:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07  1:42 bugzilla-daemon [this message]
2013-09-07  1:42 ` [Bug 69062] Corrupted visuals in Gnome3 (A6-4400M) bugzilla-daemon
2013-09-07  1:43 ` bugzilla-daemon
2013-09-07  1:43 ` bugzilla-daemon
2013-09-09 15:46 ` bugzilla-daemon
2013-09-09 16:09 ` bugzilla-daemon
2013-09-09 16:17 ` bugzilla-daemon
2013-09-09 16:34 ` bugzilla-daemon
2013-09-12  9:50 ` bugzilla-daemon
2019-11-19  8:38 ` 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-69062-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).