[00:33] <marcustomlinson> hey robert_ancell, could I ask you to please trigger these 3 autopkgtests for me:
[00:33] <marcustomlinson> https://autopkgtest.ubuntu.com/request.cgi?release=xenial&arch=s390x&package=libreoffice&ppa=marcustomlinson/libreoffice&trigger=libreoffice/1:5.1.6~rc2-0ubuntu1~xenial9~ppa1
[00:34] <marcustomlinson> https://autopkgtest.ubuntu.com/request.cgi?release=bionic&arch=amd64&package=libreoffice&ppa=marcustomlinson/libreoffice&trigger=libreoffice/1:6.0.7-0ubuntu0.18.04.9~ppa1
[00:34] <marcustomlinson> https://autopkgtest.ubuntu.com/request.cgi?release=disco&arch=amd64&package=libreoffice&ppa=marcustomlinson/libreoffice&trigger=libreoffice/1:6.2.5-0ubuntu0.19.04.1
[00:39] <robert_ancell> marcustomlinson, triggered
[00:39] <marcustomlinson> robert_ancell: thanks :)
[05:54] <didrocks> good morning
[06:05] <duflu> Morning didrocks
[06:13] <didrocks> hey duflu
[07:07] <seb128> gooood morning desktopers
[07:08] <duflu> Hi seb128. How goes?
[07:09] <seb128> duflu, good! you?
[07:10] <duflu> Alright I guess. Got another Nvidia fix landed overnight
[07:10] <duflu> And one more to go to make mutter 3.34 completely killer
[07:12] <seb128> nice!
[07:12] <seb128> duflu, what kernel do you use?
[07:12] <duflu> 5.2 now
[07:12] <duflu> eoan
[07:12] <Wimpress> o/
[07:12] <duflu> Hi Wimpress
[07:13] <Wimpress> Oooh, duflu what did you improve?
[07:13] <duflu> seb128, if you don't count my slow NIC then it boots in 3 sec
[07:13] <duflu> Wimpress, not me. Other people
[07:13] <seb128> duflu, ok, I would have expected fastboot to be on by default in 5.2 :-/
[07:14] <duflu> Looks suspicious. My monitor is showing the DisplayPort icon as a flickers during boot, like there's still a mode change
[07:14] <duflu> Actually I'll need to tweak my BIOS because that's the slow part of booting now
[07:15] <didrocks> hey seb128
[07:16] <seb128> lut didrocks, en forme ?
[07:16] <duflu> Oh Wimpress if you mean mutter then the answer is performance
[07:16] <seb128> hey Wimpress
[07:16] <didrocks> seb128: ça va, deep into test writing, et toi ?
[07:17] <seb128> ça va but with a strong cold, blocked nose a bit of fever yesterday evening :-/
[07:17] <didrocks> argh
[07:18] <seb128> duflu, right, 5.2 has that change, https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=3d6535cb
[07:18] <seb128> unsure why it's not working for you
[07:18] <duflu> Maybe I am blacklisted
[07:19] <duflu> Or maybe grub is checking for the parameter and changing its own behaviour. Though unlikely
[07:20] <duflu> seb128, there's a kernel debug message there. If I remember later I'll check for that
[07:20] <seb128> duflu, k, thx
[07:21] <seb128> it's going to look good only on a few machines at the end
[07:21] <seb128> so I wonder if we should keep the old theme default and let e.g oem opt in for the flickerfree ones on machine they know are working good with it
[07:22] <duflu> Yeah maybe. It's not something that attracts complaints right now so the only way is down
[07:22] <duflu> that I know of
[07:24] <Wimpress> duflu Are you testing flicker free boot?
[07:24] <duflu> Wimpress, yes
[07:24] <Wimpress> I saw seb128 uploaded a new Plymouth 👍
[07:25] <seb128> :)
[07:25] <Wimpress> Does it require any kernel options to work?
[07:26] <duflu> Wimpress, for some, at least for me; http://discourse.ubuntu.com/t/testing-flickerfree-boot/11854
[07:27] <seb128> Wimpress, it shouldn't on > skylake in theory but at least for Daniel it did
[07:27] <seb128> duflu, at what point exactly is the remaining flicker for you?
[07:28] <duflu> seb128, in the middle of the BIOS logo black screen. My peripherals seem to light up before that though so I think during kernel boot
[07:28] <duflu> Maybe grub?
[07:28] <seb128> before grub?
[07:28] <seb128> it's not impossible that we miss a grub patch still
[07:29] <seb128> is the grub menu displayed for you (like you multiboot)?
[07:29] <duflu> I can't tell right now but my peripherals seem to suggest the kernel is booting already before the flicker
[07:29] <duflu> No menu
[07:30] <seb128> so it would suggest that it's post grub if the kernel is already loaded
[07:30] <duflu> Maybe this (which is normal) [    2.705782] fb0: switching to inteldrmfb from EFI VGA
[07:33] <duflu> I could test that by forcing it to stay on efifb I guess
[07:35] <seb128> let me know if you do
[07:44] <duflu> seb128, yeah it's the handover to i915 that's flickering. I can only avoid it by disabling KMS and staying in efifb
[07:45] <seb128> you get a fully flicker free boot if you do that?
[07:45] <seb128> do we enable KMS by default?
[07:45] <willcooke> morning all
[07:45] <seb128> hey willcooke
[07:46] <duflu> seb128, we have to -- all the open source graphics drivers require KMS
[07:46] <duflu> Morning willcooke
[07:46] <willcooke> afternoon duflu, morning seb128
[07:46] <didrocks> hey willcooke
[07:46] <willcooke> hi didrocks
[07:47] <willcooke> didrocks, I saw something on reddit about zfs last night, did you see that already?  I didnt understand any of it though
[07:47] <duflu> seb128, yes flicker free, if I prevent the kernel from switching fb drivers
[07:47] <duflu> But that also prevents hardware acceleration
[07:48] <seb128> I wonder if that's specific to your config in some way
[07:49] <seb128> or how fedora avoids that issue
[07:49] <duflu> Maybe it's only visible on desktops with external monitors
[07:49] <duflu> that take a second to switch
[07:49] <duflu> I'll try laptops later
[07:51] <duflu> Wait, didn't it used to be "intelfb"?
[07:51] <duflu> Was it renamed or rewritten?
[07:51] <seb128> no idea...
[07:52] <duflu> Rewritten
[07:52] <duflu> The old intelfb.ko exists too
[07:56] <duflu> Oh, no
[07:56] <didrocks> willcooke: no, I didn't see it, do you have a link?
[07:56] <duflu> Just renamed internally at runtime
[07:56] <willcooke> didrocks, https://utcc.utoronto.ca/~cks/space/blog/linux/ZFSOnLinuxARCShrinkage
[07:56] <didrocks> ah, I know this blog
[07:56] <didrocks> the guy keeps trashing zfs, let's see…
[08:03] <Laney> morning!!!
[08:05] <didrocks> hey Laney
[08:06] <seb128> hey Laney
[08:07] <Laney> moin didrocks seb128
[08:11] <duflu> Morning Laney
[08:18] <Laney> hey duflu
[08:35] <marcustomlinson> morning all
[08:39] <seb128> hey marcustomlinson, how are you today?
[08:42] <marcustomlinson> seb128: I'm good thanks! you?
[08:42] <marcustomlinson> I mean, I think I could always get more sleep, but oh well that's parenthood. I'll sleep when he moves out
[08:42] <seb128> marcustomlinson, I'm ok, having a cold kicking my butt though :/ Blocked nose, a bit of fever yesterday evening and no energy
[08:43] <seb128> yeah, no kidding
[08:43] <seb128> I think the lack of sleep is how I ended up with a cold again :-/
[08:43] <marcustomlinson> seb128: ahh... that sucks. Take it easy
[08:43] <seb128> I try :)
[09:00] <duflu> Morning marcustomlinson
[09:00] <duflu> On that note a few weeks ago I found myself watching https://www.youtube.com/watch?v=5MuIMqhT8DM ... after midnight
[09:06] <duflu> jibel, seb128, I notice nvidia-430 is in bionic now. Does that complete "Initiate the new updates policy https://wiki.ubuntu.com/NVidiaUpdates" ?
[09:06] <duflu> Oh, bionic-proposed
[09:12] <jibel> duflu, it depends on your definition of initiate. It could have been considered done on the first upload to -proposed.
[09:13] <duflu> yeah
[09:18] <Laney> haha
[09:23] <duflu> Well, I wouldn't consider it done. But I understand the perspective
[09:23] <seb128> :-)
[09:37] <jibel> on eoan did snapd broke for anyone else? I cannot launch google-chrome, code, spotify and the calculator freezes
[09:38] <jibel> for example
[09:38] <jibel>  spotify
[09:38] <jibel> internal error, please report: running "spotify" failed: cannot find installed snap "spotify" at revision 35: missing file /snap/spotify/35/meta/snap.yaml
[09:39] <rbasak> duflu: what are your plans with bug 1835664? I don't understand why it's Critical. The bug only affects one person apparently, and doesn't even provide steps to reproduce or a hardware description.
[09:40] <jibel> or that
[09:40] <jibel> $ code
[09:40] <jibel> /snap/code/11/electron-launch: line 28: /snap/code/11/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: No such file or directory
[09:40] <jibel> /snap/code/11/usr/share/code/bin/code: line 44: /snap/code/11/usr/share/code/bin/../code: No such file or directory
[09:40] <jibel> seb128, ^ do you know?
[09:41] <duflu> rbasak, no plan. 'Critical' removed though
[09:42] <duflu> Actually, that's not true. My plan is to always stop answering bugs outside of my expertise when I run out of advice
[09:42] <rbasak> The reporter seems to think that because it's Critical he can ask for escalation via ubuntu-devel-discuss@
[09:43] <rbasak> And someone has then forwarded that to ubuntu-devel@ (held in moderation)
[09:43] <rbasak> It set up the expectation that he's going to get personal support from someone.
[09:43] <duflu> rbasak, I guess as you said we need hardware details
[09:44] <duflu> Well I'm not going to apologise for trying to triage bugs that other people are ignoring
[09:44] <duflu> Feel free to do whatever you like with it
[09:44] <rbasak> I think that, as part of triage, it's important to set expectations.
[09:45] <rbasak> You're raised his, and now you're going ignore him? I think that's worse than not touching the bug at all.
[09:45] <rbasak> You've
[09:46] <duflu> rbasak, yes you are right. I won't do that again. Moving on...
[09:46] <duflu> Actually he's been very active in recent weeks
[09:52] <willcooke> jibel, there was a problem with snapd not seeding properly, can you do a "snap list"?
[09:55] <jibel> willcooke, it's on my main machine, already installed. I don't think seeding is involved
[09:55] <willcooke> jibel, oh.
[09:55] <jibel> and snap list works fine
[09:55] <willcooke> not that then
[09:56] <willcooke> jibel, is it only classic snaps?
[09:57] <willcooke> oh, no, it's not, you already said Spotify
[09:57] <jibel> willcooke, no all kind of snaps
[09:57] <willcooke> both are electron apps, is that a common factor?  (I'm just guessing here, so tell me to shut up)
[09:57] <jibel> FTR https://forum.snapcraft.io/t/cannot-launch-snaps-on-eoan/12341
[09:57] <jibel> willcooke, even hello is broken
[09:57] <jibel> $ /snap/bin/hello
[09:57] <willcooke> erk
[09:57] <jibel> cannot perform operation: mount --rbind /dev /tmp/snap.rootfs_neFJcx//dev: No such file or directory
[09:58] <willcooke> jibel, might be worth dropping in to #snappy and asking them?  I will try and recreate
[09:58] <willcooke> oh, you have a reply :)
[10:30] <jibel> willcooke, kernel 5.2 is the problem apparently
[10:31] <willcooke> :( erk
[11:11] <seb128> shrug
[11:11] <seb128> we need some autopkgtest there in the futur
[11:24] <Laney> good idea
[11:31] <Laney> kernel could probably get a Testsuite-Triggers: snapd or something
[11:33] <Laney> actually the kernel did indeed trigger snapd, but it didn't catch the problem: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/snapd/20190710_215303_d028e@/log.gz
[11:34] <seb128> xnox, hey, I finally uploaded duplicity 0.8 on python3! bad news is that build failed on ppc64el on some tests issues (https://launchpadlibrarian.net/433437044/buildlog_ubuntu-eoan-ppc64el.duplicity_0.8.01-0ubuntu1_BUILDING.txt.gz) ... any chance you or someone who has a clue about ppc64el could help with those?
[12:06] <xnox> seb128:  yeah! and oh noes!
[12:07] <clobrano> hey 0/, do you think it's fine if nobody shows up on #ubuntu-meeting, the membership meeting is supposed to be right now :|
[12:08] <Laney> :(
[12:09] <xnox> seb128:  open a bugreport. and ping vorlon he can find people with power access. I'm very busy as i'm travelling on friday for two weeks.
[12:09] <xnox> seb128:  unless like Laney and I poke it at debconf together
[12:09] <Laney> clobrano: if this fails, you can apply via the DMB for 'contributing developer'
[12:09] <seb128> xnox, ok, will do, thx
[12:09] <Laney> xnox: everyone has that access now via the new cloud :-)
[12:10] <xnox> Laney:  true =)
[12:10] <xnox> Laney:  i did not test drive the new cloud yet!
[12:10] <clobrano> Laney: :( DBM's last meeting was las Monday...
[12:11] <clobrano> s/las/last
[12:11] <Laney> bah
[12:32] <willcooke> clobrano, sorry for your experience there, I will email the UMB and see if they can help
[12:33] <clobrano> hi willcooke, no problem, I have time :D
[13:44] <tkamppeter> Anyone having problems with Chromium? I have updated my system and rebooted (to make it using kernel 5.2.x) and since thenm Chromium immediately crashes with "  No such schema “com.canonical.Unity.Launcher”
[13:45] <seb128> tkamppeter, install the snap :)
[13:45] <kenvandine> +1 :)
[13:46] <seb128> hum, you might have the snap already?
[13:46] <tkamppeter> I have already the snap installed, some weeks ago an update switched it over automatically. I am using Eoan.
[13:47] <seb128> kenvandine, do you know where the vcs is?
[13:47] <seb128> for the snap
[13:47] <tkamppeter> I get also the message: /snap/chromium/784/bin/desktop-launch: line 29: /home/till/.config/user-dirs.dirs: Permission denie
[13:48] <seb128> tkamppeter, try installing unity-schemas
[13:49] <tkamppeter> seb128, what is unity-schemas?
[13:49] <tkamppeter> seb128, I have installed it now, same error:
[13:49] <tkamppeter> snap/chromium/784/bin/desktop-launch: line 29: /home/till/.config/user-dirs.dirs: Permission denied
[13:49] <tkamppeter> Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
[13:49] <marcustomlinson> isn't stuff generally out of whack on Eoan with snaps at the moment, or unrelated?
[13:50] <marcustomlinson> looking for the snapcraft.io post...
[13:50] <seb128> tkamppeter, that looks like another error?
[13:51] <seb128> tkamppeter, that looks like https://forum.snapcraft.io/t/cannot-launch-snaps-on-eoan-and-kernel-5-2/12341
[13:51] <tkamppeter> It is also the "snap/chromium/784/bin/desktop-launch: line 29: /home/till/.config/user-dirs.dirs: Permission denied".
[13:51] <kenvandine> seb128: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/?h=stable
[13:51] <kenvandine> seb128: i think
[13:51] <seb128> kenvandine, thx
[13:52] <kenvandine> the user-dirs.dirs error isn't the issue, but it is weird that you get permission denied
[13:52] <seb128> kenvandine, I was wondering if the unity schemas thing had to do with the fix for the indicator, but probably not seen the commit, that just defined a TMPDIR
[13:54] <seb128> tkamppeter, as a workaround you can try to uninstall some snaps, it looks like it's more an issue with the number of snaps installed
[13:54] <kenvandine> :(
[14:04] <tkamppeter> seb128, thanks, I got it working again, removed libreoffice (the deb works again for me for some time),  gnome-3-28-1804, gtk-common-themes, and chromium, then installed chromium again and it worked.
[14:04] <tkamppeter> seb128, and the enlarged mouse pointer works again in Chrome.
[14:07] <tkamppeter> seb128, and the Google Hangouts extension is working again.
[14:27] <seb128> tkamppeter, good :)
[14:53] <seb128> bah
[14:53] <seb128> how do I tell discourse to not mangle my ''
[14:53] <seb128> thanks for replaced those by better text versions but that doesn't work for commands
[14:53] <seb128> popey, willcooke, ^ you know maybe?
[14:59] <willcooke> seb128, sorry, was otp - what;s up?  You've got some text which you want to show preformatted?
[15:02] <seb128> willcooke, I want to include a linux command to be copied/pasted
[15:02] <seb128> but ' are replaced by pretty ` ones
[15:03] <seb128> which gives an utf error/invalid command when copied to command line
[15:05] <willcooke> seb128, got a link to the post?
[15:06] <willcooke> I found it
[15:07] <willcooke> ha
[15:08] <seb128> willcooke, grep nameserver /etc/resolv.conf | awk ‘{print $2}’
[15:08] <seb128> the awk ones should be ''
[15:08] <willcooke> so, the answer I thought was use preformatting, but in their wisdom the markdown for preformatting uses backticks
[15:08] <willcooke> so as soon as it sees a backtick it stops being preformatted
[15:08] <seb128> right, I tried that :/
[15:10] <willcooke> seb128, ahhhahahaha!  I think I win.  Have  a look now
[15:11] <seb128> willcooke, gives me errors when copied to a command line still...
[15:11] <seb128> well the \ is wrong now though
[15:12] <seb128> willcooke, =\ is wrong, should be =`
[15:12] <seb128> though I guess we can use $() instead
[15:12] <seb128> yeah, that does it
[15:12] <seb128> willcooke, thx, I fixed the remaining error
[15:14] <willcooke> ah, I see
[15:14] <willcooke> yay
[15:14] <willcooke> ok, so three backticks at the start and end seems to be the magic
[15:22] <seb128> right, not ideally formatting visually/ I would have prefered to have the command 'inline' but that will do, thx!
[15:28] <Laney> seb128: `command`
[15:30] <seb128> Laney, that doesn't work when your command is =`echo 'foo'` though
[15:30] <seb128> ` conflicting use
[15:30] <Laney> ok
[15:30] <Laney> sounds likely
[15:31] <seb128> I workarounded it by using $() instead of  ``
[15:31] <seb128> but thanks for the reply :)
[15:31] <Laney> that's actually sort of why the $() format is preferred
[15:31] <Laney> because ` nests very badly
[15:32] <seb128> right
[15:33] <Laney> (``foo`bar`` probably works btw, it does in Gitlab at least)
[15:35] <Laney> (and you can do `` `foo`bar` `` to have it at the front or end)
[15:36] <seb128> I will try that next time, I think I had tried `` and it gave me the two on the output but I'm unsure now
[15:36] <seb128> I want a <donttouchmytext></donttouchmytext> :)
[15:36] <Laney> well that's standard markdown, perhaps discourse messes it up
[16:47] <Laney> gjs has sysprof support now, means a new dependency and MIR for sysprof I think
[16:47] <Laney> duflu should like that one
[16:54] <teward> I think this is relevant to someone needing to reply from the Deskto team...
[16:54] <teward> https://askubuntu.com/q/1159010/10616
[16:54] <teward> ("Will the default swappiness be changed from swappiness=60 to swappiness=10 in Ubuntu desktop?")
[18:11] <seb128> teward, thanks for pointing it out, I've no idea what that is, might need input from foundations. Would be better asked on ubuntu-devel@ list or discourse if someone want to do that
[18:11] <teward> ack.  swappiness is the setting that controls how often data is put onto swap from memory :p
[18:11] <teward> been 60 since ever so
[18:14] <seb128> right, so yeah that's not limited to desktop and probably something foundations/kernel have also an opinion about