Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[RRM]

I think in a release build it would just skate over the problem.

Similar as it skates over the following issue, i guess.
Curious if its the same as what previously halted debug enabled aMule;
I received over 100 identical of the following warnings:

(amule:8584): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

[RRM]

I continuously keep getting these warnings (in the GDB terminal);
about 35 of these warnings per minute now!!

(amule:2128): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

Just not right away after restarting; it takes a few hours before they come back.
Once they come again, they keep coming.

[Stu Redman]

I'm always getting a flood of (amule:1544): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
. I believe it's a problem between wx and GTK. Yours might be similar.
You have any strings with strange characters on screen that don't get rendered properly?

[RRM]

You have any strings with strange characters on screen that don't get rendered properly?

I dont know, because i dont understand.
What screen?
In the GDB terminal window?
Or in aMule, in the "transfers" section?

[RRM]

I checked everything, but i couldnt find something like that anywhere.

[Stu Redman]

In aMule. Anywhere. The message indicates aMule is passing bad strings to wx to be displayed in GTK.

[btkaos]

AFAICT those warnings are GTK-related and can be safely ignored. Anyways, for the Pango warning the text doens't need to be displayed, could be a strange username of other network user, etc...

[RRM]

Thank you!