[06:06] <didrocks> good morning
[06:11] <duflu> Hi didrocks
[06:17] <didrocks> morning duflu
[07:36] <seb128> good morning desktopers
[07:36] <seb128> hey didrocks duflu
[07:36] <duflu> Hi seb128
[07:39] <didrocks> hey seb128
[07:40] <seb128> gnome-shell is such a piece of crap :(
[07:40]  * seb128 misses unity
[07:40] <seb128> bug #1799052 or bug #1799293
[07:41] <seb128> andyrock, did you end up debugging with Dimitri (was it?) why gnome-shell was failing to disable dash to dock when locking the screen?
[07:43] <didrocks> surprising that even the lock screen doesn't have the login prompt sometimes…
[07:44] <duflu> seb128, I don't miss fixing Unity. Gnome Shell is already more reliable. Only a little slower
[07:45] <duflu> I used to spend my days finding all the Compiz but reports were actually Unity bugs
[07:45] <duflu> also bug reports
[07:45] <seb128> I disagree with that statement of being more reliable
[07:45] <seb128> also there is a lot of things less nice user experience wise or not behaving
[07:46] <duflu> At least it doesn't take me till 4pm every day to get through the bug mail. It did with Compiz/Unity
[07:46] <seb128> like the overview doesn't even display names without cutting them and making them impossible to read (I know you have a fix for that one, but it's still pending review/upstream deciding to do something)
[07:47] <duflu> seb128, yeah my fix for that was complete, but rejected waiting for someone who started earlier to finish their version instead
[07:47] <duflu> And they stopped responding
[07:47] <duflu> Although that might be old news...
[07:48] <seb128> we should have another try at getting it merged
[07:48] <seb128> but yeah, unity was doing a lot more
[07:48] <seb128> dealing with touch screens, gestures, multiscreen (especially in lightdm), keyboard typeahead in the expose, etc etc etc
[07:49] <jibel> seb128, bug 1799293 is what I showed you last week on my laptop. It doesn't have to have autologin enabled
[07:49] <seb128> anyway, ranting is not useful, moving back to triaging bugs
[07:49] <duflu> Yeah 5 months ago, my fix was rejected, but also the other developer who now owns the fix stopped responding
[07:49] <seb128> hey jibel
[07:49] <jibel> hi everyone
[07:49] <jibel> :)
[07:49] <duflu> Hi jibel
[07:50] <didrocks> good morning jibel
[07:50] <seb128> jibel, can you still reproduce? could you add your journal log after getting the issue? do you have any extension/did you try without those?
[07:50] <jibel> let me try
[07:52] <seb128> didrocks, you probably know, but the "preview of open windows" feature of dash to dock, is that coming direclty from shell or tweaked/having a local variant?
[07:52] <seb128> didrocks, asked differently, is bug #1768543 a launcher bug or a shell one?
[07:52] <duflu> seb128, updated https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/58
[07:52] <gitbot> GNOME issue (Merge request) 58 in gnome-shell "WIP: Fix long application names being truncated" [1. Feature, 2. Needs Triage, 5. Icon Grid, Opened]
[07:52] <seb128> duflu, thx
[07:53] <jibel> seb128, I had to reboot, the machine was out of battery and it is not happening anymore
[07:53] <seb128> jibel, :(
[07:53] <seb128> jibel, you have persistant journal and can get the log from wednesday?
[07:54] <jibel> yes, it's what I'm lookgin for
[07:54] <seb128> or was it thursday?
[07:54] <seb128> thx
[07:54] <jibel> all of last week
[07:54] <didrocks> seb128: I'm pretty sure it's a feature from dash to dock, but let me read the bug
[07:55] <jibel> hmm, journalctl --list-boots returns "Failed to determine boots: No data available"
[07:55] <seb128> didrocks, thx
[07:55] <jibel> but the journal is there, weird
[07:56] <didrocks> seb128: if only we had those kinds of bugs to fix… :p
[07:56] <didrocks> let me just quickly look if the issue is in Yaru
[07:56] <seb128> didrocks, haha, true :p
[07:58] <didrocks> some positions in the Yaru css for the dock, but nothing for the close button
[07:58] <didrocks> just kicking a VM quickly with vanilla theme to check
[07:58] <duflu> seb128, good news, there are at least 3 fixes proposed and the chosen one has only been idle 1 month :)
[07:59] <seb128> duflu, for the overview/text cutting one?
[07:59] <duflu> Yeah
[07:59] <didrocks> seb128: reproduced with vanilla theme, confirming it's d2d specific
[07:59] <didrocks> maybe there is a css property to position it
[07:59] <didrocks> can check quickly while I'm at it
[07:59] <seb128> didrocks, k, thx, can you comment on the bug saying so? and sorry for wasting your time on a minor issue, I just wanted it triaged right :)
[07:59] <seb128> as you wish but don't feel like you have to bother
[08:00] <didrocks> seb128: no worry, while I'm at it, let's check if there is a 10 minutes fix
[08:05] <jibel> what's the command line way to know which extensions are enabled?
[08:05] <jibel> gnome extensions
[08:06] <Laney> oops
[08:06] <Laney> hi!
[08:07] <jibel> seb128, I attached the journal from last week.
[08:09] <didrocks> jibel: gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell --method org.gnome.Shell.Extensions.ListExtensions
[08:09] <didrocks> check all extensions that have state: 1.0
[08:10] <jibel> thx
[08:11] <seb128> jibel, thx
[08:12] <seb128> hey Laney!
[08:18] <jibel> seb128, there are stack traces that start on the 16th
[08:21] <oSoMoN> good morning desktoppers
[08:23] <Nafallo> morning
[08:23] <Nafallo> or... good day.
[08:24] <seb128> jibel, those logs are verbose, different errors, unsure which one it could be, probably one andyrock or Trevinho would have more clue about
[08:24] <seb128> "Object Shell.GenericContainer (0x55dbd4c15e10), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[08:24] <seb128> "
[08:24] <oSoMoN> good day Nafallo
[08:24] <Laney> hey seb128 jibel oSoMoN Nafallo
[08:24] <seb128> lut oSoMoN
[08:24] <seb128> hey Nafallo
[08:25] <Nafallo> how's thing in the new D? :-)
[08:25] <Nafallo> things
[08:25] <Laney> we are D-less
[08:26] <Nafallo> :-O
[08:27] <oSoMoN> hey Laney, seb128, jibel
[08:59] <duflu> Oops. Hi Laney, oSoMoN, Nafallo
[09:04] <oSoMoN> hey duflu, how goes?
[09:06] <duflu> oSoMoN, super busy with most of the week so far on bug mail and code review discussions. But progressing. You?
[09:08] <seb128> duflu, you should perhaps consider doing a but less bug triaging, or skip over non-interessing bugs. We need to be able to pick up issues out of the noise
[09:08] <seb128> ups, enter too early
[09:08] <seb128> but no point trying to fight the noise/triage every report
[09:09] <duflu> seb128, I can keep up, and at least this load only happens twice a year now
[09:09] <duflu> Looking at thousands of bug reports is how you find the patterns
[09:09] <seb128> you can keep up but it has an high cost
[09:10] <seb128> it costs you time that could be spent on fixing issues, or tackling other topics
[09:11] <duflu> I don't think it's a high cost. This spike only lasts a week or so after the release. It's not 365 days a year like compiz/unity used to be
[09:17] <duflu> seb128, btw Shell.GenericContainer no longer exists in gnome-shell 3.30.2+
[09:17] <seb128> context?
[09:17] <duflu> (scrolling up)
[09:18] <duflu> seb128, in the conversation with jibel
[09:18] <seb128> ah ok
[09:19] <seb128> so maybe that bug is fixed
[09:19] <seb128> we need to update to .2
[09:19] <duflu> It looks like they're going to release that big change in 3.30.2, which is weird. I would expect them to branch first and defer it to 3.32
[09:23] <duflu> seb128, this week is actually good news. I started with 3 Nvidia+Xorg bugs to investigate and so far only one of them looks valid
[09:24] <oSoMoN> duflu, I'm good, juggling between firefox, chromium, libreoffice and snapcraft
[10:02] <jbicha> duflu: I think they are deferring to 3.32. Arch Linux had enough issues with the git snapshot that they used an epoch to revert to gnome-shell 3.30.1
[10:03] <duflu> jbicha, yeah 3.30.2 seemed to break zoom and alt-tab, maybe other things
[10:04] <duflu> I thought it was a poor choice to re-architect things in a maintenance point release before the regressions were found
[10:04] <duflu> So the regressions were unsurprising
[10:12] <duflu> Is that what epochs are usually for?
[10:12] <duflu> I always wondereed
[10:17] <jbicha> in Debian/Ubuntu these days, we'd probably use something like 3.30.1+30+really3.30.1-1 to avoid the epoch bump
[10:20] <jbicha> epochs are an extra detail to remember when setting dependencies. You'd need to depend/break/whatever on gnome-shell >= 1:3.30 instead of the simpler >= 3.30
[10:20] <Laney> they break existing relations too
[10:21] <Laney> https://www.debian.org/doc/debian-policy/ch-controlfields.html#epochs-should-be-used-sparingly
[10:28] <andyrock> jibel: which logs?
[10:36] <seb128> hey andyrock
[10:36] <andyrock> hey seb128
[10:37] <seb128> how are you today?
[10:38] <jibel> andyrock, in the journal attached to the bug report
[10:38] <andyrock> tbh I didn't sleep well :/ But nothing that a good coffee and a hot shower can't fix :D
[10:38] <andyrock> jibel: which bug? :D
[10:39] <jibel> I suppose bug 1799293
[10:39]  * andyrock should look in backlog
[10:39] <andyrock> let me take a look
[10:39] <jibel> andyrock, I had this problem last week but autologin was not enabled
[10:39] <jibel> andyrock, now I had to reboot and cannot reproduce it anymore
[10:40] <andyrock> mmm it can be the same issue Adam had during the release sprint
[10:41] <jibel> andyrock, what happens is 1rst press on super+l it locks the input but gnome-shell is still visible, second press it shows the lock scren
[10:42] <andyrock> before the second super+l the desktop is visible but you can't interact with it, isn't it?
[10:43] <jibel> andyrock, exactly
[10:49] <andyrock> jibel: so those warnings appear because something is tried to call a javascript callback (most likely tied to a "destroy" signal) during garbage collection. If gjs detects this it will avoid executing the javascript code and not crash the shell. Buuuut this can lead to an inconsistent state that could be the cause of the issue
[10:49] <andyrock> Trevinho: ^^^ what do you think?
[10:51] <andyrock> jibel: btw I need to take a better looks to logs. Do you remember more or less in which day the problem was happening?
[10:51] <jibel> andyrock, from tuesday onward until the system has been rebooted
[10:52] <andyrock> jibel: nice, I'll take a look later
[10:53] <jibel> andyrock, that's the part of the journal I attached to the report but it's rather difficult to read
[11:04] <jbicha> Laney: the icon theme should be Yaru in https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gtk+3.0/tree/debian/settings.ini#n3 right?
[11:05] <Laney> jbicha: guess so, whatever ubuntu-settings says
[11:19] <Trevinho> andyrock: yeah, I was already on a fix for that
[11:20] <andyrock> Trevinho: nice :)
[11:20] <andyrock> next time remember to update the bug status :P
[11:20] <Trevinho> we also have a crash related to that I think
[11:20] <Trevinho> it's another bug
[11:20] <Trevinho> but apparently with similar cause
[11:23] <Trevinho> mh, no actually no... it's another js trace
[11:32] <Trevinho> seb128: can you make a new team updates thread? Or can I?
[12:03] <andyrock> Trevinho: bug number?
[12:08] <Trevinho> andyrock: can't find it now xD  it was from e.u.c crashing when calling get_theme_node
[12:08] <Trevinho> but there were similar shell container messages
[12:09] <Trevinho> we should probably tag those child better though
[12:10] <andyrock> Trevinho: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796606 ?
[12:10] <andyrock> yeah would be nice to have the a tag with the javascript line where they were created
[12:45] <seb128> Trevinho, you mean on the hub? I can't, I'm not admin, but willcooke should be online in the afternoon you can ask him
[13:29] <xnox> seb128, i provided a long traceback, and was told "yeah that's enough" we didn't chat more about it; and restarting gnome-shell "fixed it" for me.
[13:29]  * xnox not sure if you got the reply for this =))) and not reading the scrollback.
[13:30] <xnox> seb128, re:deb-vs-snap /snap/bin is always *appended* to path, and thus snaps are always lower priority than debs. At least when called without an absolute name.
[13:30] <xnox> seb128, does gnome-system-monitor broken only for me, or everyone?
[13:31] <seb128> xnox, I didn't, thanks
[13:31] <seb128> xnox, just for you, did you provide the info I asked for on the bug?
[13:31] <xnox> seb128, let me check the bug =)
[13:38] <xnox> seb128, responded on the bug 1) deb now works 2) there are denies 3) pastebined denies & interfaces
[13:40] <willcooke> morning
[13:41] <didrocks> hey willcooke
[13:41] <andyrock> Trevinho: mind taking a look https://github.com/ubuntu/gnome-shell-extension-appindicator/pull/151
[13:41] <gitbot> ubuntu issue (Pull request) 151 in gnome-shell-extension-appindicator "interfaces: Explicitly convert raw data to strings" [Open]
[13:43] <seb128> hey willcooke
[13:43] <seb128> xnox, weird, I don't know :/
[13:43] <xnox> seb128, i guess is hould try to off-and-on-again by like reinstalling the snap?
[13:43] <seb128> jdstrand, kenvandine, do you have an idea about bug #1798996
[13:44] <seb128> the journal has
[13:44] <seb128> "audit: type=1400 audit(1540388224.625:95): apparmor="DENIED" operation="capable" profile="/usr/lib/snapd/snap-confine" pid=5645 comm="snap-confine" capability=19  capname="sys_ptrace""
[13:44] <seb128> xnox, I would try to get input from the snap people first, reinstall is not a solution it's a workaround
[13:45] <kenvandine> seb128: not sure, lets see what jdstrand says
[13:49] <Trevinho>  andyrock: ok
[13:49] <xnox> kenvandine, jdstrand - given it's me, i wonder if i have werid things mounted / setup on my system, which gnome-system-monitor tries to read, and fails. E.g. nvme hard drives, uefi partitions, lvm volumes, encrypted things
[14:03] <andyrock> Trevinho: also would be nice to sync the ubuntu branch with the master one
[14:03] <andyrock> Trevinho: if you prefer I can take care of it
[14:03] <andyrock> your call
[14:15] <seb128> andyrock, is https://bugs.launchpad.net/oem-priority/+bug/1730211 different from the one you were looking at/talking to garnacho about before 3.30?
[14:26] <Trevinho> andyrock: yes, I also have other fixes that I wanted to land....
[14:26] <andyrock> seb128: that should be already fixed
[14:26] <andyrock> at least in cosmic
[14:27] <andyrock> seb128: so in Cosmic there is already a fix that allows you to type in the osk whatever key that can be entered with your current input layout
[14:29] <andyrock> seb128: my fix is to include also those letters that are showed in the osk but CANNOT be entered with your keyboard layout
[14:29] <andyrock> so capital letters should work because (at least in Cosmic)
[14:29] <andyrock> we need to cherry-pick that fix in Bionic
[14:30] <andyrock> seb128: do you want me to take a look?
[14:31] <seb128> andyrock, yes please, oem team wants to see it fixed
[14:31] <andyrock> seb128: I also pinged garnacho to take another look to my fix
[14:31] <andyrock> but no feedback 💔
[14:33] <andyrock> Trevinho: what's the status of gnome-shell in Bionic? are you planning to do an SRU already?
[14:36] <seb128> jdstrand, hey again, I reopened bug #1798091 since it still seems to be there with your update, your "owner /tmp/{,.}gnome_desktop_thumbnail.* w," rule doesn't seem to catch "/tmp/gnome-desktop-thumbnailer.png" which is what is used here (_ vs -, but also the .* at the end doesn't seem to catch "thumbnail*er.png*"
[14:40] <seb128> xnox, you get a "snap version" output info requested on that bug :)
[14:42] <xnox> seb128, done
[14:42] <andyrock> Trevinho: actually mutter SRU
[14:52] <seb128> bah, found a way to deadlock the shell :/
[14:53] <seb128> start in timed login (or auto login), you get a modal prompt at login for your keyring password
[14:53] <seb128> ignore that and hit the top right indicator and pick to shutdown
[14:54] <seb128> -> the shutdown button changes in a pause one and then the shell is stucked, even after dismissing the keyring dialog
[14:56] <Laney> /o\
[15:05] <seb128> jdstrand, I know you are probably busy this week/in SLC, but is bug #1794064 something you plan to own? (since you have a suggested way which could work)
[15:14] <ricotz> hey desktopers
[15:14] <seb128> hey ricotz
[15:14] <ricotz> Laney, hi, is 2.56.3-0ubuntu0.18.04.1 causing trouble in proposed?
[15:15] <ricotz> seems like a candidate for failing ppa build not being able to install libglib2.0-dev libgirepository1.0-dev
[15:15] <ricotz> seb128, hey
[15:16] <ricotz> Laney, https://launchpadlibrarian.net/394658919/buildlog_ubuntu-bionic-amd64.vala-git_0.43.0~git20181024.6c68de5e-0ubuntu1~18.04~valateam0_BUILDING.txt.gz
[15:22] <Laney> not that I know of, that can happen with skew on non-amd64 arches if the package fails to build or something
[15:22] <Laney> try in a chroot?
[15:22] <ricotz> updating my pbuilder chroots currently
[15:23] <ricotz> still pretty persistent https://launchpad.net/~vala-team/+archive/ubuntu/daily/+sourcepub/9501328/+listing-archive-extra
[15:27] <ricotz> ok, I blame launchpad ;)
[15:38] <seb128> kenvandine, could you look at bug #1778361 or get someone assigned to it? I don't think it's important enough to be rls tagged but still we should fix it, those snaps that are default should be at parity with their deb equivalent otherwise it's hurting our/the snap reputation
[15:40] <seb128> Trevinho, did you see my msg earlier?
[15:40] <seb128> about bug #1745888
[15:54] <kenvandine> seb128: looking
[16:05] <seb128> kenvandine, thx
[16:06] <kenvandine> seb128: it's interesting, if you tick "All Processes" it briefly shows other user processes
[16:06] <kenvandine> then the UI updates removing other users
[16:06] <kenvandine> feels like a bug, not a confinement issue
[16:06] <seb128> the journal has denial warnings though
[16:06] <kenvandine> yeah, ptrace right?
[16:07] <kenvandine> jdstrand suggested that might have been unrelated
[16:08] <seb128> kenvandine, "audit: type=1400 audit(1540397297.169:54174): apparmor="DENIED" operation="open" profile="snap.gnome-system-monitor.gnome-system-monitor" name="/proc/2280/wchan" pid=21148 comm="gnome-system-mo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0"
[16:09] <seb128> but yeah, you are right, the UI seems to list the root ones for a second and then they go
[16:09] <kenvandine> so not blocked by apparmor
[16:09] <seb128> also after restarting the app I've all processes listed
[16:09] <seb128> the apparmor denial warnings are still noise that should be better off though
[16:11] <Trevinho> andyrock: as for sru, I wanted to wait an upstream point release. But seems not possible
[16:13] <andyrock> Trevinho: kk. I created https://trello.com/c/2hg9HKfq/111-backport-unable-to-type-capital-letters-using-onscreen-keyboard-to-bionic with the two commits that need to backported in cosmic
[16:13] <seb128> kenvandine, there are also denials about reading /var/lib/snapd/desktop/applications/ .desktop entries, which is probably done to match the active apps to their icons/name and such
[16:13] <andyrock> *bionic sorry
[16:13] <kenvandine> seb128: yeah
[16:13] <Trevinho> andyrock: please link to the sru card.. There's a check list there
[16:14] <andyrock> Trevinho: we could also consider to include my fixes (not yet  included upstream because getting a review seems impossible)
[16:20] <andyrock> seb128: have you got a bug regarding the "dead-lock" thing?
[16:20] <andyrock> seb128: I can easily reproduce this
[16:20] <andyrock> so I can take a look
[16:25] <kenvandine> jdstrand: anything i can do to allow access to '@{PROC}/@{pid}/cgroup' and '@{PROC}/@{pid}/wchan' ?
[16:26] <kenvandine> not sure how important that is, but it generates a ton of noise
[16:30] <Laney> ricotz: if you turn off proposed it works
[16:30] <Laney> not sure why
[16:36] <seb128> andyrock, I don't, unsure if that's an important one though, it's not really a common scenario to see those dialogs and not dismiss them
[16:36] <ricotz> Laney, yeah, will do that, doesn't seem to be temporary problem
[16:37] <andyrock> seb128: I've been experiencing similar problems in the past
[16:37] <seb128> andyrock, I can open a bug if you want?
[16:37] <andyrock> seb128: I can do it np
[16:37] <seb128> thx
[16:41] <kenvandine> seb128: looks like a UI issue, regardless of which radio box you tick, it quickly reverts until you restart the APP
[16:41] <kenvandine> app... sorry for yelling :)
[16:41] <seb128> lol
[16:41] <seb128> yeah
[16:41] <Laney> 📣 *APP*
[16:41] <seb128> still worth debugging since it doesn't happen with the deb for some reason
[16:41] <seb128> could be racy behaviour
[16:42] <seb128> and the denial warnings would still be nice to fix, at least the .desktop ones could result in incorrect icon matching for active snaps
[16:42] <seb128> kenvandine, thx for responding/have a look! I hope SLC is still going well
[16:43] <kenvandine> yeah
[16:43] <kenvandine> it is
[16:43] <kenvandine> just really busy :)
[16:43] <kenvandine> but it is nice to have jdstrand in the same room :-D
[16:44] <kenvandine> seb128: of interest, in the snap when i tick any of those radio boxes i see this
[16:44] <kenvandine> Allocating size to gnome-system-monitor 0x26542c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
[16:44] <oSoMoN> kenvandine, got any word from mvo about xdg-open in core18 ?
[16:44] <kenvandine> not yet
[16:44] <kenvandine> haven't been able to track down mvo today
[16:45] <seb128> kenvandine, I see those warnings as well
[16:45] <seb128> so yeah, probably an upstream code bug
[16:45] <kenvandine> only in the snap though
[16:45] <kenvandine> i'm wondering if some signal isn't sent or caught
[16:45] <seb128> or maybe it tries to fetch some property or something that fails for some reason
[16:45] <kenvandine> the radio box does update though visually
[16:46] <kenvandine> maybe not getting gsettings signals?
[16:46] <seb128> could be, it's weird though, the view does refresh before resetting
[16:46] <seb128> it needs code debugging...
[16:46] <Laney> it is communicated to the UI by a gsettings change signal
[16:46] <Laney> so if that gets set and reset that would explain it
[16:47] <Laney> handy function to put a g_debug in there ;-)
[16:47] <kenvandine> yeah
[16:47] <kenvandine> just painful in a snap :)
[16:47] <kenvandine> need to rebuild the snap and iterate
[16:47] <Laney> or a gdb
[16:47] <Laney> (cb_show_whose_processes_changed)
[16:47]  * kenvandine guesses Laney has the code open :)
[16:49] <Laney> I actually made wallpaper out of it
[16:49] <Laney> it's in my bathroom
[16:50] <Laney> just wanted to see how it was communicated about
[16:51] <Laney> fun that there's a C++ part of g-s-m :-o
[16:52] <kenvandine> :)
[16:53]  * Laney finishes adventures in rebaseland for today
[17:02] <oSoMoN> calling it a day, have a good evening everyone!
[17:14] <Trevinho> wow, I didn't know lenovo was already in partnership with fwupd... Hugsie told me that he was about to sign some months ago, but I didn't notice this was reality :) https://usercontent.irccloud-cdn.com/file/lm1s6e98/image.png
[17:14] <kenvandine> Trevinho: yay
[17:16] <xnox> whoop whoop
[17:19] <Trevinho> apparently it's there for a few months (according to reddit) and https://fwupd.org/lvfs/devicelist but I never looked at that gnome-software tab xD
[17:33] <seb128> Trevinho, you should have got notifications about it without having to go looking :-/
[17:33] <Trevinho> seb128: I got it in fact
[17:34] <Trevinho> seb128: but... I'm overwhelm of them, so not always I look at them
[17:35] <Trevinho> also looks like I forgot for months to have the `/boot/efi/EFI` path mounted, so, it wasn't working :D
[17:35] <Trevinho> fstab for the glory
[17:42] <Trevinho> praying... https://www.irccloud.com/pastebin/Hg6nFN1b/
[17:45] <willcooke> seb128, I tried this: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1789925
[17:46] <willcooke> but I'm still getting the old URL
[17:46] <willcooke> maybe I need to restart shell
[17:46] <willcooke> lemme try
[17:47] <willcooke> nope
[17:48] <willcooke> hrm, the package version says: 3.28.0-2ubuntu6.16.04.3
[19:53] <jbicha> seb128: there was a comment at Debian bug 911161 complaining about the evince apparmor change but I don't know if he is using the proposed patch (didn't land in Debian) or reload his profile or what
[20:51] <seb128> jbicha, that comment is basically the same I wrote on launchpad
[20:52] <seb128> jdstrand is at a sprint this week, so unsure he has time to look at that, I'm might try to just SRU my suggested change tomorrow if he doesn't comment in between though
[20:52] <seb128> but for now calling it a day, see you tomorrow desktopers!