Bug 1128565 - [abrt] lpf: subprocess.py:573:check_output:CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state']' returned non-zero exit status -15
Summary: [abrt] lpf: subprocess.py:573:check_output:CalledProcessError: Command '['/us...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: lpf
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alec Leamas
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:ca0719f331655a7c62f22fb08ed...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-11 06:16 UTC by Stefan Ringel
Modified: 2016-07-19 12:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 12:00:26 UTC


Attachments (Terms of Use)
File: backtrace (859 bytes, text/plain)
2014-08-11 06:16 UTC, Stefan Ringel
no flags Details
File: environ (2.50 KB, text/plain)
2014-08-11 06:16 UTC, Stefan Ringel
no flags Details

Description Stefan Ringel 2014-08-11 06:16:39 UTC
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'],)

Comment 1 Stefan Ringel 2014-08-11 06:16:41 UTC
Created attachment 925618 [details]
File: backtrace

Comment 2 Stefan Ringel 2014-08-11 06:16:43 UTC
Created attachment 925619 [details]
File: environ

Comment 3 Alec Leamas 2014-08-30 08:15:42 UTC
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"

Comment 4 Stefan Ringel 2014-08-30 11:53:24 UTC
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!

Comment 5 Jaroslav Reznik 2015-03-03 16:11:51 UTC
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

Comment 6 Fedora End Of Life 2016-07-19 12:00:26 UTC
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.


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