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 519618 - Outdated headphones icon
Outdated headphones icon
Status: RESOLVED DUPLICATE of bug 696402
Product: adwaita-icon-theme
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Jakub Steiner
Jakub Steiner
Depends on:
Blocks:
 
 
Reported: 2008-02-29 20:37 UTC by Bastien Nocera
Modified: 2013-04-28 13:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2008-02-29 20:37:17 UTC 
This icon is used in bluez-gnome and in gvfs' ObexFTP support, but it doesn't have any sizes bigger than 24x24, and wasn't updated for the new style of icons.
Comment 1 Andreas Nilsson 2008-09-24 08:00:59 UTC 
What is the name of this icon?
Comment 2 Bastien Nocera 2008-09-24 08:20:12 UTC 
"stock_headphones" is what was used in bluez-gnome. Marcel was interested in using it as the icon name in bluez itself as well (which would mean that pretty much every bluetooth app would use it for headset icons). Right now it uses "audio-card" as it's the closest icon to what we'd need...
Comment 3 Lapo Calamandrei 2008-09-24 09:48:18 UTC 
I think it would be usefull to have some audio related icons blessed by the naming specs. What do you think Rodney?
I think something like device/headphones, device/speaker, device/headset will cover most of the use cases.
Comment 4 Bastien Nocera 2008-09-24 16:38:32 UTC 
We probably don't need separate icons for headphones and headsets, except if you make the headset look like a bluetooth earpiece I guess.
Comment 5 Lapo Calamandrei 2010-03-29 16:34:19 UTC 
These icons make sense a naming specs addition would be nice. What do you think Jakub?
Comment 6 Bastien Nocera 2013-04-28 13:03:31 UTC 
Icons have been added in bug 696402

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