[06:14] good morning [06:46] Morning didrocks and oSoMoN [06:46] hey duflu [07:00] hey duflu [07:00] salut didrocks [07:00] and good morning desktoppers === pstolowski|afk is now known as pstolowski [07:14] hey oSoMoN [07:18] Hi seb128 [07:18] hey duflu & desktopers [07:18] salut seb128 [07:18] lut oSoMoN, didrocks [07:18] did everyone had a good w.e? [07:19] salut seb128, ça allait et toi ? [07:20] bon w.e en France, tranquille :) [07:22] hi all [07:24] oSoMoN: I found some small minor typo in the README.Debian in firefox, I open a bug for this? Or can I just paste it here? :) [07:25] salut jibel [07:27] dupondje, pasting here is fine, thanks [07:27] salut jibel [07:27] oSoMoN: $ sudo aparmor_parser -R /etc/apparmor.d/usr.bin.@MOZ_PKG_NAME@ [07:27] its apparmor_parser :) [07:27] took me at least 30 seconds before I realised why it didn't work lol :D [07:28] dupondje, I'll fix this right away, thanks [07:28] seb128, more or less… house got burgled while we were out for dinner on Saturday, not fun. Rest of the week-end was good though, spent quality time with my daughters yesterday, much needed to get over the hassle. [07:28] oSoMoN, urg, sorry man :( [07:28] that sucks [07:29] did they steal much? [07:29] argh :/ [07:29] not much, luckily they didn't touch my laptop [07:30] it's more the hassle of paperwork with the police and insurance company, and getting the windows fixed now [07:31] and my eldest's trauma, cause they entered the house through her bedroom [07:31] :((((( [07:31] that's the more annoying part, indeed… [07:36] dupondje, https://bazaar.launchpad.net/~mozillateam/firefox/firefox.eoan/revision/1320 [07:36] I'll now backport to the branches for other stable releases [07:37] :) Great, its very minor, but at least its fixed for next releases :) [07:43] yeah, details matter. thanks for reporting it! [08:02] hey [08:03] hi all [08:03] hey willcooke, Laney [08:03] did you have a good w.e? [08:03] pretty good thanks [08:03] how about you seb128? [08:03] w.e in France, good and relaxing [08:04] a bit rainy, but nothing compared to .nl today :( [08:04] Morning Laney and willcooke [08:05] good morning Laney, willcooke [08:06] I did a news review on Friday from the 19.10 articles: All good. [08:06] I'll look again today [08:09] hey Laney, willcooke [08:10] willcooke, did you find real reviews like ones? all the ones I saw/read were mostly factual/summary of the release notes [08:11] e.g not much opinion from the reviewers/users [08:12] seb128, I found a few. Jack Wallen (Tech Radar, or something like that) did a proper review. But yeah, a lot of them rehased the release notes - and used the screenshots pack that I made, so they all had the same screenshots too. [08:12] Lazy journalists :) [08:13] :) [08:14] hey seb128 duflu oSoMoN didrocks [08:14] weekend was nice, yeah [08:14] * Laney hugs oSoMoN :( [08:26] I feel there should have been some final editing and polish on the release notes, but mostly they're very useful even to us [08:44] duflu: about the "HDR" bug.. so am I right that deep colour is first needed before media can show HDR content? [08:44] tjaalton, kind of :) [08:44] tjaalton, most people would want deep colour first, but it's not really a requirement [08:45] it's a confusing topic, the intel guy asked me directly by email so I created the bug without knowing much about the topic nor having any (display) hw to support it [08:45] actually I have the telly [08:46] but aiui it needs hdmi 2.0 / dp 1.4 [08:46] tjaalton, maybe less confusing to just say yes it is a requirement. Because the latest HDR standards probably ask for 10-bit as a requirement (checking now) [08:47] maybe I should drop the version from the topic [08:48] I think my deep colour monitors are going to die of old age before I see deep colour on them :( [08:48] hehe [08:49] Because they're already old [08:49] how old? [08:49] Good question [08:49] my monitor is at 8y now [08:49] and was planning on getting a new one at some point, maybe during the next 6mo [08:50] Several years, but probably not 8 [08:51] but seems impossible or very expensive to get a model which works for both photo management and games (which I don't play much, but would like to have the potential) [08:51] Yeah, pick one [08:52] but not both [08:53] yep, cope with the tearing [08:53] at least it'd look good [08:54] morning desktoppers [08:54] oSoMoN: ah so sorry! :( [08:55] Morning marcustomlinson [08:57] hey duflu! === pstolowski is now known as pstolowski|afk [11:47] kenvandine, hi :), https://gitlab.gnome.org/Community/Ubuntu/gnome-sdk/merge_requests/7 [11:51] ricotz, kenvandine, can snapcraft?yaml use variables? it seems suboptimal to have the version coded like that in env tricks, would be easy to overlook changing it [11:52] seb128, I just followed existing things ;) [11:52] ricotz, right, it was more a question for Ken (or marcustomlinson) [11:53] seb128, you can use snapcraftctl set-version from inside the build steps of a part [11:53] (reading a git tag or Version.h or whatever from a script to hand it to that command) [11:53] ogra, that doesn't really adapted to that case though [11:54] ok [11:54] seb128: sure could probably use a single environment variable to store the version once [13:41] ricotz, FYI, I created focal branches for firefox, firefox-beta, and thunderbird [13:42] good morning desktopers! [13:42] hellsworth: morning [13:42] good morning hellsworth [13:42] hey hellsworth [13:42] hellsworth: could you review this: https://gitlab.gnome.org/Community/Ubuntu/gnome-sdk/merge_requests/7 [13:43] sure looking at it [13:43] I suspect you'll need to give the whole thing a rebuild and see if it works [13:44] shoot. these changes are already merged in my branch but not in the community oneyet [13:44] i was waiting to merge until i had all the things [13:45] and i'm stuck on librsvg so marcustomlinson i was going to ask you for your advice there.. [13:45] hellsworth: seb128 brought up a good point too that perhaps we should think of a cleaner way to update versions like that instead of writing '0.46' on 3 different lines. Perhaps a single environment variable per version? Not sure [13:45] hellsworth: no rush on that, take the time you need [13:45] yeah a single env var is better for sure [13:46] hellsworth: no rush on the MR, no rush on the version number cleanup. You just got in, take it easy :) [13:47] it's ok to rush a little tho :) [13:48] oSoMoN, hi. ack === charles_ is now known as charles [13:49] marcustomlinson, when you have time could you take a look at the librsvg failure? it's still the same as i emailed. it's a rust thing and i think that https://gitlab.gnome.org/GNOME/librsvg/commit/78219898d17440a41d21a206afa5a5d982dcbf9f is the reason for it. i just don't know how to compensate for this architecture change. there is no librsvg.pc file === ecloud_wfh is now known as ecloud [15:54] kenvandine: hey, did you see my recent comments on that drawing snap post? https://forum.snapcraft.io/t/drawing-snap-not-working/13669/12?u=marcustomlinson [15:54] super weird [15:55] i read through it and it is weird [16:02] going off irc for a bit while i setup weechat because hexchat isn't doing it for me [16:05] marcustomlinson: i did [16:05] but the theme changes still only seem to affect snaps using gnome-3-32-1804 [16:06] right [16:06] I'll carry on with it [16:06] thx [16:49] marcustomlinson: my hunch is something to do with librsvg [16:54] night all [16:58] kenvandine: marcustomlinson did i miss something about librsvg while changing irc clients? [16:58] btw librsvg is the last bit to be updated in the build snap [16:59] so i went ahead and merged the rest of the changes so ew can get it in the snap store [16:59] cool [16:59] hellsworth: well, there something about a recent change in gtk-common-themes (adwaita and yaru) that is triggering a crash of snaps using gnome-3-32-1804 [16:59] but we can't reproduce it with gnome-3-28-1804 [17:00] oh right the drawing snap issue [17:00] yeah [17:00] marcustomlinson's test snaps are reproducing the same issue [17:00] right [17:04] kenvandine, hellsworth: maybe once we've figured out the librsvg issue in gnome-3-34-1804 we can see if the problem goes away by using the new 3.34 platform [17:05] if so, we can backport it [17:05] that sounds good [17:05] hellsworth: I'll look at that librsvg thingy tomorrow [17:06] i think that https://gitlab.gnome.org/GNOME/librsvg/commit/78219898d17440a41d21a206afa5a5d982dcbf9f is the reason for the 3.34 librsvg build snap failures [17:06] is there a way i can use maybe source-commit or something in yaml instead of a git branch/tag? [17:06] if so, i could verify my hunch [17:07] well let me go ask in #snapcraft.. [18:36] hellsworth: you could go back to the librsvg-2.44 source branch [18:36] that would be before that change [18:58] yep. i'm doing a bisect between the two branches to find the commit that breaks the build [18:59] kenvandine: what is in the community/ubuntu/gnome-3-34-1804-sdk is all changes except librsvg (so it's still at librsvg-2.44) [19:00] I thought finding the librsvg commit that breaks the build snap build would help discover the fix, so that we could potentially go to the newer librsvg-2.46 branch [19:02] I'm not sure the context, but one potential problem is new versions of librsvg are in rust, and rust targets fewer platforms than ubuntu; it's also possible that librsvg is using new language featuers faster than we can package up the rust toolchain that provides the features [19:04] sarnold: the context is that this newer branch of librsvg won't build and fails with a rust failure. the reason could be any of those you mention. [19:05] may be that we just hang out on the older librsvg-2.44 branch for a while [19:07] wow that's a lot of changes :( [19:10] 241 [19:11] i can tell you that at least the first 120 changes don't break it :) [19:22] oh my i was wrong about the number of commits [19:23] its 1546 :( [19:30] I would walk through them like 100 at a time :) [19:30] when it breaks, then start narrowing the gap [19:30] hellsworth: ^^ [19:31] yep thanks kenvandine, that's essentially what' i'm doing [19:31] good :) [19:31] and i have several systems at home doing this to try and speed it up [19:34] lunchtime [19:34] :) [19:34] enjoy [19:34] you should not forget lunch too :) [19:36] soon :) [19:36] like 3 more usn refreshes to test :) [19:37] there was quite a list today === sergiusens_ is now known as sergiusens [20:31] Is the ubuntu-canary image still meant to be a thing in focal? If not, we should tear it out of cdimage. If so, you need a package (well, a Packages.gz in an empty archive, at least) in your PPA to stop the build from exploding.