Rigo/Fonts Issues with latest updates [Solved]

[linuxfluesterer]

Have any of you guys ever thought of launching Rigo from CLI?
Open a terminal or a konsole and run

Code: Select all

$ rigo

Of course I started rigo from CLI (konsole) for error message display after first time, when I launched Rigo by clicking.
The result is the same (for me). For you not? I'd really wonder, if it would work properly when launched by CLI.

-Linuxfluesterer (I love KDE ...)

[Butch Cassidy]

Every search looks like that. Reinstall didn't do much. Any clues?

TY.

[dunsurfin]

Is that a fault - or a new UI? A double click will open the item with details.

[Butch Cassidy]

Ah. If you see it then you're probably right.

It looks messy compared to before but I'll live with it.

Thanks anyway.

[dunsurfin]

Ah. If you see it then you're probably right.

It looks messy compared to before but I'll live with it.

Thanks anyway.

I'm not sure - it was just a guess - as it is messy. Rigo is a work in progress though.

[Ryuno-Ki]

Every search looks like that.

It's a known issue.
However, I'll report this topic and ask for closing or merging. It's more comfortable to discuss at just one place, you know?

[Ryuno-Ki]

Of course I started rigo from CLI (konsole) for error message display after first time, when I launched Rigo by clicking.
The result is the same (for me). For you not? I'd really wonder, if it would work properly when launched by CLI.

No, it does not work on my system either. But I am used to expect more … verbose error messages on CLI than on GUI. Hm, I tend to assume a problem with GTK-libraries. Maybe someone should fork rigo and implement a Qt-version

[Butch Cassidy]

I really don't care one way or another.

[dunsurfin]

I really don't care one way or another.

[linuxfluesterer]

No, it does not work on my system either. But I am used to expect more … verbose error messages on CLI than on GUI. Hm, I tend to assume a problem with GTK-libraries. Maybe someone should fork rigo and implement a Qt-version

Due to the GTK error messages, when rigo is launched by CLI I agree to a problem with GTK also. And I see it system immanent. And if I'm right, other members have problems with GTK also, when using Cairo (only assumption).
So, I've done a test to proof the assumption, that GTK is the reason: I have replaced the actual libgtk*.* in /usr/lib/ by libgtk*.* from my backup, I did before I made my upgrade on 17/01/2013.
Two libgkt-files were changed in last upgrade:
/usr/lib/libgtk-3.so.0.600.3 (before it was libgtk-3.so.0.400.4)
and
/usr/lib/libgtk-x11-2.0.so.0.2400.14 (before it was libgtk-x11-2.0.so.0.2400.10)
So, I replaced the newer libgtk-files with the older and also I replaced the files which are linked to those two libgtk-files:

Code: Select all

/usr/lib/libgtk-3.so -> libgtk-3.so.0.400.4
/usr/lib/libgtk-3.so.0 -> libgtk-3.so.0.400.4

and

Code: Select all

/usr/lib/libgtk-x11-2.0.so -> libgtk-x11-2.0.so.0.2400.10
/usr/lib/libgtk-x11-2.0.so.0 -> libgtk-x11-2.0.so.0.2400.10

After replacing (no reboot necessary) I've launched Rigo and that's what I get now:


So, this proofs, that gtklibs are the cause for weird appearing. And I assume in every programme, which uses gtklibs, those problems can appear.
I'd call it a bug, so hereby I'd like to ask, to whom I can send gtk bugs (moderators?).

Hope to help anyway. At the moment, I'll work with old gtk-libraries.

-Linuxfluesterer (I love KDE ...)