Bug 1059655

Summary: [abrt] fros: fros:37:<module>:ImportError: No module named pyfros.froslogging
Product: [Fedora] Fedora Reporter: Anton Ohorodnyk <anton>
Component: frosAssignee: Jakub Filak <jfilak>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: anton, jberan, jfilak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:99bb0cf6ba5f8eb9b12220241a01b3250f714bb3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-31 11:01:26 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
File: environ none

Description Anton Ohorodnyk 2014-01-30 10:14:52 UTC
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

Comment 1 Anton Ohorodnyk 2014-01-30 10:14:56 UTC
Created attachment 857416 [details]
File: backtrace

Comment 2 Anton Ohorodnyk 2014-01-30 10:15:02 UTC
Created attachment 857417 [details]
File: environ

Comment 3 Jakub Filak 2014-01-30 10:22:08 UTC
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

Comment 4 Anton Ohorodnyk 2014-01-30 15:33:43 UTC
$ 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

Comment 5 Jakub Filak 2014-01-30 15:42:29 UTC
(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

Comment 6 Anton Ohorodnyk 2014-01-31 09:37:06 UTC
File doesn't exist

Comment 7 Jakub Filak 2014-01-31 10:00:21 UTC
(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

Comment 8 Anton Ohorodnyk 2014-01-31 10:06:55 UTC
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

Comment 9 Anton Ohorodnyk 2014-01-31 10:08:30 UTC
If really fixed, write please, i close this task.

Comment 10 Jakub Filak 2014-01-31 10:26:21 UTC
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 $?

Comment 11 Anton Ohorodnyk 2014-01-31 10:33:57 UTC
$ fros --is-available
$ fros --is-available
$ echo $?
1
$

$ sudo yum install fros-recordmydesktop
$ fros --is-available
$ echo $?
0
$

Comment 12 Jakub Filak 2014-01-31 10:48:31 UTC
(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.

Comment 13 Anton Ohorodnyk 2014-01-31 11:01:26 UTC
Thanks for you