After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 315286 - Warn if there are engines missing
Warn if there are engines missing
Status: RESOLVED OBSOLETE
Product: gnome-tweak-tool
Classification: Applications
Component: general
unspecified
Other All
: Normal minor
: ---
Assigned To: GNOME Tweak Tool maintainer(s)
GNOME Tweak Tool maintainer(s)
Depends on:
Blocks: 511065
 
 
Reported: 2005-09-05 11:21 UTC by Sven Herzberg
Modified: 2011-10-22 02:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
gtkrc that seems to have a missing engine (28.09 KB, text/plain)
2008-11-29 20:32 UTC, Gil Forcada
Details
Message without any engine, just the quotes (100.21 KB, image/png)
2008-11-30 12:27 UTC, Gil Forcada
Details
My whole gtk theme (37.69 KB, application/x-compressed-tar)
2008-11-30 12:29 UTC, Gil Forcada
Details

Description Sven Herzberg 2005-09-05 11:21:01 UTC
Please describe the problem:
If one installs a theme that requires an engine that's not installed, the theme
looks ugly.

Steps to reproduce:
easily, install and select a theme with a missing engine

Actual results:
the selected theme looks crappy

Expected results:
i would expect to check whether the referenced engines are installed, if not,
open up a warning "you need to install the gtkfoobar-engine for this theme"

Does this happen every time?
only when engines are missing

Other information:
Comment 1 Thomas Wood 2005-12-30 15:25:05 UTC
The theme manager would have to parse the gtkrc that it has just installed and check any engines referenced actually exist.
Comment 2 Nickolay V. Shmyrev 2006-02-24 22:12:43 UTC
I would prefer to see something about

(STOP) This theme requires engine '...' that is not installed yet 

in theme list rather than popup.
Comment 3 Sergey Al. Safonov 2006-02-24 22:13:47 UTC
I'm going to work on this bug.
Comment 4 Markus Bertheau 2006-02-24 22:46:24 UTC
Probably the theme should not be shown at all if the engine is not installed.
Comment 5 Thomas Wood 2006-06-13 09:58:16 UTC
Should the warning appear when you install the theme, or every time you selected it?
Comment 6 Luca Cavalli 2006-06-13 10:08:30 UTC
If the theme is installed system-wide and two users select it, none of them has instaled the theme, but both of them should receive the warning.
Comment 7 Luca Cavalli 2006-06-13 10:14:36 UTC
Indeed, as Nickolay already suggested, it would be better to have the theme disabled in the list, maybe with an emblem over the thumbnail and an explaining message with the missing engine name.
Comment 8 Sven Herzberg 2006-06-13 10:36:00 UTC
As Luca said: we should have an emblem (somthing like GTK_STOCK_WARNING or GTK_STOCK_ERROR) in front of the theme name and print that warning everytime the user selects that theme (we could popup a dialog from within the _iter_selectable() callback of the selection and return true if the user said "yes, i want an ugly desktop").

But on the other hand, an additional warning on theme installation would be useful too (maybe using the same check mechanism after installing the theme and then asking the user whether he want's to undelete that theme again).

It's both not useful to select a partial theme or to install one.
Comment 9 Thomas Wood 2008-04-11 16:29:37 UTC
gnome-theme-manager has been superseded by gnome-appearance-properties.
Comment 10 Gil Forcada 2008-11-29 20:31:10 UTC
Maybe this is implemented already?

I have a warning above the buttons that tells my that is missing and engine. But it doesn't tell me which one.

Seems the gtk_theme_info_missing_engine() function doesn't return the correct results.

Attaching my gtkrc, if it helps.
Comment 11 Gil Forcada 2008-11-29 20:32:10 UTC
Created attachment 123662 [details]
gtkrc that seems to have a missing engine
Comment 12 Jens Granseuer 2008-11-30 10:18:35 UTC
Yes, parts of this are implemented. The error message should give the engine name, though. What's the message you get?

The gtkrc you attached makes my gtk crash, so, erm, there seems to be something else wrong with it.
Comment 13 Gil Forcada 2008-11-30 12:27:06 UTC
Created attachment 123688 [details]
Message without any engine, just the quotes
Comment 14 Gil Forcada 2008-11-30 12:28:49 UTC
Maybe it crashes because it misses the images?

I'm attaching the whole theme.
Comment 15 Gil Forcada 2008-11-30 12:29:41 UTC
Created attachment 123690 [details]
My whole gtk theme
Comment 16 Gil Forcada 2008-11-30 12:30:32 UTC
btw ... there's any way to debug a gtkrc?
Comment 17 Jens Granseuer 2008-11-30 12:47:02 UTC
Hm, ok, this part from the gtkrc causes that to happen:

# This prevents Sodipodi from crashing while opening the
# Object-Style dialog.


style "unstyle"
{
  engine ""
  {
  }
}

I'll add a workaround.
Comment 18 Gil Forcada 2008-11-30 19:46:45 UTC
Oh, great.

It doesn't display any error know :)