Bug 10664

Summary:	Filezilla shuts itself down
Product:	Mageia	Reporter:	Sascha Schroeder <sascha.schroeder>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal
Version:	3
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	filezilla	CVE:
Status comment:

Description Sascha Schroeder 2013-06-30 20:33:45 CEST

Description of problem:

Filezilla is completely buggy.

Neither the official RPM form the repos nor the version 3.7.1.1 is working with Mageia right now.

It is shutting itself down permanently. I am completely unable to get files from my server. About 90MB or less, the program disappears completely.

This is not good, folks.

Here is the error protocol:

*** Error in `filezilla': corrupted double-linked list: 0x0000000003165760 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7a86d)[0x7f1c4399786d]
/lib64/libc.so.6(+0x7b7ad)[0x7f1c439987ad]
/lib64/libc.so.6(__libc_malloc+0x68)[0x7f1c4399a988]
/usr/lib64/nvidia-current/tls/libnvidia-tls.so.319.17(+0x21f6)[0x7f1c386d41f6]

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

How reproducible:
see below

Steps to Reproduce:
1. Install Filezilla (doesn't matter which version right now, both, the official repo program and 3.7.1.1 show same misbehavior)
2. connect to a server (does not matter if encrypted or not, happens in both cases)
3. start syncing files from a server to your PC
4. about 70-80MB the program shuts itself down. You loose all connections and will not be able to make backups


Reproducible: 

Steps to Reproduce:

Comment 1 Manuel Hiebel 2013-07-03 09:51:11 CEST

seems we are not alone https://retrace.fedoraproject.org/faf/reports/50032/ (and I saw bugs on launchpad

Source RPM: (none) => filezilla

Comment 2 Marja Van Waes 2015-03-31 16:04:34 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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