Audacious - OLD, PLEASE USE GITHUB DISCUSSIONS/ISSUES

Lots of questions come up here.

Which runtime environment (Linux distribution, desktop environment)?
Which version of Audacious?
Has it been like that before with an older version of Audacious? Or is it regression?
Have you customized the fonts in Audacious (right-click > View > Interface Preferences)?

It's likely a fonts issue. The line above looks more large and more bold than normal.

Ubuntu 13.10 x64, Unity
Audacious v. 3.4.3, it was also in version 3.4
I do not set up fonts (installed default settings)

In a terminal I get this when starting playback (and where you see the white line nothing is displayed):

$ LC_ALL=ru_RU.UTF-8 audacious

• (audacious:5106): CRITICAL **: textbox_render_bitmap: assertion 'utf32' failed

• (audacious:5106): CRITICAL **: textbox_draw: assertion 'data && data->buf' failed

In temrinal the same, but there is a white line

It doesn't matter whether there's a white line or a "black line", it's a bug/problem in either case. The kbps/kHz/mono/stereo info ought to be visible in that area of the window.

The problem is that the song info string is limited to 32 bytes, and the Russian translation is being truncated in the middle of a multi-byte character. The string shouldn't be translated anyway, since any non-English characters will just display as question marks. Fixed in Git master branch.

Hi John,
since there is no more translation, perhaps there is no more reason to format the text as before and the line:

snprintf (scratch, sizeof scratch, "%d %s", bitrate / 1000, "kbps");

could be improved as:

snprintf (scratch, sizeof scratch, "%d kbps", bitrate / 1000);

Same thing for the "kHz" text.

Fixed, thanks.

When playing some songs instead of the white line is displayed here such symbols

So it can somehow fix it?

Alex Zakl wrote:

When playing some songs instead of the white line is displayed here such symbols

Go back and read the thread again. Notice the part that says, "The string shouldn't be translated anyway, since any non-English characters will just display as question marks."

So yes, not translating the string also fixes the question marks.