Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 464858 [details] Example crash report, taken from machine A Description of problem: Can't start Tuxguitar. 50% of the time it just hangs on the splash screen. The rest of the time, it generates a fatal error. Version-Release number of selected component (if applicable): tuxguitar-1.2-3.fc14.i686 How reproducible: It fails 100% of the time. Steps to Reproduce: 1. Open a command prompt 2. launch tuxguitar 3. observe that it either hangs on the splash screen, or bails with a fatal error Actual results: Either one of the following: 1) Hangs on the splash screen 2) Generates a fatal error and an associated error report. Expected results: Tuxguitar should open fully and work, without error. Additional info: Tuxguitar worked on Fedora 13. This has only started since upgrade to fedora 14 Reinstalling F14 from fresh makes no difference. The same problem exists on 3 other Fedora 14 machines that I've tested. Attached is an example crash report, taken from one machines. This machine is consistent in where the fatal error occurs. Other machines seem to differ, but are always consistent with themselves.
Created attachment 464860 [details] Example crash report, taken from machine B Added a second example crash report, from a different machine, to show how the reports differ.
Hi Russ, are all these 4 machines running 32bit version of Fedora (i686)? Or is there a 64bit one (x86_64). If there is a 64bit one, can you post its crash backtrace?
Hi Orcan. All of my machines are running the 32-bit version of Fedora. I do have some 64-bit machines, but they are production servers, in a rack and running headless, so booting one to a 64-bit image will be a pain. I did try to boot a 64-bit image using qemu-system-x86_64, to see if I could get a crash report that way, but it's so slow as to not be practical. Not sure how else to get a crash report from a 64-bit version of Fedora.
Don't worry if you don't have a 64bit workstation nearby. Recently we started getting these reports about tuxguitar crashes. What I noticed is, there is still no crash report from a 64bit machine. Unfortunately, I don't have a 32bit machine, and I can't reproduce the crash with what I have. I wonder if this is really a bug in tuxguitar, as we didn't modify the package and it was running fine until very recently. Stay tuned.
Maybe most musicians are too poor to afford 64-bit hardware ;o) Any chance of replicating the 32-bit problem using a live image in VirtualBox, or similar? I've now tried tuxguitar on five 32-bit F14 machines, and it always fails. In at least my case, the traceback reports seem to indicate the crashes always happening in native code. They seem to happen variously in: libasound.so libtuxguitar-alsa-jni.so: libtuxguitar-fluidsynth-jni.so libfluidsynth.so I find it a bit funky that the crash location isn't consistent.
Hi. I've just been looking at tuxguitar bug 644219, which also describes a start-up failure. There's a comment in that report about disabling the alsa and fluidsynth plugins. Since all of the failures I see happen in either alsa or fluidsynth native libraries, I give it a try. As it turns out, if I remove BOTH alsa and fluidsynth plugins, then tuxguitar starts. Maybe this bug report is a duplicate of bug 644219?
This is likely a duplicate of bug 644219. As you observed, the crash happens at different places, and the backtrace is generated differently each time. It might be a set of independent bugs although I doubt it.
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