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 562752 - Some icons are not visible while no gtk-icon-theme-name is set
Some icons are not visible while no gtk-icon-theme-name is set
Status: RESOLVED DUPLICATE of bug 596309
Product: balsa
Classification: Other
Component: general
2.3.x
Other All
: Normal minor
: ---
Assigned To: Balsa Maintainers
Balsa Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-30 11:58 UTC by Robert Cernansky
Modified: 2009-10-10 01:34 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
proposed patch (698 bytes, patch)
2008-12-01 01:08 UTC, Peter Bloomfield
none Details | Review
replacement patch (702 bytes, patch)
2008-12-01 02:52 UTC, Peter Bloomfield
none Details | Review

Description Robert Cernansky 2008-11-30 11:58:05 UTC
Please describe the problem:
For users that has no ~/.gtkrc-2.0 file or has not gtk-icon-theme-name option set in it, some icons in toolbar and in folder treeview are not displayed. Just empty place for icon and text is displayed but no icon picture.

In main window toolbar following icons are missing: Check, Compose, Continue, Reply, Forward.

In folder treeview icons for 'Inbox' and 'Outbox' are missing. When hovering the mouse over these two entries following messages are printed to console:

(balsa:12245): Gtk-WARNING **: could not load image: Icon 'balsa_mbox_in' not present in theme
(balsa:12245): Gtk-WARNING **: could not load image: Icon 'balsa_mbox_out' not present in theme

When add following entry to ~/.gtkrc-2.0, all icons are visible:

gtk-icon-theme-name = "gnome"


Steps to reproduce:
1. Prepare user that has not ~/.gtkrc-2.0 file or has not gtk-icon-theme-name option in it.
2. Run balsa as user prepared in 1).


Actual results:
Balsa is running with some of the icons missing.


Expected results:
Balsa should have all icons visible also for (non-gnome) users that has no ~/.gtkrc-2.0 file.


Does this happen every time?
Yes.


Other information:
Comment 1 Jack Ostroff 2008-11-30 14:23:27 UTC
I have had exactly the same problem.  In my case, I run primarily a KDE system, with only a few Gnome utilities, like Balsa, which may account for having never created a .gtkrc-2.0 file.
Comment 2 Peter Bloomfield 2008-12-01 01:08:19 UTC
Created attachment 123716 [details] [review]
proposed patch

Could you try the attached patch?  In principal, it should remove the need to set up your ~/.gtkrc.  All I can say is that on a Gnome system, it doesn't break anything (yet!).
Comment 3 Peter Bloomfield 2008-12-01 02:52:38 UTC
Created attachment 123718 [details] [review]
replacement patch

The first patch was missing a newline--this one may work better.
Comment 4 Robert Cernansky 2009-05-20 19:33:19 UTC
Sorry for late answer. Unfortunatelly the patch is not working. Icons are still not visible. Patch tested with 2.3.28.
Comment 5 Peter Bloomfield 2009-05-22 17:20:40 UTC
No problem!  But also no progress :(

As far as anyone can tell, the only way to get those icons is to use the ~/.gtkrc file.  For the record, the issue was discussed in a thread[1] on the balsa list, with no further insights.

Let's leave this open, in case someone comes up with a bright idea.

[1] <URL:http://mail.gnome.org/archives/balsa-list/2008-December/msg00050.html>
Comment 6 Peter Bloomfield 2009-09-27 17:14:25 UTC
A patch suggested by Stanislav Brabec, using gtk_settings properties, is attached to bug #596309.  Please see whether it solves the problem.  Thanks!
Comment 7 Peter Bloomfield 2009-10-10 00:54:53 UTC

*** This bug has been marked as a duplicate of bug 59609 ***
Comment 8 Morten Welinder 2009-10-10 00:59:49 UTC
> *** This bug has been marked as a duplicate of bug 59609 ***

I think you have the wrong bug number.
Comment 9 Peter Bloomfield 2009-10-10 01:34:07 UTC
Apparently my '3' is sticky--thanks for pointing out the error!

*** This bug has been marked as a duplicate of bug 596309 ***