Bug 877780 - ERROR: "spawn of helper failed"
Summary: ERROR: "spawn of helper failed"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-18 18:38 UTC by Andrei ILIE
Modified: 2013-08-01 00:49 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 00:49:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
err (50.15 KB, image/png)
2012-11-18 18:38 UTC, Andrei ILIE
no flags Details

Description Andrei ILIE 2012-11-18 18:38:14 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0
Build Identifier: 

When trying to use Apper or PackageKit we get the following error: "Spawn of helper '/usr/share/PackageKit/helpers/yum/yumBackend.py' failed". Please see the attached screenshot for details.


Bug reproduced using the following rig:
    ~ Apper v0.7.2
    ~ PackageKit v0.7.5
    ~ yum v3.4.3
    ~ Fedora 17


$ pkcon get-updates
Getting updates               [=========================]         
Waiting in queue              [=========================]         
Starting                      [=========================]         
Fatal error: Spawn of helper '/usr/share/PackageKit/helpers/yum/yumBackend.py' failed


$ NETWORK=TRUE /usr/share/PackageKit/helpers/yum/yumBackend.py get-updates none
bash: /usr/share/PackageKit/helpers/yum/yumBackend.py: Permission denied


$ ll /usr/share/PackageKit/helpers/yum/yumBackend.py
-rw-r--r--. 1 root root 149087 Jun 27 10:54 /usr/share/PackageKit/helpers/yum/yumBackend.py


$ head /usr/share/PackageKit/helpers/yum/yumBackend.py
#!/usr/bin/python
# Licensed under the GNU General Public License Version 2
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of

Reproducible: Always

Comment 1 Andrei ILIE 2012-11-18 18:38:43 UTC
Created attachment 647260 [details]
err

Comment 3 Fedora End Of Life 2013-07-03 22:44:13 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2013-08-01 00:49:33 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.