Version-Release number of selected component: lpf-0.1-7.36e5aa0.fc21 Additional info: reporter: libreport-2.2.3 cmdline: python /usr/bin/lpf-gui dso_list: python-libs-2.7.8-3.fc22.x86_64 executable: /usr/bin/lpf-gui kernel: 3.16.0-1.fc22.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: subprocess.py:573:check_output: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 204, in on_view_item_activate_cb self.update_main_grid() File "/usr/bin/lpf-gui", line 279, in update_main_grid subprocess.check_output([here('lpf'), 'state']).split('\n') 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']' returned non-zero exit status -15 Local variables in innermost frame: retcode: -15 process: <subprocess.Popen object at 0x7f28100dbb10> cmd: ['/usr/share/lpf/scripts/lpf', 'state'] unused_err: None kwargs: {} output: '' popenargs: (['/usr/share/lpf/scripts/lpf', 'state'],)
Created attachment 925618 [details] File: backtrace
Created attachment 925619 [details] File: environ
Hm... what happens if you run that command: /usr/share/lpf/scripts/lpf state Also what happens if you run that command in group pkg-build? sg pkg-build "/usr/share/lpf/scripts/lpf state"
today this: /usr/share/lpf/scripts/lpf state [sringel@media12 totem]$ /usr/share/lpf/scripts/lpf state flash-plugin OK 11.2.202.394-1.fc22 [sringel@media12 totem]$ sg pkg-build "/usr/share/lpf/scripts/lpf state" flash-plugin OK 11.2.202.394-1.fc22 [sringel@media12 totem]$ ps: many updates between 2014-08-11 and today!
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
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
*** Bug 1893616 has been marked as a duplicate of this bug. ***
*** Bug 1795339 has been marked as a duplicate of this bug. ***
*** Bug 1953055 has been marked as a duplicate of this bug. ***
*** Bug 1511182 has been marked as a duplicate of this bug. ***
*** Bug 1190482 has been marked as a duplicate of this bug. ***
*** Bug 1844703 has been marked as a duplicate of this bug. ***
*** Bug 1288753 has been marked as a duplicate of this bug. ***
*** Bug 1355826 has been marked as a duplicate of this bug. ***
*** Bug 1833687 has been marked as a duplicate of this bug. ***
*** Bug 1740931 has been marked as a duplicate of this bug. ***
*** Bug 1898434 has been marked as a duplicate of this bug. ***
*** Bug 1109596 has been marked as a duplicate of this bug. ***
*** Bug 1885081 has been marked as a duplicate of this bug. ***
*** Bug 1818428 has been marked as a duplicate of this bug. ***
*** Bug 1518827 has been marked as a duplicate of this bug. ***
*** Bug 1776122 has been marked as a duplicate of this bug. ***
*** Bug 1787771 has been marked as a duplicate of this bug. ***
*** Bug 1582872 has been marked as a duplicate of this bug. ***
*** Bug 1481369 has been marked as a duplicate of this bug. ***
*** Bug 1173893 has been marked as a duplicate of this bug. ***
*** Bug 1252011 has been marked as a duplicate of this bug. ***
*** Bug 1963729 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
FEDORA-2021-e89aff3128 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e89aff3128
FEDORA-2021-86e4837cee has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-86e4837cee
FEDORA-2021-d655861edd has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d655861edd
FEDORA-2021-d655861edd has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d655861edd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d655861edd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-86e4837cee has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-86e4837cee` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-86e4837cee See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-e89aff3128 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e89aff3128` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e89aff3128 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
*** Bug 1981098 has been marked as a duplicate of this bug. ***
*** Bug 2008000 has been marked as a duplicate of this bug. ***
FEDORA-EPEL-2021-b81b53b69f has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b81b53b69f
FEDORA-EPEL-2021-b81b53b69f has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b81b53b69f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-d655861edd has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-86e4837cee has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2021-b81b53b69f has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 2016793 has been marked as a duplicate of this bug. ***
FEDORA-2021-e89aff3128 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.