From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72732] Missing NULL check; radeon_drm_winsys.c
Date: Wed, 01 Jan 2014 01:26:19 +0000 [thread overview]
Message-ID: <bug-72732-502-8Bp0a8yPz0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72732-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72732
--- Comment #1 from Dave Gilbert <freedesktop@treblig.org> ---
OK, I believe the case that's causing it to go down this route is a perms screw
up somewhere; I was running this test in a separate X session (just logging as
a normal user on the console and running X :2 )
But with a bit of debug I'm seeing:
libGL: OpenDriver: trying /usr/lib64/dri/tls/r600_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/r600_dri.so
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: r600
[dg@major ~]$ ls -lZ /dev/dri/card0
crw-rw----+ root video system_u:object_r:dri_device_t:s0 /dev/dri/card0
[dg@major ~]$ id -Z
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
So I'm not quite sure what the perm screw up is, but that's separate - this
will seg in glxgears or anything if the drm device won't open.
Dave
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1739 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:[~2014-01-01 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 16:05 [Bug 72732] New: Missing NULL check; radeon_drm_winsys.c bugzilla-daemon
2014-01-01 1:26 ` bugzilla-daemon [this message]
2014-01-01 14:43 ` [Bug 72732] " bugzilla-daemon
2014-02-08 21:09 ` bugzilla-daemon
2019-09-18 19: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-72732-502-8Bp0a8yPz0@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