[06:19] <didrocks> goodm orning
[06:20] <duflu> Morning didrocks
[06:20] <duflu> and later...
[06:20] <didrocks> hey duflu
[06:49] <oSoMoN> good morning desktoppers
[06:55] <duflu> Morning oSoMoN
[06:56] <oSoMoN> hey duflu
[07:02] <didrocks> hey oSoMoN
[07:03] <oSoMoN> salut didrocks
[07:06] <seb128> good morning desktopers
[07:11] <duflu> Hi seb128
[07:11] <oSoMoN> salut seb128
[07:13] <seb128> hey duflu, lut oSoMoN, how are you?
[07:14] <duflu> seb128, I feel normality returning. Might have got to be before midnight finally. How are you?
[07:14] <duflu> -be +bed
[07:15] <seb128> ah, nice
[07:15] <oSoMoN> seb128, I'm good, how are you?
[07:15] <seb128> I'm fine today, played some tennis yesterday which was nice despite the fact that I manage to slip when changing direction and fall and bruised my elbow and hand
[07:16] <duflu> The cost of physical activity...
[07:16] <seb128> right
[07:16] <duflu> Better than desk-induced injuries
[07:20] <duflu> Unless the desk is encountered on the a tennis court
[07:25] <seb128> :)
[07:50] <willcooke> morning desktoppers
[07:51] <duflu> Morning-ish willcooke
[07:52] <didrocks> hey willcooke
[07:52] <willcooke> afternoon duflu
[07:52] <willcooke> duflu, thanks for looking at the gdm issue
[07:52] <willcooke> testing the workaround now
[07:52] <duflu> willcooke, in the end I could not help but see it :/
[07:53] <willcooke> funny that this test machine should be "too fast", since it's old
[07:53] <duflu> Weird I had to try a third cosmic machine before I hit it
[07:53] <duflu> Maybe not weird. Just a faster system for the kernel to boot on
[07:53] <willcooke> on this machine once it "fixes" itself, it's very hard to break again
[07:53] <willcooke> very odd
[07:54] <duflu> Mine too. But the problem returned immediately on the first boot after I removed the workaround
[07:54] <seb128> hey willcooke
[07:54] <willcooke> duflu, do I edit the gdm3 service file or the gdm service file?
[07:54] <duflu> willcooke, one is a symlink to the other
[07:55] <duflu> so edit either
[07:55] <willcooke> so it is
[07:55] <willcooke> :)
[07:56] <willcooke> duflu, and do I add a second ExecPre line, or remove the one that's there are replace it?
[07:56] <duflu> willcooke, add a second one. Seems to work
[07:56] <duflu> I suspect removing existing stuff might break
[07:57] <willcooke> can haz gdm
[07:58] <willcooke> Could this be as simple as moving gdm later in the boot process?
[07:58] <seb128> the boot is not a fixed sequence
[07:58] <willcooke> ah
[07:58] <seb128> especially not with systemd
[07:59] <seb128> services reacts to other parts to be ready
[07:59] <seb128> upstream said it was a known bug in the gdm code, that's probably the best place where to fix it
[07:59] <seb128> also changing ordering of services might have side effect and create other problems
[08:00] <willcooke> duflu, triggereed the bug even with sleep 5
[08:00] <willcooke> I'll try sleep 120
[08:00] <willcooke> *10
[08:00] <duflu> Yeah
[08:01] <Laney> yo
[08:01] <seb128> lol
[08:01] <seb128> hey Laney, how are you?
[08:03] <duflu> Hi Laney
[08:04] <didrocks> hey Laney
[08:04] <willcooke> oh, my bad, I'd spelled Pre wrong
[08:04] <willcooke>  /o\
[08:10] <Laney> hey seb128 duflu didrocks
[08:10] <Laney> I'm alright, went to a nice gig last night
[08:11] <willcooke> Laney, is Rock City still there?
[08:12] <Laney> yeah, that's one of the big beasts
[08:12] <willcooke> \m/
[08:12] <Laney> they have the big student night on wednesdays there, "crisis"
[08:12] <Laney> this was at folk club in the pub down the road though :-)
[08:12] <willcooke> I have fond memories of student night in there.
[08:12] <willcooke> or rather, I dont
[08:12] <willcooke> Laney, nice :) Less students
[08:13] <willcooke> Less Fosters
[08:14] <Laney> tuborg
[08:14] <willcooke> duflu, now I've removed the sleep I can't  break it
[08:14] <Laney> that's what I remember from rock city
[08:14] <willcooke> urgh
[08:14] <Laney> also the floor being so sticky that it took my shoe off
[08:14] <duflu> willcooke,  didn't it take an hour or so to return yesterday?
[08:14] <willcooke> yes!  That I remember
[08:15] <willcooke> duflu, I reinstalled
[08:15] <willcooke> duflu, I'll try doing something else for a while
[09:13] <willcooke> tjaalton, any more ideas about that virtualbox thing?
[09:13] <willcooke> tjaalton, also hi! :)
[09:13] <willcooke> Laney, is your n-m fix in the new iso?
[09:14] <Laney> noh
[09:14] <Laney> should be in cosmic laer
[09:14] <tjaalton> willcooke: show xorg log
[09:26] <tjaalton> I bisected xserver-xorg-video-fbdev driver and reverted a commit which made kvm with bochs vga fail, but doubt it helps here
[09:26] <tjaalton> it's in proposed now
[09:28] <tjaalton> anyway, gdm/X is started too early before the native driver has a chance
[09:29] <tjaalton> but there's no easy way to determine how to keep it waiting, sometimes /dev/fb0 is enough, some need /dev/dri/card0. not sure if either would work on nvidia..
[09:32] <popey> Just dist upgraded my cosmic vm (virtualbox) and now gnome shell segfaults on boot
[09:32] <popey> is this known?
[09:37] <popey> https://www.irccloud.com/pastebin/KcXDhLnb/
[09:38] <popey> http://termbin.com/tcdg
[09:41] <tjaalton> popey: does it work after restarting gdm?
[09:41] <popey> tjaalton: no
[09:41] <tjaalton> k
[10:01] <willcooke> I wonder if the same fix for gdm will work on vbox as well.  I'll try it
[10:04] <tjaalton> you mean adding some sleep? most likely
[10:22] <Laney> seb128: could you delete gjs gjs-tests libgjs-dev libgjs0g/s390x/cosmic and promote mozjs60 libmozjs-60-dev libmozjs-60-0 please?
[10:22] <Laney> popey: a backtrace would be useful, e.g. by using apport to report the .crash file
[10:24] <seb128> Laney, "4 packages successfully removed."
[10:24] <popey> Laney: what's the best way to do that?
[10:26] <seb128> Laney, "11 publications overridden."
[10:27] <Laney> popey: ubuntu-bug <crash file>
[10:27] <Laney> seb128: kiss you on both cheeks
[10:27] <seb128> :)
[10:28] <Laney> 😘 🍑
[10:32] <popey> Laney: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1796056
[10:32] <willcooke> tjaalton, yeah.  Just done in meetings, will test it in a mo
[10:59] <Laney> popey: thx, that's a tjaalton thing
[11:01] <seb128> tjaalton, ^ saw that bug?
[11:02] <seb128> SIGABRT in glamor_egl_init()
[11:02]  * Laney assumed using the nick exactly would cause a highlight
[11:05] <seb128> Laney, right, I'm never sure if people do bother when they are just being mentioned or if direct ping has a different effect/more chance to give you a reply
[11:05] <seb128> I know for sure some people go "whatever" when you mention their name without a direct question
[11:05] <seb128> (not stating it's the case here though)
[11:06] <Laney> righto
[11:06] <tjaalton> saw it now
[11:06] <tjaalton> never before
[11:07] <seb128> it doesn't seem to have duplicates
[11:09] <willcooke> tjaalton, https://paste.ubuntu.com/p/mDPNsJmnRv/
[11:09] <willcooke> that's the xorg log from a live session
[11:09] <Laney> I mean the last patch did touch that line
[11:09] <Laney> so ;-)
[11:10] <seb128> right
[11:14] <willcooke> Is it possible for me to edit files inside an ISO image?  I'd like to try that sleep hack in the live session and I don't know how to
[11:15] <willcooke> or am I wasting my time?
[11:15] <willcooke> I suspect the later
[11:15] <jamesh> if your edits don't change the size of the file it might be possible
[11:16] <willcooke> it will
[11:16] <willcooke> I wont bother
[11:16] <willcooke> :)
[11:16] <tjaalton> remove some comments ;)
[11:16] <willcooke> ha
[11:16] <jamesh> does the change need to be live on bootup, or just when it is running?
[11:17] <willcooke> well, I'd like to try adding a sleep to the gdm service file for the live session
[11:17] <willcooke> oh, perhaps the live session isnt even using gdm
[11:17] <jamesh> if it is just at runtime, copy the file to /tmp, edit it, and then bind mount it to the original location
[11:17] <jibel> willcooke, depending on what you want to do you have to rebuild the ISO or you can stop in casper, edit the file you want and continue
[11:17] <jibel> the live session is using gdm
[11:18] <tjaalton> I'll discuss the new glamor_egl_init crash with upstream
[11:18] <Laney> thx!
[11:19] <willcooke> jibel, ah, stopping in casper sounds like what I want.  How do I make that work?
[11:19] <jbicha> willcooke: the 19.04 trello board doesn't appear to be part of the Ubuntu Desktop team like the 18.10 board is
[11:19] <tjaalton> willcooke: I suspect the corruption comes when modesetting takes over from vesa..
[11:19] <willcooke> jbicha, yes it's part of the Canonical group because we have a paid subscription, and so more toys.  It shouldn't affect anything else though.  If you dont have access I can add you
[11:20] <jbicha> I have read access but not write access
[11:20] <willcooke> tjaalton, so not much I can do then?  Do you need more logs or anything?
[11:21] <jbicha> probably should add darkxst there too
[11:21] <willcooke> jbicha, done and done
[11:22] <jbicha> thanks
[11:24] <tjaalton> willcooke: nah
[11:24] <willcooke> tjaalton, shout if I can help
[11:36] <jibel> willcooke, sorry, actually that won't work if you want to modify the squashfs, and if you boot in rescue mode it'll alter the boot sequence and invalidate your test (if what you want is modfying a systemd file)
[11:42] <Laney> jibel: what's wrong with break=bottom and modifying files in /root?
[11:50] <jibel> Laney, if it breaks after the squashfs is mounted it should work indeed
[11:51]  * Laney nods
[11:52] <Laney> be prepared for editing files in there to be a hateful experience though :-)
[11:52] <jibel> willcooke, then you boot, press space, F6 and add break=bottom to the kernel command line, Enter to boot. when it stops in the initramfs chroot /root and do your edit
[11:52] <jibel> ctrl+d twice and boot will continue
[11:55] <willcooke> oki, that sounds fun.  I'll have ago
[11:55] <willcooke> but first food
[13:26] <jibel> willcooke, when you install in legacy mode on a uefi system, does it boot after installation?
[13:27] <jibel> ah, I get the "no gdm" issue now
[13:32] <tjaalton> that new crasher is because eglMakeCurrent doesn't seem to work, and that's a bug in mesa or glvnd
[13:32] <jibel> willcooke, when I said "does it boot" I meant does it detect a bootable device?
[13:33] <seb128> Laney, jibel, willcooke, do you know what's the deal with ubiquity-slideshow-ubuntu? you guys commited changed but there was no upload, was it waiting on something?
[13:34] <seb128> jbicha, I don't understand the point of that upload http://launchpadlibrarian.net/391652443/grilo-plugins_0.3.8-1ubuntu1_0.3.8-2ubuntu1.diff.gz
[13:35] <jibel> seb128, no, just someone to release it.
[13:35] <seb128> jibel, k, I'm going to merge the yaru changes and upload then
[13:35] <jibel> ok
[13:36] <Laney> I thought there were some other changes coming, but I had it on my list to check back tomorrow
[13:36] <Laney> you can do it if you want
[13:36] <seb128> I'm reviewing https://code.launchpad.net/~madsrh/ubiquity-slideshow-ubuntu/Yaru-CSS/+merge/355913
[13:36] <seb128> so I think I'm just going to upload with that
[13:36] <seb128> we can do another upload if there a late change still coming
[13:36] <seb128> if that's fine with others
[13:38] <Laney> if you want to do it then you can do it
[13:38] <seb128> thx
[13:38] <Laney> new gjs went in
[13:38] <Laney> and n-m and plymouth
[13:38] <Laney> #goodupdateday
[13:38] <seb128> \o/
[13:38] <seb128> NEW ISO TIME
[13:38] <seb128> :)
[13:39] <Laney> would need to publish, then takes a couple of hours
[13:39] <seb128> tomorrow morning sounds like it then
[13:39] <Laney> probably won't do an extra one
[13:40] <Laney> maybe there's an xorg fix or two in the meantime ;-)
[13:40] <ahayzen> hey, does anyone know if there is going to be a new gnome-software update for cosmic before release? eg bumping to 3.30.1 or pushing of what is in the ubuntu-3-30 branch ?  I was hoping a fix i landed in the ubuntu-3-30 branch a few weeks ago would make it ...
[13:40] <seb128> ahayzen, we should have it updated to .1, https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1789451
[13:41] <seb128> kenvandine, can you make sure that robert_ancell has that on his list?
[13:41] <kenvandine> seb128: will do
[13:41] <seb128> thx
[13:42] <ahayzen> seb128, ok thanks, as i fixed this https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1791553  ... which doesn't affect the default install, but i saw youtube's hating on ubuntu because of it. So was trying to prevent bad press from the release :-)
[13:43] <seb128> ahayzen, ah, flatpak ...
[13:43] <seb128> is youtube hating a thing?
[13:43]  * seb128 is too old for knowing about that :p
[13:44] <ahayzen> yeah it was a feature listed in the gnome 3.30 release, so people were getting a bit ragy that wasn't in ubuntu cosmic :-) Anyway, if what is in ubuntu-3-30 branch is pushed to cosmic that'll fix it
[13:44] <seb128> it should yes
[13:44] <seb128> thx for raising it up/asking though
[13:44] <seb128> and for fixing it :)
[13:45] <Laney> you might want to comment on the bug to make sure that robert_ancell knows about it
[13:45] <seb128> ahayzen, that change is confusing though
[13:45] <seb128> unsure it's a good idea to land that in cosmic
[13:46] <seb128> was there anything done to communicate that the setting apply to flatpak only?
[13:47] <ahayzen> seb128, i worked with robert and he approved the merges :-)  i think long term snappy could hook into it as well.  I'm happy to modify the text to mention flatpak or something if required
[13:47] <seb128> the fact that you worked with Robert doesn't reply to my question
[13:47] <seb128> I guess it means "no"?
[13:48] <ahayzen> not visually to the user, no. Suggestions welcome :-)
[13:48] <seb128> it's too late for a string change
[13:48] <seb128> I would vote -1 for landing that change/fix in cosmic
[13:48] <seb128> it sucks a bit, unsure how to handle it
[13:49] <seb128> oh, wait, you only show the dialog if the flatpak plugin is installed?
[13:49] <ahayzen> ok :-/ the problem is that users are forced into auto updates unless they go and manually edit dconf
[13:49] <seb128> (which we don't install by default)
[13:49] <ahayzen> seb128, yes i only show it if gnome-software-plugin-flatpak is enabled
[13:49] <seb128> ah ok
[13:49] <seb128> then it's good enough
[13:49] <ahayzen> seb128, so for a default install there is no difference
[13:49] <ahayzen> sorry i should have mentioned that
[13:49] <seb128> the users who go manually install that can deal with the side effects
[13:49] <seb128> right, I just remembered
[13:49] <ahayzen> yes
[13:49] <seb128> so it should be all good :)
[13:49] <ahayzen> :-)
[13:50] <seb128> still not ideal but it will do
[13:50] <ahayzen> yeah :-/ i really hope that snaps can also integrate with that dialog. As it'd be nice to have a common way to disable/enable auto updates between the formats
[13:51] <ahayzen> ok, so in conclusion, it should hopefully be in cosmic when 3.30.1 is updated
[13:52] <seb128> yes
[13:52] <seb128> as for snap, let's see
[13:53] <seb128> but snapd has a metered property already, so it should be easy enough to make the UI change it
[13:53] <seb128> then unsure how to keep the settings in sync since on the backend they have different locations
[13:53] <seb128> and I doubt snapd wants to use dconf
[13:55] <ahayzen> maybe the gnome-software-plugin-snap can listen to that button and set something to libsnapd-glib ?  (i'm not familiar how the snap parts are structured though)
[13:56] <seb128> that direction is easy
[13:56] <seb128> but what it the user change the snap property through the snapctl command
[13:56] <seb128> then the dconf and snap setting disagree
[13:56] <seb128> what does the checkbox status in the UI is?
[13:57] <ahayzen> ah yeah, if you have both snap and flatpak you could get them out of sync etc. So probably something to discuss with upstream.
[13:57] <seb128> right
[13:57] <seb128> also that settings doesn't apply to debs updates either
[13:58] <seb128> but yeah, upstream design discussions
[14:02] <kenvandine> seb128: updating the cosmic seed for portals and it's dropping gdm3, gnome-shell and ubuntu-settings for s390
[14:02] <kenvandine> seb128: i guess that's not a surprise right?
[14:02] <Laney> correct
[14:02] <kenvandine> just making sure ;)
[14:02] <seb128> right
[14:03] <kenvandine> thanks
[14:03] <seb128> kenvandine, btw did you see the ping about snaps/yaru icons, yaru team waiting for a comment thing?
[14:03] <kenvandine> yesterday?
[14:04] <kenvandine> seb128: i responded yesterday, haven't had a chance to check today if there was more activity
[14:05] <seb128> kenvandine, right, sorry I don't know what that post is so I couldn't check
[14:05] <seb128> there is no recent topic with "icon" in the title
[14:05] <jbicha> seb128: I manually typed in the wrong version number when I merged grilo-plugins so gnome-music is in depwait
[14:05] <seb128> kenvandine, thanks!
[14:05] <jbicha> https://launchpad.net/ubuntu/+source/gnome-music/3.30.1-1/+build/15509465
[14:06] <seb128> jbicha, ah ok, you should perhaps have mentioned that in the changelog to help the reviewer to understand that the update has a point out of cosmic of the changelog
[14:06] <seb128> jbicha, also why did you drop the "Merge with Debian" bits?
[14:06] <seb128> from the previous changelog entry
[14:06] <jbicha> ok, let me reupload
[14:06] <seb128> well don't bother for me
[14:06] <seb128> I'm not in the release team
[14:16] <seb128> k, slideshow uploaded, rebooting to see if the issue with that usb stick is the device/image or if it's the inspiron not liking it for a reason
[14:20] <willcooke> sorry, been in docs, missed pings.  Reading
[14:23] <seb128> bah, the key works on my laptop but only in uefi mode, it gives an error in bios mode
[14:24] <seb128> the inspiron is uefi enabled though
[14:24] <seb128> but it doesn't like the key at all :/
[14:24] <seb128> rewritting the image in case that makes a difference
[14:25] <willcooke> jibel, seb128 - My inspiron is, afiact, in BIOS mode and was booting properly
[14:26] <willcooke> good update day indeed, looking forward to tomorrows iso
[14:26] <willcooke> maybe these gdm issues and vbox issues will be fixed by then too ;D
[14:27] <seb128> willcooke, how do put it in bios mode?
[14:28] <willcooke> seb128, sec
[14:28] <seb128> or you mean secure boot disabled?
[14:28] <willcooke> I think it's real BIOS mode
[14:28] <seb128> I don't find that option in the bios settings here :/
[14:29] <willcooke> Boot -> Boot List Option
[14:29] <willcooke> Legacy or UEFI
[14:29] <seb128> that line is grey for me
[14:29] <seb128> I can't select it
[14:29] <willcooke> turn off secure boot first?
[14:30] <seb128> it is off
[14:30]  * willcooke checks the other setting
[14:30] <seb128> I might need a bios update?
[14:31] <seb128> did you ever update the bios on that machine?
[14:31] <seb128> can fwupd do that? ;)
[14:31] <willcooke> never tried
[14:32] <seb128> k, it worked in a port on the left
[14:32] <seb128> I had it on the right side before
[14:32] <willcooke> BIOS version A05
[14:32] <seb128> weird
[14:32] <willcooke> ?!
[14:32] <seb128> go figure
[14:32] <seb128> willcooke, thx :)
[14:32] <willcooke> any time
[14:50] <xnox> Does ubports use upstart in bionic?
[14:50] <xnox> in user session?
[14:51] <seb128> willcooke, k, same bug that you with gdm on my inspiron
[14:51] <seb128> xnox, no idea
[14:51] <Laney> there is no upstart in bionic?
[14:52] <willcooke> seb128, cool.  If you can be bothered, add the sleep line to the systemd unit and see it fixed
[14:52] <seb128> k, did it work for you?
[14:52] <seb128> that's a workaround though...
[14:52] <willcooke> seb128, yes and yes
[14:52] <willcooke> also worked for duflu
[14:52] <willcooke> so no need to test really
[14:52] <seb128> k
[14:52] <willcooke> halfline is on the case
[14:52] <seb128> but need to fix really
[14:52] <seb128> right
[14:53] <seb128> if he doesn't get to it this week we might want to consider helping next week
[14:53] <Laney> there's a merge request
[14:53] <xnox> Laney, correct there is no upstart in bionic; but i'm going to upload "Conflicts: upstart" in systemd =/
[14:53] <xnox> which may affect them.
[14:55] <jbicha> xnox: do you telegram? if so try https://ubports.com/contact-us
[14:59] <seb128> Laney, a WIP one that needs some fixing though
[14:59] <seb128> e.g I don't think we can backport it to our package as it
[14:59] <Laney> I know Seb, I left some comments on it.
[15:01] <seb128> k, sorry, I guess I didn't get what you were trying to tell me then
[15:01] <seb128> or maybe my comment was not clear
[15:01] <Laney> that it's in hand
[15:01] <seb128> if halfline is too busy maybe we should consider helping to get to cleanup/land the work
[15:01] <seb128> is what I meant
[15:01] <seb128> but let's see
[15:01] <willcooke> +1
[15:02] <Laney> I did help
[15:02] <seb128> so we should be set :)
[15:02] <Laney> Yes.
[15:03] <seb128> thx Laney!
[15:04] <seb128> kenvandine, could you have bug #1787653 on your list/ask Robert to have a look? it's the second error on the weekly view of e.u.c/cosmic and seems to have started to spike this cycle
[15:06] <kenvandine> seb128: sure
[15:07] <seb128> thx
[15:13] <jbicha> seb128: you can remove tracker & tracker-miners from cosmic-proposed. (I checked with darkxst)
[15:13] <seb128> jbicha, k
[15:14] <seb128> jbicha, what's the reason? (the removal tools requires one)
[15:14] <seb128> "the update requires a MIR which isn't going to be approved before cosmic"?
[15:17] <jbicha> "not enough time to resolve LP: #1793550 before cosmic release"
[15:17] <seb128> thx
[15:18] <jbicha> Tim's solution would have worked but I don't want to rush it into Debian over mbiebl's concerns right now
[15:19] <seb128> jbicha, done
[15:21] <seb128> kenvandine, jamesh, we might want to keep an eye on https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1796113 if we install portal by default now
[15:21] <seb128> it has a few reports only but it was not default yet
[15:23] <seb128> andyrock, unsure how busy you are atm, if not too much maybe you can have a look to bug #1796115? that started with 3.30.0 apparently
[15:25] <seb128> changing location, brb
[15:45] <seb128> back
[15:49] <andyrock> seb128: hey I'm working on a crash that happens on gnome-shell --replace
[15:49] <andyrock> that is preventing me to do other work
[15:50] <andyrock> I took a look at 1796115 (forgot to puth in the status report!) last week, for what I understand it could happen when you launch g-c-c as root
[15:50] <willcooke> nice forum post on the gttk2 themes jamesh
[15:50] <seb128> andyrock, ah ok, thx
[15:50] <seb128> g-s seems higher priority indeed
[15:51] <andyrock> seb128: I'll take another look btw
[15:51] <andyrock> seb128: for the moment I was able to understand that this does not happen when nautilus-desktop is not running
[15:52] <andyrock> seb128: https://gitlab.gnome.org/GNOME/gnome-shell/issues/627 and https://gitlab.gnome.org/GNOME/gnome-shell/issues/595
[15:52] <gitbot> GNOME issue 627 in gnome-shell "Shell 3.30 crashed on Arch Linux" [Opened]
[15:52] <gitbot> GNOME issue 595 in gnome-shell "gnome-shell --replace crashes on 3.30" [1. Crash, 2. Needs Information, Opened]
[15:53] <andyrock> not sure if arch is running nautilus-desktop too
[15:53] <andyrock> running gnome-shell with --sync I see that crash happens whey gnome-shell creates the "Change Background..." menu
[16:23] <kenvandine> Laney: trying to refresh ubuntu-meta and it's not adding xdg-desktop-portal-gtk
[16:23] <kenvandine> the seed has been updated in git
[16:23] <kenvandine> it's been a couple hours now
[16:23] <kenvandine> Laney: ideas?
[16:23] <Laney> I suspect you need to promote it
[16:26] <kenvandine> i thought it wouldn't get promoted until something needed it
[16:26] <Laney> it does (the seed)
[16:27] <kenvandine> ah
[16:27] <Laney> https://lists.ubuntu.com/archives/ubuntu-release/2018-October/004609.html
[16:27] <kenvandine> Laney: thanks, i thought they wouldn't hit component-mismatches until ubuntu-meta was uploaded
[16:28] <kenvandine> cool, so i guess i just wait now :)
[16:29] <Laney> maybe you know a friendly archive admin :P
[16:30]  * kenvandine winks at seb128 
[16:40] <seb128> kenvandine, done
[16:40] <kenvandine> seb128: thanks!
[16:40] <seb128> I only put the main binary for xdg-desktop-portal to main
[16:40] <seb128> not the -dev nor -test binaries
[16:40] <kenvandine> that's fine
[16:41] <seb128> k, good
[16:41] <kenvandine> and xdg-desktop-portal-gtk too right?
[16:41] <seb128> yes
[16:41] <seb128> that one has only 1 binary
[16:41] <kenvandine> great, thanks
[16:41] <seb128> so no question :)
[17:24] <willcooke> good night all
[17:26] <seb128> have a nice evening desktopers
[17:28] <kenvandine> good evening seb128
[17:28] <seb128> thx! :-)
[18:35] <kenvandine> jibel: should i report a bug about the images in the installer being bionic beaver?
[18:35] <kenvandine> jibel: or is that known and just not done yet?
[18:38] <jibel> kenvandine, no, next build should have the right mascot
[18:42] <kenvandine> jibel: great
[18:42] <kenvandine> jibel: and willcooke was updating the screenshots right?
[18:47] <jibel> kenvandine, yes