From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76559] New: screen corruption after going from VT to X
Date: Mon, 24 Mar 2014 16:31:37 +0000 [thread overview]
Message-ID: <bug-76559-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1086 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=76559
Priority: medium
Bug ID: 76559
Assignee: dri-devel@lists.freedesktop.org
Summary: screen corruption after going from VT to X
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: fabio.ped@libero.it
Hardware: x86 (IA32)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
I have a MacBook Pro with a RV530 with an external Philips 22" monitor
connected (the notebook screen is disabled in X). After switching to VT and
then coming back to X the screen is corrupted (like if every odd line has an
offset). The same happens after suspend. A screenshot doesn't show the problem.
I then usually change resolution with the Ubuntu tool (selecting a different
resolution and then reapplying the previous one) and that restore the screen.
Attached dmesg and Xorg log after the X -> VT -> X cycle.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2395 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
next reply other threads:[~2014-03-24 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 16:31 bugzilla-daemon [this message]
2014-03-24 16:32 ` [Bug 76559] screen corruption after going from VT to X bugzilla-daemon
2014-03-24 16:33 ` bugzilla-daemon
2014-04-09 13:46 ` bugzilla-daemon
2015-09-02 7:46 ` bugzilla-daemon
2015-09-02 13:34 ` bugzilla-daemon
2015-09-02 13:47 ` bugzilla-daemon
2019-10-14 13:20 ` 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-76559-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