Bug 726208 - [abrt] ardour-2.8.11-5.fc14: operator++: Process /usr/lib64/ardour2/ardour-2.8.11 was killed by signal 11 (SIGSEGV)
Summary: [abrt] ardour-2.8.11-5.fc14: operator++: Process /usr/lib64/ardour2/ardour-2....
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: ardour
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anthony Green
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1cc70e76d91aa4ac8537cb0bf9f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-27 20:28 UTC by David Clark
Modified: 2012-08-16 13:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 13:21:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (53.04 KB, text/plain)
2011-07-27 20:28 UTC, David Clark
no flags Details

Description David Clark 2011-07-27 20:28:39 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 54312 bytes
cmdline: /usr/lib64/ardour2/ardour-2.8.11
component: ardour
Attached file: coredump, 330752000 bytes
crash_function: operator++
executable: /usr/lib64/ardour2/ardour-2.8.11
kernel: 2.6.35.13-92.fc14.x86_64
package: ardour-2.8.11-5.fc14
rating: 4
reason: Process /usr/lib64/ardour2/ardour-2.8.11 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1311798116
uid: 500

How to reproduce
-----
1. While trying to go back to the beginning of a song in Ardour.
2. I had also just done a couple of fairly quick undo's.
3.

Comment 1 David Clark 2011-07-27 20:28:43 UTC
Created attachment 515591 [details]
File: backtrace

Comment 2 Orcan Ogetbil 2011-07-28 01:07:12 UTC
Hi David, thanks for the report. This one looks like a bug in ardour. Could you carry this query to the ardour developers? ardour is actively maintained and the people who are actually programming it might help you easier and faster. Thank you.

Comment 3 David Clark 2011-07-28 02:47:13 UTC
Thanks for the tip, Orcan.  You say "carry this query".  Is there a standard way of doing that?  I am very new to all of this bug reporting stuff.

Comment 4 Orcan Ogetbil 2011-07-28 12:27:45 UTC
Different projects prefer different type of communication. The best way of finding it out is going to their website. For instance, for ardour, you go to
   http://ardour.org/
There is a "support" link on top. When you click on it, you will see "issue tracker" on top this time. There you can sign up for a new account, and post your problem. The developers would typically ask you questions and give you instructions to test stuff. By eliminating the middle man (me), things might go faster. From my experience, I can say that, if you don't contact the developers directly, your issue might or might not get resolved by the Fedora package maintainers (just a reminder, Fedora package maintainers are _usually_ not the actual developers of your software). In either case it is safe to post the bug report here first.

Please provide them your ardour version, OS version, jack version and the backtrace to begin with. If a solution is found, you can let us know here in this bug by giving a link. 

I hope this cleared the confusion about the process for you. Thank you for your time.

Comment 5 David Clark 2011-07-30 00:53:11 UTC
OK.  Thanks, Orcan.  I've submitted this to the Ardour bug team.

Comment 6 Fedora End Of Life 2012-08-16 13:21:10 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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


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