hydrogen crashes after closing intro box

[Edward Amsden]

Binary package hint: hydrogen

jackd is started. When I closes the changelist box that appears when I start hydrogen, the main window appears briefly then disappears and terminates. I am attaching a log copied from running hydrogen in a terminal

[Edward Amsden (amsden-linux)]

Here is the log

[Tim Harris (timharris777)]

Hydrogen Crashes after I close the opening box. Here is the text and errors I get when running in terminal.

[Tim Harris (timharris777)]

Hello, I installed Jackd and started it. My error message is slightly different but hydrogen still crashes in same place. Error message is attached.

[Emmet Hikory (persia)]

Thank you for the updates. Would you mind installing the hydrogen-dbgsym package (if it exists), and running hydrogen under gdb to generate a stacktrace? The stacktrace may provide some guidance as to the source of the crash.

[Tim Harris (timharris777)]

Hello, sorry it took so long for me to reply. The hydrogen-dbgsym package is not in synaptic. Can I run hydrogen under gdb without it? How do I run hydrogen under gdb? Thanks for your help.

[Tim Harris (timharris777)]

II figured out how to use gdb. I ran a backtrace without the hydrogen-dbgsym package because it was not available. While running gdb hydrogen did not close out when I closed the intro screen. It just froze and it was unusable. However, as soon as I quit gdb hydrogen closed as it had before. Hope this helps. Thank you very much for all your help. The file is attached.

[Emmet Hikory (persia)]

Thanks for investigating this in more depth. Based on the stacktrace, I believe it may be the same issue as for bug #147476. Were you by any chance using the Millo_MultiLayered2 drumkit in the last song? Without the debug symbols, it's hard to be sure, but it appears to be the same type of error, and there is a note about using a song from a previous version. I can't be certain, as the stacktraces for that bug are for a 64-bit machine. Would you mind trying to reproduce with hydrogen 0.9.3-4ubuntu2? I'm certain there is a dbgsym package for this, and suspect it may address the issue.

[Tim Harris (timharris777)]

I have never been able to use hydrogen. It has done this since the time I installed it with synaptic. I do not have a hydrogen-dbgsym package in synaptic. I have made sure to enable all the repos in sources.list . I am running gutsy. Should I build it from source and see if that works? Thanks,
Tim

[Emmet Hikory (persia)]

    My apologies for the lack of information. Instructions for installing the debugging symbols are available from https://wiki.ubuntu.com/DebuggingProgramCrash. If you're running gutsy, it's definitely a different problem. Also, please try removing the ~/.hydrogen directory to see if this helps (if you've never successfully run hydrogen, then there should be nothing useful saved there). If you could attach a stack trace after installing the -dbgsym package, it would be very helpful towards tracking down the issue.

[Tim Harris (timharris777)]

I tried installing the hydrogen-dbgsym package with sudo aptitude install hydrogen-dbgsym I get a reply that the package does not exist. I have all the repositories enabled. Do I need to add an extra one to get this package?

[Tim Harris (timharris777)]

I ust tried deleating the hidden folder but hydrogen still crashes. Thanks for all your help.

[Emmet Hikory (persia)]

Thanks for the confirmation that the issue is not related to the ~/.hydrogen folder. You will need to enable the debugging repositories in order to install the -dbgsym packages. Instructions for doing so are available from https://wiki.ubuntu.com/DebuggingProgramCrash. Alternately, if you prefer, it may be installed manually from http://people.ubuntu.com/~ubuntu-archive/ddebs/pool/universe/h/hydrogen/

[wolfger (wolfger)]

6 months without a reply. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!