that is crazy.  E works fine with a non root account, you should only be using
su to root your machine anyway.  i've used E ever since i first started with
Linux and have never heard of this problem before.  i chat daily on #e and
have never heard of a suid root Esound problem either.  try simply removing
your ~/.enlightenment dir and letting E make a new one for you.  usually if
you screw up anything in E you can get back to where you started by removing
that directory as E uses it to cache config info, pixmaps, everything.
join #e on efnet and ask to see what some of the authors think, mandrake and
raster wrote it and they talk all the time.  a guy with the handle of ricdude wrote
esound, he might be a good person to ask about this too.  Also perhaps you
may want to try compiling the source; i've _always_ had better luck this way.

Tom K wrote:

> > from my experience, gnome is extremely stable, running 0.99.8 and I have
> > no problems, also using the latest E..
>
> Well, perhaps you could explain this to me then - I freshly installed redhat
> 5.2 with the latest (at least a week ago) GNOME rpms, including E.
> Everything worked fine until I attempted to use E under a non-root account.
> At which point, E crashed, and would then crash no matter what I logged in
> as. I asked around some about it, and someone mentioned that "E doesn't like
> running as non-root" and that it might be a permissions problem with Esound.
> I read a bunch of FAQs, didn't find anything, then just gave up and
> installed KDE as I had already spent 3 nights just getting the sound to work
> in the first place. Anyway, if anyone is clued in on what this problem is,
> I'd be interested.
>
> Tom
>
> ---------------------------------------------------------------------------
> Send administrative requests to [EMAIL PROTECTED]

--
Tom Carlile                     [EMAIL PROTECTED]

"The world is beating a path to our door"

  -- Bruce Perens



---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]

Reply via email to