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 544784 - Frequency applet needs new icons
Frequency applet needs new icons
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: cpufreq
2.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 555794 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-07-25 23:55 UTC by Magnus Boman
Modified: 2020-11-06 19:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
Screeny (30.63 KB, image/png)
2008-07-25 23:55 UTC, Magnus Boman
Details
cpufreq-applet icons by perfectska04 preview (3.71 KB, image/png)
2009-03-19 14:28 UTC, Martin Lettner
Details
cpufreq-applet icons by perfectska04 package (4.46 KB, application/x-gzip)
2009-03-19 14:30 UTC, Martin Lettner
Details

Description Magnus Boman 2008-07-25 23:55:20 UTC
When resizing the panel, the CPU Frequency applet icon should scale up/down. This does not currently happen.
Will attach screeny
Comment 1 Magnus Boman 2008-07-25 23:55:49 UTC
Created attachment 115280 [details]
Screeny
Comment 2 Carlos Garcia Campos 2008-07-26 11:58:57 UTC
Yes, this is because we are using fixed size icons. We need new svg icons. (Adding Andreas to CC)
Comment 3 Carlos Garcia Campos 2008-10-10 17:02:59 UTC
*** Bug 555794 has been marked as a duplicate of this bug. ***
Comment 4 Andreas Nilsson 2009-02-21 11:55:12 UTC
Lapo, did you have a newer version of these somewhere, or was that someone else?
Comment 5 Martin Lettner 2009-03-19 14:28:00 UTC
Created attachment 130972 [details]
cpufreq-applet icons by perfectska04 preview
Comment 6 Martin Lettner 2009-03-19 14:30:47 UTC
Created attachment 130973 [details]
cpufreq-applet icons by perfectska04 package

put them into /usr/share/pixmaps/cpufreq-applet
Comment 7 Martin Lettner 2009-03-19 14:32:47 UTC
maybe some of you know them already but there are some really nice and modern icons for the cpufreq applet in the icon theme GNOME-colors [0] by perfectska. i'm sure the author still has the svg resources and can make vector icons for this applet.

i attached a preview and the icons so you don't have to download the whole pack.

[0] http://www.gnome-look.org/content/show.php/GNOME-colors?content=82562
Comment 8 Andreas Nilsson 2009-03-19 14:41:03 UTC
Martin: the style of the new icons looks good to me, we need more sizes though.
Do you have the sources (svg's) as well?
Comment 9 Martin Lettner 2009-03-19 15:19:59 UTC
Andreas: no i don't have svg sources but i already contacted the author (perfectska04).

anyway it seems the icons are originally by another guy: http://www.michelem.org/2007/05/22/tangoish-gnome-applets-cpufreq-and-sensors-with-tango-icons/ there's also an icon for the About dialog.
btw: this link is from the duplicate bug #555794 and the blog entry is from may 2007...
Comment 10 Andreas Nilsson 2009-03-19 16:05:07 UTC
I think they might even originate from William Szilveszter, but I can't tell for sure.
http://lokheed.deviantart.com/art/Tango-GNOME-Core-Image-Pack-38422263

I'm afraid the origins and copyright of these icons are a bit too shady for us to consider them. Better to draw new ones (and in several sizes, and what the bug is actually about).
Comment 11 Rodney Dawes 2009-04-16 14:21:32 UTC
They are originally from William Szilveszter, yes. But I'm not sure what the license is. I think they might be CC-By-SA 2.5.
Comment 12 André Klapper 2020-11-06 19:56:40 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-applets/-/issues/

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