[06:08] <didrocks> good morning
[06:15] <jibel> salut didrocks
[06:19] <didrocks> bonjour jibel, ça va ?
[06:20] <jibel> didrocks, ça va bien. J'ai passé le w-e a refaire un salle de bain. et toi ça va ?
[06:24] <didrocks> jibel: ça va, pas pu faire assez de choses par rapport à ce que j'avais prévu, mais un peu reposé :)
[06:34] <oSoMoN> good morning desktoppers
[06:34] <didrocks> hey hey oSoMoN
[06:46] <oSoMoN> salut didrocks
[06:57] <duflu> Oh, good morning didrocks, jibel, oSoMoN
[06:58] <duflu> , France, Europe, World
[07:02] <didrocks> good afternoon/evening duflu :)
[07:04] <duflu> It's a gradated scale...
[07:04] <seb128> good morning desktopers
[07:04] <duflu> Hi seb128
[07:04] <seb128> hey didrocks duflu
[07:10] <oSoMoN> good afternoon duflu
[07:10] <oSoMoN> salut seb128
[07:10] <seb128> lut oSoMoN, bon w.e?
[07:15] <oSoMoN> seb128, très bon week-end, bricolage, jardinage et barbecue, la totale :) et toi?
[07:16] <seb128> oSoMoN, bon w.e aussi, ballades, une fête de naissance, mais pas de barbecue
[07:18] <oSoMoN> ça viendra, nous c’était le premier de la saison
[07:18] <didrocks> jibel: I'm going to convert the bool string in the telemetry json for ubiquity to simply bool, as it wasn't uploaded yet
[07:24] <didrocks> jibel: btw: autopilot/ubiquity_autopilot_tests/tests/__init__.py:242:80: E501 line too long (89 > 79 characters)
[07:24] <didrocks> ;)
[07:24]  * didrocks fixes
[07:24] <didrocks> (rejected on debclean)
[07:25] <didrocks> code autopilot/ubiquity_autopilot_tests/tests/__init__.py
[07:25] <didrocks> wrong terminal…
[07:27]  * didrocks wants to milit for 120 char lines…
[07:32] <jibel> didrocks, oops, sorry
[07:32] <jibel> thanks for fixing
[07:33] <jibel> +1 for longer strings
[07:36] <didrocks> jibel: yw! yeah, especially that this line is doc content, even crazier to restrict it to 80 chars…
[07:37] <didrocks> I'll just do an install test to confirm I didn't make any booboo
[08:02] <Laney> moin
[08:03] <Trevinho> morning guys
[08:04] <duflu> Morning-ish Trevinho
[08:04] <duflu> And morning Laney
[08:05] <didrocks> hey Laney, Trevinho
[08:05] <Trevinho> hi didrocks
[08:05] <Trevinho> how is it going?
[08:06] <didrocks> jibel: ok, bool change is done and tested. I'll have another change to proceed but unsure I'll get at it today (adding the "switch to slideshow" timestamp to know how long the last step took to file in), want separate MP or will batch them in tomorrow's one?
[08:06] <didrocks> Trevinho: good good, yourself?
[08:06] <dupondje> I would have expected more people having issues with https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1757401 ... strange :)
[08:08] <jibel> didrocks, I don't mind do as you prefer as long as it doesn't end up with a 2km long MP
[08:08] <seb128> hey Laney Trevinho
[08:08] <seb128> had a good w.e?
[08:09] <Trevinho> yeah, good one... Ubuntu talk on Sat and some small roadtrip around yesterday
[08:09] <didrocks> jibel: it's going to be few line diffs, ok, will batch it then
[08:09] <seb128> dupondje, well, the people here are mostly on intel only configs I think, unsure how common hybrid configs are in people using the dev cycle
[08:10] <jibel> dupondje, I used to have the 1st issue you describe but I cannot confirm it still exists because now my system simply don't boot with an external monitor attached
[08:14] <duflu> I think to have a problem with hybrid also implies you're using two or more displays. So that's less common again
[08:15] <duflu> Is there any way to tell the system to always have debug symbols installed?
[08:15] <duflu> If you just install dbg debs then they get automatically uninstalled on update
[08:17] <seb128> duflu, they should, do you have an update log? maybe is that dbg or ddebs? maybe it's just that the ddebs server is slower to update and by the time you update the ddeb matching version is not available yet?
[08:18] <dupondje> seb128: laptop with 2 gpu's :( and always using a second screen :)
[08:18] <seb128> dupondje, right, that's uncommon, I think most people on the channel have either dell or lenovo laptops with intel only video
[08:19] <seb128> well uncommon here, among those using the devel cycle
[08:19] <duflu> seb128, yes but I don't want to fall down that rabbit hole. I have too many other holes to finish with first
[08:19] <seb128> k
[08:19] <seb128> well, to reply to your question they should stay installed and there is no specific "magic" you can use
[08:20] <seb128> if they don't you have a specific issue and that needs investigating at some point
[08:20] <Laney> hey duflu didrocks seb128
[08:21] <dupondje> seb128: dell here also :) hehe
[08:25] <seb128> dupondje, well I'm not trying to argue over details, I guess you got what I tried to say?
[08:26] <dupondje> seb128: yea sure, just want to make sure it gets fixed before release date, else alot of users will have issues I guess
[08:27] <seb128> right, I was not arguing it shouldn't be fixed, just responding to your comment about not getting more complains about the issue
[09:13] <alexarnaud> Hello all
[09:15] <seb128> Laney, can you make gnome-online-accounts ignore the gnome-photos/3.27.92-1ubuntu1 autopkgtest results? they don't need to migrate together
[09:16] <seb128> hey alexarnaud
[09:19] <alexarnaud> seb128: Are you aware of accessibility of the installer that could be in your pipe if you decide to fix them ? For now, the installation of Ubuntu is no longer doable by a blind person, see
[09:19] <alexarnaud> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1741690
[09:19] <alexarnaud> https://bugs.launchpad.net/ubuntu-mate/+bug/1741507
[09:19] <alexarnaud> *accessibility issues
[09:19] <seb128> alexarnaud, I read that in the log, patches are welcome if you feel like working on the issue :)
[09:23] <sil2100> Trevinho: hey! I rejected temporarily the ubuntu-themes SRU you pushed as the Bileto silo seems to need a rebuild
[09:23] <alexarnaud> seb128: I don't plan to work on accessibility bugs on the Ubuntu installer. I'm only involved in QA for the moment. You should be aware there are for example the GTK dialog to save file that is not correctly accessible. I never spend time to report bug about it.
[09:23] <Trevinho> sil2100: mh ok thanks
[09:23] <Trevinho> i'll do it
[09:23] <seb128> alexarnaud, k, is that a regression? would be worth opening a bug about if you can do that
[09:24] <sil2100> Trevinho: also, I see the bug is targetting artful as well - we expecting a fix for that series too?
[09:24] <alexarnaud> seb128: Yes it's a regression. It works correctly on Ubuntu 16.04
[09:24] <Trevinho> sil2100: no, as that change  has not been backported there iirc
[09:24] <seb128> alexarnaud, do you know if it's reported upstream?
[09:25] <alexarnaud> seb128: I don't understand, it's only bugs related to the ubuntu installer.
[09:25] <alexarnaud> seb128: On Fedora it seems that it works.
[09:26] <seb128> alexarnaud, we have dialogs to save files in our installer?!
[09:26] <seb128> where?
[09:30] <seb128> Laney, I'm looking at fixing the gnome-photos autopkgtests meanwhile but I don't see a reason to block goa on that
[09:30] <alexarnaud> seb128: I'm talking about other accessibility bug that exist in free software so I couldn't spend time to report bug to developers and fix bugs.
[09:31] <Laney> seb128: wait, let me try to re-run against the old version first
[09:31] <seb128> alexarnaud, right, and I asked if that one had been reported upstream, to what you replied that it was only in the ubuntu installer
[09:31] <seb128> Laney, thx
[09:32] <alexarnaud> It's just a example to explain you that accessibility bugs should be fixed by each developers on their software. Not only by impacted users.
[09:32] <seb128> alexarnaud, anyway thanks for the notice, I'm writting that one on my list of things to check
[09:32] <seb128> alexarnaud, I'm not saying users should fix them, just that we are really busy and might not manage to look at that issue so a patch would help, if you are too busy as well I understand
[09:33] <seb128> on that note stepping out for a bit
[09:36] <duflu> alexarnaud, Ctrl+Alt+T also fails in the live session. Might be a general problem with shortcuts
[09:37] <seb128> duflu, gsd-media-keys timeouts for some reasons
[09:37] <duflu> Oh, I have an old bug report for that
[09:37] <seb128> could have to do with the slowness we have since we added snaps
[09:37] <seb128> that's being worked
[09:37] <seb128> well snap slowness is
[09:38] <alexarnaud> duflu: are you able to do alt+win+s to launch the Orca screen reader on the live session?
[09:38] <seb128> the timeout things hasn't been looked at yet afaik
[09:38] <duflu> alexarnaud, never tried
[09:38] <willcooke> morning all
[09:38] <alexarnaud> morning willcooke
[09:38] <duflu> Morning willcooke
[09:40] <didrocks> hey willcooke
[09:41] <duflu> seb128, I think you mean bug 1750846. And I meant bug 1707828
[09:41] <duflu> Probably only the former is relevant
[10:04]  * duflu gives up for the day
[10:04] <duflu> o/
[11:06] <willcooke> tjaalton, hi!  Are you aware of any issues preventing the installation of the nvidia drivers atm?  Seen a report from flexiondotorg  that 390.42 is reporting a broken package
[11:08] <flexiondotorg> willcooke tjaalton I've just purged all nvidia drivers/libs and install completed.
[11:08] <willcooke> ah, kk
[11:08] <flexiondotorg> `ubuntu-drivers autoinstall` - worked.
[11:12] <flexiondotorg> willcooke: tjaalton However, still no display manager with nvidia drivers install on hybrid graphics laptops.
[11:13] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226
[11:13] <tjaalton> flexiondotorg: that was due to the new mutter though,right?
[11:13] <flexiondotorg> tjaalton: Ubuntu MATE here. No mutter.
[11:14] <tjaalton> ok, dunno what's wrong then
[11:15] <flexiondotorg> The bug a referenced has details.
[11:15] <tjaalton> tseliot is off this week
[11:25] <willcooke> Under virtualbox, if you suspend via the top-right menu (hold down on the power button) you can't then resume it again.  Seems to be a generic linux problem.  Could we detect if you're on a virtual machine and hide that option?
[11:48] <willcooke> wow, fuill session crash on Artful running xorg
[11:48] <seb128> willcooke, what about fixing the kernel instead? ;)
[11:50] <willcooke> seb128, well, yeah, but in the meantime
[11:50] <willcooke> s'no biggy.
[11:51] <seb128> we could but I would rather spend those efforts fixing an actual bug
[11:51] <seb128> but you are the one deciding
[11:51] <seb128> open a bug/milestone if you think it we needs that hack
[11:51] <seb128> ?
[11:51] <seb128> Laney, thx for gnome-online-accounts, that worked!
[11:51] <seb128> andyrock, ^ g-o-a with the sso provider and software-properties are in bionic proper now
[12:02] <andyrock> seb128: thanks!!
[12:02] <seb128> andyrock, np, thanks to L_aney as well for unblocking the autopkgtest issue
[12:02] <andyrock> in the mean while I've been working on libgtop to hide snaps from gnome-system-monitors
[12:03] <andyrock> I'll propose an upstream patch now
[12:03] <andyrock> and a distropatch after upstream's review
[12:03] <andyrock> we'll need an additional distropatch considering that this will not work for "old" snaps
[12:04] <seb128> andyrock, great, thanks
[12:05] <seb128> andyrock, you are also working on livepatch in the wizard? ;)
[12:05] <andyrock> I'll start just after this
[12:06] <seb128> cool
[12:09] <jbicha> good morning
[12:10] <jbicha> seb128: btw, some people noticed this change and didn't like it https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/2fdb48fa
[12:11] <jbicha> there are a few things that don't work as well: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22
[12:11] <seb128> hey jbicha
[12:11] <seb128> jbicha, "people" like ubuntu users? what is the complain they are having?
[12:11] <jbicha> one complaint is from desktop users who think their computer should never suspend
[12:12] <jbicha> the other is that if no one is logged in to GDM, the machine will auto-suspend and there is no gui way to stop it doing that
[12:12] <seb128> right
[12:13] <jbicha> personally, I'm happy with the new default here
[12:14] <jbicha> Phoronix did an article this weekend complaining about it (the author was apparently not aware it was a GNOME change)
[12:14] <seb128> let's wait to get extra feedback but I can see how some users can dislike it (I don't like that default personnally) ... do you know what other platforms (win10, macOS) do?
[12:14] <seb128> shrug
[12:15] <willcooke> and indeed if you're running in a VM, then it'll screw you because you can't resume
[12:15] <jbicha> willcooke: I think it might be smart enough to detect that case. Someone should try though…
[12:15] <seb128> lol
[12:16] <seb128> willcooke, is that even a reported issue?
[12:16] <willcooke> seb128, it's about to be :)
[12:16] <seb128> hehe
[12:16] <willcooke> I was trying to decide if I should log it against gnome-shell or kernel.  I guess both.
[12:16] <seb128> jbicha, I think willcooke just pointed out that it's not
[12:17] <willcooke> well, you *can* suspend on a virtualised machine by holding down the power off button
[12:17] <jbicha> willcooke: um, I'm thinking gnome-settings-daemon instead of gnome-shell
[12:17] <willcooke> in the top right corner
[12:17] <willcooke> kk, I'll start with g-s-d
[12:18] <willcooke> the resume issue is a kernel bug though I think
[12:22] <willcooke> seb128, jbicha https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1758896
[12:23] <seb128> willcooke, thx
[12:23] <jbicha> I'm checking point 3…
[12:25] <willcooke> Laney, does your xps 13 have an nvidia card?
[12:25] <Laney> no
[12:25] <willcooke> kk, thx
[12:26] <Laney> sozzles
[12:42] <jbicha> willcooke: um, what VM are you using?
[12:44] <jbicha> willcooke: ok, in VirtualBox, try the menu > Machine > ACPI Shutdown to resume after suspending
[12:45] <jbicha> not very intuitive but it sort of makes sense :(
[12:50] <jbicha> with VM, I get a notification "Automatic suspend   Computer will suspend very soon because of inactivity." (but it's lying because it doesn't actually auto-suspend
[13:05] <willcooke> jbicha, ah yes, that worked, nice one.  Could be invalid then
[13:05] <willcooke> that bug I mean
[13:05] <jbicha> I commented on the bug. You're welcome to close it or whatever :)
[13:05] <willcooke> Whether or not we ship the default 30 mins timeout is a different matter. FWIW, I dont think we should in the standard image.  OEM team might *have* to ship it, if they want energy star
[13:06] <jbicha> (20 minutes)
[13:06] <jbicha> why do you think we should disable auto-suspend?
[13:12] <seb128> jbicha, do you know what other platforms are doing (win10, macOS)?
[13:14] <jbicha> seb128: no, sorry
[13:19] <seb128> jbicha, I think windows does autosuspend but wakes up on keyboard/mouse activity so it's transparent to users, where under linux you need to press the power button which is sort of WTH
[13:19] <seb128> users expect to be able to go back to their desktop and use it
[13:20] <seb128> imho unless we make keyboard/mouse events resume the machine we should disable autosuspend by default
[13:23] <willcooke> I have a machine that can resume from USB events, I had to frig about with the kernel to make it work - so I think it can be done.
[13:24] <seb128> not likely something for this cycle though
[13:24] <willcooke> yeah, totally
[13:24] <jbicha> seb128: could you open a tracking bug for this issue?
[13:25] <seb128> jbicha, well that's just my personnal opinion, unsure I'm right
[13:25] <jbicha> I assume we would override from ubuntu-settings if we do want to change the default
[13:25] <seb128> right
[13:25] <jbicha> maybe discuss in tomorrow's meeting then
[13:26] <seb128> +1
[13:28] <jdstrand> seb128: hey. it seems like in bionic there is some churn wrt synaptics touchpads. I have one and natural scrolling and middle click don't work right. I used to use an xorg.conf.d file to fix this, but as of updates in the last few days, that is now not working
[13:29] <jdstrand> seb128: what should I be doing to adjust natural scrolling and middle click?
[13:29]  * jdstrand notes that gnome-tweaks and gnome-settings doesn't work
[13:30] <mgedmin> apt remove xserver-xorg-input-synaptics?  gnome-settings only works with the libinput driver
[13:31] <jbicha> jdstrand: are you using Wayland?
[13:31] <jdstrand> mgedmin: I read that Ubuntu was patching 18.04 to allow it to work
[13:31] <jdstrand> jbicha: I went back to X11
[13:31] <jdstrand> because wayland broke middle click in a way that wouldn't work any more
[13:31] <jbicha> jdstrand: yes, Synaptics should work work with the X11 Ubuntu/GNOME sessions now
[13:32] <jdstrand> keep in mind, my info is a week or two old
[13:32] <jdstrand> (background info that is)
[13:32] <jdstrand> right
[13:32] <jbicha> the natural scrolling switch in gnome-control-center worked for me when I tried it with synaptics on Ubuntu on X11 earlier
[13:33] <jdstrand> jbicha: what does 'should work with the X11...' mean? it should work from the settings guis?
[13:33] <jbicha> yes
[13:33] <jdstrand> let me try again. it did *not* before
[13:33] <jbicha> we updated mutter and gnome-control-center for that so be sure you upgraded and at least restarted your session since then
[13:35] <jdstrand> yeah, I restarted today
[13:37] <seb128> jdstrand, hey, what doesn't work with gnome-tweaks?
[13:40] <seb128> jdstrand, it's being discussed in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686081
[13:43] <jdstrand> seb128: sorry I was rebooting
[13:44] <kenvandine> Trevinho, http://paste.ubuntu.com/p/kd7MRzf564/
[13:44] <kenvandine> Trevinho, is that along the lines of what you were suggesting?
[13:44] <jdstrand> jbicha, seb128: I moved my xorg.conf.d settings to the side, restarted and natural scrolling seems to work ok now.
[13:44] <seb128> good
[13:44] <jdstrand> jbicha, seb128: middle click does not
[13:44] <seb128> jdstrand, tried to two fingers tap?
[13:44] <jbicha> please be more specific about middle click
[13:44] <seb128> or 3 fingers?
[13:45] <jdstrand> two fingers tap doesn't work
[13:45] <jdstrand> two fingers click doesn't work
[13:45] <seb128> jdstrand, GNOME changed https://git.gnome.org/browse/gsettings-desktop-schemas/commit/?id=77ff1d9
[13:45] <seb128> unsure if that's your issue
[13:45] <jdstrand> 3 fingers tap doesn't work
[13:46] <seb128> :/
[13:47] <jdstrand> because none of this used to work afair, I used to configure the touchpad to change the 'dimensions' of the left and right click on the touchpad to create a space for a middle button
[13:47] <seb128> jdstrand, does it make any difference if in tweaks -> keyboard & mouse ->  mouse click emulation you select "area"?
[13:47] <seb128> ah :/
[13:47] <jdstrand> this morning, that stopped working. I don't expect it wo work now that I moved my xorg.conf.d aside
[13:48] <seb128> jdstrand, open a bug on mutter as duflu suggested on the gtk bug I pointed out earlier
[13:48] <seb128> jdstrand, his hack to make "synaptics handled" limited how it's being handled it seems
[13:49] <jdstrand> seb128: 'area' would be *exactly* what I want, but it isn't working :\
[13:49] <seb128> sounds like a driver issue in your case :/
[13:50] <seb128> jdstrand, can you get it to work by settings the properties by hand using "synclient" after the session start?
[13:51] <seb128> like "synclient RightButtonAreaLeft=0"
[13:51] <jdstrand> seb128: it looks like the switch from fingers to area back to fingers reset stuff
[13:51] <jdstrand> and now 2 and 3 finger tap works
[13:52] <seb128> :/
[13:52] <seb128> can you restart your session and see if it still works?
[13:52] <seb128> or if you need to switch forth/back to have it working?
[13:52]  * jdstrand restarts
[13:55] <jdstrand> seb128: restarting the session with just 'fingers' and 2 and 3 finger tap no longer works
[13:55] <seb128> and if you change to area and back to fingers now?
[13:55] <jdstrand> meh, gnome-tweaks says it is area
[13:55] <jdstrand> jeez
[13:56]  * jdstrand wonders why it didn't remember that I put it back on fingers
[13:57] <jdstrand> to be clear, on session start it was in area even though on session exit it was on fingers
[13:57] <jdstrand> I changed to fingers and 2 and 3 finger tap works
[13:57] <jdstrand> with area right click worked, but not middle
[13:58]  * jdstrand restarts session again
[13:58] <seb128> jdstrand, gsettings get org.gnome.desktop.peripherals.touchpad click-method
[13:59] <seb128> that's where the config is set
[14:00] <jdstrand> ok, this time the restart and it stayed on fingers
[14:00] <jdstrand> not sure what happened before
[14:00] <seb128> and 2/3 fingers click worked?
[14:01] <jdstrand> gsettings get says 'fingers' and 2/3 fingers worked
[14:01] <jdstrand> yes
[14:01] <seb128> k
[14:01] <seb128> well then you are in the "normal" situation
[14:01] <jdstrand> yes
[14:01] <seb128> unsure what to report from your previous issues :/
[14:01] <jdstrand> I can work with that
[14:01] <jdstrand> but, can say that 'area' would be preferred but only right click is working there
[14:02] <seb128> there is a bug worth filling that there is no way to set custom properties for synaptic now
[14:02] <seb128> that used to work
[14:02] <seb128> but now seems mutter override the config on start
[14:02] <jdstrand> seb128: where to file a bug?
[14:03] <seb128> jdstrand, https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686081/comments/36
[14:04] <seb128> well that has the details of what duflu said and the url
[14:04] <seb128> so you have the context :)
[14:04] <jdstrand> seb128: would 'ubuntu-bug mutter' be good?
[14:05] <seb128> yes
[14:14] <Trevinho> kenvandine: yeah, plus add a .stanp file to detect changes
[14:15] <Trevinho> like an user set a different path for its download files, that file needs to be updated
[14:24] <jdstrand> seb128: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1758929
[14:24] <seb128> jdstrand, thx
[14:45] <k_alam> jbicha: I found a regression with libvte. https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1758918
[14:47] <kenvandine> Trevinho, thx
[14:55] <jbicha> k_alam: Do you happen to have budgie-desktop-common installed (or did you?)
[14:55] <kenvandine> Trevinho, should the .stamp file be to monitor when user-dirs.dirs and user-dirs.locale changes?
[15:02]  * Laney loves casper-bottom
[15:02] <Laney> best environment around
[15:02] <Laney> we should just ship that
[15:06] <GunnarHj> Hi Laney, my thought with using your branch as the target for the g-c-c proposal was that it could be added as additional commits to your merge request. After all they are closely related. Is that not a good idea?
[15:06] <Laney> Sure, that makes sense
[15:06] <Laney> I don't think the Launchpad bug is not fixed though
[15:07] <GunnarHj> Laney: So then I keep the target branch, add the C code stuff, and file a new LP bug?
[15:09] <Trevinho> kenvandine: yeah... Maybe an md5 check or just the changed date. And also real home change could be tracked
[15:09] <Laney> GunnarHj: Sure. I mean, we can fix more bugs by updating a previous patch, that's no problem.
[15:09] <GunnarHj> Ok.
[15:11] <GunnarHj> Laney: On a quite different topic: Did you ever fix systemd so it's able to handle the im-config service? Or should we keep the hacks in 18.04?
[15:12] <Laney> GunnarHj: I did quite a bit of work on it a few weeks ago, but it's not finished yet, that's an 18.10 / 3.30 topic now
[15:12] <kenvandine> Trevinho, yeah, i was thinking md5sum would be simpler
[15:13] <kenvandine> and fast
[15:13] <GunnarHj> Laney: I see. Initially I felt that the hacks were a bit fragile, but OTOH noone has complained yet, so  it's probably fine.
[15:14] <kenvandine> Trevinho, any suggestions how we can access Trash?
[15:14] <kenvandine> there isn't an XDG variable for that
[15:14] <Laney> GunnarHj: I think it's OK enough
[15:15] <Laney> it's what snapd uses to put itself in $PATH too so it better work ;-)
[15:16] <kenvandine> wow, and md5sum of user-dirs.dir is much faster than a stat to get the modification time
[15:16] <Trevinho> kenvandine: mh, mhmh i think trash should be per snap though
[15:16] <kenvandine> Trevinho, that's fine... right now it blows up
[15:17] <Trevinho> kenvandine: mh, what app can I use for testing it?
[15:17] <kenvandine> actually, if it's per-snap, how do you ever empty it
[15:17] <kenvandine> gedit
[15:17] <Trevinho> Eh... We need to change gio for that very likely
[15:17] <kenvandine> that's what i was afraid of :(
[15:17] <Trevinho> From file opener o mean?
[15:17] <kenvandine> yes
[15:18] <Trevinho> Mhmh..
[15:18] <kenvandine> i don't think it's even useful in the file selector
[15:18] <Trevinho> Not sure, but I think there's a way to disable it
[15:18] <kenvandine> i'll look
[15:19] <Trevinho> kenvandine: however consider that trash should work as it does for removable devices IMHO
[15:20] <kenvandine> indeed... but users might end up having large files in per-snap trash
[15:20] <kenvandine> and never empty the trash
[15:35] <jbicha> seb128: please look into adding bug subscribers for libbluray & libnfs LP: #1746598 LP: #1746629
[15:42] <jbicha> LP: #1740700 is a design issue. Should we wontfix it? Ask him to start a Community Hub topic?
[16:07] <willcooke> jbicha, more of an upstream issue isnt it?
[16:08] <jbicha> willcooke: no, the Rhythmbox behavior is an Ubuntu-specific patch
[16:08] <willcooke> ah
[16:08] <jbicha> it's supposed to be helpful but it confuses people too
[16:08] <willcooke> strange decision on our part there then
[16:08] <willcooke> yeah, confusing
[16:09] <willcooke> lemme see if I can find m_pt
[16:11] <willcooke> jbicha, found him.  Yeah he said that it's there because of the sound menu being promoted as a feature, but since that's not there any more, then he's OK to drop the patch.
[16:11] <willcooke> One less patch seems like a good idea
[16:12] <jbicha> oh cool
[16:12] <jbicha> seb128: ^ does that sound good to you too?
[16:12] <willcooke> I'm not espeically precious about it, but I guess it's a bit risky this late in the cycle
[16:12] <willcooke> but yeah, given a vote... +1 to drop
[16:13] <willcooke> gotta get a train, might be back online from the train if I get a seat
[16:34] <kenvandine> Trevinho, when you have time, please look at that PR again
[16:35] <didrocks> good evening
[16:52] <ximion> Laney: I might have found the magic bullet to make asgen's memory consumption sane
[16:53] <ximion> on Debian for the past two days, it is consuming almost all memory the machine has, but never more (and also frees memory if you launch something else), as I would expect the thing to behave
[16:55] <ximion> tweaking the code to pass more containers by reference, reserving memory a bit smarter, and most importantly using malloc allocator-backed HashMap/HashSet containers
[16:56] <ximion> seems to have been the thing to do
[16:56] <ximion> I'll need to see this run for longer and with more complex workloads (fonts!) though to really celebrate - it looks quite promising so far though
[17:19] <oSoMoN> chrisccoulson, chromium-browser 65.0.3325.181 is ready for publication to trusty, xenial and artful in the stage PPA
[17:35] <jbicha> andyrock: I enabled livepatch via software-properties and it installed from the edge channel. Do you have a plan for how to get users on to the stable channel?
[17:43] <ahasenack> hi, I'm being hit by https://gitlab.gnome.org/GNOME/gnome-control-center/issues/22, but my use case isn't listed there. I have spotify playing in the foreground, and after 20min the computer just suspends. Is this the same bug, or something else?
[17:44] <jbicha> ahasenack: I think that's https://bugzilla.gnome.org/show_bug.cgi?id=705942#c21
[17:44] <jbicha> which is related fallout from that change
[17:45] <ahasenack> thx, I'll subscribe to both
[17:49] <andyrock> jbicha: nope
[17:49] <andyrock> hopefully before release
[17:51] <jbicha> andyrock: would it be better to switch software-properties to use stable now so that there are less people potentially stranded on edge?
[17:53] <jbicha> or if not, could whoever runs that snap at least promote the bionic fixes to candidate or beta? edge sounds risky
[17:54] <andyrock> we just wanted to get some testing
[17:54] <andyrock> I'll ask tomorrow again what their timeline
[17:54] <jbicha> thanks
[17:55] <andyrock> also because we need this for the ubuntu-welcome thing
[18:07] <seb128> jbicha, yeah, rhythmbox seems a design issue to wontfix
[18:08] <seb128> jbicha, k for the MIRs
[18:08] <seb128> cyphermox, did you actually review those or are you just looking if a team is subscribed (and if so what's the goal behind just doing that check?)
[18:09] <jbicha> seb128: did you see Will's follow-up about possibly dropping the rhythmbox quit patch?
[18:09] <seb128> jbicha, no, where?
[18:10] <seb128> ah, I saw now
[18:16] <cyphermox> seb128: I reviewed it, why?
[18:21] <cyphermox> note, I'm interpreting "those" as meaning libbluray, the last thing I reviewed, because otherwise I don't know what you're referring to
[18:40] <seb128> cyphermox, right, sorry j_bicha listed libnfs as well and I though it was in the same category ... anyway, if you did a review and that' the only issue it would be nice to mention that in the comment, the 1 liner now doesn't convey that it was reviewed, just that it was bounced as incomplete due to the bug subscriber missing
[18:42] <seb128> cyphermox, also I really need to start that discussion with the MIR team about team subscriptions happening upfront, I think it would make more sense to do that in between accepted & promoted
[18:46] <andyrock> jbicha: I just asked. They're working on it (my guess is ~3 days)
[18:47] <jbicha> andyrock: ok, and do you think we should wait until then to do the software-properties upload to change the channel?
[18:48] <andyrock> yep
[18:48] <jbicha> ok
[18:49] <andyrock> the important thing is that we patch it before beta freeze
[18:49] <andyrock> final beta freeze
[18:49] <andyrock> so iirc next monday
[18:53] <seb128> jbicha, so yeah, unsure about rhythmbox, we need to look at the pro&con and what users like/dislike about it
[18:53] <jbicha> drop the patch and count up how much hate mail we get? ;)
[18:54] <jbicha> maybe we can discuss it at tomorrow's meeting then
[18:57] <seb128> we drop patch/do behaviour changes at the start of the cycle, not after feature freeze :/
[18:57] <seb128> but yeah, we can discuss that tomorrow
[19:00] <jbicha> ahasenack: how are you running Spotify? is it installed? is it a Snap?
[19:01] <ahasenack> jbicha: I used a snap
[19:02] <jbicha> ahasenack: there is an inhibit-suspend thing Spotify could set. I don't know if Snap has an interface for that… maybe you can try following up on that?
[19:02] <ahasenack> hm
[19:02] <ahasenack> what I could do is install the non-snap and see if the problem still happens
[19:03] <jbicha> ok
[19:05] <seb128> jbicha, snapd has at least a screen-inhibit-control interface, unsure if that's enough thoguh
[19:06] <jbicha> cool, do you know any apps that use that?
[19:06] <seb128> jbicha, vlc
[19:06] <ahasenack> hm, the deb wants to install libcurl3
[19:07] <ahasenack> but bionic is on libcurl4
[19:07] <ahasenack> yeah, their deb is not really installable on bionic these days
[19:10] <jbicha> ahasenack: ok, I verify that spotify is not using screen-inhibit-control but vlc does
[19:10] <ahasenack> how did you check that, out of curiosity?
[19:10] <jbicha> snap interfaces
[19:10] <ahasenack> so there is an interface for that?
[19:10] <jbicha> (after installing spotify and vlc)
[19:10] <ahasenack> ah, I see it
[19:11] <ahasenack> good to know
[19:11] <jbicha> meanwhile, I opened LP: #1759008 and set rls-bb-incoming so we can think about auto-suspend-by-default more tomorrow
[19:12] <seb128> if spotify tries to inhibit using that dbus interface it should lead to apparmor denies in the logs
[19:12] <seb128> jbicha, thx
[19:12] <seb128> ahasenack, you can probably install the libcurl3 deb on bionic
[19:13] <ahasenack> it removes whoopsie
[19:13] <ahasenack> but there were other deps
[19:14] <ahasenack> libavformat-ffmpeg56
[19:14] <seb128> :/
[19:20] <seb128> ahasenack, btw that's a nice example of snap benefits :)
[19:20] <seb128> no deps issues
[19:20] <ahasenack> yeah
[19:21] <ahasenack> it took 1min to start, but just the first time
[19:21] <ahasenack> haven't rebooted yet, though
[19:37] <GunnarHj> jbicha: Any chance you can make a non-change rebuild of simple-scan as an attempt to address bug #1758956?