From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 109150] "failed to set DRM interface version 1.4: Permission
denied" after resume for lock screen.
Date: Tue, 25 Dec 2018 15:49:30 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0788736309=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 0A8626E3BA
for ; Tue, 25 Dec 2018 15:49:30 +0000 (UTC)
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0788736309==
Content-Type: multipart/alternative; boundary="15457529690.3a46d85d.28152"
Content-Transfer-Encoding: 7bit
--15457529690.3a46d85d.28152
Date: Tue, 25 Dec 2018 15:49:29 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D109150
Bug ID: 109150
Summary: "failed to set DRM interface version 1.4: Permission
denied" after resume for lock screen.
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
Assignee: dri-devel@lists.freedesktop.org
Reporter: nanericwang@gmail.com
Created attachment 142890
--> https://bugs.freedesktop.org/attachment.cgi?id=3D142890&action=3Dedit
Xorg log before lock screen.
Everytime after resume from a lock screen (monitor suspend), I see the
following error from xorg log:
[ 20.962] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 20.962] (EE) /dev/dri/card0: failed to set DRM interface version 1.4:
Permission denied
There is no such errors at first boot (before lock screen).
My question:
- How to know what is trying to access "/dev/dri/card0"? Where is the log?
- Why it is trying to access "/dev/dri/card0", given that the xorg is start=
ed
already?
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15457529690.3a46d85d.28152
Date: Tue, 25 Dec 2018 15:49:29 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
| Bug ID |
109150
|
| Summary |
"failed to set DRM interface version 1.4: Permission den=
ied" after resume for lock screen.
|
| Product |
DRI
|
| Version |
unspecified
|
| Hardware |
Other
|
| OS |
All
|
| Status |
NEW
|
| Severity |
normal
|
| Priority |
medium
|
| Component |
libdrm
|
| Assignee |
dri-devel@lists.freedesktop.org
|
| Reporter |
nanericwang@gmail.com
|
Created attachment =
142890 [details]
Xorg log before lock screen.
Everytime after resume from a lock screen (monitor suspend), I see the
following error from xorg log:
[ 20.962] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 20.962] (EE) /dev/dri/card0: failed to set DRM interface version 1.4:
Permission denied
There is no such errors at first boot (before lock screen).
My question:
- How to know what is trying to access "/dev/dri/card0"? Where is=
the log?
- Why it is trying to access "/dev/dri/card0", given that the xor=
g is started
already?
You are receiving this mail because:
- You are the assignee for the bug.
=
--15457529690.3a46d85d.28152--
--===============0788736309==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0788736309==--