From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93879] kernel 4.4.0 causes application lockup and unusable interfaces with radeon hardware
Date: Wed, 27 Jan 2016 04:47:26 +0000 [thread overview]
Message-ID: <bug-93879-502-KZ1ifT1Gy9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93879-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 629 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93879
--- Comment #3 from Franklin Titus <cygnix@openmailbox.org> ---
I am having similar issue on AMD HD 7870 GPU, openSUSE Tumbleweed, and Kernel
4.4.0-1.2. I cannot say for sure the trigger, however, once the screen locks
requiring a password, the password field becomes disabled although mouse and
keyboard remain fully functional. In fact, it would seem the entire lock screen
becomes unresponsive to both mouse and keyboard, and CTRL+ALT+Backspace needs
to be employed in order to restart the session.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1467 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 prev parent reply other threads:[~2016-01-27 4:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 4:10 [Bug 93879] kernel 4.4.0 causes application lockup and unusable interfaces with radeon hardware bugzilla-daemon
2016-01-27 4:22 ` bugzilla-daemon
2016-01-27 4:29 ` bugzilla-daemon
2016-01-27 4:47 ` bugzilla-daemon [this message]
2016-01-27 6:33 ` bugzilla-daemon
2016-01-27 19:06 ` bugzilla-daemon
2016-01-27 19:30 ` bugzilla-daemon
2016-01-28 6:45 ` bugzilla-daemon
2016-01-28 7:02 ` bugzilla-daemon
2016-01-28 11:00 ` bugzilla-daemon
2016-01-28 23:00 ` bugzilla-daemon
2016-01-29 6:48 ` bugzilla-daemon
2019-11-19 9:12 ` 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-93879-502-KZ1ifT1Gy9@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).