From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36934] screen corruption after running a game
Date: Sat, 22 Oct 2011 11:12:01 +0000 [thread overview]
Message-ID: <bug-36934-502-dfiE733tBL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-36934-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=36934
--- Comment #13 from auxsvr@gmail.com 2011-10-22 04:12:01 PDT ---
Apparently, there are two kinds of corruption in my case.
The first one is triggered by display of large pixmaps or textures, and
manifests itself with corruption of fonts, menus, decorations, icons and
widgets all over the screen. It is easy to trigger this by scrolling quickly
through a PDF file in okular, or after running Google earth or a game. After
some tests for several hours, it appears that the cause is the Virtualbox
kernel modules. In fact, after removing them, I haven't been able to trigger
this type of corruption again.
The second one is the one manifested in Firefox with large pixmaps, described
in comment 9. If I open that image in Firefox and magnify it to 1:1, then it
appears black. Returning to the original magnification makes it appear partly
corrupted with the contents of other windows (I'm using kwin with compositing).
Opening and zooming the same image in Chrome does not exhibit the corruption. I
haven't found a way to resolve this yet.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-10-22 11:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 13:48 [Bug 36934] New: screen corruption after running a game through wine bugzilla-daemon
2011-05-09 11:41 ` [Bug 36934] " bugzilla-daemon
2011-05-13 10:36 ` bugzilla-daemon
2011-05-13 10:37 ` bugzilla-daemon
2011-05-13 10:38 ` bugzilla-daemon
2011-06-04 19:21 ` [Bug 36934] screen corruption after running a game bugzilla-daemon
2011-08-03 12:22 ` bugzilla-daemon
2011-08-09 10:16 ` bugzilla-daemon
2011-08-09 10:16 ` bugzilla-daemon
2011-08-09 10:16 ` bugzilla-daemon
2011-08-09 10:34 ` bugzilla-daemon
2011-08-09 19:39 ` bugzilla-daemon
2011-08-30 21:51 ` bugzilla-daemon
2011-08-31 10:44 ` bugzilla-daemon
2011-09-13 21:59 ` bugzilla-daemon
2011-10-18 16:00 ` bugzilla-daemon
2011-10-22 11:12 ` bugzilla-daemon [this message]
2011-10-22 13:11 ` bugzilla-daemon
2011-10-22 14:00 ` bugzilla-daemon
2011-10-23 8:49 ` bugzilla-daemon
2011-10-28 18:26 ` bugzilla-daemon
2013-03-08 20:11 ` bugzilla-daemon
2014-05-24 20:45 ` 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-36934-502-dfiE733tBL@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.