Bug 677490

Summary: [abrt] Mayavi-3.3.2-1.fc14: __helper.py:32:refine_import_err:LinkError: libVPIC.so: cannot open shared object file: No such file or directory
Product: [Fedora] Fedora Reporter: Marco Puccini <marco.puccini>
Component: MayaviAssignee: Rakesh Pandit <rakesh.pandit>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: hansecke, pradhanphy, supercyper1
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:54119afd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:09:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Marco Puccini 2011-02-15 00:12:01 UTC
abrt version: 1.1.14
architecture: i686
cmdline: /usr/bin/python /usr/bin/mayavi2
component: Mayavi
executable: /usr/bin/mayavi2
kernel: 2.6.35.11-83.fc14.i686.PAE
package: Mayavi-3.3.2-1.fc14
reason: __helper.py:32:refine_import_err:LinkError: libVPIC.so: cannot open shared object file: No such file or directory
release: Fedora release 14 (Laughlin)
time: 1297679235
uid: 500

backtrace
-----
__helper.py:32:refine_import_err:LinkError: libVPIC.so: cannot open shared object file: No such file or directory

Traceback (most recent call last):
  File "/usr/bin/mayavi2", line 9, in <module>
    load_entry_point('Mayavi==3.3.2', 'console_scripts', 'mayavi2')()
  File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 305, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2244, in load_entry_point
    return ep.load()
  File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 1954, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/usr/lib/python2.7/site-packages/enthought/mayavi/scripts/mayavi2.py", line 451, in <module>
    import vtk
  File "/usr/lib/python2.7/site-packages/vtk/__init__.py", line 76, in <module>
    __helper.refine_import_err('hybrid', 'vtkHybridPython', exc)
  File "/usr/lib/python2.7/site-packages/vtk/__helper.py", line 32, in refine_import_err
    raise LinkError, str(exc)
LinkError: libVPIC.so: cannot open shared object file: No such file or directory

Local variables in innermost frame:
extension_name: 'vtkHybridPython'
exc: ImportError('libVPIC.so: cannot open shared object file: No such file or directory',)
mod_name: 'hybrid'

How to reproduce
-----
1. Choose software from GNOME menu
2. type command "mayavi2" on a shell
3.

Comment 1 Marco Puccini 2011-02-15 00:12:04 UTC
Created attachment 478741 [details]
File: backtrace

Comment 2 Saurabh Pradhan 2011-02-21 09:42:41 UTC
Package: Mayavi-3.3.2-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.when i want to start mayavi 
2.it 
3.crashes....

Comment 3 Hans Ecke 2011-05-18 19:08:46 UTC
Same problem here. This happens for both 32 and 64 bit F14, fully updated as of today.

Comment 4 Fedora End Of Life 2012-08-16 15:09:03 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping