Version-Release number of selected component: lpf-0.2-1.f1f5dd9.fc22 Additional info: reporter: libreport-2.6.2 cmdline: python3 /usr/bin/lpf-gui executable: /usr/bin/lpf-gui kernel: 4.0.7-300.fc22.x86_64+debug runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: subprocess.py:620:check_output:subprocess.CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state']' returned non-zero exit status -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.4/subprocess.py", line 620, in check_output raise CalledProcessError(retcode, process.args, output=output) subprocess.CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state']' returned non-zero exit status -15 Local variables in innermost frame: popenargs: (['/usr/share/lpf/scripts/lpf', 'state'],) retcode: -15 inputdata: None process: <subprocess.Popen object at 0x7f7df8d33080> timeout: None kwargs: {} output: b'' unused_err: None
Created attachment 1061081 [details] File: backtrace
Created attachment 1061082 [details] File: environ
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
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
*** This bug has been marked as a duplicate of bug 1128565 ***