=== notem is now known as emerson [07:05] mornign [07:30] jibel, morning [07:30] Back in a while... [07:32] hey duflu [07:39] good morning! [07:41] good morning desktoppers [07:41] morning oSoMoN, andyrock [07:42] hey jamesh, andyrock [07:44] good morning desktopers [07:44] hey seb128 [07:45] lut oSoMoN, had a good w.e? [07:46] hey jamesh andyrock [07:53] hey seb128 how are you? [07:54] andyrock, good! you? === carlolo is now known as clobrano_ [07:55] * andyrock didn't not spleep much because it was too warm [07:55] 😅 [07:55] :-/ [08:00] hey seb128, yeah had a good one, went to the beach. you? [08:02] morning [08:02] oSoMoN, good as well, my gf sister and her husband were visiting for the w.e so we walked around with them and had dinner at the restaurant on saturday evening [08:03] hey Laney, happy monday! how are you? [08:03] good morning Laney [08:06] hey seb128 hey oSoMoN [08:06] I'm good! [08:06] we went to the seaside for the weekend, was nice [08:06] although I wasn't brave enough to go in :( [08:11] hey Laney! [08:12] so water was not good as in The Hague? :D [08:14] hey andyrock, you good? [08:14] hmm [08:14] that was suspiciously warm [08:14] lol [08:14] good good [08:14] come on Laney, you know it can get warm in summer here [08:14] remember the systemd hackdays [08:15] :-) [08:15] it can [08:15] Laney, come to La Hague in France it's always warmer [08:15] that sprint was in october though! [08:15] Laney, https://en.wikipedia.org/wiki/La_Hague_site [08:15] ooh yeah, bet that's like a hot tub [08:32] duflu: I see that you're working on enabling video acceleration? the wiki says intel is different than radeon, but it's not.. just install mesa-va-drivers [08:32] andyrock, did you mean to archive the snap-glib card on trust card? is that not something we want to do anymore? [08:32] hey robert_ancell already had such a card [08:33] and he already made huge progresses [08:34] https://trello.com/c/q1Zb63U7/157-bug1698984-sru-snapd-glib-to-trusty [08:34] I'll try to build a ppa out of it [08:38] tjaalton, I have not tested radeon. I'm focusing on what actually works (where "works" means over an order of magnitude improvement from software). Radeon testing isn't really a priority though, given most of the world only cares about Intel graphics on laptops... [08:40] And I've been burned several times by "accelerated" video playback that actually uses higher CPU than software [08:41] well, we enable several configs with radeon gfx.. [08:44] qsv needs opencl, does beignet work? [08:45] tjaalton: Also be careful to not use the term QSV per the wiki ;) I don't know what beignet is [08:45] opencl for intel [08:45] I assume it works, but have no interest in it [08:46] andyrock, oh ok, for next time it's a good idea to add a comment saying when you archive the card so it's more obvious to others [08:46] duflu: ok, well the wiki is misleading then [08:46] kk [08:47] duflu, great work on summarizing the current situation and next steps on that wiki page, it makes it easy to understand such a complex thing [08:47] tjaalton: No, using the term QSV is misleading. QSV is a hardware feature that is accessible via at least two different APIs. So saying QSV only refers to the silicon. And worse, it historically only refers to encoding, not decoding [08:48] duflu: ah right [08:49] anyway, from what I've heard (not proven on my radeon though iirc) is that mesa-va-drivers makes va-api work with radeons, and that it's generally fine. something to keep in mind once adding things to the default install [08:51] tjaalton: Yeah I have high hopes for mesa-va-drivers doing radeon and nvidia well. But Intel's way more important on average [08:52] the browser situation is rather sad, though [08:52] It's solveable. Just messy [08:52] I don't want to give anyone the impression that part is solveable in one cycle though [08:53] Also I need to work on other things or else go insane [08:53] hehe [08:54] oSoMoN, Thanks, I did not intend for this to be a documentation exercise. It just turned out that way as I realized nobody's really looked at the big picutre yet [08:54] or the big picture [08:55] hum [08:55] DEFINES+=TRANSLATIONS_DIR=\\\\\\\"/usr/share/qt5/translations\\\\\\\" [08:55] why that number of "\"? [08:56] that's from https://launchpadlibrarian.net/325137761/transmission_translation-fix.debdiff [09:13] seb128, have you had a chance to test my LO 5.3.3 snap? [09:13] oSoMoN, sorry no, it's on my list for today though [09:13] cool [09:14] seb128: that's funny [09:14] it'll need to be -DTRANSLATIONS_DIR=\"...\" in the compiler call [09:17] some parts of the build system must interpret the string [09:17] k, I've no clue if it's right but the upstream commit looks similar [09:17] so I assume it is [09:18] I would expect the build log to show the gcc/g++ calls and if they look like -DFOO=\"bar\" then it's right [09:19] Laney, I guess it makes sense to add least check the result, thanks [09:19] there's a funny one in livecd-rootfs [09:20] If I was to reinstall artful with the "final" gdm and lightdm removed, is that in the current iso, or not yet? [09:20] https://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/view/head:/live-build/auto/config#L66 [09:20] actually that's the same! [09:20] duflu: not yet [09:21] OK. Can't tell if I've created session bugs or if a fresh install would also have them [09:21] The problem is I can't switch between Gnome on Wayland/Xorg without rebooting [09:21] The second login fails. Have to reboot [09:23] Laney, fun :-) [11:07] IRC is quiet today! [11:07] suspicious [11:07] is everybody busy or just still hangover from the w.e? ;-) [11:09] mpt, hey, why did you reopen https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1685934 ? [11:09] Ubuntu bug 1685934 in indicator-datetime (Ubuntu) "ok button duplication" [Low,New] [11:09] oh, because there was a reply I guess [11:10] yep [11:10] it's on the wrong component according to the comment though [11:55] hey seb128, I need a REST api to get info about CVEs (like priority, description, etc.) to show in update-manager [11:56] atm there is no such thing (at least under ubuntu.com/canonical.com) domains [11:56] but I could easily deplot our own service using https://github.com/cve-search/cve-search [11:57] *deploy [11:58] so we could integrate this in http://people.canonical.com/~ubuntu-security/ [11:59] otherwise there are already public services e.g. https://cve.circl.lu/ [12:00] but not sure if we can rely on them in the long term [12:24] andyrock, sorry, just saw on irclog that you talked to me after I closed IRC, was moving between places [12:24] np [12:25] andyrock, you should probably talk to the security team about that [12:25] #ubuntu-security? [12:25] yes [12:26] i need to be invited, do you know anyone that I can talk with here? [12:28] andyrock, I don't know, I can join but it might be restricted the registered users or ubuntu group or something [12:28] yeah I guess it's restricted for a reason :) [12:30] andyrock: #ubuntu-hardened is the public room [12:30] good morning [12:31] jbicha, joining #ubuntu-security forwarded me to -hardened automatically [12:31] so if that's not doing it there is a reason? [12:33] seb128: ask in -hardened ? ;) [12:33] I'm not interested enough to chase that for others :p [12:40] for some strange reason, when you're already in #ubuntu-hardened and try to join #ubuntu-security, you get a message that you need to be invited [12:40] it's a side effect of how the redirect works [12:41] ha :p [12:42] indeed andyrock, you are already there [12:42] mdeslaur, thanks, oh and happy monday! [12:43] seb128: heh, happy monday to you too :) [12:48] oSoMoN: we're having trouble compiling LO on artful i386 https://launchpad.net/ubuntu/+source/libreoffice/1:5.3.3-0ubuntu2/+build/12778305 [12:54] looking [13:01] I think that's the final piece for the hunspell transition now [13:18] chrisccoulson, hey, are you looking at the chromium update in https://launchpad.net/~canonical-chromium-builds/+archive/ubuntu/stage/+packages ? [13:27] jbicha, that failure looks like it could possibly be related to bug #1699529, i.e. flaky tests (especially https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1699529/comments/3) [13:27] Ubuntu bug 1699529 in libreoffice (Ubuntu) "i386 autopkgtests are unstable" [High,Confirmed] [13:28] can you retry the build? [13:28] I need to investigate those failures further, but until I manage to reproduce locally I can only do guesswork [13:39] oSoMoN, I am, but I need to do something else first [13:39] chrisccoulson, getting ride of ubufox right? ;-) [13:42] oSoMoN: yes, I'll go ahead and retry again (I did retry a few times already) [14:20] jibel, what was that power tool called that we discovered the other day? [14:35] are we affected by the Debian hyper-threading bug [14:42] immu: yes, LP: #1700373 (but my understanding is that it's unlikely that you'd ever experience the bug, ocaml isn't usually installed) [14:42] Launchpad bug 1700373 in intel-microcode (Ubuntu Zesty) "Please update microcode to version 20170511 on all supported platforms" [Undecided,Confirmed] https://launchpad.net/bugs/1700373 [14:45] willcooke, gnome-power-bench [14:47] thx jibel [14:47] flexiondotorg, ^ [14:48] flexiondotorg, willcooke gnome-battery-bench sorry [14:48] https://git.gnome.org/browse/gnome-battery-bench/ [14:53] mpt: hey, can you give a look to this plase https://code.launchpad.net/~3v1n0/unity-control-center/unity-lowgfx-support/+merge/321827 ? [15:02] willcooke jibel Thanks. [15:04] Trevinho, done, I need a Before screenshot to compare :-) [15:04] mpt: ok [15:06] mpt: https://usercontent.irccloud-cdn.com/file/kl5jlXtA/lp-gui2.png [15:06] so I'm handling the case livepatch knows there is a security issue and a fix available [15:06] mpt: http://imgur.com/KGnYl4z [15:06] but the fix cannot be installed using livepatch [15:08] and then there are the cases where the fix can be patched using LivePatch but it failed for some reasons [15:55] robert_ancell: if you've got a sec, want to review https://paste.debian.net/973397/ ? [15:55] also hi ;-) [15:55] hope london is treating you well [15:57] andyrock: +1 looks good :) [15:58] Laney, looks good [15:58] thx [15:58] Laney, there probably should be a convert_error() function so it's done consistenly [15:59] I noticed that G-S started complaining at some point about non-GS errors being returned by the snap plugin [15:59] do you do the same thing in other places? [15:59] I saw some local_errors [15:59] brb [16:00] haha [16:00] talking to people at sprints sucks [16:27] Hi jbicha! Did you see https://code.launchpad.net/~gunnarhj/ubuntu-seeds/ubuntu.artful_lang-support/+merge/326261 ? [16:29] oSoMoN, do you have a list of known issues with the libreoffice snap? I installed it and I'm playing a bit with it but I'm unsure what to test or conclude from the testing [16:34] Hi seb128! Any thoughts about bug #1696418? [16:34] bug 1696418 in language-pack-gnome-es-base (Ubuntu) "gnome-help/shell-introduction.page link to removed files" [Undecided,Confirmed] https://launchpad.net/bugs/1696418 [16:35] GunnarHj, hey, no [16:36] or "trusty is old" [16:36] :-) [16:37] seb128: In short I'd like to propose a rebuild without translation stripping to fix it. [16:37] I've it in my inbox for a while but I can't be bother trying to debug trusty issues [16:37] that's not a fix [16:37] that's a workaround [16:37] I would prefer for somebody to try to understand the issue [16:38] seb128: But will that ever happen, considering that trusty is old? ;) [16:38] seb128: hey... :) [16:38] Trevinho, good morning! [16:38] GunnarHj: yes I saw but I didn't look through it yet, it looks complex :) [16:38] seb128: I've splitted the branches [16:38] seb128: ahah, well... I'm not such a night owl yet :D [16:39] :-) [16:39] Trevinho, nice [16:39] GunnarHj, well, you seem to have interest in trusty since you are asking about it and wanting to work on a workaround...:p [16:42] jbicha: Many small changes, but not really complex. The overall goal is to achieve consistency as regards pulling of lang support. I could be standby to clarify the details, if that may help. === ratliff_ is now known as ratliff [16:45] seb128: As regards interest... I saw the bug report. But as jbicha pointed out at the report, there will be no more point releases for trusty, so we don't need to worry about ISO size, do we? [17:04] GunnarHj, I don't know, trusty got extended support, unsure if somebody plans to roll iso updates [17:17] seb128: I see. Ok, the alternative is to figure out what happened and why and make a full langpack update (without a requirement to verify). I tend to think it's a "won't fix" bug. [17:20] I think so too [17:21] but the few mbs are probably no issue for the iso in any case if there is a need for a respin [17:21] so feel free to do upload an unstripped documentation [17:21] seb128: Ok, great. Why didn't you say so immediately? ;) [17:22] GunnarHj, because I don't like much the idea to workaround an issue we didn't understand [17:22] that might bite you back [17:22] at the same time I'm not waiting to debug trusty issues [17:22] seb128: Fair enough. [17:56] seb128, those are all the reported LO snap issues: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bugs?field.tag=snap , and all those that are marked "in progress" should be fixed by my updated snap [17:57] (sorry for the delayed answer, was out running errands) [18:38] jbicha, I see that the i386 build of LO 5.3.3-0ubuntu2 in -proposed failed again, the failure looks pretty consistent [18:38] I've just uploaded a 5.3.4 test build in https://launchpad.net/~osomon/+archive/ubuntu/lo-test/+packages , let's see if that one fares better [18:44] oSoMoN: or you could get crazy and upload 5.4 RC1? [18:44] that too :) [18:44] do you intend to SRU a newer 5.3 to zesty? or just snap it? [18:44] it's on my list for this week (5.4 RC1) [18:45] I don't think Sweetshark really did SRUs except for the final LO point release for the LTS [18:45] we'll try to go the snap route as much as possible to avoid SRUs where possible [18:46] is there a reason we distrust later LO point releases? [18:46] or is just not enough time to do everything? ;) [18:48] the latter I think [18:48] ok [18:48] and I'm still working my way through LO packaging, I’ll get faster at it eventually, but I'm still ramping up [18:50] no problem, LO's not your only job either === bregma__ is now known as bregma === JanC_ is now known as JanC