Bug 1184038 - GTK applications dump missing theme warning on console during startup
Summary: GTK applications dump missing theme warning on console during startup
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: cinnamon-control-center
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: leigh scott
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-20 14:04 UTC by m.oliver
Modified: 2015-12-02 17:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 07:40:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description m.oliver 2015-01-20 14:04:08 UTC
Description of problem:
When starting GTK applications from the console, they write a warning about missing theme files to stdout.  This is part of a larger problem of GUI applications indiscriminately writing unhelpful messages onto the console, and should be fixed.


Version-Release number of selected component (if applicable):
Tested with gtk3-3.14.6-1.fc21, likely applicable to a wide range of version numbers.

How reproducible:
Always

Steps to Reproduce:
[oliver@localhost ~]$ emacs &
[4] 4302
[oliver@localhost ~]$ 
(emacs:4302): Gtk-WARNING **: Theme file for default has no name


(emacs:4302): Gtk-WARNING **: Theme file for default has no directories


Actual results:
See above

Expected results:
No warning output.


Additional info:
This happens with applications other than emacs as well.  Applications seem to be working flawlessly.  Thus, the warning output should not be there.  In the event that the missing theme files can cause subtle problems, the package dependencies should be updated to ensure that the necessary files are actually there.  There is no point bothering the user about it.
For some discussion, I refer to the following fedora-devel thread:
https://lists.fedoraproject.org/pipermail/devel/2015-January/206484.html

Comment 1 Matthias Clasen 2015-01-26 19:14:15 UTC
Try 

gsettings reset org.gnome.desktop.interface icon-theme

This setting appears to have the value 'default' on your system, which is not the name of an existing icon theme, so GTK+ is perfectly right to complain.

Comment 2 m.oliver 2015-01-26 21:08:50 UTC
Only that the above reset has no effect:

[oliver@localhost ~]$ gsettings reset org.gnome.desktop.interface icon-theme
[oliver@localhost ~]$ emacs&
[1] 2824
[oliver@localhost ~]$ 
(emacs:2824): Gtk-WARNING **: Theme file for default has no name


(emacs:2824): Gtk-WARNING **: Theme file for default has no directories

For the record, I am using the cinnamon desktop.  Does that make a difference?

Comment 3 Matthias Clasen 2015-01-26 23:54:35 UTC
Yes, that is likely. No idea where cinnamon stores its settings, or how to reset them. Here is something you can do to confirm the problem:

run

GTK_DEBUG=interactive emacs

This should open a GtkInspector window in addition to the emacs window. In the inspector window, switch to the Visual tab, and check what the Icon Theme combobox shows as the current icon theme.

Comment 4 m.oliver 2015-01-27 07:54:03 UTC
OK, this is what I found: The GTK+ Inspector claims that the Icon Theme is "Adwaita".  The cinnamon theme dialog claims that the icon theme is "default" (the GTK+ Theme was consistently "Adwaita" on both).  Setting the cinnamon dialog to "Adwaita" (or anything else) silences the warning.

On the cinnamon side, I can always select "default" and it seems to resolve to "Adwaita", but gives the warning.

But here is a really funny thing: If I start emacs without GTK_DEBUG=interactive, it will show my selected cinnamon icon theme.  If I start with GTK_DEBUG=interactive, it will always show "Adwaita" icons and also claim on the Visual tab of the GtkInspector that "Adwaita" is the selected icon theme.

The debug option should not really interfere with what is being debugged?!

Comment 5 Matthias Clasen 2015-01-28 14:29:14 UTC
Thanks for this information - I think this points at cinnamon setting the wrong icon theme name.

Just to give some background information: The warnings appear to be harmless because GTK+ will always fall back to looking in the 'Adwaita' and 'hicolor' icon themes for missing icons.

Comment 6 Fedora End Of Life 2015-11-04 13:55:26 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2015-12-02 07:41:01 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.