Bug 631516 - [abrt] easytag-2.1.6-5.fc12: Process /usr/bin/easytag was killed by signal 11 (SIGSEGV)
Summary: [abrt] easytag-2.1.6-5.fc12: Process /usr/bin/easytag was killed by signal 11...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: easytag
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Saou
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2ea68f94c59a5c55630284b3f9c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-07 20:00 UTC by Dale Snell
Modified: 2010-12-03 17:35 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 12:34:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (26.61 KB, text/plain)
2010-09-07 20:00 UTC, Dale Snell
no flags Details

Description Dale Snell 2010-09-07 20:00:50 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: easytag
component: easytag
crash_function: vorbiscomment_find_entry_from_
executable: /usr/bin/easytag
kernel: 2.6.32.21-166.fc12.x86_64
package: easytag-2.1.6-5.fc12
rating: 4
reason: Process /usr/bin/easytag was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1283889436
uid: 500

comment
-----
I opened EasyTag and moved to my Downloads directory, which has an MP3 
file I wanted to examine.  It also has a very large amount of non-music files
and directories.  As soon as EasyTag started to scan the directory, it crashed.

How to reproduce
-----
1.  Open EasyTag
2.  Navigate to ~/Downloads directory
3.  Crash-boom-thud

Comment 1 Dale Snell 2010-09-07 20:00:52 UTC
Created an attachment (id=445771)
File: backtrace

Comment 2 Bug Zapper 2010-11-03 10:20:30 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2010-12-03 12:34:39 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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 
Fedora please feel free to reopen this bug against that version.

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

Comment 4 Dale Snell 2010-12-03 17:35:07 UTC
I just checked EasyTag in F-14, and it does the same thing.  So how do I re-open the bug?  Clone it for F-14, or is there some other method?

While I was checking the backtrace abrt generated, I noticed the file that EasyTag crashed on.  It's the same file as it crashed on the first time.  It's a FLAC file that I believe is supposed to exhibit behavior described in CVE-2007-4619.  It's part of a set of such files used to test the Mutagen tag library (used by Quod Libet, among others).  So it's probably not the fact that there are a large number of non-music files being scanned, but that this particular file is mal-formed in a way that EasyTag can't deal with.  It's still a bug -- EasyTag should probably complain about the file, but it certainly shouldn't crash.


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