Version-Release number of selected component: fros-1.0-4.fc20 Additional info: reporter: libreport-2.1.11 cmdline: /usr/bin/python /usr/bin/fros --is-available executable: /usr/bin/fros kernel: 3.12.8-300.fc20.x86_64 runlevel: N 5 type: Python uid: 1003 Truncated backtrace: fros:37:<module>:ImportError: No module named pyfros.froslogging Traceback (most recent call last): File "/usr/bin/fros", line 37, in <module> from pyfros.froslogging import error, info, set_verbosity ImportError: No module named pyfros.froslogging Local variables in innermost frame: util: <module 'ctypes.util' from '/usr/lib64/python2.7/ctypes/util.pyc'> DISPLAY: 19326928 __builtins__: <module '__builtin__' (built-in)> cdll: <ctypes.LibraryLoader object at 0x7f0391bee310> __file__: '/usr/bin/fros' XLIB_PATH: 'libX11.so.6' __package__: None sys: <module 'sys' (built-in)> XLIB: <CDLL 'libX11.so.6', handle 1292530 at 7f0398188310> __name__: '__main__' __doc__: None
Created attachment 857416 [details] File: backtrace
Created attachment 857417 [details] File: environ
Thank you for the report. What is the output of the following command? : $ fros --is-available Does the following file exist? : /usr/lib/python2.7/site-packages/pyfros/froslogging.py
$ fros --is-available Traceback (most recent call last): File "/usr/bin/fros", line 37, in <module> from pyfros.froslogging import error, info, set_verbosity ImportError: No module named pyfros.froslogging
(In reply to Anton Ohorodnyk from comment #4) Thank you! Does the following file exist? : $ ls -al /usr/lib/python2.7/site-packages/pyfros/froslogging.py
File doesn't exist
(In reply to Anton Ohorodnyk from comment #6) > File doesn't exist Please run the following command and report the results here: $ rpm -V fros
after reinstall fros (sudo yum reinstall fros), worked all right, i think =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= $ ls -al /usr/lib/python2.7/site-packages/pyfros/froslogging.py -rw-r--r-- 1 root root 1653 Aug 6 17:18 /usr/lib/python2.7/site-packages/pyfros/froslogging.py =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= $ fros --is-available $ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Thanks, Anton
If really fixed, write please, i close this task.
Yes, the missing files was the root of the crash. The empty output is desired behaviour, the result of the operation is reported via return code. If screen casting is available, 'fros --is-available' exits with 0; otherwise it exits with 1. $ fros --is-available $ echo $? $ sudo yum install fros-recordmydesktop $ fros --is-available $ echo $? If the exit code is still 1, try to install another fros plugin: $ sudo yum install fros-gnome $ fros --is-available $ echo $?
$ fros --is-available $ fros --is-available $ echo $? 1 $ $ sudo yum install fros-recordmydesktop $ fros --is-available $ echo $? 0 $
(In reply to Anton Ohorodnyk from comment #11) It looks like that fros works. If there is no other issue, please close this bug report.
Thanks for you