Ubuntu

Industrial broken in Edgy

Bug #54550 reported by Paul Nolan
6
Affects Status Importance Assigned to Milestone
Ubuntu
Fix Released
Undecided
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gtk2-engines

Selecting a GTK theme based on the Industrial engine (IndustrialTango, Gorilla etc.) reverts GNOME to the default theme.

When launching an app from the command line the following warning appears:

/usr/share/themes/IndustrialTango/gtk-2.0/gtkrc:29: error: invalid identifier `xthickness', expected valid identifier

(I don't know much about GTK themes, but I can't see a problem when I look at the gtkrc)

I also noticed that in /usr/share/themes there is a folder called GTK2-Industrial-Engine, containing the source code for Industrial (surely that shouldn't be there?)

Revision history for this message
John Vivirito (gnomefreak) wrote :

Thank you for filing this bug. Can you please update your edgy there were gnome theme updates today. Are you using xgl by chance?

Changed in gtk2-engines:
status: Unconfirmed → Needs Info
Revision history for this message
Paul Nolan (paul-nolan) wrote :

I updated to gnome-themes_2.15.90-0ubuntu3 and it's still the same.

I'm not using Xgl (I have an Nvidia card, and it doesn't seem to like xorg 7.1 very much - the text kept disappearing, so I turned off Xgl & RenderAccel)

Revision history for this message
Arion (arion24-gmail) wrote :

Been having the same broblem

/usr/share/themes/Gray/gtk-2.0/gtkrc:35: error: invalid identifier `xthickness', expected valid identifier
/usr/share/themes/IndustrialTango/gtk-2.0/gtkrc:29: error: invalid identifier `xthickness', expected valid identifier

John Vivirito (gnomefreak)
Changed in gtk2-engines:
status: Needs Info → Confirmed
Revision history for this message
Daniel Holbach (dholbach) wrote :

Gray and IndustrialTango are not part of gtk2-engines. This must be a problem somewhere else a bit more deep down the stack.

Changed in gtk2-engines:
assignee: nobody → desktop-bugs
Revision history for this message
John Vivirito (gnomefreak) wrote :

Please make sure your system is up-to-date using gnome 2.16.1 and try to reproduce this error. Thank you for your bug report. let us know if it is fixed in fully updated system.

Revision history for this message
Paul Nolan (paul-nolan) wrote :

I'm up to date, and yes: it's working again.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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