Description of problem: After installing and updating Fedora 20 GNOME desktop (from DVD), I ran sudo yum install @sugar-desktop sugar-runner. I then edited /usr/share/applications/sugar-runner.desktop and added the icon to my favorites sidebar in GNOME. On first launch of Sugar, this bug popped up. Version-Release number of selected component: sugar-runner-0.100.1-2.fc20 Additional info: reporter: libreport-2.1.11 cmdline: /usr/bin/python2 /usr/libexec/sugar-runner/xinitrc dso_list: python-libs-2.7.5-9.fc20.x86_64 executable: /usr/libexec/sugar-runner/xinitrc kernel: 3.12.7-300.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: subprocess.py:1308:_execute_child:OSError: [Errno 2] No such file or directory Traceback (most recent call last): File "/usr/libexec/sugar-runner/xinitrc", line 86, in <module> if subprocess.call(["sugar"]) != 0: File "/usr/lib64/python2.7/subprocess.py", line 524, in call return Popen(*popenargs, **kwargs).wait() File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__ errread, errwrite) File "/usr/lib64/python2.7/subprocess.py", line 1308, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory Local variables in innermost frame: errread: None c2pread: None gc_was_enabled: True errwrite: None shell: False errpipe_write: 5 executable: 'sugar' close_fds: False self: <subprocess.Popen object at 0x14dfc90> env: None cwd: None child_exception: OSError(2, 'No such file or directory') args: ['sugar'] c2pwrite: None data: 'cexceptions\nOSError\np0\n(I2\nS\'No such file or directory\'\np1\ntp2\nRp3\n(dp4\nS\'child_traceback\'\np5\nS\'Traceback (most recent call last):\\n File "/usr/lib64/python2.7/subprocess.py", line 1263, in _execute_child\\n os.execvp(executable, args)\\n File "/usr/lib64/python2.7/os.py", line 344, in execvp\\n _execvpe(file, args)\\n File "/usr/lib64/python2.7/os.py", line 380, in _execvpe\\n func(fullname, *argrest)\\nOSError: [Errno 2] No such file or directory\\n\'\np6\nsb.' creationflags: 0 errpipe_read: 4 preexec_fn: None p2cread: None startupinfo: None p2cwrite: None universal_newlines: False
Created attachment 851202 [details] File: backtrace
Created attachment 851203 [details] File: environ
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.