[01:48] <duflu> Hold onto your hats. Ubuntu 17.10 is now just days behind the latest Gnome Shell code
[05:02] <didrocks> good morning
[05:04] <tsimonq2> o/ didrocks
[05:04] <didrocks> hey tsimonq2
[05:50] <oSoMoN> good morning desktoppers
[06:18] <flexiondotorg> Morning didrocks tsimonq2 oSoMoN
[06:18] <didrocks> hey flexiondotorg, oSoMoN
[06:19] <tsimonq2> o/ flexiondotorg and oSoMoN
[06:19] <oSoMoN> hey flexiondotorg, didrocks, tsimonq2
[06:22] <seb128> good morning desktopers
[06:22] <seb128> hey flexiondotorg tsimonq2 oSoMoN
[06:22] <seb128> re didrocks
[06:22] <tsimonq2> o/ seb128
[06:23] <flexiondotorg> Morning seb128
[06:24] <flexiondotorg> Who should I talk to about the nvidia proprietary driver packages?
[06:25] <flexiondotorg> They've regressed significantly between 17.10 Alpha 2 and Beta 1.
[06:25] <flexiondotorg> Prime simply doesn't work anymore.
[06:26] <flexiondotorg> I've had an investigate, got some info.
[06:38] <seb128> flexiondotorg, talk to tseliot
[06:38] <flexiondotorg> ty
[06:38] <seb128> yw
[06:39] <oSoMoN> good morning seb128
[07:13] <tseliot> flexiondotorg: can you reproduce the problem and show me your /var/log/gpu-manager.log , please?
[07:14] <flexiondotorg> Sure. I've got a couple of meetings and then I'll do more tests.
[07:16] <flexiondotorg> The crux of the issue is it is impossible to enable prime. There are no options to enable the nvidia drivers.
[07:30] <flexiondotorg> tseliot: http://paste.ubuntu.com/25443451/
[07:31] <flexiondotorg> That is what is in /var/log/gpu-manager.log.
[07:31] <flexiondotorg> I've just installed updates and there was an update for nvidia-375, so I'm going to reboot and see if anything has changed.
[07:32] <flexiondotorg> I did see this while updating
[07:33] <flexiondotorg> Setting up nvidia-375 (375.82-0ubuntu3) ...
[07:33] <flexiondotorg> dpkg: error: version '-' has bad syntax: revision number is empty
[07:33] <flexiondotorg> INFO:Enable nvidia-375
[07:33] <flexiondotorg> DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
[07:33] <flexiondotorg> DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
[07:33] <flexiondotorg> DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
[07:33] <flexiondotorg> Loading new nvidia-375-375.82 DKMS files...
[07:33] <flexiondotorg> Building for 4.12.0-11-generic
[07:33] <flexiondotorg> Building for architecture x86_64
[07:33] <flexiondotorg> Building initial module for 4.12.0-11-generic
[07:33] <flexiondotorg> Done.
[07:34] <tseliot> flexiondotorg: the nvidia module doesn't seem to be loaded. Also, I don't see your nvidia card in the system (did you disable it from the BIOS?)
[07:35] <flexiondotorg> No. I have an nvidia 1080 Ti in a Razer Core connected via Thunderbolt 3.
[07:35] <alexarnaud> good morning all :)!
[07:36] <oSoMoN> good morning alexarnaud
[07:42] <flexiondotorg> tseliot: http://paste.ubuntu.com/25443484/
[07:42] <flexiondotorg> After update and reboot.
[07:43] <tseliot> flexiondotorg: what does your new /var/log/gpu-manager.log look like?
[07:44] <flexiondotorg> nvidia-settings is now offering the choice of Intel or Nvidia
[07:45] <flexiondotorg> tseliot: Here is the new gpu-manager.log http://paste.ubuntu.com/25443490/
[07:47] <flexiondotorg> So the last update has appeared to resolved the issue I encountered yesterday.
[07:50] <didrocks> flexiondotorg: hey, have you pushed the new ambiance gtk theme btw?
[07:50] <didrocks> flexiondotorg: I don't see any review on https://code.launchpad.net/~3v1n0/ubuntu-themes/better-destructive-action/+merge/329392, correct?
[07:50] <flexiondotorg> didrocks: I'm going to rebase it today.
[07:51] <didrocks> flexiondotorg: nice! so all pending branches will be reviewed and package pushed by EOD? \o/
[07:51] <flexiondotorg> I will try.
[07:52] <flexiondotorg> I've only got my spare time to work on this.
[07:53] <tseliot> flexiondotorg: it looks the same, with nvidia being disabled. If that works, then it's all good
[07:58] <flexiondotorg> Yeah, I was able to select nvidia log out/in and all working.
[07:59] <tseliot> great
[08:02]  * Laney nods
[08:12] <seb128> hey Laney, happy friday
[08:14] <Laney> hey seb128, happy friday to you!
[08:14] <Laney> are you well?
[08:15] <davmor2> Morning all
[08:15] <didrocks> happy friday Laney & davmor2
[08:15] <seb128> Laney, yes, looking forward getting some more sleep but I managed to get some work done yesterday before going to bed and had an not-too-late morning today so that might be a productive friday :-)
[08:15] <seb128> Laney, you?
[08:23] <Laney> hey didrocks & davmor2!
[08:23] <Laney> seb128: tired too, looking forward to the weekend
[08:24] <Laney> we're supposed to be going to a river or lake or something to go wild swimming, should be fun
[08:25] <davmor2> Hey Laney didrocks
[08:29] <seb128> nice
[08:44] <didrocks> Trevinho: maybe you would know, the ubuntu font in G-S panel is quite blurry, as you worked on hdpi (but I'm only in 1x), is there any font hinting in the Shell that you know of?
[08:45] <Trevinho> didrocks: mh, no.... I guess it's because it has a slight shadow
[08:45] <Trevinho> didrocks: you can check it better by forcing it 2x
[08:45] <seb128> oh, Trevinho is up
[08:46] <seb128> good morning Trevinho :-)
[08:46] <didrocks> Trevinho: how can I do this?
[08:46] <Trevinho> hi seb128, yes :)
[08:46] <didrocks> just changing the font size by *2?
[08:46] <didrocks> I don't see any shadow that way
[08:48] <Trevinho> didrocks: mhmh..  https://usercontent.irccloud-cdn.com/file/03ExjSYA/
[08:48] <Trevinho> there's shadow, but... might not be very well visible
[08:48] <didrocks> Trevinho: you have younger and better eyes than I do :p
[08:48] <didrocks> do you know how we can improve this?
[08:48] <Trevinho> didrocks: maybe younger, not sure if better :-D
[08:49] <Trevinho> didrocks: it's managed by theme
[08:49] <didrocks> Trevinho: is it a css property to disable it?
[08:49] <didrocks> Trevinho: rember the shell css is different :p
[08:49] <Trevinho> didrocks: as for magnifying all up, not sure if you can run gnome-shell nested there with GDK_SCALE=2..
[08:49] <Trevinho> yeah, there's a theme node indeed
[08:49] <Trevinho> let me check which one
[08:50] <Trevinho> didrocks: here's where is loaded
[08:50] <Trevinho> https://www.irccloud.com/pastebin/EQFegTGS/
[08:50] <Trevinho> so... text-shadows: manages it from StLabel
[08:51] <didrocks> ah nice!
[08:51] <didrocks> let me try to disable it only for the panel
[08:51] <oSoMoN> good morning popey, have you seen jd_strand's questions at https://forum.snapcraft.io/t/chromium-snap-doesnt-work-with-the-nvidia-proprietary-driver/1825/7 ?
[08:52] <oSoMoN> I wonder if there's an easy way for you to test with snapd 2.28
[08:52] <Trevinho> didrocks: I guess this one
[08:52] <Trevinho>   #panel .panel-button {
[08:52] <Trevinho>     -natural-hpadding: 12px;
[08:52] <Trevinho>     -minimum-hpadding: 6px;
[08:52] <Trevinho>     font-weight: bold;
[08:52] <Trevinho>     color: #eee;
[08:52] <Trevinho>     text-shadow: 0px 0px 2px rgba(0, 0, 0, 0.9);
[08:52] <Trevinho>     transition-duration: 100ms; }
[08:52] <Trevinho> err. sorry for the flooding :|
[08:52] <didrocks> Trevinho: yeah, I was on that one
[08:52] <didrocks> Trevinho: just trying to see wha tother impacts it has
[08:53] <didrocks> Trevinho: and actuallllllllllyyyyyyyyyy no
[08:53] <didrocks> :p
[08:53] <Trevinho> didrocks: mh, it seems here too... mhmh
[08:53] <didrocks> let's apply globally first
[08:54] <didrocks> hum, no, something is overriding it
[08:54] <Trevinho> didrocks: might be more local yes
[08:55] <Trevinho> for example the 'overview' class manages the panel
[08:55] <didrocks> Trevinho: no, it's only #panel
[08:55] <didrocks> overview is the panel in overview mode
[08:57] <didrocks>     #panel.solid .panel-button {
[08:57] <didrocks> I can at least change the color here :)
[08:57] <didrocks> but text-shadow is none
[08:57] <didrocks> are you sure the shadow is coming from only that property?
[08:58] <didrocks> (.solid is when you have a maximized app or any app touching the top panel)
[08:59] <didrocks> Trevinho: confirmed, there is no text-shadow applied to that node, so not that…
[08:59] <didrocks> just replace the text-shadow: none with an horrible color
[08:59] <didrocks> you will see it's applied
[09:00] <didrocks> so, the blur doesn't come from there
[09:01] <didrocks> and also way more blurry under wayland
[09:01] <didrocks> which is weird
[09:01] <didrocks> duflu: hey, any thoughts on this? (fonts is more blurry under wayland in the Shell panel) ^
[09:02] <duflu> didrocks, I am burried in GDK madness. Can you give more hints as to what you mean?
[09:02] <oSoMoN> ricotz, hey, I’ve got a build of 5.4.1 going in https://launchpad.net/~osomon/+archive/ubuntu/lo-stage/+packages
[09:03] <didrocks> duflu: so, wayland session, look at the panel font in the ubuntu session (like date/time entry)
[09:03] <didrocks> it's really blurry here
[09:03] <didrocks> not that much on X
[09:03] <duflu> Let me check X again
[09:04] <didrocks> (the blur is even more visible once we start attaching the gradient from our theme)
[09:06] <duflu> didrocks, Not sure I can see it but I had been suspecting parts of the panel fonts were blurry. That's either a different hinting mode, or lack of subpixel order information. We had the latter problem in Mir (DRM failed to provide it) so I guess X might have been guessing when it wasn't available
[09:08] <didrocks> duflu: let me take a screenshot with the new theme, I guess it's really visible there (so that you can confirm)
[09:08] <duflu> didrocks, Confirmed with screenshots - Wayland is missing subpixel info so is doing greyscale
[09:09] <duflu> which is of course a bit more blurry
[09:09] <duflu> I had to zoom into screenshots to see it
[09:10] <didrocks> duflu: ah, however, our decorators aren't that blurry, are we giving more font hintings?
[09:10] <didrocks> Trevinho: FYI ^
[09:10]  * didrocks wonders why his current captures aren't in ~/Images
[09:10] <duflu> didrocks, if ~/Pictures or whatever doesn't exist then they are in ~/
[09:11] <didrocks> well, it's ~/Images in french
[09:11] <didrocks> (translated XDG path)
[09:11] <didrocks> and not in ~/
[09:11] <didrocks> retrying
[09:11] <didrocks> duflu: Trevinho: http://imgur.com/a/I8klB
[09:11] <duflu> Subpixel rendering also seems to have slightly stronger hinting (less vertical blur) but might be in the same hinting level
[09:12] <didrocks> we can clearly see that the decoration is "fine", not the panel
[09:12] <didrocks> so, missing some hinting info in the Shell?
[09:13] <duflu> didrocks, I think hintint is probably not a contributor. But lack of subpixel definitely is (I can see in my own screenshots)
[09:13] <didrocks> duflu: I don't get how the decoration, with the same font size (I think?) is giving a different result
[09:14] <duflu> didrocks, different subpixel order enum passed into the font rendering functions
[09:14] <didrocks> ah, that makes sense, so different treatment
[09:14] <duflu> It's blurry on gdm too
[09:14] <didrocks> yeah, gdm is actually the Shell
[09:14] <didrocks> (same panel, different css class)
[09:15] <didrocks> I guess there is no quick way for us to fix this, correct?
[09:16] <duflu> didrocks, https://bugzilla.gnome.org/show_bug.cgi?id=645433
[09:19] <duflu> It's had a patch waiting since 2012 :)
[09:19] <didrocks> duflu: I quickly skimmed through it, but yeah, that matches what you were telling
[09:19] <didrocks> duflu: unsure the patch fixes it with the followup comments
[09:19] <duflu> That's OK. So long as it's still an open bug
[09:19] <didrocks> the patch landed
[09:19] <didrocks> though
[09:19] <didrocks> in 3.6
[09:24] <didrocks> yeah, it doesn't respect it anymore under wayland, I guess https://bugzilla.redhat.com/show_bug.cgi?id=1411272 is the good reference
[09:25] <duflu> didrocks, yes seems like the right bug. Where "hinting" means "hinting and subpixel order"
[09:26] <duflu> The extra vertical blur suggests the hinting is different
[09:26] <didrocks> duflu: I bet this is quite involved in term of changes and will take time? (I created a trello card anyway so that we can keep an eye on it)
[09:26] <didrocks> unfortunately, I find it very glaring with the new theme
[09:27] <didrocks> (due to the gradient I guess)
[09:28] <duflu> didrocks, yes I was mostly subconsciously irritated by it. Don't see why it should be a big bug though... most of the code should be common between X and Wayland there. Font rendering is almost always done with software blitting
[09:28] <duflu> I mean I don't see why it should be too hard to fix, but maybe it is
[09:29] <didrocks> duflu: ah, if you are hopeful about it and think you can tackle it before release, that's awesome!
[09:29] <didrocks> Let me log it as a launchpad bug, I think we'll get people refering to it once I land the new theme
[09:29] <duflu> I hope to have the time in future
[09:29] <didrocks> let me target it against gnome-shell, then you can retarget where it fits better (wayland or mutter)
[09:30] <duflu> didrocks, actually there's an old bug I found back in May. You might want to close that and use your new one...
[09:31] <duflu> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/893859
[09:31] <didrocks> duflu: which one do you prefer? I can reuse and change the description of the old one if you prefer it that way
[09:32] <duflu> didrocks, I think the old bugs are too old (they don't cover the fact that it works in Xorg)
[09:32] <didrocks> duflu: ok, let's close the old one.
[09:32] <duflu> Use a new LP bug and the redhat one
[09:34] <didrocks> duflu: https://bugs.launchpad.net/gnome-shell/+bug/1714459
[09:34] <duflu> Fun fun
[09:34] <didrocks> thanks a lot for looking at it duflu :)
[09:35] <didrocks> (and giving me hints I'm not crazy and my eyes still worth something :p)
[09:35] <duflu> didrocks, no problem. Yes it annoyed me too
[09:37] <Trevinho> didrocks: mh, not sure then... For sure there's some shadow in the git version I'm using
[09:38] <didrocks> Trevinho: look above ^ it's another kind of issues
[09:38] <didrocks> not wanted "shadow" at least ;)
[09:39] <Trevinho> didrocks: ack, I saw that now
[09:51] <duflu> I'm done
[09:51] <duflu> Catch you next week
[10:12] <popey> oSoMoN: replied to that thread with the data I have..
[10:36] <fossfreedom> Laney, thanks for your suggestions - I've reworked the two patches; any chance you can pass your eyes over again please ? https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1703690
[10:41] <Laney> fossfreedom: hopefully later on, have to look at tseliot's patch too but some other things to do first :(
[10:49] <oSoMoN> popey, thanks
[10:49] <seb128> didrocks, https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714330 is the multilogin segfault session backtrace
[10:49] <seb128> jbicha, ^
[10:49] <didrocks> seb128: thx!
[10:49] <seb128> yw
[10:50] <seb128> the upstream bug pointed is fixed in git
[10:50] <seb128> that's not the same report but might be worth testing with current git
[10:51] <didrocks> indeed. I won't today, but can add it to next week list
[10:51] <didrocks> (big set of patches)
[10:51] <seb128> easier if jbicha makes a git snapshot
[10:51] <seb128> or if we wait for the next tarballs
[10:52] <didrocks> yeah, .92 isn't far away
[10:58] <ricotz> oSoMoN, hi, ack
[10:59] <ricotz> oSoMoN, I assume there are no additional packaging changes compared to the current git tree?
[11:03] <oSoMoN> ricotz, correct
[11:07] <ricotz> oSoMoN, ok
[11:13] <seb128> jbicha, hey
[11:13] <jbicha> good morning
[11:15] <seb128> jbicha, when you do GNOME updates using meson, can you include a debian/rules snippet like I added to gnome-bluetooth?
[11:15] <seb128> jbicha,
[11:15] <seb128> override_dh_translations:
[11:15] <seb128> 	ninja -C obj-$(DEB_HOST_GNU_TYPE) <domain>-pot
[11:15] <seb128> 	dh_translations
[11:16] <jbicha> seb128: you want that for all of main, right?
[11:16] <seb128> jbicha, I've on my todolist to look at the translation tools integration with the new build systems but it's not trivial and meanwhile the workaround would give us working langpacks
[11:16] <seb128> jbicha, those using meson only, but yes
[11:16] <seb128> you need to figure out the <domain> manually
[11:16] <jbicha> I just got us in sync with Debian on several packages ;)
[11:16] <seb128> don't copy it like that, it's the actual domain
[11:17] <seb128> jbicha, you can diff the pre-meson and new version see if there are strings changes
[11:17] <jbicha> I might push that in to Debian since I think an unrecognized override would just be ignored…
[11:17] <seb128> if there are not no need to get the updated template
[11:17] <seb128> k
[11:17] <seb128> put a comment saying it's a temporary hack until dh_translations learn to deal with meson
[11:18] <jbicha> since they're getting most of GNOME 3.24 and 3.26 faster than expected, I'm hoping they won't mind
[11:18] <seb128> Trevinho, what's the status of those 2 indicators gcc buildfix landing?
[11:19] <jbicha> seb128: do you have a goal of when you want those snippets added by?
[11:20] <seb128> no
[11:20] <seb128> I'm not even sure most projects got strings changes this cycle
[11:20] <seb128> but would be nice to have them as we land 3.26
[11:22] <jbicha> right and meson modules would be mostly likely to be doing 3.25.92 and 3.26 this time (since some modules skip releases)
[11:23] <seb128> jbicha, if you can do to or include those changes when you do updates that would be useful
[11:24] <seb128> jbicha, but let me know if you want me to look list and check which ones are needed
[11:24] <seb128> that's a bit of work but maybe most have no string change
[11:24] <jbicha> sure, mostly done with Debian updates this week
[11:25] <jbicha> seb128: what about LP: #1688994 since that's not strictly meson?
[11:26] <seb128> jbicha, it's on my todolist for a while, just didn't get to it yet
[11:26] <jbicha> meson projects don't use intltool but some other stuff doesn't use intltool either
[11:26] <jbicha> ok
[11:26] <seb128> do you have an example or non-meson non-intltool?
[11:27] <jbicha> gnome-sudoku
[11:27] <seb128> thanks
[11:28] <jbicha> btw, LP: #1631750 is a high priority bug for language support
[11:28] <seb128> right
[11:28] <jbicha> that broke when we updated to PackageKit1 last year
[11:28] <seb128> still quite some work to do this cycle :-/
[11:30] <jbicha> decision on trying to land a mutter git snapshot in artful or wait until later next week for next tarball release?
[11:30] <seb128> I think it can wait next week
[11:31] <seb128> but if you have the slots to do a snapshot that would be useful
[11:31] <seb128> could avoid a few users to loose work by having their session closing
[11:31] <seb128> if that actually fixes the segfault
[11:33] <jbicha> I guess the nice part about a snapshot is if we find any thing that still doesn't work, there are still a few days before 3.26 code freeze for those to get fixed
[11:34] <jbicha> too bad mutter isn't using meson yet because making tarballs with meson is pretty easy these days
[11:40] <seb128> hehe
[11:41] <seb128> jbicha, gnome-sudoko should be easy to fix for dh_translations, but unsure how common that case is
[11:41] <seb128> it has a configure.ac with the gettext domain
[11:41] <seb128> but most projects do
[11:41] <seb128> GETTEXT_PACKAGE=<domain>
[11:41] <seb128> AC_SUBST(GETTEXT_PACKAGE)
[11:41] <seb128> where gnome-sudoku does
[11:41] <seb128> AC_SUBST([GETTEXT_PACKAGE], [gnome-sudoku])
[11:42] <seb128> our parser does
[11:42] <seb128> 	    $domain = $1 if /^GETTEXT_PACKAGE\s*=\s*(\S*)/;
[11:42] <seb128> so we can easily add a regexp for the other syntax
[11:42] <jbicha> that's sort of what happened with evolution except evolution is cmake and we don't do much cmake now?
[11:43] <seb128> not really, we do cmake as well
[11:43] <seb128> but evolution has the subst using a variable
[11:43] <seb128> like $project_name or something
[11:43] <seb128> and we don't do variables resolution
[11:44] <seb128> that's too complex for our simple tool, we don't want to reimplement a build system parser :-)
[11:45] <jbicha> ok
[12:02] <seb128> Trevinho, hey, did you see my ping earlier?
[12:02] <Trevinho> seb128: hey, no... sorry
[12:03] <seb128> Trevinho, k, no worry, what's the status of the indicator build fixes landing?
[12:03] <Trevinho> seb128: indicators landing is fine for me, we need to publish it though..
[12:03] <seb128> that was my question
[12:03] <Trevinho> seb128: I've no powers for that
[12:04] <seb128> then ping/ask on the channel! :-)
[12:04] <Trevinho> seb128: and dobey asked something in ubuntu-devel IIRC
[12:04] <seb128> right, let's ignore that cleanup for now, it's not important
[12:04] <seb128> I was just looking at the approved changes when we discussed doing a landing
[12:05] <Trevinho> seb128: ok, so feel free to publish it... Sorry I didn't pinged you about, I thought you were monitoring the silo :)
[12:05] <seb128> no
[12:06] <seb128> I don't even know what silo that is
[12:06] <seb128> you said you would move them out of the silo that includes unity
[12:06] <Trevinho> https://bileto.ubuntu.com/#/ticket/2928
[12:06] <seb128> thanks
[12:08] <Trevinho> I still have build issue in the unity side instead, but I need a porter box and RT was still working in a chroot... As I only see issues in some archs
[12:10] <seb128> you are still waiting for access to a porter box?
[12:20] <Trevinho> seb128: I've the access, but not the right chroot to test it
[12:20] <seb128> ah
[12:36] <jibel> didrocks, the app indicator is not always displayed, is it known?
[12:37] <jbicha> didrocks: mozjs52 is stuck in artful-proposed because I enabled mandatory build tests which fail on s390x so s390x doesn't build
[12:37] <jibel> didrocks, I mean I've 2 apps in this indicator and sometimes it's there, sometimes not
[12:37] <jbicha> we know that s390x doesn't work any way, how do you want to handle this?
[12:37] <jbicha> do I need to specific architectures in debian/control?
[12:38] <seb128> jibel, you should ask Trevinho and not didrocks
[12:38] <seb128> he's the one looking after the appindicators integration
[12:38] <seb128> stop bouncing all issues to Didier please
[12:41] <jibel> sorry
[12:41] <jibel> Trevinho, then ^
[12:43] <Trevinho> jibel: what are the apps?
[12:44] <jbicha> seb128: is there an LP bug for https://bugzilla.gnome.org/786978 ?
[12:44] <seb128> jbicha, I don't think so, I noticed it myself and worked directly upstream
[12:45] <jibel> Trevinho, synology cloud client and hp systray
[12:46] <Trevinho> jibel: are they both qt apps, right?
[12:48] <jibel> Trevinho, hp is a qt app, I don't think synology is
[12:49] <jibel> Trevinho, cloud client is a gtk app
[12:51] <jibel> Trevinho, are there any log I could check?
[12:51] <kenvandine> i'm not getting any indicators either, i should have hexchat there
[12:51] <jibel> there is nothing in the journal regarding this extension
[12:53] <kenvandine> Trevinho, does it require indicator-application?
[12:53] <kenvandine> i don't have that installed
[12:53] <kenvandine> but i do have indicator-messages running
[12:53] <Trevinho> kenvandine: nope... the extension should do that
[12:53] <kenvandine> cool
[12:54] <Trevinho> I'm now working in fractional stuff, but I'll be back to that in next days,,
[12:54] <kenvandine> ok
[12:56] <kenvandine> damn, gnome-software is using all 4 cores :/
[13:08] <seb128> bah, the GNOME updates screwed suspend
[13:09] <seb128> gnome-tweak-tool-lid-inhibtor stopped working it seems
[13:09] <seb128> and the g-s extension to display a suspend button still lists it but it doesn't work
[13:10] <seb128> jbicha, shouldn't that gnome-builder update require a ffe?
[13:11] <jbicha> it's unseeded universe so um I thought it didn't need a FFe
[13:11] <Laney> feature freeze applies to the whole archive
[13:12] <xnox> jbicha, if binaries are removed for s390x from artful-release; britney will stop considering a missing build as a regression and the package will become a valid candidate
[13:12] <jbicha> it was late because it split out 3 libraries which had to go through the Ubuntu or Debian new queues
[13:13] <seb128> doesn't matter much why it's late, it's still a feature update after ffe :-)
[13:13] <seb128> I'm +1 for the update btw, was looking at versions over lunch and I though it would be good to update
[13:13] <jbicha> the libraries were in the NEW queue weeks ago (before Feature Freeze)
[13:14] <jbicha> the bad part about the new version is that I disabled terminal because trying to hack it to work with our vte2.91 seemed too much
[13:14] <jbicha> so I'll file a FFe if I get that working then I guess
[13:15] <didrocks> jibel: you can check which extensions are enabled with alt + f2, "lg", then 3rd tab to ensure you have the extension on
[13:16] <didrocks> jibel: you can as well "show error logs"
[13:18] <jibel> didrocks, thanks it's loaded and no error
[13:18] <jibel> Trevinho, bug 1714504
[13:18] <didrocks> jibel: ok, for Trevinho thus!
[13:18] <didrocks> :)
[13:19] <kenvandine> i guess the app indicator doesn't actually show stuff from the messaging indicator right?
[13:19] <kenvandine> which i think the legacy tray must have been doing
[13:19] <didrocks> yeah, it's only "appindicators" AFAIK
[13:19] <jbicha> didrocks: please remove mozjs52/s390x from artful-release per xnox's comment
[13:19] <seb128> kenvandine, hey Ken, how are you?
[13:19] <kenvandine> that explains why hexchat isn't showing up there
[13:19] <kenvandine> seb128, hey, good and you?
[13:19] <seb128> kenvandine, I'm good thanks
[13:20] <seb128> kenvandine, did we have new GNOME snaps that got published in the store this week? (for the desktop weekly news)
[13:20] <didrocks> jbicha: sorry, didn't see xnox's commenting on this right now? or do you mind, the old comment a week or so ago?
[13:20] <kenvandine> seb128, gnome-system-monitor
[13:20] <jbicha> didrocks: his comment about 8 minutes ago here
[13:20] <seb128> kenvandine, did you get the autoconnect assertion done?
[13:20] <kenvandine> seb128, i also have branches for all the snaps that add the wayland interface, ready for snap 2.28 release
[13:20] <kenvandine> seb128, it has 2 votes
[13:20] <didrocks> jbicha: did you check rdepends?
[13:21] <kenvandine> but i don't think it's added yet
[13:21] <kenvandine> seb128, i've also tested all the snaps, they work with wayland
[13:21] <kenvandine> with a few tweaks :)
[13:21] <kenvandine> all in my branches
[13:21] <seb128> great
[13:22] <kenvandine> i also cleaned up plugs, like some of them had home and network when they didn't really need them
[13:22] <jbicha> didrocks: yes the only rdepends is gjs which already had its s390x binaries removed
[13:22] <didrocks> jbicha: Could not find binaries for 'mozjs52/None' in artful .  Exiting.
[13:22] <didrocks> abnd indeed, there is none
[13:22] <kenvandine> didrocks, i have an eog snap which has thumbnailer issues.  I think it's failing to query the mime type
[13:23] <kenvandine> didrocks, have you seen any snap using desktop helpers that we know successfully queries the mime cache?
[13:23] <didrocks> kenvandine: no, I don't think this was ever tested
[13:23] <kenvandine> ok
[13:24] <kenvandine> i think i've found a bug, need to keep digging
[13:24] <kenvandine> it calls a function _can_thumbnail which requires a mimetype arg
[13:24] <jbicha> libmozjs-52-0 libmozjs52-dev libmozjs52-0-dbgsym libmozjs52-dev-dbgsym
[13:24] <kenvandine> which is NULL
[13:29] <oSoMoN> anyone interested in trying out the libreoffice snap, there's an update to 5.4.1 in the edge channel
[13:29] <oSoMoN> I'm not issuing a wider call for testing yet, as I have a few known issues to iron out first
[13:29] <oSoMoN> but it's already fairly usable it seems
[13:30] <oSoMoN> except on wayland where it crashes at startup, that is
[13:30] <seb128> oSoMoN, oh, good, I can include that in the weekly news :-)
[13:30] <seb128> ah
[13:34] <didrocks> jbicha: the -dev is arch:all, so only the lib actually. Done
[13:38] <amano> jbicha, if we need a ffe for gnome builder, we will probably need one for gnome games at well...
[13:38] <seb128> kenvandine, what sort of issues have the snap currently under wayland?
[13:38] <jbicha> amano: yes, would you be interested in filing that bug?
[13:39] <kenvandine> seb128, one of them needed opengl interface as well
[13:39] <kenvandine> the rest i just added the wayland interface
[13:39] <seb128> kenvandine, I was just wondering if the libreoffice crashes under wayland oSoMoN mentioned could be the same issue
[13:39] <kenvandine> could be
[13:40] <kenvandine> oSoMoN, ^^ you might need to add opengl to the plugs
[13:40] <amano> Yup. Over the weekend. For the gnome games app, I guess...
[13:40] <kenvandine> oSoMoN, and have you tested it with the wayland interface?  which is in core from the edge channel?
[13:41]  * kenvandine installs it
[13:48] <kenvandine> oSoMoN, seb128: i see it does connect to wayland and opengl, so that's not the problem
[13:48] <kenvandine> and i can confirm it doesn't start for me with wayland :/
[13:57] <didrocks> jbicha: there is a lot of people on the french forum who reports that Tweaks doesn't display the right status for mode enabled extensions
[13:57] <didrocks> jbicha: it displays them as being disabled
[13:58] <didrocks> I guess you should read the css file to see if they are loaded, and if the user disable them, add to the list of "disabled-extensions" which works with the Shell
[14:01] <didrocks> jbicha: basically, those guys are starting to make extensions like that: https://extensions.gnome.org/review/7279 (and I would prefer them to use Tweaks)
[14:02] <seb128> baaaah
[14:02] <seb128> gnome-shell stopped listing calendar events since the 3.25 updated here
[14:02] <seb128> is anybody else having the same issue?
[14:03] <didrocks> oh correct
[14:03] <seb128> :-/
[14:04] <seb128> jbicha, ^ known?
[14:07] <jbicha> gsettings get org.gnome.shell disabled-extensions
[14:07] <jbicha> No such key “disabled-extensions”
[14:07] <oSoMoN> seb128, kenvandine: I just tried an earlier build of the same snap (https://code.launchpad.net/~libreoffice/+snap/libreoffice/+build/66888) and that one works under wayland
[14:07] <jbicha> GNOME Classic has the same issue with their extensions not showing up as On in Tweaks app
[14:08] <kenvandine> oSoMoN, ok, so some code change i guess
[14:08] <jbicha> didrocks: but it's actually a gnome-shell bug, try running gnome-shell-extension-prefs to see the same thing
[14:08] <oSoMoN> the next build in the list fails, and the actual changes to the branch are not meaningful, so I'm guessing a build dep or a stage package changed in the meantime
[14:08] <oSoMoN> I'll compare the build logs
[14:09] <didrocks> jbicha: well, you can detect it still, no?
[14:09] <seb128> jbicha, didrocks, from the build log
[14:09] <seb128> dh_install: Please use dh_missing --list-missing/--fail-missing instead
[14:09] <didrocks> jbicha: or you are using some external API and not the gsettings key?
[14:09] <seb128> dh_install: This feature will be removed in compat 11.
[14:09] <seb128> dh_missing: usr/${libdir}/gnome-shell/gnome-shell-calendar-server exists in debian/tmp but is not installed to anywhere
[14:09] <seb128> jbicha, didrocks, we need --fail-missing :-)
[14:09] <didrocks> seb128: +1
[14:09] <seb128> dh_missing: usr/${libdir}/gnome-shell/gnome-shell-hotplug-sniffer exists in debian/tmp but is not installed to anywhere
[14:09] <seb128> also
[14:09] <didrocks> I can turn it up in my next upload
[14:09] <didrocks> (monday?)
[14:09] <kenvandine> didrocks, i've confirmed it's the mime query that's breaking thumbnails
[14:10] <seb128> well and some others
[14:10] <kenvandine> i have a branch of eog that hard codes the mimetype to "image/png"
[14:10] <kenvandine> and it works :)
[14:10] <kenvandine> so at least i know i'm on the right path
[14:10] <didrocks> jbicha: how Tweaks is detecting enabled extensions?
[14:11] <jbicha> https://git.gnome.org/browse/gnome-tweak-tool/tree/gtweak/tweaks/tweak_group_shell_extensions.py
[14:11] <kenvandine> g_file_info_get_content_type is failing
[14:11] <jbicha> I didn't build Tweaks so I don't know
[14:12] <didrocks> well, you are the current maintainer, aren't you?
[14:12] <didrocks> ok, it's querying over dbus
[14:12] <jbicha> but I think it shares functionality with gnome-shell-extension-prefs
[14:13] <oSoMoN> kenvandine, seb128 : for reference https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1714520
[14:13] <didrocks> https://git.gnome.org/browse/gnome-tweak-tool/tree/gtweak/gshellwrapper.py
[14:13] <didrocks> yep
[14:13] <didrocks> ok, I'll try to fix it there then
[14:14] <jbicha> ask Red Hat to send you a bonus check if you fix it (since RHEL ships both GNOME Classic and Tweak Tool by default) ;)
[14:15] <didrocks> \o/
[14:15] <seb128> jbicha, didrocks, also
[14:15] <didrocks> actually, they don't expose the "enabled" state
[14:16] <seb128>  /usr/share/dbus-1/services/org.gnome.Shell.CalendarServer.service:Exec=/usr/${libdir}/gnome-shell/gnome-shell-calendar-server
[14:16] <seb128> the ${libdir} there looks boggus
[14:16] <didrocks> and so tweaks fallback to the gsettings key
[14:16] <seb128> it should be replaced by the actual value I guess?
[14:16] <didrocks> seb128: indeed
[14:18] <jbicha> seb128: I think the libdir problem needs to be fixed in debian/rules since IIRC meson wants explicit directory names instead of variables
[14:18] <seb128> jbicha, can you have a look to the libdir/missing files issue today?
[14:18] <seb128> I want to look at the g-c-c dock patch still
[14:19] <jbicha> yes
[14:19] <seb128> thanks
[14:19] <seb128> want a bug report?
[14:20] <jbicha> probably not needed but you can if you want
[14:20] <seb128> no it's fine
[14:20] <seb128> jbicha,
[14:20] <seb128> 		--libdir=/usr/lib \
[14:20] <seb128> 		--libexecdir="\$${libdir}
[14:21] <jbicha> I am annoyed that debhelper emits that dh_missing warning, if I wanted debhelper 11 compatibility, I would have set it!
[14:21] <seb128> I guess we can just put the value for libexecdir
[14:21] <jbicha> yes, that's my plan
[14:21] <seb128> libdir is not going to change without direct edit
[14:23] <jbicha> I'm surprised by how little work is done on GNOME Classic (the theme in particular could use love)
[14:23] <oSoMoN> build logs for parallel builds are hard to compare :/
[14:24] <seb128> oSoMoN, indeed :-/
[14:25] <oSoMoN> let's see if I can compare the squashfs of a working snap and a broken one instead
[14:26] <ogra_> oSoMoN, you are not building the libreO snap on non-xenial without cleanbuild, do you ?
[14:27] <ogra_> (that wont work because your lib versions wont match whats in the core snap ... you need to build against xenial (i.e. use cleanbuild))
[14:31] <oSoMoN> ogra_, nope, I'm building on launchpad, xenial
[14:31] <ogra_> ah, k the beginning of the description in the bug sounded like you are building natively on artful
[14:31] <oSoMoN> hu ho, the desktop-launch script differs between the two versions, and by a wayland-related snippet
[14:32] <oSoMoN> ogra_, testing on artful, not building on artful
[14:32] <ogra_> yeah, got it
[14:33] <oSoMoN> I think I found my culprit
[14:33]  * oSoMoN looks at kenvandine 
[14:33] <oSoMoN> https://github.com/ubuntu/snapcraft-desktop-helpers/commit/c19eff033485cbd5a81093bef1f049e351b3d699
[14:34] <kenvandine> oSoMoN, yes?
[14:34] <oSoMoN> kenvandine: is there anything specific I need to do to make the snap work with that change in the desktop helpers?
[14:34] <kenvandine> oSoMoN, no
[14:35] <kenvandine> should just work[tm]
[14:35] <kenvandine> worked for all of my snaps :)
[14:35] <oSoMoN> let me test by commenting out that snippet in the snap
[14:35] <kenvandine> oSoMoN, good idea
[14:44] <jbicha> seb128: done https://launchpad.net/ubuntu/+source/gnome-shell/3.25.91-0ubuntu2
[14:44] <seb128> jbicha, thanks
[14:45] <seb128> didrocks, ^
[14:45] <seb128> didrocks, includes fail-missing so you can remove from your todo
[14:46] <jbicha> didrocks: libmozjs-52-dev is not arch:all and needs to be removed to unblock proposed migration
[14:47] <oSoMoN> kenvandine, confirmed, reverting that change in the desktop helpers "fixes" the libreoffice snap
[14:47] <oSoMoN> the issue is probably somewhere else in the snap though
[14:47] <oSoMoN> but at least I know where to start looking
[14:48] <ogra_> oSoMoN, well, i doubt you have a wayland interface unless you run snapd master ... it hasnt been released yet
[14:51] <kenvandine> ogra_, i tested his snap with the wayland interface
[14:51] <kenvandine> failed
[14:51] <ogra_> ah
[14:51] <kenvandine> oSoMoN, not sure what that could have to do with it though
[14:51] <kenvandine> it sets additional env
[14:52] <didrocks> jbicha: done
[14:52] <oSoMoN> kenvandine, maybe missing stage packages? can you point me to a snap of yours that works under wayland with that change?
[14:52] <seb128> oSoMoN, can you try which line/env creates the issue?
[14:52] <oSoMoN> seb128, yep, was going to try that
[14:53] <kenvandine> oSoMoN, mine all use the gnome-3-24 content interface
[14:53] <kenvandine> oSoMoN, maybe the wayland libs are missing?
[14:53] <oSoMoN> kenvandine, which package provides them?
[14:54] <kenvandine> oSoMoN, it does link to gtk right?
[14:54] <oSoMoN> yes
[14:54] <kenvandine> maybe it's because it's built with the old wayland libs?
[14:54] <kenvandine> try getting a build with the backport ppa
[14:54] <kenvandine> https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/gnome-3-24
[14:55] <seb128> that might well be the issue
[14:55] <kenvandine> yeah
[14:55] <kenvandine> if it's using gtk from xenial, that's an old wayland
[14:55] <seb128> oSoMoN, kenvandine, xenial wayland libs aren't going to work with the artful server
[14:55] <kenvandine> might not be compatible
[14:55] <seb128> iirc
[14:55] <kenvandine> right
[15:00] <oSoMoN> kenvandine, wayland 1.12.0-1~ubuntu16.04.1 is already in xenial, how does the version in https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/gnome-3-24/+packages differ?
[15:01] <oSoMoN> (in xenial-updates, that is)
[15:02] <kenvandine> hmmm
[15:02] <seb128> oh, that's quite recent
[15:02] <seb128> it was not at the time of the backport
[15:03] <kenvandine> right
[15:03] <kenvandine> it was 1.9 then
[15:04] <oSoMoN> commenting out the export of GDK_BACKEND to "wayland" makes the snap work
[15:04] <seb128> so it probably use x11/xwayland
[15:05] <seb128> now to debug what is wrong with wayland...
[15:05] <seb128> does setting an env override the launcher one?
[15:05] <kenvandine> so...
[15:05] <kenvandine> gtk3 hasn't been rebuilt in xenial since that upload
[15:05] <seb128> oSoMoN, I don't think using native wayland is important atm, so maybe just override the env if you can
[15:06] <kenvandine> looks like latest gtk3 upload was april
[15:06] <kenvandine> wayland was july
[15:07] <kenvandine> i'm curious if it might work built against the backports ppa
[15:07] <seb128> it's not even clear that the gtk version in xenial works with that newer wayland
[15:07] <kenvandine> maybe that gdk wayland backend is broken in xenial right now
[15:07] <kenvandine> yeah... it might even fail to build!
[15:07] <oSoMoN> kenvandine, I'll try building the snap against the backports PPA, it's gonna take a while though…
[15:07] <kenvandine> oSoMoN, yeah
[15:08] <seb128> oSoMoN, kenvandine, try building with the ppa
[15:08] <seb128> oSoMoN, that's what the w.e is for :-)
[15:08] <seb128> surprise on monday
[15:08] <kenvandine> :-D
[15:08]  * kenvandine gets a 3 day weekend this weekend :)
[15:08] <seb128> and as a bonus you don't get to be disappointed on a friday
[15:08] <seb128> oh?
[15:08] <kenvandine> monday is a us holiday
[15:08] <seb128> national holiday on monday? or vac day?
[15:09] <seb128> lucky you
[15:09] <seb128> enjoy!
[15:09] <kenvandine> :)
[15:10] <oSoMoN> seb128, nah, a local build should take less than 4 hours, I can report back before going on EOW^W on holidays
[15:11] <oSoMoN> (I'm out all of next week)
[15:12] <seb128> oh, I forgot about that
[15:12] <seb128> oSoMoN, enjoy!
[15:13] <oSoMoN> will sure do, flying to France for a few days tomorrow
[15:13] <seb128> oSoMoN, btw I didn't follow but the .1 artful update is for after your holidays then? (it's fine, just curious since I saw you discuss updates with rico this week)
[15:13] <seb128> nice
[15:13] <Laney> poor you
[15:13] <didrocks> nice timing as well with the weather being a little bit more enjoyable :)
[15:14] <oSoMoN> seb128, well the update should be ready for publication tonight, but it will have received little testing
[15:14] <seb128> oSoMoN, I can block it in artful-proposed next week if you want to land it but feel a bit nervous about it
[15:15] <seb128> at least the time we get some testing
[15:15] <oSoMoN> seb128, if you don't mind waiting a week, I can give it some serious testing when I'm back
[15:16] <seb128> oSoMoN, waiting is fine, do you prefer have it in proposed or just not uploaded until the week after?
[15:17] <oSoMoN> seb128, if the build completes shortly, I can stress-test it a bit before my EOD and if it looks good let's push it to -proposed (and keep it there), otherwise let's just wait
[15:18] <seb128> oSoMoN, k, it's fine either way so don't overstress yourself
[15:20] <ricotz> seb128, oSoMoN, having it sitting in -proposed would be preferred imo
[15:21] <seb128> ricotz, why?
[15:21] <ricotz> I guess this way it will get into autopkgtest too
[15:21] <seb128> right
[15:22] <seb128> but it might block things if it turns out to not be ready and has to be blocked there for a while
[15:22] <oSoMoN> it would also give people using -proposed a chance to try it out and report issues
[15:22] <seb128> that's the + side indeed
[15:22] <seb128> I don't expect transitions now so it's not likely to block much
[15:23] <ricotz> please do so then
[15:23] <ricotz> it seems there is more care about a dev-release than the current stable one ;)
[15:23] <ricotz> (regarding libreoffice)
[15:25] <oSoMoN> ricotz, regarding the zesty SRU I simply haven't had time to do it, it's not that I don't care
[15:25] <seb128> jbicha, you added a gtksourceview4 to versions but that package doesn't exist (yet)?
[15:27] <ricotz> oSoMoN, I understand that, but the zesty version is 5 months old, and minor 5 releases behind
[15:28] <seb128> ricotz, there is no really point discussing a situation which is known and where everybody agrees it's suboptimal and understand the reason why it is (understaffing)
[15:28] <seb128> no real*
[15:29] <ogra_> also ... use snaps, not backported debs ;)
[15:30] <jbicha> seb128: someone needs to make a package for it eventually
[15:30] <ricotz> seb128, I would agree on that if it would be some less important package, I was hoping this would change, just reminding about it
[15:31] <jbicha> a year ago, gtk4 was said to be really soon…
[15:32] <seb128> jbicha, right, but until then it lists as an empty/boggus line on the page :p
[15:32] <ricotz> jbicha, gtksourceview4 wasn't meant to work with gtk4, does it?
[15:32] <seb128> ricotz, k, fair enough, still it's only Olivier doing libreoffice & chromium, snap&debs, current&stable series
[15:33] <jbicha> ricotz: I believe that's the point of gtksourceview4 but I haven't looked into it
[15:33] <ricotz> jbicha, there was some confusing about the naming, and I believe there was meant to be another bump/name change for that
[15:35] <ricotz> seb128, I know that
[15:35] <jbicha> oh, gtksourceview 3.99.5 in git master still lists gtk 3.20 in its configure.ac
[15:36] <ricotz> jbicha, https://wiki.gnome.org/Projects/GtkSourceView/TransitionToGtkSourceView4
[15:44] <seb128> do others also have right right on a gedit titlebar that open/activate the context menu direct
[15:44] <seb128> which leads to minimize
[15:44] <seb128> ?
[15:45] <didrocks> yes
[15:45] <didrocks> I didn't remember if that was the behavior prior to latest G-S update
[15:45] <didrocks> that's why I didn't report it
[15:46] <didrocks> you have to keep right click pressed
[15:46] <didrocks> to select another item
[15:53] <seb128> didrocks, it works on nautilus though
[15:54] <didrocks> ohhhhhhhh, correct
[15:54] <seb128> "fun", gedit page up/down doesn't work/scroll if the right side of the window is out of the screen
[15:54] <didrocks> looks like I only had the case yesterday with gedit
[15:54] <didrocks> ah
[15:54] <didrocks> didn't try that
[15:54] <seb128> not going to get borred any time soon!
[15:54] <didrocks> job4life :)
[15:55] <seb128> indeed!
[16:03] <jbicha> gedit also doesn't work well if you have too many docs open, I think it needs a tab switcher like epiphany has
[16:15] <seb128> jbicha, didrocks, I looked a bit to updating the dock settings patch but it's more than a one hour job, so that's going to be for next week
[16:16] <didrocks> seb128: yeah, as seeing that we need to do the display matching, unsure how "easy" it's going to be its own panel (which it should IMHO)
[16:16] <didrocks> seb128: so, still undecided on it, but clearly not trivial
[16:17] <didrocks> I rebased the theme branch on jbicha's work (but using git-remote-bzr to do the easy rebase)
[16:17] <didrocks> I must say it worked very smoothly
[16:19] <jbicha> didrocks: are you planning a gnome-shell upload soon?
[16:20] <didrocks> jbicha: Monday, with the new theme
[16:21] <jbicha> didrocks: could you try adding this snippet to d/rules ?
[16:21] <jbicha> https://anonscm.debian.org/viewvc/pkg-gnome/desktop/experimental/gnome-shell/debian/rules?r1=53319&r2=53320
[16:21] <jbicha> the translations part, the test part isn't needed
[16:21] <didrocks> jbicha: are we sure the tests works?
[16:22] <didrocks> yeah, I didn't want to block after the announce on this
[16:22] <jbicha> tests are enabled in Ubuntu already so you can ignore that
[16:22] <didrocks> ok
[16:22] <didrocks> so ninja is a build-dep already?
[16:22] <jbicha> yes it's what meson uses to do the actual build
[16:22] <jbicha> and gnome-shell is meson only now
[16:22] <didrocks> good! will add this thus!
[16:22] <seb128> thanks didrocks
[16:23] <didrocks> jbicha: on Tweaks, I'll do the change first on -prefs (probably end of next week), but more changes are needed in tweaks as well
[16:23] <jbicha> build tests aren't working for me in clutter, mutter, and gnome-shell in Debian but I don't know why
[16:23] <seb128> k, I'm going to do some wayland debugging for https://bugs.freedesktop.org/show_bug.cgi?id=102475 so closing my session
[16:23] <seb128> then I probably call it a week
[16:23] <seb128> have a nice w.e desktopers
[16:24] <didrocks> thanks, you too seb128!
[16:24] <kenvandine> seb128, you too!
[16:24] <jbicha> btw, GNOME is in code freeze next week
[16:25] <seb128> good, less new bugs added!
[16:25] <jbicha> finally :)
[16:26] <seb128> :-)
[16:26] <didrocks> jbicha: yeah, I'll add that as a distro-patch but still report it to G-S upstream, I don't think they worry much seeing for how long they have this bug with classic :p
[16:26] <seb128> k, on that note session closing
[16:27] <jbicha> gnome-shell will probably be late on code freeze, it's funny because they are the part that most needs freezes
[16:27] <didrocks> due to the last bugs? I didn't see that discussed
[16:27] <didrocks> or the top panel changes ?
[16:28] <jbicha> gnome-shell is usually late for release deadlines
[16:28] <jbicha> like deadline is Monday so they release on Thursday 3 or 4 days later
[17:02] <Laney> tseliot: your patch seems to work - I'll give you a code review on monday morning
[17:02] <Laney> fossfreedom: you too
[17:03] <Laney> tseliot: looks like something has locked up when my screen dimmed though :(
[17:05] <Laney> https://paste.ubuntu.com/25445993/
[17:05] <Laney> anyways
[17:05] <Laney> goodnight!
[17:31] <tseliot> Laney: thanks! Yes, it looks like an nvidia/wayland bug, nothing my code could ever cause. Have a nice weekend!
[20:11] <oSoMoN> kenvandine, re-built the libreoffice snap with the gnome-3-24 PPA, and am still getting the same crash at startup
[20:14] <kenvandine> oSoMoN, ok
[20:14] <kenvandine> that rules that out
[20:18] <oSoMoN> I’ll resume investigation on that issue on the 11th when I’m back from holidays
[20:23] <kenvandine> oSoMoN, have a good vacation!
[20:27] <oSoMoN> thanks!