From: Richard Hughes <ee21rh@surrey.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: OpenOffice crashes due to incorrect access permissions on /dev/dri/card*
Date: Sat, 29 Jan 2005 12:49:16 +0000 [thread overview]
Message-ID: <pan.2005.01.29.12.49.13.177016@surrey.ac.uk> (raw)
In-Reply-To: <E1CurmR-0000H8-00@calista.eckenfels.6bone.ka-ip.net>
On Sat, 29 Jan 2005 13:32:47 +0100, Bernd Eckenfels wrote:
> it is not a permission thing, it tells you, that you have not card14 - and i
> dont know the dri interface but it looks unlikely that there ever will be
> one .)
I figured (maybe incorrectly) that oo was just going thru the dri card*
files:
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card8", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card9", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card10", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card11", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card12", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card13", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
geteuid32() = 500
stat64("/dev/dri", {st_mode=S_IFDIR|0755, st_size=80, ...}) = 0
stat64("/dev/dri/card14", 0xbfec2e8c) = -1 ENOENT (No such file or directory)
munmap(0x9b4838, 8192) = -1 EINVAL (Invalid argument)
munmap(0x9d55248, 3219928560) = -1 EINVAL (Invalid argument)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
from 0 to 14 until it found a card that it could use. The root cause
has to be that it can't use dri/card* because of access permissions.
Note, that strace glxgears gives exactly the same output, going from 0 to
14 and then seg-faulting, so it's *not just a oo problem*.
Richard Hughes
--
http://www.hughsie.com/PUBLIC-KEY
next prev parent reply other threads:[~2005-01-29 12:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 16:56 [Bug 4081] New: OpenOffice crashes while starting due to a threading error Martin J. Bligh
2005-01-22 17:33 ` Matthias-Christian Ott
2005-01-23 2:05 ` Felipe Alfaro Solana
2005-01-23 9:31 ` Matthias-Christian Ott
2005-01-23 2:38 ` Randy.Dunlap
2005-01-23 12:22 ` Martin Josefsson
2005-01-26 21:25 ` Stephen Hemminger
2005-01-27 3:14 ` Parag Warudkar
2005-01-27 17:54 ` Trever L. Adams
2005-01-27 23:49 ` Parag Warudkar
2005-01-28 2:38 ` Trever L. Adams
2005-01-28 17:31 ` Stephen Hemminger
2005-01-28 23:11 ` Parag Warudkar
2005-01-28 23:21 ` Lee Revell
[not found] ` <41FACEC5.6070703@comcast.net>
2005-01-28 23:57 ` Stephen Hemminger
2005-01-29 10:44 ` Richard Hughes
2005-01-29 12:32 ` Bernd Eckenfels
2005-01-29 12:49 ` Richard Hughes [this message]
2005-01-29 13:02 ` OpenOffice crashes due to incorrect access permissions on /dev/dri/card* Richard Hughes
2005-01-29 17:40 ` Alessandro Suardi
2005-01-29 19:25 ` Jon Smirl
2005-01-29 19:57 ` Trever L. Adams
2005-01-31 2:34 ` Trever L. Adams
2005-01-29 20:36 ` Lee Revell
2005-01-29 20:40 ` Dr. David Alan Gilbert
2005-01-29 20:48 ` Lee Revell
2005-01-29 20:57 ` Parag Warudkar
2005-01-29 21:05 ` DRI (was Re: OpenOffice crashes due to incorrect access permissions on /dev/dri/card*) Lee Revell
2005-01-29 23:16 ` Dave Airlie
2005-01-29 20:40 ` OpenOffice crashes due to incorrect access permissions on /dev/dri/card* Gene Heskett
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=pan.2005.01.29.12.49.13.177016@surrey.ac.uk \
--to=ee21rh@surrey.ac.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®