Bug 186819
Summary: | Update to audacity 1.3.0beta: requesting reviews | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gérard Milmeister <gemi> |
Component: | audacity | Assignee: | Gérard Milmeister <gemi> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | bugs.michael, extras-qa, johnthacker, kevin, mattdm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-01-13 18:40:43 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Gérard Milmeister
2006-03-26 21:44:01 UTC
Will have a look. WRT libmp3lame.so -> libmp3lame.so.0 http://limpet.net/audacity/bugzilla/show_bug.cgi?id=234 I'm going to update to wxGTK 2.6.3 in devel I think tonight, and FC5 once wxPython is ready, and FC4 after that goes okay. First test-run, built in a clean FC5 environment without mp3 decoder, then checking out Help menu and trying to load a .mp3 file afterwards: $ audacity (audacity:24686): Gdk-CRITICAL **: gdk_drawable_get_depth: assertion `GDK_IS_DRAWABLE (drawable)' failed (audacity:24686): Gtk-CRITICAL **: gtk_pixmap_set: assertion `gdk_colormap_get_visual (gtk_widget_get_colormap (GTK_WIDGET (pixmap)))->depth == gdk_drawable_get_depth (GDK_DRAWABLE (val))' failed Segmentation fault Second try: $ rm -rf ~/.audacity $ audacity Floating point exception So, apparently it crashes without mp3 support built-in. Compared with current stable release 1.2.4b in FE5, that one gives an error dialog. Indeed it shows a very erratic behavior when trying to load an mp3 file, when mp3 is not compiled in. The first time it segfaults, another time the CPU jumps to 100%, at still another time it shows the correct error dialog. I wonder, if it would not be better to move audacity completely over to wilma? WTF, wilma...? livna, I meant, of course :-) I really hope that doesn't have to happen. Any suggestion what to do about this? Has this been reported/discussed upstream? |