All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Trever L. Adams" <tadams-lists@myrealbox.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: linux-kernel@vger.kernel.org, ee21rh@surrey.ac.uk
Subject: Re: OpenOffice crashes due to incorrect access permissions on /dev/dri/card*
Date: Sun, 30 Jan 2005 19:34:30 -0700	[thread overview]
Message-ID: <1107138870.3398.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1107028644.5718.3.camel@localhost.localdomain>

My problem is some things changed in the installed package changed and
some things in my home directory in .openoffice (setup and soffice) were
incorrect. I erased the symlinks and my problem is over.  I would
suggest others having problems try the same. This may have NOTHING to do
with the kernel (as in my case).

Trever

On Sat, 2005-01-29 at 12:57 -0700, Trever L. Adams wrote:
> For the record, this has nothing to do with my crash. Mine still crashes
> all the time if I try to save a new document.
> 
> Trever
> 
> On Sat, 2005-01-29 at 14:25 -0500, Jon Smirl wrote:
> > On Sat, 29 Jan 2005 13:02:51 +0000, Richard Hughes <ee21rh@surrey.ac.uk> wrote:
> > > On Sat, 29 Jan 2005 12:49:16 +0000, Richard Hughes wrote:
> > > > 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*.
> > > 
> > > I know it's bad to answer your own post, but here goes.
> > > 
> > > I changed my /etc/udev/permissions.d/50-udev.permissions config to read:
> > > 
> > > dri/*:root:root:0666
> > > 
> > > changing it from
> > > 
> > > dri/*:root:root:0660
> > > 
> > > And oowriter and glxgears work from bootup. Shall I file a bug with udev?
> > 
> > Your user ID needs to belong to group DRI.
> > 
> --
> Legal Warning: Anyone sending me unsolicited/commercial email WILL be
> charged a $100 proof-reading fee. See US Code Title 47,
> Sec.227(a)(2)(B), Sec.227(b)(1)(C) and Sec.227(b)(3)(C).
--
"The Master doesn't talk, he acts. When his work is done, the people
say, 'Amazing: we did it, all by ourselves!'" -- Lao-tzu


  reply	other threads:[~2005-01-31  2:34 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                     ` OpenOffice crashes due to incorrect access permissions on /dev/dri/card* Richard Hughes
2005-01-29 13:02                       ` 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 [this message]
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=1107138870.3398.3.camel@localhost.localdomain \
    --to=tadams-lists@myrealbox.com \
    --cc=ee21rh@surrey.ac.uk \
    --cc=jonsmirl@gmail.com \
    --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 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.