Bug 589139 - [abrt] crash in hydrogen- jack_slist_prepend: Process /usr/bin/hydrogen was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in hydrogen- jack_slist_prepend: Process /usr/bin...
Alias: None
Product: Fedora
Classification: Fedora
Component: hydrogen
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Anthony Green
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:c9c46698b92ee6c1768b6696387...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-05 13:49 UTC by Giovanni Mauri
Modified: 2010-12-03 15:03 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-03 15:03:16 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (58.16 KB, text/plain)
2010-05-05 13:49 UTC, Giovanni Mauri
no flags Details

Description Giovanni Mauri 2010-05-05 13:49:42 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: hydrogen
component: hydrogen
crash_function: jack_slist_prepend
executable: /usr/bin/hydrogen
global_uuid: c9c46698b92ee6c1768b669638711bd8f1ceef1c
package: hydrogen-
rating: 4
reason: Process /usr/bin/hydrogen was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

I also tried to start it without jack, the problem is almost the same.
Few days ago i tried to compile wineasio to work with vst, but was unable.

How to reproduce
1. start qjackctl
2. start jack
3. start hydrogen
4. get this error

Comment 1 Giovanni Mauri 2010-05-05 13:49:45 UTC
Created attachment 411610 [details]
File: backtrace

Comment 2 Orcan Ogetbil 2010-05-05 20:43:26 UTC
I can forward this to the developers. But they will most likely ask
- What flags were used to start jack? this can be found in qjackctl logs
- How is hydrogen configured? (audio and midi)
- How reproducable is the crash?

or you can report these upstream yourself, which will be much more efficient.

Comment 3 Bug Zapper 2010-11-03 15:34:21 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: 

Comment 4 Bug Zapper 2010-12-03 15:03:16 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.

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