Bug 19399 - Filezilla fails to launch in M5.1 CI install
Summary: Filezilla fails to launch in M5.1 CI install
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: ISO building group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 19518
Blocks:
  Show dependency treegraph
 
Reported: 2016-09-17 19:25 CEST by William Kenney
Modified: 2016-12-17 10:05 CET (History)
4 users (show)

See Also:
Source RPM: filezilla
CVE:
Status comment:


Attachments

Description William Kenney 2016-09-17 19:25:49 CEST
Description of problem:

Installed per MCC: Ver. 3.10.2-1.mga5

[root@localhost wilcal]# urpmi filezilla
No package named filezilla

Launching filezilla from a desktop icon fails

Launching filezilla from terminal results in the fillowing error message:

[wilcal@localhost ~]$ filezilla
filezilla: relocation error: filezilla: symbol _ZN8wxString8ms_cacheE, version WXU_3.0 not defined in file libwx_baseu-3.0.so.0 with link time reference
Comment 1 William Kenney 2016-09-17 19:28:37 CEST
In VirtualBox, M5, KDE, 32-bit

Install media:

Mageia-5.1-i586-DVD.iso
md5sum: 819b10abe4736876df6f1e201e5bd279
Comment 2 William Kenney 2016-09-17 19:38:36 CEST
Update from repo:

The following 3 packages are going to be installed:

- filezilla-3.16.1-1.mga5.i586
- libfilezilla0-0.4.0.1-1.mga5.i586
- libpugixml1-1.7-1.mga5.i586

[root@localhost wilcal]# urpmi filezilla
Package filezilla-3.16.1-1.mga5.i586 is already installed

And it works fine.
Comment 3 William Kenney 2016-09-18 18:08:59 CEST
I confirm that this situation occurs on real hardware.
Comment 4 Ben McMonagle 2016-09-20 10:45:42 CEST
in a all DE in one install, filezilla launches ok

( Mageia-5.1-x86_64-DVD.iso
DATE.txt: Fri Sep  9 23:54:09 CEST 2016
md5sum:   36f2a8fa62d9cd7ba381edefe2ffa48d )

CC: (none) => westel

Comment 5 Marja Van Waes 2016-09-21 16:34:13 CEST
was filezilla one of the "mixed version" package sets on the iso??

CC: (none) => marja11
Assignee: bugsquad => geiger.david68210

Comment 6 David GEIGER 2016-09-21 16:36:30 CEST
Why assigned to me? this is an ISO build issue not an issue from filezilla.
Comment 7 David GEIGER 2016-09-21 16:44:09 CEST
Since version 3.16.0 filezilla need now an new lib on libfilezilla, so for the new mga 5.1 ISO we should adding both:

- filezilla-3.16.1-1.mga5
- lib(64)filezilla0-0.4.0.1-1.mga5
Comment 8 Marja Van Waes 2016-09-22 12:37:49 CEST

(In reply to David GEIGER from comment #6)
> Why assigned to me? this is an ISO build issue not an issue from filezilla.

Sorry about that, but I was too much in a hurry to check whether it really was an issue with a wrong package version on the iso, and even if I hadn't been in a hurry, it would have taken me 10 times as much time as you.

(In reply to David GEIGER from comment #7)
> Since version 3.16.0 filezilla need now an new lib on libfilezilla, so for
> the new mga 5.1 ISO we should adding both:
> 
> - filezilla-3.16.1-1.mga5
> - lib(64)filezilla0-0.4.0.1-1.mga5


Thanks, David :-D

Re-assigning to the isobuilders

Would it greatly annoy you if I do this again (assign to you when not sure)?

Assignee: geiger.david68210 => isobuild

Comment 9 William Kenney 2016-11-09 19:56:34 CET
Seems like the initial install of Filezilla is ver: 3.10.2.1 which fails.
If just do an update 3.16.1.1 gets installed and that's just fine.
Comment 10 Martin Whitaker 2016-11-09 21:07:19 CET
The out-of-date Filezilla is on the list in bug 19518, so this should be fixed in the next round.

CC: (none) => ennael1, mageia

Martin Whitaker 2016-11-15 23:40:24 CET

Keywords: (none) => 5.1
Depends on: (none) => 19518

Comment 11 Martin Whitaker 2016-12-17 10:05:44 CET
It appears this was fixed on the 64-bit CI ISO but not on the 32-bit one. But as it can be resolved by an update, and its too late to rebuild 5.1 ISOs now, I'll close this now. Please change the resolution if you think I've got it wrong.

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


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