[01:15] I've bought a controller (yay!) and I noticed that when I'm playing a game using it, the screen turns off because of the power settings, as if I was not pressing anything [01:54] FurretUber: yeah, controller input doesn't register as a power inhibiting event [01:54] Updated release notes for final beta, https://wiki.xubuntu.org/releases/18.04/release-notes [02:04] Are there plans to correct https://bugzilla.xfce.org/show_bug.cgi?id=13979 ? [02:04] bugzilla.xfce.org bug 13979 in General "Some application names are not localized in applications menu" [Normal,Needinfo] [02:09] For 18.04 release [02:09] FurretUber: makes sense to. Not sure garcon has a current maintainer, but I might try to resolve it this weekend. [02:14] Tidied up blueprints a bit [02:14] nighty all [03:53] bluesabre: thanks :) [04:10] Unit193: grabbed numlockx from -proposed - I assume the update should change the naughty line in 55numlockx? or do we need to do that seperately? [04:10] because if we don't 'need' to - I've got news for you :p [04:11] that said as I wake up - I think my assumption is wrong in the first place ... I now assume that's from one of our xubuntu-* things [04:27] 55numlockx is from numlockx. [04:28] mmm perhaps it took a reboot then - now see else ... /usr/bin [04:28] if I had a useful laptop I'd check :p [04:51] vm showed change immediately so I guess I was half asleep [05:01] ali1234 bluesabre - re 'someone noticed it in debian in november' so that's around when I first noticed it and asked if anyone could reproduce ... really must ask these things in CAPSLOCK next time ;) [05:05] bluesabre: last ping this morning for you - marked us ready [06:47] hi all. I'll have time to do some more testing later today. Just wondering what the right strategy is: should I keep testing with the beta 2 ISO as I downloaded it yesterday? Or should I use zsync to keep it up to date? === sorinello_ is now known as sorinello [07:32] willem, unless there has been respins, the ISO is the same (that's the whole point of the freezes) [07:51] I'm new to this, so bear with me: a respin is a new version/build of something? The final beta will be frozen for now? And if there is a respin of the beta that will be announced so that I can update my iso? [09:52] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 18.04 - i386 - i386 built. [10:16] flocculant: CAPSLOCK? Did you say something, that's all I was able to read. :D [10:17] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 18.04 - amd64 - amd64 built. === TJ_Remix is now known as TJ- [16:33] willem: I marked final beta ready this morning - so no more required - and you only need zsync when a respin happens [16:34] so, no worries then? [16:35] nope - all good :) [16:36] :-) [16:36] I'll resume testing the dailies again then, shall I? [16:39] you can have a rest now - the daily is effectively pointless now till tomorrow :) [16:42] flocculant: i think laney just uploaded the fontconfig patch [16:42] Is the number of "issues" found in the second beta more or less what you'd expect in this point of time? [16:43] willem: pretty much [16:43] ali1234: ack - just been looking in -desktop [16:46] good. I´ll be at the piano then... :-) Back tomorrow, end of the day I expect. [16:46] have a good time in between then :)( [16:46] :) [19:23] Humm, who shoul be IPv6-enabling the xubuntu services please? [19:23] canonical have IPv6-enabled on vairous fty anh otherwise, as well as their 91.189. etc [e.g. for www.xubuntu.org] [19:23] the wiki.xubuntu.org, on linode, needs tohe server advin to turn on IPv6 with linode (NB: be careful of IPv6 forward-formimed reverse-DNS to avoid email trouble), and add AAAA-pointers there. [19:23] knome pleia2 ^^ [19:24] yes, I'm very familiar with using IPv6 on Linode ;) [19:25] we just haven't bothered since the migration from canonical, I can do it if there's interest [19:26] the main blocker is that xubuntu.org can't have it (still Canonical-hosted) so I wasn't sure about enabling some of our resources, but not others [19:26] pleia2:what!?!?!? caninical have IPv6 [19:26] pleia2: e.g. ftp.ubuntu.com all dual stacked [19:26] pleia2: you can definitely enabled separate services one at atime [19:27] enyc: are you sure? the last time I asked they hadn't added IPv6 to the community servers [19:27] enyc, thing is we have root access to only certain subdomains. [19:27] enyc: I know I can ;) I do know how to use computers [19:27] pleia2: what you must NOT do is create (a) a broken AAAA-pointer (before service ready / consistent ipv6 address /firewall-rule etc working) and (b) IPv6-enable a host without setting up forward-confirmed reverse-DNS on the address (assuming dost requires revers, which is very good practice and CRITICAL for getting emails out especially to gmail) [19:28] pleia2, maybe we should create a new RT ticket and try? [19:28] enyc: you're kind of insulting my intelligence at this point, maybe stop? [19:28] please try, though i wonder if its' best todo after 18.04 'released' ? [19:28] enyc, please, pleia2 doesn't need technical advice. as she describes, this is a social issue [19:29] pleia2: knome asked about "wasn't sure about enabling some of our resources, but not others" hence giving reasonable answer [19:29] as knome explains, this is a social thing, not a technical barrier [19:29] enyc, that refers to what i said; we have root acces to only some resources [19:29] enyc: it's extremely doubtful this would even get looked at by the team before 18.04 is released - we've got a distro to release [19:29] I certainly won't have time to think about it [19:30] flocculant: right yes, hence my point about best todo after 18.04 released [19:30] yes, but even if our team looked at it, it's likely that the canonical IS team will likely not do anything or even reply before release... [19:30] they've got a hugh queue I read elsewhere [19:30] knome: right yes nthat makes snes, so make a project issue/diary/alarm/whatever to choose better time to requset it =) [19:31] main thing is your project aware of the issue =) [19:31] yeah, it's something I've spoken to Canonical about before, and we do have the techincal expertise to address, it just hasn't gotten much attention of late [19:31] My organizization relevant IS team, simply needed telling about TLS1.0 limit on a key/core authentication system and they quickte quickly tested/fixed it to TLS1.2 enablement, for example. [19:33] enyc, you could file a bug here: https://bugs.launchpad.net/xubuntu-website; no need for the technical details, just mention enabling ipv6 [19:33] i wish all IS teams were as responsive as yours then, i guess [19:34] you have to remember they are paid to provide services mostly for other people who are paid [19:34] community like xubuntu is just a thing they do in the side when they have time (not completely true, but it helps understand the situation we're in) [19:37] well [19:37] that is pretty much the case - just sometimes we manage to make some time [19:38] well i was about to say "or when there is enough pressure to make canonical look bad if they don't do anything" but i didn't want to be that aggressive... [19:38] and tbh, that's not correct either [19:38] there are things that happen very quickly.... [19:38] (even when they aren't critical to anybody by any means) [19:39] this is all mostly related to repeating processes though, but still [19:39] at least they've got something fixed :) [19:39] :) [19:40] aiui, the IS team is also very overloaded with work [19:41] but enough of that. [19:44] I just tested the beta iso instalation process. Would it be helpful if i submit the result here? http://iso.qa.ubuntu.com/qatracker/milestones/388/builds/169633/testcases/1301/results [19:44] ondondil, yes, yes and yes! [19:44] (if you don't submit, it's next to useless) [19:44] ondondil: you have to - I closed the beta earlier today :) [19:44] oh :P [19:45] it was about versions [19:45] * knome hides [19:45] any and all reports of tests are welcome - and I even read the archived ones :) [19:45] * flocculant can still see knome ... [19:45] dang [19:45] :) [19:47] willem: re did you by any chance look at systemctl status system-reboot.service? https://i.imgur.com/mUzRaIv.png [19:59] got a weird bug to post for suspend on lid close for a laptop.. an old core2duo.. just need to check that its not the laptop first [19:59] akxwi-dave: there has been talk in here for days about some lid close issue [19:59] which has completely passed me by because - no lid ... [20:00] aye.. thats why I ran extra tests :-) [20:00] akxwi-dave: I'm still working on it [20:00] akxwi-dave: is it this? Bug #1759950 [20:00] bug 1759950 in light-locker (Ubuntu) "Lid-close suspend: blank screen when switching to user session" [Undecided,New] https://launchpad.net/bugs/1759950 [20:02] nope this is really weird.. when i open it teh screen is all blue and when I move the mouse it sort of moves another bl;ue screen up and down screen [20:02] hang on i'll video it [20:02] akxwi-dave: does it happen if you switch away from the GUI tty before closing the lid? [20:03] knome: if no-one turns up at meeting it's because the time link was wrong :p [20:03] not tried that [20:03] flocculant, haha [20:04] I only noticed - because utc and uk summer confuses me till about October :D [20:04] yes... [20:04] then time=utc and I'm cool for another 6 months [20:05] !team | reminder: community meeting in roughly 2hrs [20:05] reminder: community meeting in roughly 2hrs: akxwi-dave, bluesabre, dkessel, flocculant, jjfrv8, knome, krytarik, ochosi, pleia2, slickymaster and Unit193 [20:05] not sure I'll be functioning still ochosi [20:05] DST should not be used... [20:05] flocculant: anything you wanna mention now so we can carry it to the meeting? [20:05] I took both the links I had on there off - both look soon sorted [20:05] kewl [20:05] okay, so I submitted a passed test result. I'm not entirely sure if I did it right but I hope that helps tho [20:05] thank the new testers [20:05] awesome [20:06] ondondil: thanks \o/ [20:06] excellent [20:06] o7 [20:07] ondondil: where did you post it? [20:07] and thanks :) [20:07] or are you seanmc ? [20:08] http://iso.qa.ubuntu.com/qatracker/milestones/388/builds/169633/testcases/1301/results my nick there is imrahil [20:08] where teh best place to post a video? [20:08] internet [20:08] ondondil: thanks [20:08] lol.. (sod off mate.. 😃 [20:08] :p [20:09] akxwi-dave: some ppl use youtube..? :) [20:09] I often use streamable.com [20:09] ochosi: lol [20:10] I cnnt believe I forgot about yourtube [20:10] well you also forgot I'd likely say 'internet' ... [20:11] ochosi, some people also use 4chan (: [20:11] https://youtu.be/3UcvvfL_2ag [20:12] when reopen a second time the bug stops. [20:12] I've seen that before [20:13] obviously not the youtribe video [20:13] never seen The Photon Raiders though [20:13] ahhh :-) old gaming clanm I used to help run [20:14] :) [20:15] The laptop is a HP Compaq 6730b core2duo P8700 with intel 1625 video [20:17] I think laptop isn't necessarily the issue - I've had that on desktop way back [20:17] sorry Intel GMA 4500MHD [20:17] ahh [20:17] couldn't reproduce though [20:18] it used to just happen [20:26] bluesabre: i just found another small icon bug that needs fixing for 18.04 - can we do another xubuntu-artwork upload? [20:27] we can't keep changing the release note you know :p [20:28] hehe [20:28] it's really just a bugfix ;) [20:28] (and it's also unreported, so nothing to announce apart from: we have nicer icons!) [20:29] * flocculant changes release note to 'Ochosi just keeps on finding icon issues' [20:29] :D [20:29] * flocculant goes looking for elusive elliptical circles [20:33] i didn't know flocculant was so grumpy and against change that he didn't even allow fixes for bugs ;) [20:33] :p [20:38] hehe [20:48] ochosi: sorry - can't stay awake for another 90 minutes - so I will read the logs in the morning. [20:48] sure thing [20:48] nighty flocculant [20:48] nighty flocculant [20:48] final beta is likely to be released late 'today' or tomorrow if you want to announce - but frankly I'd rather we didn't advertise milestones - will leave that decision to you [20:49] as long as you make the right one :D [20:49] quick shout to testers [20:49] would probably make sense to write down some policies on announcement stuff etc. [20:49] mmm [20:49] the release note/announcement differences too [20:49] but... later [20:49] :) [20:49] yea that for sure - should be different [20:49] they have been too [20:50] anyway - night all [20:50] yea I know :) [20:50] but good to have stuff documented [20:50] ngihty [20:50] and nighty :P [20:50] :) [20:53] night [21:38] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: thunar 1.7.2 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-thunar-1-7-2-released-tp50883.html (by Alex) [21:57] LP #1685502 has just been reassigned btw. [21:57] Launchpad bug 1761606 in network-manager-applet (Ubuntu) "duplicate for #1685502 Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session." [Undecided,Confirmed] https://launchpad.net/bugs/1761606 [21:58] !team | final reminder: meeting in <5min [21:58] final reminder: meeting in <5min: akxwi-dave, bluesabre, dkessel, flocculant, jjfrv8, knome, krytarik, ochosi, pleia2, slickymaster and Unit193 [21:58] a very brief reminder;) [21:58] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: thunar 1.6.15 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-thunar-1-6-15-released-tp50885.html (by Alexander Schwinn) [21:58] :) [22:00] Nice timing [22:00] Evening all [22:01] Hello! [22:01] indeed [22:02] #startmeeting Xubuntu Community Meeting [22:02] Meeting started Thu Apr 5 22:02:39 2018 UTC. The chair is ochosi. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [22:02] Available commands: action commands idea info link nick [22:02] hullo [22:02] hiiii [22:02] hello [22:03] #chair ochosi knome bluesabre [22:03] Current chairs: bluesabre knome ochosi [22:03] hi everyone :) [22:03] * bluesabre is wired in at a coffee shop [22:03] hi ochosi [22:03] noice [22:03] enjoy that coffee! [22:03] bluesabre, a coffee IV? [22:04] Something like that [22:04] #topic Open action items [22:04] are there any..? [22:04] (there aren't on the agenda, but then again) [22:04] not from meetings [22:04] some coordination regarding social-media-ing of final beta testing..? [22:06] but i presume that has been done [22:06] i noticed at least on the things i use [22:06] it's past that time, yes [22:06] and this has been a fairly awesome cycle wrt new testers anyway [22:06] i'm pretty sure pleia2 worked hard to get it done because this time i didn't do anything :) [22:06] hehe [22:06] well done pleia2 [22:06] :) [22:06] not that i do anything else than twitter anyway... :P [22:06] and thanks to flocculant for reminding me to do the things ;) [22:06] good teamwork then (knome doing nothing, flocculant doing the reminding and pleia2 doing all the work) [22:06] lol [22:06] lol [22:06] well i didn't step on anybody's toes or tell them they did it wrong...! [22:06] anyway, if there are no open action items i'll move along [22:07] ack from me [22:07] carry on [22:07] #topic Updates and Announcements [22:07] btw, i forgot... [22:07] #undo [22:07] Removing item from minutes: TOPIC [22:07] there you go ;) [22:07] who's all here? [22:08] jd109: wanna introduce yourself? [22:08] or any other new faces? [22:08] Hi [22:08] what to say [22:08] (those who haven't typed anything, just make any noise now) [22:08] How is everyone doing [22:08] I am one of the wallpaper submitters [22:08] ah cool [22:08] Fantastic [22:08] submitters or also winners? [22:08] (great in any case!) [22:09] have the winners been announced? [22:09] i think so - knome ? [22:09] no, but we've reached out to them [22:09] right [22:09] that's what i meant [22:09] I have been keeping an eye out [22:09] alas, if you haven't heard from us, you are not one of the finalists [22:09] WHich one(s) did you submit? [22:09] lol [22:09] but the competition this time was fierce, we've never had so many high quality submissions [22:10] it was hard deciding [22:10] Yeah, it was pretty great [22:10] um quite a few [22:10] the arch [22:10] the opera house [22:10] the flowers in the tea house [22:10] Pilatus [22:10] i hit some lag that might mean i need to use this webclient... [22:10] and sesto [22:11] just those 5 [22:11] alrighty [22:12] yeah there were lots of good submissions [22:12] anyway, thanks for showing up and we're glad if you wanna stick around! [22:12] thanks [22:12] did i miss the #subtopic? [22:12] there are lots of ways to contribute - not just wallpapers ;) [22:12] I agree I have been testing the latest iso too [22:12] knome_web: not really, i didn't want to discuss the walls really, just have jd109 introduce himself [22:12] aha, goodie :) [22:13] that's great [22:13] testing helps a lot too [22:13] (there i go!) [22:13] anyway, let's move the meetnig along a bit [22:13] jd109: the perspective on the arch one is really awesome btw :) [22:13] #topic Updates and Announcements [22:13] &n [22:13] not that. [22:13] thanks! [22:13] but hello from here again... [22:13] hello again knome [22:13] #subtopic Wallpaper contest results [22:14] knome: you're on [22:14] great! [22:14] so [22:14] since i'm going to post to our blog soon, no spoiling here, but: [22:14] #info We have 6 winning wallpapers from 6 different contestants! [22:15] \o/ [22:15] #info We're still working with the contestants, but at least 5 of the winning submissions will be included in 4k resolution (woot!) [22:15] * pleia2 has envelopes queued up to send them all stickers [22:15] #info Blog will be updated soon with winners' names and winning submissions :) [22:16] yes, we also have the addresses for all winners so we're good to with our prizes as well! [22:16] do we want to make all contributions available somewhere on the website? [22:16] they are already available on the contests website :) [22:16] oh crap :D [22:16] :D [22:16] and yes, we will link to that page and for now it shouldn't disappear [22:17] * ochosi should better shut up [22:17] disclaimer: the 4k versions aren't available on the contests page [22:17] yeah, that's fine though [22:17] as long as they are included in the release [22:17] we'll have to figure out if we want to make them available somewhere apart from the package and its bzr branch [22:18] mostly a question of bandwidth usage i guess [22:18] and finally [22:18] #info A huge thank you everybody for submitting! We had a total of 162 submissions compared to less than 100 last time. We have an awesome (and I hope a growing) community! [22:19] <3 [22:19] +1000 [22:19] Thanks for running the contest! [22:19] yeah, it was really great [22:19] no problem! [22:20] that's all from me :) [22:20] (thanks to the team for getting your votes in a timely manner too) [22:21] yes [22:21] next time we will make voting easier... [22:21] (even easier than it was now) [22:21] :) [22:21] alrighty, perfect [22:21] any other topics for updates and announcements..? [22:21] Sure [22:22] f-f-f-freezes [22:22] #subtopic Release Schedule [22:22] knome: I kept having to refresh the page for the indicator on each image to refresh after voting yay/nay. [22:22] #info Bionic Final Beta should be landing soon, today/tomorrow [22:22] hooray [22:22] #info Translations are due next week [22:23] #info Final Freeze is the 23rd [22:23] there shouldn't be much changed apart from the slideshow? [22:23] #info Final Freeze is the 26th [22:23] i mean at least that will have time to land? [22:23] knome: yeah, will be doing a batch of translation updates this weekend probably [22:23] And bug fixes [22:23] ahha [22:23] #undo [22:23] Removing item from minutes: INFO [22:23] #info Final Release is the 26th [22:24] :) [22:24] Contributors, come and get it :) [22:24] That's it for dates [22:24] pleia2, maybe a social media run for making people translate the slideshow? [22:24] oh [22:24] one more [22:24] :) [22:25] #info Release Candidate on the 19th [22:25] knome: if we have some very clear instructions as to how to do this, we absolutely should [22:25] bluesabre: so i presume we can still get today's thunar release in? [22:25] pleia2, we should be able to make it relatively brief... [22:26] ochosi: pretty sure, yeah [22:26] bluesabre: plus i pushed two small icon fixes today that should also go in [22:26] (small but not irrelevant) [22:26] ochosi: will take a look and upload sometime in the next 36 hours [22:26] awesome, thanks a bunch [22:27] anything else regarding the release schedule? [22:27] Nope [22:28] k, any other subtopics for "updates and announcements"? [22:28] None from me [22:28] i don't think - yet [22:28] either on the last meeting of the cycle or first after [22:28] :) [22:28] Unit193, pleia2 ? [22:29] ochosi: Hi! [22:29] nothing from me [22:29] :] [22:29] or the hiding krytarik [22:29] :D [22:29] Well, there's the new thunar we should try and "slip" in. [22:29] Oh, numlockx is fixed. [22:29] hooray! [22:29] @lurkers: rise from ye dwellings! [22:30] noice [22:30] alright then [22:31] #topic Discussion [22:31] #subtopic Icon changes after UIF (ochosi) [22:31] so i just briefly wanted to run something by you [22:31] there have been a few changes in our icon theme's upstream (elementary) [22:31] they have started to rework the palette [22:32] and you can see this already in bionic because i pulled in quite a few reworked icons [22:32] now we have e.g. some inconsistent greens [22:33] http://i.imgur.com/ppHvVhK.png [22:33] left is new, right is old [22:33] i could spend some more time updating these icons to the new green [22:33] but we're past UIF [22:33] so the main question is: does this qualify as bugfix? [22:33] meh [22:33] or: would you even care enough for me to do the work and for us to push this? [22:34] I'd say... not really a bugfix. But the purpose of the freezes is to make sure we're not crunched for time with replacing screenshots and the like [22:34] i don't think it's a bugfix, but i don't think the UIFe paperwork or getting the ack is too much work if we want this in [22:34] on another note: will this rework finish before the release? [22:35] well we're already in this semi-consistent state [22:35] or in other words, will we release with all-consistent icons even with the UIFe paperwork and uploading thingy? [22:35] so there's really not much to lose [22:35] hard to say, it's a lot of icons [22:35] and to go even further: do we want to release an SRU? [22:35] even if the work is repetitious and anyone could help, i doubt anybody apart from me will contribute [22:36] That's the nature of these things :) [22:36] as we dont use the icons in screenshots in our docs i consider an SRU absolutely doable [22:36] bluesabre: the nature of icon updates is that i have to work on them alone..? :D [22:36] What sort of work load is involved? Surely it's more than search & replace? [22:37] well i have to open every icon and add a new gradient, replacing the old one [22:37] i doubt the svgs are consistent enough to be able to script this [22:37] i didn't mean the SRU would be not doable even if we had screenshots or that [22:37] most of them are in the actions/ subfolders though [22:37] i would be willing to have a go at scripting if you can explain what needs to be done [22:37] the question is if we think that getting this consistency is important enough for an SRU on itself [22:38] (and i already fixed a lot of icons already) [22:38] ali1234: that'd be awesome! [22:38] because the SRU process is a different beast than an UIFe [22:38] Yeah [22:38] and that said... [22:38] knome: i know, my main target would be UIFe [22:38] if we think we will be doing an SRU, then don't sweat on the UIFe's now [22:38] but if we think we can get it all in by release, then for sure i vote for some more sweat for ochosi - and can do the UIFe paperwork [22:40] I think it'd be a nice to have. [22:40] right [22:40] The difference isn't drastic, but any additional polish we can have is welcome [22:40] definitely - we're kind of in a state where i'd rather go all way than leave the inconsistency there [22:40] If we enter SRU territory, it gets painful [22:40] (so the two current commits are in fact fixes of icons that were broken - we should get those in anyway) [22:40] bluesabre, i vote for more polish only for the polish speaking users! [22:41] ok, so then i propose the following: [22:41] 1) bluesabre uploads the two commits that are bugfix as bugfix [22:41] 2) ochosi tries the scripted approach with ali1234 [22:41] 3) if 2) fails ochosi tries to update the icons manually (as many as possible) [22:41] 4) knome does the paperwork for UIFe [22:41] can I make a suggestion [22:41] sure [22:41] if It is not stepping on toes [22:41] :) [22:41] how many icons are we talking about, approximately? [22:42] how about switch the greens on the new icons [22:42] ochosi, ack from me on that proposal [22:42] back to be consistent with all the others [22:42] it would be much less work [22:42] jd109: not really, the new greens outnumber the old ones by far [22:42] oh okay [22:42] :-( [22:42] ali1234: hmm, maybe 50? [22:43] (and even if not, then we would be "outdated" for two years until the next LTS) [22:43] 50 x 8 different sizes each or 50 total? [22:43] pretty sure × [22:43] 50 total [22:43] oh wow [22:43] really? [22:43] x8 would include the symlinks [22:43] Seems obvious [22:43] Let's go for it :D [22:43] hey - i've done a lot of work already! [22:43] i guess svg doesn't have different sizes [22:43] :) [22:43] yes indeed, let's go for it [22:43] >900 icon updates in this cycle [22:44] with just one ochosi... we need more ochosis to be more productive [22:44] ochosi, now the proposal with #action and we're good to go ;) [22:44] just one more follow-up question [22:44] i can also clear out some other inconsistencies [22:44] like? [22:44] where icons look very different in different sizes [22:45] e.g. MS excel files look totally different in 128px [22:45] if the changes are trivial (eg. don't take a huge amount of time), go for it [22:45] we can bunch this all up as an "consistency" update [22:45] 128px: http://i.imgur.com/a01oBEf.png [22:45] 64px and below: http://i.imgur.com/gPuWqVn.png [22:46] hah, yes [22:46] that's really confusing and misleading [22:46] i just noticed it a short while ago [22:46] indeed [22:46] (i obviously don't work with office files "enough") [22:46] yes, i'm all for fixing this as well while we are at it [22:46] hence your sanity [22:46] lol [22:46] I agree [22:47] One nice UIFe bug to cover it all [22:47] yep [22:47] #action bluesabre will push beaaf3f6f47fb1e80fb7821fe69b3513a707cfbe and 28120d05e011ec89412d33d7dc5897d7f6bcf8ee from elementary-xfce to xubuntu-artwork as bugfix [22:47] ACTION: bluesabre will push beaaf3f6f47fb1e80fb7821fe69b3513a707cfbe and 28120d05e011ec89412d33d7dc5897d7f6bcf8ee from elementary-xfce to xubuntu-artwork as bugfix [22:47] and not even by a stretch, it really is one thing [22:47] * bluesabre is prepared [22:47] #action ochosi and ali1234 will try to script the gradient swap-out for most icons that need updating [22:47] ACTION: ochosi and ali1234 will try to script the gradient swap-out for most icons that need updating [22:48] #action ochosi will manually update whatever icons are left over from the script approach [22:48] ACTION: ochosi will manually update whatever icons are left over from the script approach [22:48] #action knome will file the UIFe paperwork once the branch is ready [22:48] ACTION: knome will file the UIFe paperwork once the branch is ready [22:48] #action bluesabre will again be doing the uploading honours [22:48] ACTION: bluesabre will again be doing the uploading honours [22:49] i'm filing the bug now that it's ready for subbing appropriate teams to it [22:49] what's the latest point in time for getting the UIFe approved? [22:49] Lots of xubuntu-artwork uploads in the next few days :) [22:49] ochosi, as long as it happens before the release... [22:49] yeah, but how many days before [22:49] i can't remember what was a realistic window [22:49] i think we don't want to go into the final freeze territory [22:50] ochosi: RC is the 19th, archive probably locked at that point [22:50] ok [22:50] so i have roughly 10 days [22:50] sounds do-able [22:50] thanks, we can move on to other discussion items (if there are any) [22:50] * bluesabre believes in ochosi [22:50] yes, i have one [22:50] k go ahead [22:51] I need to relocate, bbiab [22:51] #topic Discussion [22:51] #subtopic 18.04 Community Wallpaper Contest Winners [22:51] https://xubuntu.org/news/18-04-community-wallpaper-contest-winners/ [22:51] done :) [22:52] noice [22:52] well done [22:52] Nice! [22:52] any other discussion items? [22:52] not from me [22:52] (we're slowly but surely running out of meeting time) [22:55] ok, if not... [22:55] #topic Schedule next meeting [22:56] #action Unit193 to schedule the next meeting [22:56] ACTION: Unit193 to schedule the next meeting [22:56] iiiiit's Uniiiiiiiit193! [22:56] thanks for chairing, ochosi [22:56] weeeee [22:56] back [22:56] thanks everyone for participating [22:56] hah, right in time for the wrap-up, bluesabre [22:56] thank you ochosi [22:56] thanks! [22:56] #endmeeting [22:56] Meeting ended Thu Apr 5 22:56:59 2018 UTC. [22:56] Minutes: http://ubottu.com/meetingology/logs/xubuntu-devel/2018/xubuntu-devel.2018-04-05-22.02.moin.txt [22:57] Thanks everybody! [22:57] Dang, I'm awful at those. [22:57] Thanks Unit193! [22:57] :D [22:57] knome: shall I social media the wallpaper post? [22:57] What'd I do? [22:57] pleia2, yes please [22:57] bug 1761623 [22:57] bug 1761623 in xubuntu-artwork (Ubuntu) "[UIFe] Fix inconsistencies in the elementary-xfce icon theme" [Undecided,New] https://launchpad.net/bugs/1761623 [22:58] so that's there, ready for the process to roll [22:58] Very nice [22:58] Guess I have some work to do when I get home :) [22:58] :) [22:59] Testbuilt thunar. [22:59] :) [22:59] kewl [23:00] ali1234: for the scripting, shall i start to describe the manual process..? [23:01] okay so what am i looking at? i cloned elementary-xfce repo [23:01] ok, navigate to elementary-xfce/actions/24 [23:01] back.svg, bottom.svg look like the old green? [23:02] open edit-redo.svg, take the gradient from there and apply to go-bottom, go-down, ... [23:02] take the green from the path (the outline of the arrow from edit-redo.svg) and apply that too [23:02] knome: how do we get the wallpaper winners blog post to the front of xubuntu.org ? [23:02] oh [23:03] okay. so this is just purely a colour change right? [23:03] pleia2, there we go [23:03] ty [23:03] np [23:03] the answer: make sure the post is in the "Articles" category [23:04] ali1234: yes [23:04] good to know :) [23:04] ochosi: can you show me a git commit where you've done this? [23:04] ali1234: that's why it could be scriptable [23:04] sure, one sec [23:05] pleia2, updated the excerpt to a hand-tailored one [23:06] * pleia2 thumbs up [23:06] ali1234: unfortunately the one i did manually and that would be a good example is part of a bigger commit: https://github.com/shimmerproject/elementary-xfce/commit/b85a1d068836f07accd7c4b1605720581ba0b041#diff-a3092494930a2366b914d2f431145af7 [23:07] look for 16/dialog-ok-apply.svg [23:08] okay, i'm a bit puzzled by this [23:09] what happened to xlink:href="#linearGradient2264" [23:09] is that still in the file? [23:10] i don't think that has any meaning [23:10] see how the nodes refer to the id(2427) later [23:10] ali1234: i think not, there are oftentimes lots of unused gradients in svgs [23:10] would need to run the vacuum script more often... [23:10] ochosi, this isn't even an unused gradient [23:10] (or simply as a pre-commit hook or something) [23:11] i think this is an inkscape-internal (?) link/id [23:11] which isn't referred to from anywhere [23:13] okay so the old gradient has only two stops, the new one has four, is that right? [23:14] actually the xlink:href is referred from the other linearGradient element... [23:15] and there that 2264 is too when you expand the code [23:15] * knome facepalms [23:15] handling different amount of steps can be a bit tricky :) [23:16] the stroke is different colour too? [23:16] that's likely [23:17] indeed [23:17] so the transition that is probably hard is the steps [23:17] and then the path/stroke also needs to be changed [23:17] ochosi, do you know if the steps/offset is always the same though? [23:18] between icons of the new gradient you mean? [23:18] tbh for the icons i'm interested in the steps would always be the same [23:19] yes [23:19] if it helps with the script, i can manually fix one single arrow icon [23:19] then you have something to go on [23:19] do you know the exact colours before and after? [23:19] or is it a case of "move the sliders until it looks right" [23:20] no, this should be consistent across icons [23:20] so we should be able to derive the colors before and after from a single example [23:21] some of these svgs have like 15 copies of the original gradient [23:21] yeah [23:21] i know [23:21] could we create a simple script that runs inkscape without the GUI and vacuums? [23:22] that's why i said, vacuuming [23:22] yeah [23:22] and repeat that on alllllll the icons [23:22] those scripts already exist [23:22] that would likely help [23:22] i'm sure [23:22] and it's a oneliner most likely so not an issue [23:22] just figure out the inkscape parameter [23:22] found on google: for f in *.svg; do inkscape --file="$f" --verb="FileVacuum" --verb="FileSave" --verb="FileQuit"; done [23:23] oh lewl? [23:23] output from "inkscape --help" is funny [23:23] google master [23:23] oh there is a --vacuum-defs parameter [23:24] ali1234, that sounds like a lot better than that verb crap [23:24] https://temp.knome.fi/other/inkscape-cli-help.png [23:24] i'd say it would be more useful if it was the *other* column with more width [23:25] can't always win [23:25] (or be helpful) [23:25] mine looks different [23:25] anyway... [23:25] interesting.. [23:25] https://github.com/elementary/icons/blob/master/pre-commit [23:25] that's most likely what we want [23:25] looks fantastic :) [23:26] don't need -z and --export-plain according to the manual page [23:26] automatic stuff ftw [23:26] it's assumed no gui and in place if you just say --vacuum-defs $file [23:26] right, but --export-plain removes all the sodipodi and inkscape namespaced nodes [23:26] ah okay [23:27] plain SVG vs. inkscape SVG [23:27] yeah that would probably be a good idea [23:27] i think i never vacuumed the theme because it gets converted to png anyway... [23:27] former is smaller in size as well as easier to read [23:28] gonna be one huge commit if you vacuum the whole thing :) [23:28] sure :) [23:29] i know [23:29] feel free to propose a pullrequest for that one [23:29] i gotta get some sleep now [23:30] nighty ochosi :) [23:30] nighty ochosi [23:32] export-plain really messes around with the files [23:32] yes [23:32] i think it would probably be ideal to have a quick visual look at the files after doing that... [23:32] running it now. i have a feeling it will take quite some time [23:33] actually if you believe the inkscape wiki, no visual changes are made [23:33] but somehow this is so fishy;) [23:33] :D [23:33] lossless-ish [23:34] it is re-ordering the attributes on nodes, causing diff inflation [23:34] like "i'll change 75% of your file, but don't worry, it's the exact same thing!" [23:34] but not much in the way of real changes [23:40] nighty! [23:43] 3859 files changed, 439255 insertions(+), 986530 deletions(-) [23:44] Welp. [23:46] :| [23:47] trying just vacuum now [23:51] i'm off to bed as well [23:51] nighty and thanks for looking at this (too) ali1234 :) [23:52] nighty cnoma [23:52] :) [23:53] night [23:53] ... and just using vacuum defs ends up adding more cruft than it removes [23:54] the diff is still significantly smaller though [23:58] 3829 files changed, 49015 insertions(+), 466754 deletions(-) [23:59] Both are effectively rewrites. If we're considering using that upstream git hook, might as well go for the full vacuum