Bug 1511182

Summary: [abrt] lpf: run(): subprocess.py:418:run:subprocess.CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state']' died with <Signals.SIGTERM: 15>.
Product: [Fedora] Fedora Reporter: jan
Component: lpfAssignee: Alec Leamas <leamas.alec>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: leamas.alec, negativo17, sergio
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d4b859f678f618c22b3ad43870988276b7487a56
Whiteboard: abrt_hash:b65f2373f58ffd8f5b44f9cd9ee9e4390e8174b2;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:40:50 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: cgroup
none
File: cpuinfo
none
File: environ
none
File: mountinfo
none
File: namespaces
none
File: open_fds none

Description jan 2017-11-08 20:22:04 UTC
Version-Release number of selected component:
lpf-0.2-4.f1f5dd9.fc26

Additional info:
reporter:       libreport-2.9.1
cmdline:        python3 /usr/bin/lpf-gui
crash_function: run
exception_type: subprocess.CalledProcessError
executable:     /usr/bin/lpf-gui
kernel:         4.13.5-200.fc26.x86_64
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
subprocess.py:418:run:subprocess.CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state']' died with <Signals.SIGTERM: 15>.

Traceback (most recent call last):
  File "/usr/bin/lpf-gui", line 14, in <module>
    lpf_gui_base.main()
  File "/usr/share/lpf/scripts/lpf_gui_base.py", line 453, in main
    Handler(builder)
  File "/usr/share/lpf/scripts/lpf_gui_base.py", line 424, in __init__
    statebytes = subprocess.check_output([here('lpf'), 'state'])
  File "/usr/lib64/python3.6/subprocess.py", line 336, in check_output
    **kwargs).stdout
  File "/usr/lib64/python3.6/subprocess.py", line 418, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state']' died with <Signals.SIGTERM: 15>.

Local variables in innermost frame:
retcode: -15
stderr: None
stdout: b''
process: <subprocess.Popen object at 0x7f984785c390>
kwargs: {'stdout': -1}
popenargs: (['/usr/share/lpf/scripts/lpf', 'state'],)
check: True
timeout: None
input: None

Comment 1 jan 2017-11-08 20:22:09 UTC
Created attachment 1349567 [details]
File: backtrace

Comment 2 jan 2017-11-08 20:22:10 UTC
Created attachment 1349568 [details]
File: cgroup

Comment 3 jan 2017-11-08 20:22:12 UTC
Created attachment 1349569 [details]
File: cpuinfo

Comment 4 jan 2017-11-08 20:22:13 UTC
Created attachment 1349570 [details]
File: environ

Comment 5 jan 2017-11-08 20:22:15 UTC
Created attachment 1349571 [details]
File: mountinfo

Comment 6 jan 2017-11-08 20:22:16 UTC
Created attachment 1349572 [details]
File: namespaces

Comment 7 jan 2017-11-08 20:22:17 UTC
Created attachment 1349573 [details]
File: open_fds

Comment 8 Fedora End Of Life 2018-05-03 08:14:30 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 9 Fedora End Of Life 2018-05-29 11:40:50 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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 10 Sergio Basto 2021-05-27 10:25:30 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 11 Sergio Basto 2021-05-27 10:35:16 UTC

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