Red Hat Bugzilla – Bug 221126
audacity, fc6: immediate segmentation error in gdk library on running
Last modified: 2007-11-30 17:11:52 EST
Description of problem:
After downloading audacity (pirut), on running it in FC6, was preseneted with a
dialog asking me to select a language (selected english). After pressing ok it
crashed with the following error:
Gdk-CRITICAL **: file gdkfont.c: line 337 (gdk_string_width): assertion `font !=
Have uninstalled and re-installed. Have also tried the other version from livna.
Always the same.
? Missing dependency ?
All software on the system has been loaded directly using pirut, using fedora
core, updates, extras, and livna repositories.
Have seen another (German) user report exactly the same problem:
Seems to be a missing font issue.
Please provide the output of:
rpm -qa | grep fonts
Yes, I've tried loading what I could find..
rpm -qa | grep fonts gives:
Fonts seem to be ok.
What is your LANG setting? Try to start audacity with "CFLAGS=C audacity".
There is a new build of audacity (1.2.6) on its way. Try again with the new version.
If everything fails, provide the output of "strace -f audacity".
LANG setting made no difference.
OK, will wait till the new build gets released.
Created attachment 144843 [details]
Log of trace output
Output of the command:
strace -f audacity 2> Desktop/audacity.log
This was done following installation of the new audacity version today.
The program still crashes on first running with:
Gdk-CRITICAL **: file gdkfont.c: line 337 (gdk_string_width): assertion `font
!= NULL' failed.
Hope this helps! Looking at the trace output, I have the suspicion that the font
is a redherring - the program seems to have got into some sort of a loop...
Looking around, I have found this has happened to other users, eg:
(I tried this - it didn't work).
So I suspect there is a bug in audacity somewhere, or a build issue...
You can try to move the .gtkrc* files in your home directory out of the way
temporarily. You may run gdb with audacity-debuginfo installed, but I doubt this
will give any useful information. Otherwise you should report the bug upstream.
I cannot reproduce the bug on my machine...
Good news :-))
Have just updated to the new, new version (1.3.2 beta), and it RUNS!!!
Thx for the help.