.gtkrc-2.0 broken

Bug #54552 reported by Elias Amaral
4
Affects Status Importance Assigned to Milestone
gtk-qt-engine (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gtk2-engines-gtk-qt

I am using ubuntu dapper (not kubuntu) when I installed all gtk engines on repositories. Finished it, all gtk apps stopped work - and, yes, when i rebooted X, i could not login in GNOME. So i moved all .gtk* and .gnome* from my home to a backup dir and added one file per time, so I found that the .gtkrc-2.0 was broken. Here is it's contents:

---

# This file was written by KDE
# You can edit it in the KDE control center, under "GTK Styles and Fonts"

include "/usr/share/themes/Qt/gtk-2.0/gtkrc"

style "user-font"
{
        font_name="DejaVu Sans 9"
}
widget_class "*" style "user-font"

gtk-theme-name="Qt"
gtk-font-name="DejaVu Sans 9"

---

So i think it's somewhat related to gtk2-engines-gtk-qt package. Simply removing this file avoids all problems described.

When I tried to open a gtk2 program, the X says about a unknown device 166, opcode 4, or something like this. I don't noticed at time this information would be useful.. but when trying to reproduce it now, the program says only Segmentation Fault..

Revision history for this message
David Sansome (me-davidsansome) wrote :

This should be fixed in version 0.7 of the gtk-qt engine. Unfortunately it seems that Dapper still only packages version 0.6.

Revision history for this message
Elias Amaral (dlight) wrote :

OK. Gtk-qt isn't so useful while I am on GNOME, so I can wait the version 0.7 on Ubuntu. :)

Revision history for this message
Michael S. (jellicle) wrote :

I'm having the following symptoms (using Edgy): fonts are very poorly rendered in certain GTK2 applications, under KDE. For instance, Gaim and Gnucash are both rendering terrible, jaggy fonts. Firefox, somewhat oddly, seems unaffected and is rendering fonts properly.

Would these symptoms also be caused by this same bug? The version of gtk2-engines-gtk-qt that I have installed is 0.70-0ubuntu1, from Edgy.

Revision history for this message
David Sansome (me-davidsansome) wrote :

Michael,

I've never heard of that happening before. It sounds like a font configuration problem - maybe you have your antialiasing settings turned off in Gnome?

It seems unlikely to be a problem with the gtk-qt-engine, but just to be sure could you try using another GTK theme and telling me if it still occurs? You can change your GTK theme under "GTK Styles and Fonts" in the KDE control center.

Thanks.

Revision history for this message
da1l6 (da1l6) wrote :

Yet another graphics problem with gtk2-engines-gtk-qt:

On a fresh installed Kubuntu Edgy (final release) gtk apps (tested with synaptic, gimp and eclipse) have an ugly dark window backgound, while KDE apps have not. Screenshot attached.

Revision history for this message
David Sansome (me-davidsansome) wrote :

In reply to da1l6,

I'm unable to reproduce your colour problem with a fresh install of Edgy and the latest gtk-qt engine from svn.
Maybe that bug has been fixed already?

Revision history for this message
Bertrand Croq (bcroq) wrote :

I still get this bug with Feisty (with Eclipse too) ! This bug is said to be fixed on Debian's 0.8~svn-rev26-1 but I can't confirm.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. Do you still have this issue with the latest stable release of Ubuntu ?

Changed in gtk-qt-engine:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Ryan Kavanagh (ryanakca) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gtk-qt-engine:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.