On Tue, 2011-12-13 at 07:04 -0800, Dustin Jenkins wrote:
> Did this ever get resolved? I've had this problem since day one, it's
> weird, but I've kind of gotten used to it now. The thought of fixing it
> is nice, however.
>
> What are the proper permissions on sysactions.conf exactly?
>
> Th
On Dec 13, 2011, at 9:58 PM, Carsten Haitzler (The Rasterman) wrote:
> On Tue, 13 Dec 2011 19:52:02 -0500 mh said:
>
>>
>> On Dec 13, 2011, at 6:48 PM, Carsten Haitzler (The Rasterman) wrote:
>>
>>> On Tue, 13 Dec 2011 15:33:20 -0500 mh said:
>>>
To fix this, tested on Debian Sid thoug
On Tue, 13 Dec 2011 19:52:02 -0500 mh said:
>
> On Dec 13, 2011, at 6:48 PM, Carsten Haitzler (The Rasterman) wrote:
>
> > On Tue, 13 Dec 2011 15:33:20 -0500 mh said:
> >
> >> To fix this, tested on Debian Sid thought I suppose it works on other
> >> versions, edit the sysactions.conf file. B
On Dec 13, 2011, at 6:48 PM, Carsten Haitzler (The Rasterman) wrote:
> On Tue, 13 Dec 2011 15:33:20 -0500 mh said:
>
>> To fix this, tested on Debian Sid thought I suppose it works on other
>> versions, edit the sysactions.conf file. Below the line that says "# root is
>> allowed…", add your us
On Tue, 13 Dec 2011 15:33:20 -0500 mh said:
> To fix this, tested on Debian Sid thought I suppose it works on other
> versions, edit the sysactions.conf file. Below the line that says "# root is
> allowed…", add your username as below:
>
> # root is allowed to do anyting - but it needs to be he
To fix this, tested on Debian Sid thought I suppose it works on other versions,
edit the sysactions.conf file. Below the line that says "# root is allowed…",
add your username as below:
# root is allowed to do anyting - but it needs to be here explicitly anyway
user: root
Nope never got this resolved on the Debian system.
On Tue, Dec 13, 2011 at 9:04 AM, Dustin Jenkins wrote:
> Did this ever get resolved? I've had this problem since day one, it's
> weird, but I've kind of gotten used to it now. The thought of fixing it
> is nice, however.
>
> What are the prope
Did this ever get resolved? I've had this problem since day one, it's
weird, but I've kind of gotten used to it now. The thought of fixing it
is nice, however.
What are the proper permissions on sysactions.conf exactly?
Thanks,
Dustin
On 21/11/2011 12:29 AM, Robert Krambovitis wrote:
> On
On Sun, 2011-11-20 at 21:18 -0600, Jeff Hoogland wrote:
> .xsession-errors has four "Error: Unable to Assume Root Privileges" which I
> am assuming is related to my issue at hand.
>
> Running *sudo ldconfig *didn't fix anything.
>
> other ideas?
>
> On Sun, Nov 20, 2011 at 8:41 PM, Carsten Haitz
On Sun, 20 Nov 2011 21:18:28 -0600 Jeff Hoogland said:
well that means that enlightenment_sys is now setuid and/or not owned by root
OR that somehow your distro has some security setup that is barring setuid
(root) apps unless whitelisted or something.
> .xsession-errors has four "Error: Unable
.xsession-errors has four "Error: Unable to Assume Root Privileges" which I
am assuming is related to my issue at hand.
Running *sudo ldconfig *didn't fix anything.
other ideas?
On Sun, Nov 20, 2011 at 8:41 PM, Carsten Haitzler wrote:
> On Sun, 20 Nov 2011 20:07:06 -0600 Jeff Hoogland
> said:
On Sun, 20 Nov 2011 20:07:06 -0600 Jeff Hoogland said:
> So for some reason my normal users on a Debian based system with E can only
> "lock" or "log out" from the system screen. I had this issue awhile back
> under Ubuntu based systems and the solution then was to set the proper
> permissions to
So for some reason my normal users on a Debian based system with E can only
"lock" or "log out" from the system screen. I had this issue awhile back
under Ubuntu based systems and the solution then was to set the proper
permissions to the enlightenment_sys like so:
sudo chmod u+s /usr/lib/enlighte
13 matches
Mail list logo
