On 19.01.2014 03:27, Garry T. Williams wrote:
> On 1-17-14 21:03:39 poma wrote:
>>> # setenforce 0
>>> #
>>> # setenforce 1
>>
>> I think I don't remember that I ever had to do it.
>> This nullifies the very purpose of the SELinux.
>
> The problem was caused by a bad SELinux policy that blocks rp
On 1-17-14 21:03:39 poma wrote:
> > # setenforce 0
> > #
> > # setenforce 1
>
> I think I don't remember that I ever had to do it.
> This nullifies the very purpose of the SELinux.
The problem was caused by a bad SELinux policy that blocks rpm
updates. You must set to permissive to get the corr
# yum reinstall x2go\* libXcomp\* libssh libNX\* nx\*
No hay errores! :)
poma
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-condu
On 17.01.2014 21:59, Michael Schwendt wrote:
> On Fri, 17 Jan 2014 21:53:50 +0100, poma wrote:
>
>> On 17.01.2014 21:34, Michael Schwendt wrote:
>>> On Fri, 17 Jan 2014 21:03:39 +0100, poma wrote:
>>>
This nullifies the very purpose of the SELinux.
>>>
>>> Not really. You might want to run
>>
On Fri, 17 Jan 2014 21:53:50 +0100, poma wrote:
> On 17.01.2014 21:34, Michael Schwendt wrote:
> > On Fri, 17 Jan 2014 21:03:39 +0100, poma wrote:
> >
> >> This nullifies the very purpose of the SELinux.
> >
> > Not really. You might want to run
> >
> > semodule -B
> >
> > instead.
>
> # se
On 17.01.2014 21:34, Michael Schwendt wrote:
> On Fri, 17 Jan 2014 21:03:39 +0100, poma wrote:
>
>> This nullifies the very purpose of the SELinux.
>
> Not really. You might want to run
>
> semodule -B
>
> instead.
# semodule -v -B
Committing changes:
Ok: transaction number 0.
# yum --enabl
On Fri, 17 Jan 2014 21:03:39 +0100, poma wrote:
> This nullifies the very purpose of the SELinux.
Not really. You might want to run
semodule -B
instead.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/
On 17.01.2014 20:44, Suvayu Ali wrote:
> On Fri, Jan 17, 2014 at 08:39:00PM +0100, poma wrote:
>> On 17.01.2014 20:18, Suvayu Ali wrote:
>>> On Fri, Jan 17, 2014 at 08:14:52PM +0100, poma wrote:
On 17.01.2014 20:04, Richard Shaw wrote:
> On Fri, Jan 17, 2014 at 12:49 PM, poma wrote:
>
On Fri, Jan 17, 2014 at 08:39:00PM +0100, poma wrote:
> On 17.01.2014 20:18, Suvayu Ali wrote:
> > On Fri, Jan 17, 2014 at 08:14:52PM +0100, poma wrote:
> >> On 17.01.2014 20:04, Richard Shaw wrote:
> >>> On Fri, Jan 17, 2014 at 12:49 PM, poma wrote:
> >>>
> To X2Go or not to X2Go!?
>
>
On 17.01.2014 20:18, Suvayu Ali wrote:
> On Fri, Jan 17, 2014 at 08:14:52PM +0100, poma wrote:
>> On 17.01.2014 20:04, Richard Shaw wrote:
>>> On Fri, Jan 17, 2014 at 12:49 PM, poma wrote:
>>>
To X2Go or not to X2Go!?
>>> Not sure I can answer that but I don't think this is a proble
On Fri, Jan 17, 2014 at 08:14:52PM +0100, poma wrote:
> On 17.01.2014 20:04, Richard Shaw wrote:
> > On Fri, Jan 17, 2014 at 12:49 PM, poma wrote:
> >
> >> To X2Go or not to X2Go!?
> >>
> >>
> > Not sure I can answer that but I don't think this is a problem in x2go, I
> > installed it fine a few
On 17.01.2014 20:04, Richard Shaw wrote:
> On Fri, Jan 17, 2014 at 12:49 PM, poma wrote:
>
>> To X2Go or not to X2Go!?
>>
>>
> Not sure I can answer that but I don't think this is a problem in x2go, I
> installed it fine a few weeks ago. There have been several reports of
> failed scriplets among
On Fri, Jan 17, 2014 at 12:49 PM, poma wrote:
> To X2Go or not to X2Go!?
>
>
Not sure I can answer that but I don't think this is a problem in x2go, I
installed it fine a few weeks ago. There have been several reports of
failed scriplets among various packages.
Richard
--
users mailing list
use
# yum install x2go\*
…
Running transaction
Installing : nx-libs-3.5.0.21-3.fc20.i686
1/47
warning: %post(nx-libs-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
nx-libs-3
14 matches
Mail list logo