filezilla crashed with signal 5 in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
filezilla (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1) Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) filezilla:
Installed: 3.28.0-1
Candidate: 3.28.0-1
Version table:
*** 3.28.0-1 500
3) Normal use of FTP program
4) Filezilla was opened and connected to a remote site, I was using Atom editor and after sometimes Filezilla crashed
Notes:
I'm testing Ubuntu 18.04 with communitheme and Filezilla at the start shows an error dialog with assertion failed and this message:
ASSERT INFO:
../src/
BACKTRACE:
[1] wxTopLevelWindo
[2] wxTopLevelWindo
[3] wxEvtHandler:
[4] wxEventHashTabl
[5] wxEvtHandler:
[6] wxEvtHandler:
[7] wxEvtHandler:
[8] wxEvtHandler:
[9] wxTimerImpl:
[10] g_main_
[11] g_main_loop_run
[12] gtk_main
[13] wxGUIEventLoop:
[14] wxEventLoopBase
[15] wxAppConsoleBas
[16] wxEntry(int&, wchar_t**)
[17] __libc_start_main
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: filezilla 3.28.0-1
ProcVersionSign
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu-
Date: Tue Mar 13 11:15:16 2018
ExecutablePath: /usr/bin/filezilla
InstallationDate: Installed on 2017-10-22 (141 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: filezilla
Signal: 5
SourcePackage: filezilla
StacktraceTop:
raise (sig=<optimized out>) at ../sysdeps/
wxGUIAppTraits
() at /usr/lib/
wxAppConsoleBa
wxApp:
Title: filezilla crashed with signal 5 in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
tags: | removed: need-amd64-retrace |
tags: | added: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1737374, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.