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 352432 - Really small tray icon
Really small tray icon
Status: RESOLVED FIXED
Product: tomboy
Classification: Applications
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on: 354416
Blocks:
 
 
Reported: 2006-08-22 18:13 UTC by Michael Monreal
Modified: 2008-02-26 20:50 UTC
See Also:
GNOME target: 2.18.x
GNOME version: ---

Attachments
Screenshot (2.44 KB, image/png)
2006-08-22 18:15 UTC, Michael Monreal 		Details

Description Michael Monreal 2006-08-22 18:13:41 UTC 
Sometimes tomboy seems to start up with a really improperly scaled tray icon. The icon is really small, only 2x2 pixels I think. See screenshot.

I can't reproduce this properly, but it did happen a few times now.
Comment 1 Michael Monreal 2006-08-22 18:15:38 UTC 
Created attachment 71386 [details]
Screenshot

The small yellow dot in between the mugshot and the networkmanager icons is the tomboy icon!
Comment 2 Boyd Timothy 2006-11-20 23:01:13 UTC 
Just checked-in a fix into CVS Head for this.
Comment 3 Michael Monreal 2006-11-21 15:03:53 UTC 
This doesn't seem to be fixed for me: I updated to HEAD this night (no checkins since then) and after rebooting now it started with the small bitmap again.
Comment 4 Boyd Timothy 2006-11-21 15:30:48 UTC 
Yeah, sorry.  I used the wrong Gtk.Image () constructor.  The same code is being touched for Bug #354416, which I believe will fix this issue.  If you'd like to grab that patch (http://bugzilla.gnome.org/attachment.cgi?id=76962&action=view) and see if it fixes this problem, that'd be great.  Otherwise, wait for us to get that one checked-in before you try it out.
Comment 5 Boyd Timothy 2006-11-21 22:00:38 UTC 
This should be fixed now (as part of the fix to Bug #354416).