tracker-extract crashed with signal 5 in g_malloc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Tracker |
Fix Released
|
Medium
|
|||
Ubuntu GNOME |
Fix Released
|
High
|
Unassigned | ||
tracker (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Unassigned |
Bug Description
* Impact
An integer overflow occurs when tracker-extract comes across an extremely large GIF image or one which is specifically crafted.
* Test case
If for instance this file https:/
* Regression potential
I have not tested these patches but the fix is in the Yakkety version and I do not experience the crash there and no regressions.
-------
Original report:
Lock Interface and PC
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: tracker-extract 0.16.0-
ProcVersionSign
Uname: Linux 3.8.0-19-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
Date: Thu May 9 16:45:04 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-04-29 (9 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANGUAGE=
LANG=pt_BR.UTF-8
Signal: 5
SourcePackage: tracker
StacktraceTop:
g_malloc () from /lib/i386-
tracker_
?? ()
?? ()
?? ()
Title: tracker-extract crashed with signal 5 in g_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
information type: | Private → Public |
tags: | removed: need-i386-retrace |
Changed in tracker (Ubuntu): | |
importance: | Undecided → High |
Changed in tracker: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in tracker: | |
importance: | Medium → Unknown |
status: | Confirmed → Unknown |
Changed in tracker: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Changed in tracker (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in tracker (Ubuntu Xenial): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in ubuntu-gnome: | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
Changed in ubuntu-gnome: | |
status: | Triaged → Fix Committed |
Changed in tracker (Ubuntu Trusty): | |
status: | Triaged → Fix Committed |
Changed in tracker (Ubuntu Xenial): | |
status: | Triaged → Fix Committed |
Changed in ubuntu-gnome: | |
status: | Fix Committed → In Progress |
Changed in tracker (Ubuntu Trusty): | |
status: | Fix Committed → In Progress |
Changed in tracker (Ubuntu Xenial): | |
status: | Fix Committed → In Progress |
Changed in tracker (Ubuntu): | |
assignee: | nobody → Nikita Yerenkov-Scott (yerenkov-scott) |
Changed in ubuntu-gnome: | |
assignee: | nobody → Nikita Yerenkov-Scott (yerenkov-scott) |
Changed in tracker (Ubuntu Trusty): | |
assignee: | nobody → Nikita Yerenkov-Scott (yerenkov-scott) |
Changed in tracker (Ubuntu Xenial): | |
assignee: | nobody → Nikita Yerenkov-Scott (yerenkov-scott) |
Changed in ubuntu-gnome: | |
status: | In Progress → Fix Released |
I have the same problem in Ubuntu 14.04