Version-Release number of selected component: lpf-0.1-6.36e5aa0.fc20 Additional info: reporter: libreport-2.2.2 cmdline: python /usr/bin/lpf-gui dso_list: python-libs-2.7.5-11.fc20.x86_64 executable: /usr/bin/lpf-gui kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: subprocess.py:575: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 452, in <module> Handler(builder) File "/usr/bin/lpf-gui", line 426, in __init__ subprocess.check_output([here('lpf'), 'state']).split('\n') 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']' returned non-zero exit status -15 Local variables in innermost frame: retcode: -15 process: <subprocess.Popen object at 0x19e3ed0> cmd: ['/usr/share/lpf/scripts/lpf', 'state'] unused_err: None kwargs: {} output: '' popenargs: (['/usr/share/lpf/scripts/lpf', 'state'],)
Created attachment 908935 [details] File: backtrace
Created attachment 908936 [details] File: environ
Hm... some questions: - What happens if you run that command manually by issuing 'lpf state' on the command line? - What were you actually doing when this happened? Running some lpf cli command, running a lpf gui command, or...?
I think I was running graal online a video game for PC or I could of been running imvu which is running wine. I figured to just send all my reports even though they were older ones.
Hm... in other words: can you reproduce this?
I'll keep you guys on here posted on new crashes for now don't worry too much about it. Thank you for the quick responses this is my first time using this crash report. Now I know to put more information next time.
OK, thanks for this report! I will leave this bug open for some time, but unless there is more input (i. e., more similar crashes) I will eventually close it.
There is no more similr input. Closing this bug. Thanks for reporting!
Happened to me just now. I'll see if I can get more data for you.
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 ***