| 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?
Created attachment 142891 [details]
xorg log after resume from lock screen (monitor suspended)
| What | Removed | Added |
|---|---|---|
| Attachment #142890 mime type | text/x-log | text/plain |
| What | Removed | Added |
|---|---|---|
| Attachment #142891 mime type | text/x-log | text/plain |
The log says systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration Thus the FD is handled manually and for some reason fails on your end. Norm= ally I would suggest adding the -keeptty. If that's not an option please bisect which project/commit cause this issue - kernel, libdrm or Xorg.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/mesa/drm/issues/26.