[06:01] <ricotz> chrisccoulson, hi, you can find a tarball for thunderbird 52.9.0 here https://launchpad.net/%7Emozillateam/+archive/ubuntu/ppa/+packages
[07:28] <seb128> good morning desktopers
[07:34] <jibel> hi seb128
[07:40] <seb128> lut jibel
[07:42] <seb128> jibel, thanks for the testing on bug #1778817
[07:53] <duflu> Morning seb128, jibel. Anyone feel the need for a BT meeting?
[07:56] <seb128> duflu, hey, I don't, I'm currently looking at your bionic SRU but that's the only bluetooth thing I've been dealing with recently. do you?
[07:56] <duflu> seb128, no, nothing. I guess you could count the PulseAudio12 update too
[07:56] <duflu> Almost nothing
[07:56] <seb128> I need to look at that MIR
[07:56] <seb128> it's on my todo as well :)
[07:57] <duflu> I could drop the prereq but it's been requested since last year
[07:57] <seb128> let's skip the bluetooth hangout then, willcooke is having computer issues apparently so he's not around
[07:57] <seb128> seems like we don't like full disks
[07:59] <seb128> duflu, the update can stay in proposed for a bit while the MIR is sorted out, let's try to move forward and get the issue resolved rather than workaround around
[07:59] <jibel> Hi duflu , I've nothing for the meeting.
[07:59] <jibel> seb128, I'm trying to reproduce the 1st part of the bug now.
[08:00] <seb128> k
[08:02] <duflu> Hmm, mutter's timing is still terrible. Even complex animations render in under 3ms and I can't get it to run faster than 43 FPS
[08:02] <Laney> moin
[08:02] <duflu> Morning Laney
[08:03] <willcooke> BOOOOOOOOOOOM
[08:03] <willcooke> Fixed
[08:03] <duflu> Morning willcooke
[08:03] <willcooke> afternoon duflu
[08:03] <seb128> hey Laney willcooke
[08:04] <willcooke> We need to look in to how we can make things less bad when you run out of disk space
[08:04] <seb128> willcooke, rm ~/Videos/somepornmovies? ;)
[08:04] <willcooke> I won't delete my porn for anyone
[08:04] <willcooke> So, fun story
[08:04] <willcooke> I had a Raspberry Pi which was running some house services stop working yesterday
[08:05] <willcooke> Couldnt get the thing to boot at all, so I took the SD card out and tried to mount it here
[08:05] <willcooke> The thing was screwed
[08:05] <willcooke> I used disktest to recover some files which was very slow, so after the football finished I just left it running over night
[08:05] <willcooke> This was an 8GB SD Card
[08:06] <willcooke> testdisk must have got in to some strange loop
[08:06] <willcooke> the recovered folder (after I delete a 14GB postfix spool file) is......
[08:06] <willcooke> (still counting)
[08:06] <alexarnaud> Morning willcooke seb128 andyrock jbicha Trevinho duflu and all
[08:07] <willcooke> ((I think there must be some horrible recursive directory in itself thing going on)
[08:07] <willcooke> )
[08:07] <willcooke> 26 GB
[08:07] <willcooke> so 40GB of files on an 8GB SD card
[08:07] <willcooke> ?!
[08:07] <willcooke> anyway, left it running over night, came down this morning, couldn't unlock my machine
[08:07] <willcooke> couldnt switch to a different vt
[08:08] <duflu> A couple of users report their disks get filled with gigabytes of gnome-shell logging. I can't reproduce it myself
[08:08] <willcooke> could get it to boot in to single user mode
[08:08] <willcooke> and it wouldn't boot normally, lots of errors about things not starting
[08:08] <willcooke> as you might expect
[08:08] <willcooke> so I had to boot of a USB stick in to live mode and delete a few files,
[08:09] <willcooke> then everything came back to life
[08:09] <willcooke> It's totally my fault that the disk filled up
[08:09] <willcooke> but I think we need to try and make it more tolerant to such situations
[08:09] <willcooke> for the list next cycle.
[08:09] <willcooke> THE END
[08:10] <willcooke> didrocks, you missed my exciting story
[08:10] <jibel> is anyone else seeing a snapd timeout on boot of bionic ?
[08:10] <didrocks> willcooke: the one you started on telegram about full disk?
[08:10] <jibel> didrocks, hi, I'm reviewing the sru of ubuntu-report. Where is the report stored again?
[08:10] <willcooke> jibel, yes, but I put that down to disk being full.  Seems ok now
[08:10] <willcooke> didrocks, yeah
[08:11] <seb128> I didn't for snapd
[08:11] <jibel> willcooke, I'm seeing it on a fresh installation
[08:11] <willcooke> jibel, yeah seems to be working ok now
[08:11] <seb128> lut didrocks
[08:11] <willcooke> jibel, I'll fire up a VM
[08:11] <willcooke> jibel, in fact, I will install my other laptop with the iso I just downloaded
[08:11] <seb128> willcooke, disk full handling was something we worked on the past, but another of those topics were we don't have regular testing and that we regressed of the cycles
[08:12] <duflu> willcooke, don't need to fix everything, but making the machine boot and the GUI not freeze would itself be a significant challenge. People write new code that isn't tolerant of it all the time. Even writing a log message to the disk could hang everything if done wrong
[08:13] <willcooke> duflu, yeah I expect fixing everything would be impossible, but we should be able to make it better.  Not being able to get to a shell if your disk is full SUCKS
[08:14] <duflu> Yeah, people report all sorts of failures (in bug reports) when it happens to them
[08:14] <willcooke> I'm sure we used to do something which would stop you being able to fill your disk more than 95%
[08:16] <didrocks> salut seb128
[08:19] <Laney> willcooke: you're probably thinking of the ext4 reserved block count
[08:19] <Laney> root can write to that though
[08:19] <Laney> moin didrocks
[08:21] <didrocks> hey Laney
[08:21] <jibel> willcooke, by default there is 5% of  the blocks reserved for privileged processes
[08:22] <jibel> tune2fs -l <dev> will tell you how much on your system
[08:24] <seb128> willcooke, https://wiki.ubuntu.com/BootLoginWithFullFilesystem
[08:24] <seb128> is what we did in the past
[08:25] <seb128> so I think it's one of those polish feature that would be nice to work on
[08:25] <seb128> we need to debug what components are having issues
[08:26] <Laney> yeh, that would be a nice task to do
[08:26] <willcooke> ah yeah, this process had to run as root
[08:26] <willcooke> I've added it to the list for next cycle anyway
[08:26] <seb128> good
[08:27] <seb128> like that spec ^ mentions
[08:27] <seb128> At boot time, check whether /tmp has at least 1Mby free. (This should be done after filesystems are mounted and after /tmp has been cleaned.)
[08:27] <seb128> If not, mount a 1Mby tmpfs over /tmp.
[08:27] <seb128> I bet we lost some of those things over time
[08:27] <willcooke> jibel, just booted a newly installed machine, snapd seems to be running ok
[08:27] <seb128> changing to systemd etc
[08:27] <Laney> that's going to touch foundations areas too
[08:27] <seb128> likely
[08:28] <Laney> which is a gentle way of me suggesting it for brussels :-)
[08:28] <seb128> willcooke, the fact that you said you couldn't get to grub sounds weird though
[08:28] <seb128> Laney, yeah, that's probably the right venue to discuss topics for next cycle
[08:28] <willcooke> I looked at the Brussels spreadsheet yesterday to see if I could add sessions, but not yet it seems.  Laney, if I forget can you try and remember?
[08:29] <seb128> willcook_e said he's putting it on the list
[08:29] <willcooke> I put it on the product roadmap list
[08:29] <seb128> willcooke, just put a google calendar reminder?
[08:29] <seb128> like for before Brussel with "add fulldisk boot to the agenda"
[08:29] <seb128> computers are good at those reminders :p
[08:30] <jibel> willcooke, and it booted reasonably fast?
[08:30] <willcooke> seb128, done
[08:30] <willcooke> jibel, yeah, seems fine
[08:31] <willcooke> jibel, I'll upgrade everything and try again
[08:31] <seb128> willcooke, :)
[08:32] <willcooke> didrocks, jibel - can you take a look at this post and see if we can help lubuntu & kubuntu with using ubuntu-report? https://community.ubuntu.com/t/extending-ubuntu-report/6851
[08:32] <willcooke> seb128, fyi ^
[08:32] <jibel> willcooke, which image did you use?
[08:33] <jibel> daily or release?
[08:33] <willcooke> jibel, release
[08:33]  * willcooke downloads daily
[08:33] <jibel> willcooke, I had this issue with the daily image
[08:33] <didrocks> willcooke: I'm in the board meeting, is it something to be done today?
[08:33] <seb128> willcooke, I saw that discussion yesterday evening, thanks for the ping though :)
[08:34] <willcooke> jibel, will try again.  Yesterday Mark Murphy pinged to stay he couldnt get networking in a vm on the daily image too, but said he would try some stuff and report back, but didnt
[08:34] <willcooke> didrocks, whenever you get time
[08:34] <willcooke> I dont think there is an immediate rush
[08:35] <didrocks> sure
[08:35] <willcooke> jibel, this one?  http://cdimage.ubuntu.com/xenial/daily-live/current/xenial-desktop-amd64.iso
[08:35] <willcooke> didrocks, merci
[08:35] <duflu> jibel, are the daily images installing yet? Last I tested 20180627 which was "current" it would crash on both systems I tried
[08:36] <duflu> (a long way into installation)
[08:36] <seb128> duflu, bionic or cosmic?
[08:36] <duflu> seb128, cosmic daily
[08:36] <seb128> duflu, they are talking about bionic there
[08:36] <duflu> ok
[08:36] <jibel> duflu, yes
[08:36] <seb128> but cosmic should work
[08:37] <seb128> do you have a report of the problem you hit?
[08:37] <duflu> seb128, no, it was late at night and I had too many things to deal with
[08:37] <jibel> seb128, it was a problem with missing efi files
[08:37] <seb128> k, no worry
[08:37] <seb128> seems like it's known anyway from what jibel just said
[08:37] <jibel> then grub failing to remove some files
[08:37] <duflu> That was a different bug with efi. I'm talking about a new issue after the fix
[08:38] <seb128> jibel, "was" so it's fixed now?
[08:38] <seb128> ah
[08:38] <duflu> Nevermind. When I get time I'll try fresher images
[08:39] <jibel> duflu, there was a dependency issue with grub that the installation fail. It's fixed now but if there is anything else please file a report and i'll have a look
 willcooke, the fact that you said you couldn't get to grub sounds weird though
