[06:28] good morning [06:51] good morning desktoppers === pstolowski|afk is now known as pstolowski [07:17] salut oSoMoN [07:18] salut didrocks, le garçon d’anniversaire :) [07:18] tu ne poses pas la journée pour fêter ça? [07:21] oSoMoN: héhé ;) Non, je suis pas un spécial fêtard des annivs [07:21] donc, c'est + business as usual :p [07:31] Oh? Happy birthday didrocks (?) [07:31] Morning oSoMoN [07:31] hey duflu [07:36] hey duflu, thanks! :) [07:43] good morning desktopers [07:43] salut seb128 [07:43] hey seb128 [07:43] lut oSoMoN & didrocks, en forme ? [07:43] ça va, et toi, bien rentré ? [07:43] nuit agitée, mais on a connu pire [07:43] morning [07:44] mornin' willcooke [07:46] oui, j'suis arrivé vers 16h comme prévu :) [07:47] Morning seb128, willcooke [07:51] hey duflu, how are you? [07:52] seb128, going well-ish. I'm trying to understand a large profile graph that is over 50% unreadable due to Javascript. Ask again in a week :) You, seb128? [07:53] haha [07:53] I'm good :) [07:53] it's nice and sunny this morning [07:54] I only learned today that it's often possible to see Venus during the day. If only it was clear enough to try [08:01] hey team [08:02] good morning Laney [08:04] duflu, question re: libva via: https://linustechtips.com/main/topic/917059-need-help-with-steam-home-streaming-in-ubuntu-1804/ [08:05] libva and libva2 are both available on 18.04 aren't they? [08:06] duflu, re: Venus - we're lucky to see the sun :) [08:07] hey Laney [08:10] willcooke, It seems our 'libva' source package only offers the 'libva2' binary package. So if anyone is depending on version 1 then it won't work. I don't think that's the main issue though... libva is VA-API, for which NVIDIA support is so unreliable it's best to call it non-existent. If anyone ever had that working on NVIDIA then good luck to them but I would not expect it to work [08:10] We're really at the stage of only confidently saying it works for Intel GPUs [08:10] Because nvidia is all about vdpau? [08:11] Yeah Nvidia is mostly VDPAU. You can translate between the two, which often works, but seldom performs well [08:11] The best authority on that question would be (1) Valve or (2) existing Steam users who have used that stuff [08:13] willcooke, the existing answer is right though - we don't publish the libva1 ABI in 18.04 and later [08:13] Valve probably did that work on 16.04 [08:13] And being proprietary they wouldn't be rebuilding their binaries very often [08:14] So that's two problems: (1) Doesn't work in 18.04 and later; and (2) Not expected to work on Nvidia in any version, but might [08:16] Morning Laney [08:17] good morning Laney [08:28] call for testing the chromium snap (and replacing the debs altogether): https://community.ubuntu.com/t/please-test-chromium-snap-as-a-replacement-for-the-deb/7978 [08:28] please give it a go and report issues! [08:38] duflu, ack, thanks [08:39] oh noes, my gmail got upgraded [08:41] you can toggle back to the "classic UI" I think? [08:41] at least I managed to do that when I tried the new one recently [08:47] hey seb128 didrocks duflu oSoMoN [08:47] sry, got distracted by review comments [08:47] what's up? [08:50] seb128, only for the next week, then its MANDATORTY [08:50] *MANDATORY [08:54] is it bad? [08:54] * Laney is a non user of gmail :< [09:43] Laney, it's slightly different. And we all know how that goes ;) [09:43] Just the usual cheese relocation [09:51] Does anyone have an interest in SDL2 libs? [09:52] RAOF, hey, I guess you saw the colord update still failed to build? also do we need a ffe to get the update in Ubuntu, and if so do you plan to file it? ;) [09:53] seb128 : yes, and yes [09:54] tjaalton, hey, xbitmaps is still due a minor update if you wanted to do that :) [09:54] RAOF, great, thx! [09:54] I don't know why my patch to not check for spotread didn't take, but that's the problem. [09:55] * RAOF apparently needs to check building from a fresh clone, not just a clean checkout. [09:56] or build from the source package? ;) [10:01] seb128: nah, just janitorial changes, nothing in the bitmaps themselves.. [10:01] tjaalton, k, I'm going to mark it to skip on our report then, thanks [10:01] yeah [10:26] RAOF, https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1792356 opened as place holder / so it's linked on our report, the content still needs to be written (and the build to be fixed) [10:26] Ubuntu bug 1792356 in colord (Ubuntu) "[ffe] Update to 1.4.3" [Wishlist,New] [10:28] RAOF, oh, also the build issue might my fault :/ [10:28] RAOF, seems you did that change inline, https://salsa.debian.org/debian/colord/commit/81cebfd1 [10:29] RAOF, I ended up sponsoring by copying the debian dir over a tarball unpack because I had issues with gbp [10:29] so I discarded that inline change [10:30] RAOF, I'm happy to do another upload with that converted to a proper debian/patches changes if you want :) [13:01] kenvandine, I poked at the gnome-contacts snap further to try and figure out this camera issue, but no luck so far, and I don't want to use too much time on this [13:04] oSoMoN, yeah [13:04] thanks [13:43] oSoMoN: ah, I didn't spot that build-packages: [sassc] won't work for gtk-common-themes, because we don't use build it on bionic [13:43] kenvandine: you are building gtk-common-themes on bionic or xenial? [13:43] (the docker containers for snapcraft are xenials) [13:43] xenial* [13:43] didrocks, i'm not building it [13:44] if you are fine with switching to bionic, I can do the same than for communitheme [13:44] ok, let's say we settle down on bionic then? [13:44] that way we don't forward/backward on all stage-packages [13:44] oh, wait oSoMoN setup builds on LP [13:45] bionic? [13:46] just checked, no xenial [13:46] hum [13:46] I have issues with xenial, like meson and so on… [13:46] https://launchpad.net/~ubuntu-desktop/+snap/gtk-common-themes [13:46] oh, that's why we have the backports PPA [13:47] which we should be using for everything desktop [13:47] do you have sassc in it? [13:47] that doesn't help me on Travis CI though :/ [13:48] ok, as it's only sassc which is staged for me, I think it's fine to build using bionic for gtk-common-themes Yaru part [13:48] (the rest is just unpacked/repacked) [13:50] kenvandine: looks like https://gitlab.gnome.org/Community/Ubuntu/gnome-software/commit/f01f43c3237912e6d425e73b60bdb0722dc6651c it's kind of broken [13:54] kenvandine: also if you can take a look to https://gitlab.gnome.org/Community/Ubuntu/gnome-software/merge_requests/6 [13:54] Ubuntu issue (Merge request) 6 in gnome-software "shell-search-provider: implement XUbuntuCancel" [Opened] [13:56] andyrock, oh i guess we don't even need that old MR now [13:56] i'll close it [13:56] kenvandine: oSoMoN: FYI: https://github.com/ubuntu/yaru/pull/826 [13:56] ubuntu issue (Pull request) 826 in yaru "Build gtk-common-themes using bionic docker image" [Open] [13:56] kenvandine: would be good if you at least publish the devel channel to stable from time to time as we discussed a while ago, as there are a lot of Yaru fixes which are automatically pushed to you :) [13:57] didrocks, yeah, that's what we've been working on this week [13:57] stable: 0.1 (319) [13:57] edge: 0.1 (700) [13:57] we're testing candidate now [13:57] kenvandine: it's not a MR. It has already been committed to master [13:57] great! [13:57] andyrock, oh :) [13:58] didrocks, we need it setup to automatically build though, not just on yaru changes [13:59] kenvandine: agreed [13:59] andyrock, i see, it was an old MR that robert just merged [13:59] which we actually don't even care about now :) [13:59] i'll revert it [13:59] kk [14:08] kenvandine, didrocks: gtk-common-themes has a sassc part to work around the lack of it in xenial [14:09] it's not being installed, only used to build yaru [14:09] see https://git.launchpad.net/~ubuntu-desktop/gtk-common-themes/+git/master/tree/snap/snapcraft.yaml#n230 [14:10] yeah [14:10] when we start building on bionic, this can be removed [14:13] yeah, let's do the same than Yaru itself in Travis CI [14:14] oSoMoN: ah, source: . [14:14] this is wrong, we are in gtk-common-themes, not Yaru [14:14] didrocks, is the sed command to replace xenial entries by bionic in apt sources not likely to blow up at some point, pulling in packages we don't want? [14:14] hum, this is becoming complex ;) [14:15] oSoMoN: it's only build-packages which are pulled (sassc only) [14:15] and snapd [14:15] but yeah, your Yaru part needs more thinking [14:15] let me iterate on it [14:16] the thing is that you can't try master [14:16] because there are PR branches as well [14:17] you probably need to sed for SOURCE_REPO and TRAVIS_BRANCH in the yaml we inject [14:18] oSoMoN: sorry for not spotting that on review! [14:18] the SnapsRev failures has hidden us from that failure… [15:14] Hello. Is there anyone I can ping about bug 1792000? Obviously it is not critical, as the "proper" version of VirtualBox works, but it is annoying. [15:14] bug 1792000 in gnome-shell-extension-ubuntu-dock (Ubuntu) "VirtualBox icon does not show un dock until screen locks" [Undecided,New] https://launchpad.net/bugs/1792000 [15:14] jbicha, ^^ any idea? [15:15] Sorry if I respond slowly, I am on a wobbly Internet connection. [15:15] oSoMoN: I have some free slots, do you want me to have a look at the gtk-common-themes in Yaru? [15:17] didrocks, ah, I wouldn't mind as I haven't gotten to it yet, and gotta get out soon for a chiropractor appointment [15:17] oSoMoN: no worry! Will handle it :) [15:17] cheers! [15:19] michael-vb: I'm not sure we can really support issues with non-packaged stuff like that. GNOME does expect a .desktop with specific requirements for the dock icons to work [15:19] and I have no idea how your local virtualbox install works [15:20] michael-vb: I recommend you either use the regular Ubuntu package or I guess you could try Oracle's repository https://www.virtualbox.org/wiki/Linux_Downloads [15:22] jbicha: I am one of the VirtualBox developers, so I run it straight from the build directory. It has a standard X11 icon property which the dock picks up, but not immediately. [15:22] As I said, not a critical use case of course. Just a would-be-nice if it can be solved. [15:23] Would the dash-to-dock upstream people be the right ones to ask? [15:23] Trevinho is the one who knows those matching problem best around [15:23] michael-vb: oh that would explain your username :) [15:23] but otherwise yes, maybe dash-to-dock upstream would be a good pick to ask [15:24] michael-vb: I suggest trying in a stock GNOME session since it might be more of a gnome-shell issue than an extension issue [15:24] you can install gnome-session, restart your computer. Click GNOME from the gear button as you log in [15:28] Ah right, so dash-to-dock just asks GNOME Shell for the information? I sort of thought that from their page. And gnome-session also uses GNOME Shell underneath? [15:28] Will try that. Yes, I have done GUI debugging a couple of times, so I have a bit of practice at installing different sessions and window managers. [15:29] Thanks. [16:05] oSoMoN: so, the correct branch/repo is picked (https://travis-ci.org/ubuntu/yaru/builds/428228954), now merging with debug to check for master pulling the expected branch as well [16:05] I've done other cleanups with recent snapcraft as well, while I was at it :p === pstolowski is now known as pstolowski|afk [16:20] michael-vb: mhmh, I can look at that, a bit in the rush now, but I'll check it latetr [16:30] Trevinho: thanks! [18:53] night all