Bug 109150

Summary: "failed to set DRM interface version 1.4: Permission denied" after resume for lock screen.
Product: DRI Reporter: nanericwang
Component: libdrmAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log before lock screen.
none
xorg log after resume from lock screen (monitor suspended) none

Description nanericwang 2018-12-25 15:49:30 UTC
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 xorg is started already?
Comment 1 nanericwang 2018-12-25 15:50:23 UTC
Created attachment 142891 [details]
xorg log after resume from lock screen (monitor suspended)
Comment 2 Emil Velikov 2019-02-07 18:09:06 UTC
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. Normally I would suggest adding the -keeptty. If that's not an option please bisect which project/commit cause this issue - kernel, libdrm or Xorg.
Comment 3 GitLab Migration User 2019-09-24 17:09:34 UTC
-- 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.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.