[08:50] <willcooke> I think that is probably because my laptop starting thinking the shift key was stuck and ignored it
[08:50] <willcooke> but I couldnt fix it by powering off and back on
[08:50] <willcooke> I'd still say it's a laptop issue rather than a software issue.  I'll play around when I get time
[08:51] <seb128> k, that would make sense
[08:52] <seb128> it's likely that the ENOSPACE issue start with gdm/login manager
[08:52] <seb128> as that was the case in the gutsi time when we first looked at it
[08:52] <seb128> probably similar reason, some auth file that needs to be written on disk and can't
[08:57] <ricotz> hey desktopers
[08:58] <seb128> hey ricotz
[08:58] <ricotz> there seems to be some delay regarding libreoffice updates
[08:59] <willcooke> gah. stupid idiot.  I downloaded the xenial image.
[08:59] <ricotz> is there a need for a prepared libreoffice 6.0.5 package?
[08:59] <ricotz> see https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages
[09:04] <seb128> ricotz, right, our maintainer is on paternity leave and we don't have enough resources to have backup maintainers :/ I guess any help on getting the updates ready will make the work easier once he's back
[09:05] <ricotz> seb128, so you want to wait for him to come back before pushing an update?
[09:06] <seb128> "want" is a bit strong
[09:06] <ricotz> I have pushed the relevant changes to the packaging branches so it is there to be picked up
[09:06] <seb128> I don't think we have a choice
[09:06] <ricotz> ok
[09:07] <seb128> ricotz, I just looked at our calendar, Olivier is supposed to be back tomorrow
[09:07] <ricotz> (libreoffice 6.1 rc will be available this week which is the target series for cosmic)
[09:07] <seb128> so not long to wait
[09:07] <ricotz> ah good then
[09:08] <seb128> then I guess he's going to have some backlog so unsure what his priorities are, but I guess getting libreoffice updated is going to be on his list
[09:08] <ricotz> alrighty
[09:46] <willcooke> woo.  Hard lock up
[09:46] <willcooke> (while still scanning that SD card)
[10:04] <willcooke> jamesh, ace job on the snap themes howto
[10:04] <jamesh> willcooke: hopefully we can cut down on the boilerplate once templates are a thing
[10:07] <jamesh> willcooke: is the screenshot I added to the blog draft okay?  It's hard to do something that doesn't just look like a file chooser
[10:08] <willcooke> jamesh, where am I looking?
[10:08] <jamesh> willcooke: the "Support for XDG Desktop Portals" section
[10:09] <jamesh> the 18.04.1 blog draft
[10:12] <willcooke> ah, got ya. yeah, that'll do nicely, thanks
[10:42] <willcooke> oh, jibel I forgot - installed daily and it seems fine.  What should I be looking for?
[10:53] <jibel> willcooke, is there any timeout for snapd in the journal?
[11:04] <jibel> willcooke, is it with bionic daily?
[11:04] <jibel> willcooke, this is the image I tried http://cdimage.ubuntu.com/bionic/daily-live/pending/
[11:04] <willcooke> jibel, http://cdimage.ubuntu.com/bionic/daily-live/current/bionic-desktop-amd64.iso
[11:05] <willcooke> will retry with pending
[11:06] <jibel> willcooke, it shouldn't make any difference.
[11:06] <jibel> willcooke, I'll have a look on my system
[11:06] <willcooke> I see snapd starting
[11:07] <willcooke> no obvious problems
[11:07] <willcooke> jibel, you want this log somewhere?
[11:10] <jibel> willcooke, yes please to compare with my boot. journalctl -b -o short-monotonic in a pastebin will be fine
[11:11] <willcooke> jibel, https://pastebin.com/eK0bDcsR
[11:15] <jibel> willcooke, thanks
[11:16] <jibel> seb128, no way to reproduce the screen lock during upgrade issue with 16.04 to 18.04. I tried with the garphical and text upgrader with a user or root and the screen lock is always inhibited. I'm wondering if I experienced it with 17.10 instead. I'll try that to confirm
[11:32] <Laney> nothing like a good tidy up rebase session
[11:32] <Laney> rearranged the stuff so there's all mergable things and then one small switchover commit
[11:32]  * Laney proposed
[11:32] <Laney> s
[11:39] <seb128> jibel, thanks for testing
[13:59] <seb128> do we have people around who are still on bionic and have livepatch enabled? do you see sometime notifications about livepatch updates?
[14:09] <willcooke> o/
[14:09] <willcooke> and no
[14:09] <Laney> I just enabled it
[14:09] <Laney> and it did Jul 04 15:09:00 nightingale canonical-livepatch[12007]: Applied patch version 40.7 to 4.15.0-23.25-generic
[14:09] <Laney> but I didn't get a notification, should I have?
[14:10] <Laney> oops I forgot to eat lunch, back soon
[14:23] <seb128> andyrock, ^
[14:23] <seb128> bug #1780093
[14:45] <seb128> Laney, oh, and thanks for testing and enjoy your lunch :)
[14:54] <Laney> was a good lunch
[15:08] <Laney> oh MY
[15:08] <Laney> I just learned about edit-and-execute-command
[15:08] <Laney> type a command and then hit ctrl-x ctrl-e in bash
[15:09] <Laney> probably one of those things that everyone knows about apart from me :-)
[15:10] <Laney> that and 'fc'
[15:28] <willcooke> oooooh
[15:28] <willcooke> nice
[15:59] <willcooke> Laney, your snapd blocking issue could be related to waiting for entropy
[15:59] <willcooke> m_vo is on the case, natch
[16:00] <Laney> o rly
[16:21] <Laney> seb128: did you want to try merging the latest gvfs upload(s) into git?
[16:21] <Laney> only noticed because it broke my hint :-)
[16:22] <Laney> been trying to push things through proposed on the side today
[16:48] <Laney> k, everything systemd --user is merge proposed now
[16:48] <Laney> early start for the train tomorrow, so o/
[16:48] <Laney> will try to be online from it
[16:48] <seb128> Laney, yeah, I noticed after doing the changes, but I wanted to get that SRU out today
[16:48] <seb128> I plan to read the git documentation from Didier while travelling tomorrow
[16:49] <seb128> then I can have a look to put that new knowledge in use
[16:49] <seb128> but feel free to merge that one for me if you need to pile up other changes, I'm sure I can find another one to do :)
[16:49] <seb128> Laney, well done, enjoy your evening and safe travel tomorrow
[16:50]  * seb128 has a plane at 7:45, going to be an early start so I'm going to wrap now as well
[17:31] <willcooke> night all, safe travels tomorrow