Bug 1217955 - Mismatch between the program and library build versions
Summary: Mismatch between the program and library build versions
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: timeline
Version: 22
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-03 10:53 UTC by rvcsaba
Modified: 2015-06-15 01:27 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-15 01:27:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description rvcsaba 2015-05-03 10:53:05 UTC
Description of problem:

/usr/bin/timeline 
Fatal Error: Mismatch between the program and library build versions detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1008,wx containers,compatible with 2.8),
and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1002,wx containers,compatible with 2.8).
Aborted (core dumped)


Version-Release number of selected component (if applicable):

timeline-1.5.0-1.fc22.noarch


Actual results:

Timeline crashed.


Expected results:

Timeline working.


Additional info:

I "build" latest v1.6.0 release, but same problem. :(

Comment 1 markusN 2015-05-04 21:23:58 UTC
It seems to be a generic wxPython problem (we just found the same issue when
running GRASS GIS 7):

$ python -c "import wx"
Fatal Error: Mismatch between the program and library build versions detected.
The library used 3.0 (wchar_t,compiler with C++ ABI 1008,wx
containers,compatible with 2.8),
and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1002,wx
containers,compatible with 2.8).
Cancelled (core dump created)

Comment 2 markusN 2015-05-04 21:27:49 UTC
See also bug #1208813

Comment 3 Scott Talbert 2015-06-15 01:07:42 UTC
Is this still a problem?  I rebuilt wxPython a while back which should've resolved this.

Comment 4 rvcsaba 2015-06-15 01:23:59 UTC
Timeline is work, thanks!


Note You need to log in before you can comment on or make changes to this bug.