Bug 1289239 - fldigi won't run in 32 bit F23 system
Summary: fldigi won't run in 32 bit F23 system
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fldigi
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Shaw
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-07 17:46 UTC by Jim Haynes
Modified: 2015-12-09 14:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-09 14:34:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jim Haynes 2015-12-07 17:46:45 UTC
Description of problem:
attempting to run fldigi 
Version-Release number of selected component (if applicable):

fldigi-3.23.05-1.fc23.i686
How reproducible:

always
Steps to Reproduce:
1.give fldigi command
2.
3.

Actual results:
$ fldigi
fldigi: symbol lookup error: fldigi: undefined symbol: _ZN6XmlRpc12XmlRpcServer14executeRequestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE




Expected results:

Program should run
Additional info:

Comment 1 Richard Shaw 2015-12-08 17:17:42 UTC
Ok, so that translates to:

$ c++filt _ZN6XmlRpc12XmlRpcServer14executeRequestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
XmlRpc::XmlRpcServer::executeRequest(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)

The only thing I can guess is that an incompatible change was made to fldigi and it will no longer work with flxmlrpc. The only fix is likely to go back to the bundled xmlrpc.

Comment 2 Richard Shaw 2015-12-08 18:36:22 UTC
Just noticed you were running 3.23.05... I have .06 in testing, please see if you can reproduce the problem with it:

dnf --enablerepo=updates-testing update fldigi

Comment 3 Jim Haynes 2015-12-08 22:41:43 UTC
That one from updates-testing seems to work OK on the machine in question.
Curiously, I have another 32 bit F23 machine where the one from the regular
repo runs OK.

Comment 4 Richard Shaw 2015-12-09 14:34:17 UTC
Bad download perhaps? Unlikely.... Well I'll close this bug for now but if you run into problems just reopen it.


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