From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90079] drmSetMaster and drmDropMaster need root privileges
Date: Fri, 17 Apr 2015 21:11:41 +0000 [thread overview]
Message-ID: <bug-90079-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1222 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90079
Bug ID: 90079
Summary: drmSetMaster and drmDropMaster need root privileges
Product: DRI
Version: unspecified
Hardware: All
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
Assignee: dri-devel@lists.freedesktop.org
Reporter: g1938560@trbvm.com
I run a small, user-space program that renders images in my virtual console
with drmModeSetCRTC and family. I also support virtual terminal switching with
ioctl() on stuff from linux/vt.h and some basic signal handling.
Switching back to X server, however, just renders... nothing.
Apparently I'm supposed to call drmDropMaster so that X server can pick up from
there. I get -1 and errno is set to Permission Denied. When run as root, it
works as expected.
Is there any reason why these functions require root privileges?
More importantly, is there any workaround for this so that my user space
program can let X server draw its stuff once user switches back to X's virtual
terminal?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2453 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 reply other threads:[~2015-04-17 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 21:11 bugzilla-daemon [this message]
2015-04-20 1:21 ` [Bug 90079] drmSetMaster and drmDropMaster need root privileges bugzilla-daemon
2015-04-21 17:49 ` bugzilla-daemon
2019-10-14 13:20 ` 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-90079-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.