From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94272] machinectl shell causes screen to get scrambled
Date: Fri, 26 Feb 2016 10:01:48 +0000 [thread overview]
Message-ID: <bug-94272-502-1SINQwQwT5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94272-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1244 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94272
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|Mesa |xorg
Version|11.1 |unspecified
Component|Drivers/Gallium/r600 |Server/DDX/Xorg
QA Contact|dri-devel@lists.freedesktop |xorg-team@lists.x.org
|.org |
Assignee|dri-devel@lists.freedesktop |xorg-team@lists.x.org
|.org |
--- Comment #1 from Michel Dänzer <michel@daenzer.net> ---
Looks like machinectl / polkitd is doing something funky wrt VTs: The first
time I run it, it switches away from X to an empty VT with just a blinking
cursor. However, the line
(II) AIGLX: Suspending AIGLX clients for VT switch
only appears in the Xorg log when I switch to *another* VT, so apparently the
Xorg server/driver doesn't get notified about the first VT switch. As such, it
can't really be a graphics driver issue. Reassigning to Xorg for now.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2927 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-02-26 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 0:50 [Bug 94272] machinectl shell causes screen to get scrambled bugzilla-daemon
2016-02-26 10:01 ` bugzilla-daemon [this message]
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-94272-502-1SINQwQwT5@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).