Ouch! X2Go needs a couch!

[poma]

# 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.5.0.21-3.fc20.i686
…
  Installing : libXcomp-3.5.0.21-3.fc20.i686
                                                                   10/47
warning: %post(libXcomp-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
libXcomp-3.5.0.21-3.fc20.i686
  Installing : libNX_X11-3.5.0.21-3.fc20.i686
                                                                   11/47
warning: %post(libNX_X11-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_X11-3.5.0.21-3.fc20.i686
  Installing : libNX_Xext-3.5.0.21-3.fc20.i686
                                                                   12/47
warning: %post(libNX_Xext-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_Xext-3.5.0.21-3.fc20.i686
  Installing : libNX_Xtst-3.5.0.21-3.fc20.i686
                                                                   13/47
warning: %post(libNX_Xtst-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_Xtst-3.5.0.21-3.fc20.i686
  Installing : libNX_Xrender-3.5.0.21-3.fc20.i686
                                                                   14/47
warning: %post(libNX_Xrender-3.5.0.21-3.fc20.i686) scriptlet failed,
exit status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_Xrender-3.5.0.21-3.fc20.i686
  Installing : libNX_Xrandr-3.5.0.21-3.fc20.i686
                                                                   15/47
warning: %post(libNX_Xrandr-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_Xrandr-3.5.0.21-3.fc20.i686
…
  Installing : libNX_Xdamage-3.5.0.21-3.fc20.i686
                                                                   19/47
warning: %post(libNX_Xdamage-3.5.0.21-3.fc20.i686) scriptlet failed,
exit status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_Xdamage-3.5.0.21-3.fc20.i686
  Installing : perl-Sys-Syslog-0.33-4.fc20.i686
                                                                   20/47
  Installing : libssh-0.6.0-1.fc20.i686
                                                                   21/47
warning: %post(libssh-0.6.0-1.fc20.i686) scriptlet failed, exit status 127
Non-fatal POSTIN scriptlet failure in rpm package libssh-0.6.0-1.fc20.i686
…
  Installing : libXcompshad-3.5.0.21-3.fc20.i686
                                                                   24/47
warning: %post(libXcompshad-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
libXcompshad-3.5.0.21-3.fc20.i686
  Installing : libNX_Xinerama-3.5.0.21-3.fc20.i686
                                                                   25/47
warning: %post(libNX_Xinerama-3.5.0.21-3.fc20.i686) scriptlet failed,
exit status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_Xinerama-3.5.0.21-3.fc20.i686
  Installing : libNX_Xpm-3.5.0.21-3.fc20.i686
                                                                   26/47
warning: %post(libNX_Xpm-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_Xpm-3.5.0.21-3.fc20.i686
  Installing : libXcompext-3.5.0.21-3.fc20.i686
                                                                   27/47
warning: %post(libXcompext-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
libXcompext-3.5.0.21-3.fc20.i686
…
  Installing : libNX_Xdmcp-3.5.0.21-3.fc20.i686
                                                                   29/47
warning: %post(libNX_Xdmcp-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_Xdmcp-3.5.0.21-3.fc20.i686
  Installing : libNX_Xfixes-3.5.0.21-3.fc20.i686
                                                                   30/47
warning: %post(libNX_Xfixes-3.5.0.21-3.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_Xfixes-3.5.0.21-3.fc20.i686
  Installing : libNX_Xcomposite-3.5.0.21-3.fc20.i686
                                                                   31/47
warning: %post(libNX_Xcomposite-3.5.0.21-3.fc20.i686) scriptlet failed,
exit status 127
Non-fatal POSTIN scriptlet failure in rpm package
libNX_Xcomposite-3.5.0.21-3.fc20.i686
  Installing : nxagent-3.5.0.21-3.fc20.i686
…
  Installing : x2goagent-3.5.0.21-3.fc20.i686
                                                                   41/47
error: %pre(x2goserver-4.0.1.10-1.fc20.i686) scriptlet failed, exit
status 127
Error in PREIN scriptlet in rpm package x2goserver-4.0.1.10-1.fc20.i686
error: x2goserver-4.0.1.10-1.fc20.i686: install failed
error: %pre(x2goserver-printing-4.0.1.10-1.fc20.i686) scriptlet failed,
exit status 127
Error in PREIN scriptlet in rpm package
x2goserver-printing-4.0.1.10-1.fc20.i686
  Installing : x2goserver-fmbindings-4.0.1.10-1.fc20.i686
                                                                   44/47
error: x2goserver-printing-4.0.1.10-1.fc20.i686: install failed
warning: %post(x2goserver-fmbindings-4.0.1.10-1.fc20.i686) scriptlet
failed, exit status 127
Non-fatal POSTIN scriptlet failure in rpm package
x2goserver-fmbindings-4.0.1.10-1.fc20.i686
error: %pre(x2godesktopsharing-3.1.1.0-4.fc20.i686) scriptlet failed,
exit status 127
Error in PREIN scriptlet in rpm package
x2godesktopsharing-3.1.1.0-4.fc20.i686
  Installing : x2goplugin-4.0.1.2-1.fc20.i686
                                                                   46/47
error: x2godesktopsharing-3.1.1.0-4.fc20.i686: install failed
  Installing : x2goclient-4.0.1.2-1.fc20.i686
                                                                   47/47
warning: %post(x2goclient-4.0.1.2-1.fc20.i686) scriptlet failed, exit
status 127
Non-fatal POSTIN scriptlet failure in rpm package
x2goclient-4.0.1.2-1.fc20.i686
warning: %posttrans(x2goclient-4.0.1.2-1.fc20.i686) scriptlet failed,
exit status 127
Non-fatal POSTTRANS scriptlet failure in rpm package
x2goclient-4.0.1.2-1.fc20.i686
…
Failed:
  x2godesktopsharing.i686 0:3.1.1.0-4.fc20         x2goserver.i686
0:4.0.1.10-1.fc20         x2goserver-printing.i686 0:4.0.1.10-1.fc20

Complete! <= :)

To X2Go or not to X2Go!?


poma

[Garry Williams]

On 1-17-14 21:03:39 poma wrote:
>  > # setenforce 0
>  > # <update selinux>
>  > # 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 corrected policy
installed.

-- 
Garry T. Williams

[poma]

On 19.01.2014 03:27, Garry T. Williams wrote:
>  On 1-17-14 21:03:39 poma wrote:
> >> # setenforce 0
> >> # <update selinux>
> >> # 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 corrected policy
>  installed. 
You don't need to do it that way!
Besides I've already done it via 'rpm', successfully. :)
Although it can be done in a more direct way,
e.g./i.e.

# yum install x2goserver
…
Running transaction
error: %pre(x2goserver-4.0.1.10-1.fc20.i686) scriptlet failed, exit
status 127
Error in PREIN scriptlet in rpm package x2goserver-4.0.1.10-1.fc20.i686
  Installing : x2goagent-3.5.0.21-3.fc20.i686
    2/2
Error unpacking rpm package x2goagent-3.5.0.21-3.fc20.i686
error: x2goserver-4.0.1.10-1.fc20.i686: install failed
error: unpacking of archive failed on file /usr/share/x2go/rgb;52dbea18:
cpio: open
  Verifying  : x2goagent-3.5.0.21-3.fc20.i686
    1/2
  Verifying  : x2goserver-4.0.1.10-1.fc20.i686
    2/2

Failed:
  x2goagent.i686 0:3.5.0.21-3.fc20       x2goserver.i686
0:4.0.1.10-1.fc20

Complete!

# rpm -qa selinux-policy\*
selinux-policy-3.12.1-116.fc20.noarch
selinux-policy-targeted-3.12.1-116.fc20.noarch

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

# rm -f /etc/selinux/targeted/modules/active/modules/unconfineduser.pp

# rpm2cpio
http://kojipkgs.fedoraproject.org/packages/selinux-policy/3.12.1/117.fc20...
| cpio -id *unconfineduser.pp

# semodule -i etc/selinux/targeted/modules/active/modules/unconfineduser.pp

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

# yum install x2goserver
…
Installed:
  x2goserver.i686 0:4.0.1.10-1.fc20


Dependency Installed:
  x2goagent.i686 0:3.5.0.21-3.fc20


Complete!


poma

[poma]

# yum reinstall x2go\* libXcomp\* libssh libNX\* nx\*
No hay errores! :)


poma

[poma]

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
> >>
> >>   semodule -B
> >>
> >> instead.
> >
> > # semodule -v -B
> > Committing changes:
> > Ok: transaction number 0.
> >
> > # yum --enablerepo updates-testing update selinux-policy-targeted
> > …
> > Running transaction
> > error: %pre(selinux-policy-targeted-3.12.1-117.fc20.noarch) scriptlet
> > failed, exit status 127
>  
>  Well, you do need to install the package first, because it contains the
>  corrected policy module. I had assumed you've managed to install it
>  somehow, but were still facing the script errors. If you refuse to install
>  it in permissive mode, not much is left other than doing it within a
>  chroot from a rescue disk. 
Is this a valid method?

# rpm -Uvh --nopre
http://kojipkgs.fedoraproject.org/packages/selinux-policy/3.12.1/118.fc20...
Retrieving
http://kojipkgs.fedoraproject.org/packages/selinux-policy/3.12.1/118.fc20...
Preparing...                          #################################
[100%]
Updating / installing...
   1:selinux-policy-targeted-3.12.1-11#################################
[ 50%]
warning: %post(selinux-policy-targeted-3.12.1-118.fc20.noarch) scriptlet
failed, exit status 127
Cleaning up / removing...
   2:selinux-policy-targeted-3.12.1-11#################################
[100%]

# rpm -q selinux-policy selinux-policy-targeted
selinux-policy-3.12.1-118.fc20.noarch
selinux-policy-targeted-3.12.1-118.fc20.noarch

# yum install x2go\*
…
Running transaction
Warning: RPMDB altered outside of yum.
** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
x2goagent-3.5.0.21-3.fc20.i686 has missing requires of x2goserver
x2goserver-fmbindings-4.0.1.10-1.fc20.i686 has missing requires of
x2goserver = ('0', '4.0.1.10', '1.fc20')
  Installing : x2goserver-4.0.1.10-1.fc20.i686
                                                                     1/3
  Installing : x2goserver-printing-4.0.1.10-1.fc20.i686
                                                                     2/3
  Installing : x2godesktopsharing-3.1.1.0-4.fc20.i686
                                                                     3/3
  Verifying  : x2godesktopsharing-3.1.1.0-4.fc20.i686
                                                                     1/3
  Verifying  : x2goserver-printing-4.0.1.10-1.fc20.i686
                                                                     2/3
  Verifying  : x2goserver-4.0.1.10-1.fc20.i686
                                                                     3/3

Installed:
  x2godesktopsharing.i686 0:3.1.1.0-4.fc20         x2goserver.i686
0:4.0.1.10-1.fc20         x2goserver-printing.i686 0:4.0.1.10-1.fc20

Complete!

# yum check
Loaded plugins: langpacks, refresh-packagekit
check all



poma

[Michael Schwendt]

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.
>  
>  # semodule -v -B
>  Committing changes:
>  Ok: transaction number 0.
>  
>  # yum --enablerepo updates-testing update selinux-policy-targeted
>  …
>  Running transaction
>  error: %pre(selinux-policy-targeted-3.12.1-117.fc20.noarch) scriptlet
>  failed, exit status 127 
Well, you do need to install the package first, because it contains the
corrected policy module. I had assumed you've managed to install it
somehow, but were still facing the script errors. If you refuse to install
it in permissive mode, not much is left other than doing it within a
chroot from a rescue disk.

[poma]

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 --enablerepo updates-testing update selinux-policy-targeted
…
Running transaction
error: %pre(selinux-policy-targeted-3.12.1-117.fc20.noarch) scriptlet
failed, exit status 127
Error in PREIN scriptlet in rpm package
selinux-policy-targeted-3.12.1-117.fc20.noarch
selinux-policy-targeted-3.12.1-116.fc20.noarch was supposed to be
removed but is not!
  Verifying  : selinux-policy-targeted-3.12.1-116.fc20.noarch
                                                                     1/2
  Verifying  : selinux-policy-targeted-3.12.1-117.fc20.noarch
                                                                     2/2

Failed:
  selinux-policy-targeted.noarch 0:3.12.1-116.fc20
  selinux-policy-targeted.noarch 0:3.12.1-117.fc20

Complete!

# rpm -q selinux-policy selinux-policy-targeted
selinux-policy-3.12.1-117.fc20.noarch
selinux-policy-targeted-3.12.1-116.fc20.noarch

It doesn't give up so easily! :)
http://www.youtube.com/watch?v=eOUtsybozjg


poma

[Michael Schwendt]

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.

[poma]

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 <pomidorabelisima(a)gmail.com&gt;
> 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.
> >>>
> >>> I see scriptlets breakdown only with those packages.
> >>> Bummer!
> >>> https://bugzilla.redhat.com/show_bug.cgi?id=1054932
> >>
> >> https://lists.fedoraproject.org/pipermail/users/2014-January/445554.html
> >> https://lists.fedoraproject.org/pipermail/users/2014-January/445555.html
> >>
> >> After applying the above fix, reinstall the packages with scriptlet
> >> failures.
>  
>  Please read the second message carefully; did you set selinux to
>  permissive before applying the update?
>  
>  # setenforce 0
>  # <update selinux>
>  # setenforce 1 
I think I don't remember that I ever had to do it.
This nullifies the very purpose of the SELinux.
If I'm not mistaken it seems as if the dog bites its own tail! :)
Not you, I mean the SELinux.


poma

[Suvayu Ali]

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 <pomidorabelisima(a)gmail.com&gt;
> 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.
>  >>
>  >> I see scriptlets breakdown only with those packages.
>  >> Bummer!
>  >> https://bugzilla.redhat.com/show_bug.cgi?id=1054932
>  > 
>  > https://lists.fedoraproject.org/pipermail/users/2014-January/445554.html
>  > https://lists.fedoraproject.org/pipermail/users/2014-January/445555.html
>  > 
>  > After applying the above fix, reinstall the packages with scriptlet
>  > failures. 
Please read the second message carefully; did you set selinux to
permissive before applying the update?

# setenforce 0
# <update selinux>
# setenforce 1

-- 
Suvayu

Open source is the future. It sets us free.

[poma]

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 <pomidorabelisima(a)gmail.com&gt; 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.
> >
> > I see scriptlets breakdown only with those packages.
> > Bummer!
> > https://bugzilla.redhat.com/show_bug.cgi?id=1054932
>  
>  https://lists.fedoraproject.org/pipermail/users/2014-January/445554.html
>  https://lists.fedoraproject.org/pipermail/users/2014-January/445555.html
>  
>  After applying the above fix, reinstall the packages with scriptlet
>  failures. 
# yum --enablerepo updates-testing update selinux-policy
…
Running transaction
  Updating   : selinux-policy-3.12.1-117.fc20.noarch
                                                                     1/4
warning: %post(selinux-policy-3.12.1-117.fc20.noarch) scriptlet failed,
exit status 127
Non-fatal POSTIN scriptlet failure in rpm package
selinux-policy-3.12.1-117.fc20.noarch
warning: %triggerin(selinux-policy-3.12.1-117.fc20.noarch) scriptlet
failed, exit status 127
Non-fatal <unknown> scriptlet failure in rpm package
selinux-policy-3.12.1-117.fc20.noarch
error: %pre(selinux-policy-targeted-3.12.1-117.fc20.noarch) scriptlet
failed, exit status 127
Error in PREIN scriptlet in rpm package
selinux-policy-targeted-3.12.1-117.fc20.noarch
  Cleanup    : selinux-policy-3.12.1-116.fc20.noarch
                                                                     3/4
error: selinux-policy-targeted-3.12.1-117.fc20.noarch: install failed
error: selinux-policy-targeted-3.12.1-116.fc20.noarch: erase skipped
warning: %postun(selinux-policy-3.12.1-116.fc20.noarch) scriptlet
failed, exit status 127
Non-fatal POSTUN scriptlet failure in rpm package
selinux-policy-3.12.1-116.fc20.noarch
  Verifying  : selinux-policy-3.12.1-117.fc20.noarch
                                                                     1/4
selinux-policy-targeted-3.12.1-116.fc20.noarch was supposed to be
removed but is not!
  Verifying  : selinux-policy-targeted-3.12.1-116.fc20.noarch
                                                                     2/4
  Verifying  : selinux-policy-3.12.1-116.fc20.noarch
                                                                     3/4
  Verifying  : selinux-policy-targeted-3.12.1-117.fc20.noarch
                                                                     4/4

Updated:
  selinux-policy.noarch 0:3.12.1-117.fc20


Failed:
  selinux-policy-targeted.noarch 0:3.12.1-116.fc20
  selinux-policy-targeted.noarch 0:3.12.1-117.fc20

Complete!

# rpm -q selinux-policy
selinux-policy-3.12.1-117.fc20.noarch

# yum install x2go\*
…
Running transaction
error: %pre(x2goserver-4.0.1.10-1.fc20.i686) scriptlet failed, exit
status 127
Error in PREIN scriptlet in rpm package x2goserver-4.0.1.10-1.fc20.i686
error: x2goserver-4.0.1.10-1.fc20.i686: install failed
error: %pre(x2goserver-printing-4.0.1.10-1.fc20.i686) scriptlet failed,
exit status 127
Error in PREIN scriptlet in rpm package
x2goserver-printing-4.0.1.10-1.fc20.i686
error: x2goserver-printing-4.0.1.10-1.fc20.i686: install failed
error: %pre(x2godesktopsharing-3.1.1.0-4.fc20.i686) scriptlet failed,
exit status 127
Error in PREIN scriptlet in rpm package
x2godesktopsharing-3.1.1.0-4.fc20.i686
  Verifying  : x2godesktopsharing-3.1.1.0-4.fc20.i686
                                                                     1/3
  Verifying  : x2goserver-printing-4.0.1.10-1.fc20.i686
                                                                     2/3
  Verifying  : x2goserver-4.0.1.10-1.fc20.i686
                                                                     3/3

Failed:
  x2godesktopsharing.i686 0:3.1.1.0-4.fc20         x2goserver.i686
0:4.0.1.10-1.fc20         x2goserver-printing.i686 0:4.0.1.10-1.fc20

Complete!

Still no (X2)go! :)
Bummer!


poma

[Suvayu Ali]

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 <pomidorabelisima(a)gmail.com&gt; 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.
>  
>  I see scriptlets breakdown only with those packages.
>  Bummer!
>  https://bugzilla.redhat.com/show_bug.cgi?id=1054932 
https://lists.fedoraproject.org/pipermail/users/2014-January/445554.html
https://lists.fedoraproject.org/pipermail/users/2014-January/445555.html

After applying the above fix, reinstall the packages with scriptlet
failures.

-- 
Suvayu

Open source is the future. It sets us free.

[poma]

On 17.01.2014 20:04, Richard Shaw wrote:
>  On Fri, Jan 17, 2014 at 12:49 PM, poma
> <pomidorabelisima(a)gmail.com&gt; 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. 
I see scriptlets breakdown only with those packages.
Bummer!
https://bugzilla.redhat.com/show_bug.cgi?id=1054932


poma

[Richard Shaw]

On Fri, Jan 17, 2014 at 12:49 PM, poma <pomidorabelisima(a)gmail.com&gt; 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