I guess it’s really as you prefer. We can’t close bugs opened against the package on launchpad, so we’ll definitively get some there. Then, having in github+launchpad, github+launchpad and reporting launchpad bugs on github or only launchpad depends on how the team prefers to work.
Personally, I would prefer github since a) we have the whole history on there and b) Issues and PRs are just one tab away 
Don’t know how the others would prefer it.
2 Likes
@madsrh @frederik-f @3v1n0 @didrocks
Looking at this page diffs I noticed something that can explain the issue with the sound theme. not sure but please check it, you experts, and confirm if related.
The line I’m referring :
@@ -46,8 +46,13 @@ media-type-presets = {‘audio/x-vorbis’:‘Ubuntu’, ‘audio/mpeg’:‘Ubuntu’}
the URL : lp merge into master
Basically, If I understand it correctly the sound theme is not configured as Yaru/comunithen in gdm/ubuntu setting.
The issue on GitHub : Sound theme issue
Dismiss it as an unnecessary noise if I’m totally wrong about it 
2 Likes
I think that the code, and then the PR, will always be on github. It is just a matter of keeping and eye on both sites and reports links
I was really excited to release some new improvement on the Yaru dark variant theme, however, due to technical issues, we won’t be able to release the stable channel today 
Edge channel is affected by the same problem, however it is ahead respect stable and so you can test some of the content we worked on this week. Waiting for your feedback 
2 Likes
We made it, at last!
The Yaru team is happy to announce a new stable release!
This week we made a lot of improvements on the dark variant, let us know your opinion
- checked buttons in headerbar, dialog, notification and hotplug fully flat
- reduced differences from upstream to simplify future upgrades
- improved dark and light radio/check buttons backdrop and insensitive states
- improved dark Nautilus tabs (as well generic notebook tabs), in order to make it more similar to Gnome-terminal
- Suru Icon refresh
- improved dark pathbar
and thanks @didrocks for fixing the build 
6 Likes
This release has just been uploaded to Cosmic as well!
2 Likes
Hi everyone. Good job on the Yaru theme. It is a very nice refresh.
I’m worried about the logon screen background however. Is the purple the final color or is this a placeholder?
Has it been considered to use a background similar to the concept which was presented much higher in this thread? https://www.behance.net/gallery/28804097/Ubuntu-1604-Stupendously-Hot-Charmander-concept
I’m currently doing something similar to the concept in 18.04 by using a similar jpg file in ubuntu.css. It looks much more polished than the 18.04 default and than the 18.10 purple. Remember that the logon screen is the first screen a user sees. Shouldn’t it be amazing?
2 Likes
I agree! Sadly, gnome shell is a) a little bit limited when it comes to special effects and b) it needs to look good on any resolution down to 1360xno… wait… I think even lower…
I think we will keep this purple until the new GNOME login screen hits ubuntu
Edit: but if you have ideas, just post them here. Most of the ideas we implemented came out of this thread
Edit 2: if your idea with the image works on different resolutions, I personally interested in the implementation!
1 Like
Yes I noticed this, too in 18.04 with the calculator snap. I wonder why this happens Maybe it was build without the plug to Suru (I have really not the slightest idea how snaps work)
1 Like
In cosmic (thus without the snap) gnome-calculator is fine. Just gnome-system-monitor leaves out the suru icon in the shell, but shows it in the “about” dialog. Strange.
Since I can not answer in the “Theme-refresh topic” here Yaru-dark-variant , I want to add that I have an almost finished/functional Gtk2 dark variant. Not much to do but certainly not ready yet.
I can clean it, zip-it as is and hopefully some one can HELP with the finishing touches needed.
Some samples :
I’m slow and it’s a time consuming for a non coder as I am.
Anyway, I’ll have a dark variant to use with Ubuntu 18.10 for sure but if you want/can to help finish it I’ll be more then happy to share it .
5 Likes
Maybe you can already do a PR with your current changes so that further merge will be smaller? That’s fine to land WIP if that’s functional (and already better than before, no support at all ;))
Also: note that UIF is this week (Thursday), so it needs to be merged tomorrow and on Wednesday morning at the latest to cut it for 18.10
3 Likes
Wow thank you! This is a good surprise
Is a PR realistic or should we find other ways to use your code?
1 Like
… I PM-ed a dropbox link to @mozit there’s a problem with the package you shared
basically scale-horz-trough.png seems to be a link to another file instead that a proper file. Could you fix that?
EDIT: moreover, are you sure GTK2 accepts .svg files? I see only .png file in current version.
I believe (but I might be wrong) you should have changed the pictures inside assets.svg (and eventually assets-external.svg) file(s), instead that create a new .svg file for each element. Does this make sense?
@c-lobrano,
I’m almost sure it’s something I forgot to delete while cleaning the code. I’ll check it later today and let you know. .
svg is working just fine.
Not sure I understand what do you mean, so probably I didn’t do that
EDIT : I chedked, You can delete that link safely.
Not sure I understand what do you mean, so probably I didn’t do that
In your new package there is a long list of new .svg files, more o less one for each widget (e.g. arrow-blank.svg for arrow-blank.png). I assume you changed the aspect of the widgets file by file generating those new .svg.
Now, if you download Yaru project, you should see a file gtk/src/gtk-2.0/assets.svg which contains all the widgets in svg format. As far as I understood (or at least, is what I did last time), one is supposed to modify the widgets inside this file, then we can use the script render-assets.sh to generate the .png files for each asset to be used inside gtkrc and the others *.rc files
Being svg, I suspect I can move your new files inside the general assets.svg, however, I will hardly make it on time for tomorrow
Sorry for the mess I did. I’m not skilled enough to do it the right/easier way.
Now if you look at the main.rc file you will notice that the assets used are both .png and .svg. Can’t you use them as they come? - I mean, should you convert them to .png’s? .
Novice here - so my question is as stupid probably… 
In my Yaru-dark folder I have Gtk-2.0 folder… The one i sent to you, and it simply works. That’s all to it in my way of doing things - That’s why I’m not in the production table and can’t do my PR’s.