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 775170 - missing mono testing icons in sound panel
missing mono testing icons in sound panel
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Sound
git master
Other Linux
: Normal normal
: ---
Assigned To: Jakub Steiner
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-11-27 11:51 UTC by Matthias Clasen
Modified: 2018-01-12 21:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
mono speaker test (39.18 KB, image/png)
2016-11-27 11:51 UTC, Matthias Clasen
  Details
sound: update artwork (344.48 KB, patch)
2017-09-26 15:35 UTC, Jakub Steiner
committed Details | Review

Description Matthias Clasen 2016-11-27 11:51:51 UTC
Created attachment 340839 [details]
mono speaker test

Saw this recently
Comment 1 Bastien Nocera 2016-11-28 11:06:24 UTC
The missing icon names are "audio-speaker-mono-testing" and "audio-speaker-mono".
Comment 2 Jakub Steiner 2017-09-26 14:48:48 UTC
Looks like the sound panel ship these pixmaps. Makes sense to add to the set there. Also some styling tweaks are due.
Comment 3 Jakub Steiner 2017-09-26 15:35:54 UTC
Created attachment 360463 [details] [review]
sound: update artwork

- restyle all assets symbolic
- add missing mono speaker
Comment 4 Mario Sánchez Prada 2017-10-13 09:37:00 UTC
Just reproduced this one on Endless as well. Ubuntu worked it around so far by symlinking to audio-speaker-center*[1], but I personally would rather integrate the proposal here, including the style changes.

Any chance this will land soon?

[1] https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1704002
Comment 5 Rui Matos 2017-10-13 14:02:52 UTC
Review of attachment 360463 [details] [review]:

definitely looks good. unfortunately it break the UI freeze on stable that's why I didn't push it yet, but let's do it now
Comment 6 Mario Sánchez Prada 2017-10-16 10:17:10 UTC
Sounds good. @Jakub: would you mind pushing your patch to master then?
Comment 7 Jakub Steiner 2017-10-17 21:54:47 UTC
Attachment 360463 [details] pushed as 8bfd0b9 - sound: update artwork
Comment 8 Jan-Michael Brummer 2017-10-21 20:32:32 UTC
Relates to https://bugzilla.gnome.org/show_bug.cgi?id=780546 

There are still 4 icons missing.
Comment 9 Mario Sánchez Prada 2018-01-12 19:13:19 UTC
I've just noticed this patch is in the master branch but it's not in the gnome-3-26 branch. @Rui, any reason not to push it there?
Comment 10 Bastien Nocera 2018-01-12 20:53:01 UTC
(In reply to Mario Sánchez Prada from comment #9)
> I've just noticed this patch is in the master branch but it's not in the
> gnome-3-26 branch. @Rui, any reason not to push it there?

Rui doesn't work for RH anymore, so probably won't be looking at GNOME patches for a while. The patch (in commit 8bfd0b97d6a4af2fdf3db5d8920d22db4b5f3106) changes the style of the icons, so is a UI change that we can't apply to a stable branch.

Please file a new bug, and attach a patch for gnome-3-26 within the existing style if you want it fixed in that version.
Comment 11 Mario Sánchez Prada 2018-01-12 21:43:13 UTC
(In reply to Bastien Nocera from comment #10)
> (In reply to Mario Sánchez Prada from comment #9)
> > I've just noticed this patch is in the master branch but it's not in the
> > gnome-3-26 branch. @Rui, any reason not to push it there?
> 
> Rui doesn't work for RH anymore, so probably won't be looking at GNOME
> patches for a while. The patch (in commit
> 8bfd0b97d6a4af2fdf3db5d8920d22db4b5f3106) changes the style of the icons, so
> is a UI change that we can't apply to a stable branch.

Oops! Right... the patch landed after 3.26 got released, doesn't make sense to apply on the stable branch, sorry.

> Please file a new bug, and attach a patch for gnome-3-26 within the existing
> style if you want it fixed in that version.

No problem, we're good backporting this one ourselves, no need to force things. Thanks for clarifying, I completely overlooked that fact :)