Bug 1190482

Summary: [abrt] lpf: subprocess.py:573:check_output:CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state', 'flash-plugin']' returned non-zero exit status -15
Product: [Fedora] Fedora Reporter: Mihai Harpau <mihai>
Component: lpfAssignee: Alec Leamas <leamas.alec>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: leamas.alec, sergio
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/efb6caab81026382ff651fbbb6e74e17727f0b28
Whiteboard: abrt_hash:8c7988b54319928f481d3238633811cd35119f14
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 08:45:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: environ none

Description Mihai Harpau 2015-02-08 14:30:31 UTC
Description of problem:
GUI interface was frozen during installing flash and skype packages

Version-Release number of selected component:
lpf-0.1-7.36e5aa0.fc21

Additional info:
reporter:       libreport-2.3.0
cmdline:        python /usr/bin/lpf-gui
dso_list:       python-libs-2.7.8-7.fc21.x86_64
executable:     /usr/bin/lpf-gui
kernel:         3.17.8-300.fc21.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
subprocess.py:573:check_output:CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state', 'flash-plugin']' returned non-zero exit status -15

Traceback (most recent call last):
  File "/usr/bin/lpf-gui", line 207, in on_view_item_activate_cb
    self.update_details(pkg_name)
  File "/usr/bin/lpf-gui", line 307, in update_details
    stateline = subprocess.check_output([here('lpf'), 'state', pkg_name])
  File "/usr/lib64/python2.7/subprocess.py", line 573, in check_output
    raise CalledProcessError(retcode, cmd, output=output)
CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state', 'flash-plugin']' returned non-zero exit status -15

Local variables in innermost frame:
retcode: -15
process: <subprocess.Popen object at 0x7fa060094750>
cmd: ['/usr/share/lpf/scripts/lpf', 'state', 'flash-plugin']
unused_err: None
kwargs: {}
output: ''
popenargs: (['/usr/share/lpf/scripts/lpf', 'state', 'flash-plugin'],)

Comment 1 Mihai Harpau 2015-02-08 14:30:34 UTC
Created attachment 989393 [details]
File: backtrace

Comment 2 Mihai Harpau 2015-02-08 14:30:35 UTC
Created attachment 989394 [details]
File: environ

Comment 3 Fedora End Of Life 2015-11-04 13:44:13 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora  'version'
of '21'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 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 this bug is closed as described in the policy above.

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 2015-12-02 08:45:45 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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

Comment 5 Sergio Basto 2021-05-27 10:25:31 UTC
this is comment in several at same time, all these bugs I believe are duplicated , but mass bug change doesn't let me mark it as duplicated , I will try do it manually 

I think I found a way to reproduce it , finally .

Do you see a message "Error getting authority: Error initializing authority: Could not connect: No such file or directory" before the stacktrace

Comment 6 Sergio Basto 2021-05-27 10:35:22 UTC

*** This bug has been marked as a duplicate of bug 1128565 ***