filezilla crashed with SIGABRT in __assert_fail_base()
Bug #971334 reported by
Anders Pamdal
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| filezilla (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
Bug Description
Just closed filezille without closing the connections first.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: filezilla 3.5.3-1ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-21-generic x86_64
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Mon Apr 2 09:45:16 2012
ExecutablePath: /usr/bin/filezilla
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: filezilla
ProcEnviron:
LANG=sv_SE.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: filezilla
Title: filezilla crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Revision history for this message
| Anders Pamdal (anders-pamdal) wrote | #1 |
Revision history for this message
| Apport retracing service (apport) wrote Stacktrace.txt | #3 |
Revision history for this message
| Apport retracing service (apport) wrote StacktraceTop.txt | #4 |
Revision history for this message
| Apport retracing service (apport) wrote ThreadStacktrace.txt | #5 |
| Changed in filezilla (Ubuntu): | |
| importance: | Undecided → Medium |
| summary: |
- filezilla crashed with SIGABRT in raise() + filezilla crashed with SIGABRT in __assert_fail_base() |
| tags: | removed: need-amd64-retrace |
| security vulnerability: | no → yes |
| visibility: | private → public |
| security vulnerability: | yes → no |
Revision history for this message
| Paul White (paulw2u) wrote | #6 |
| Changed in filezilla (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in filezilla (Ubuntu): | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Anders,
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https:/
We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are and you find the bug is still present in a newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.
Paul White
[Ubuntu Bug Squad]