Bug 1079698

Summary: [abrt] lpf: subprocess.py:575:check_output:CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state', 'skype']' returned non-zero exit status -15
Product: [Fedora] Fedora Reporter: Paul DeStefano <prd-fedora>
Component: lpfAssignee: Alec Leamas <leamas.alec>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: leamas.alec
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ceb887c9a7e2de79434ad0a3de0404ecbcb58212
Whiteboard: abrt_hash:58cf4533418f13e61c12367809fbd6a533fabb42
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-30 07:57:55 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

Description Paul DeStefano 2014-03-23 09:49:05 UTC
Description of problem:
I clicked on the "more" button and that caused a pop-up window asking me to add myself to the pkg-build group.  But, I had already done that, so I clicked on the window close button.  That caused this crash. 

Version-Release number of selected component:
lpf-0.1-6.36e5aa0.fc20

Additional info:
reporter:       libreport-2.2.0
cmdline:        python /usr/bin/lpf-gui
dso_list:       python-libs-2.7.5-11.fc20.x86_64
executable:     /usr/bin/lpf-gui
kernel:         3.13.6-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            13013

Truncated backtrace:
subprocess.py:575:check_output:CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state', 'skype']' 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 575, in check_output
    raise CalledProcessError(retcode, cmd, output=output)
CalledProcessError: Command '['/usr/share/lpf/scripts/lpf', 'state', 'skype']' returned non-zero exit status -15

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

Comment 1 Paul DeStefano 2014-03-23 09:49:14 UTC
Created attachment 877748 [details]
File: backtrace

Comment 2 Alec Leamas 2014-04-03 12:01:21 UTC
Hi!

This is probably just as it is. After you have been added to the pkg-build group you need to log out and in again for this change to be effective. Until you have done that, you need to answer the question correctly each and every time.

Sorry about this, but this is more or less what's possible without resorting to patch the kernel. The list of effective grouos is only re-evaluated after a fresh login (or using newgrp(1)) This is documented in the manpage.