[06:36] <didrocks> good morning
[06:48] <didrocks> hum, my gdm GNOME Shell went crazy CPU wise
[06:49] <didrocks> can't reproduce it now though
[06:50] <duflu> Morning didrocks
[06:50] <duflu> Good or bad
[06:51] <oSoMoN> good morning desktoppers
[06:52] <duflu> Hi oSoMoN
[06:53] <didrocks> hey duflu & oSoMoN
[06:53] <duflu> didrocks, my user session gnome-shell used to do that occasionally. Stayed high for some time before dropping.
[06:53] <didrocks> :(
[06:55] <duflu> Maybe it was the old deferred garbage collection. And it hasn't happened since we started using much more frequent collection
[07:02] <oSoMoN> hey duflu, salut didrocks
[07:02] <oSoMoN> popey, is there a way to get rid of borders around small images in posts on discourse.ubuntu.com ? https://discourse.ubuntu.com/t/monday-1st-october-2018/8203/10 looks kind of ugly
[07:06] <duflu> oSoMoN, may try switching between inline and reference syntax?? https://daringfireball.net/projects/markdown/syntax#img
[07:07] <duflu> +be
[07:11] <duflu> didrocks, I wonder in 19.04 if using the Ubuntu purple wallpaper for the login screen might look nice, or terrible
[07:12] <oSoMoN> duflu, nah, I even tried BBCode and HTML tags, I guess the border is a CSS property applied to all small images, regardless of how they are defined
[07:13] <duflu> oSoMoN, including the old style <img .... border=0> ?
[07:13] <duflu> which is apparently deprecated in HTML 5
[07:18] <oSoMoN> ah, I didn't try that
[07:18] <oSoMoN> let's see
[07:21] <didrocks> duflu: we can't use wallpapers, due to multimonitor handling in gnome-shell/gdm being bad
[07:22] <oSoMoN> duflu, doesn't work either, nor style="border: 0", which I suppose makes sense, the CSS takes precedence over style attribute in HTML
[07:26] <Wimpress> Morning desktopers
[07:27] <duflu> Hi Wimpress. Can you answer oSoMoN's question about discourse? ^
[07:34] <oSoMoN> good morning Wimpress
[07:41] <seb128> good morning desktopers
[07:42] <Trevinho> Morning folks
[07:42] <oSoMoN> salut seb128
[07:42] <oSoMoN> buon giorno Trevinho
[07:42] <seb128> lut oSoMoN, en forme ?
[07:43] <jibel> duflu, hi, any idea about the problem with Optimus systems upgraded from 17.10 reported on https://community.ubuntu.com/t/cosmic-cuttlefish-18-10-beta-testing/8132/17 ?
[07:43] <seb128> hey Trevinho, how was Lille btw, I forgot to ask yesterday
[07:43] <seb128> lut jibel
[07:43] <jibel> Salut seb128
[07:43] <Trevinho> Merci oSoMoN y seb
[07:43] <didrocks> hey seb128
[07:43] <oSoMoN> seb128, peu dormi, mais oui, le contrecoup viendra après le déjeuner…
[07:43] <didrocks> morning Trevinho
[07:43] <seb128> lut didrocks
[07:43] <seb128> oSoMoN, siesta! :)
[07:43] <oSoMoN> I wish…
[07:43] <seb128> :(
[07:44] <seb128> good luck, they eventually do their nights one day :p
[07:45] <willcooke> andyrock, jamesh - updates please:  https://discourse.ubuntu.com/t/monday-1st-october-2018/8203
[07:45] <willcooke> morning
[07:45] <jamesh> willcooke: writing it now
[07:45] <willcooke> merci jamesh
[07:46] <jibel> I like this new format to report status updates BTW
[07:46] <willcooke> Excellent!  Me too.  I like oSoMoN's icons especially :)
[07:48] <duflu> Also, you can write your reports almost in changelog format. Only the third indent needs to be - and not .
[07:48] <oSoMoN> seb128, can't even blame the baby, I just went to bed late and then I couldn't sleep for some reason
[07:48] <duflu> jibel, I usually assume I know nothing about Optimus but will check that bug again
[07:49] <seb128> oSoMoN, ah ok, those happens too!
[07:50] <willcooke> anyone will a Dell E6430?  https://bugs.launchpad.net/nouveau/+bug/1683445  The OEM team don't have one
[07:50] <Trevinho> seb128: very nice... Sunny and tasty salamis there 😂. But really liked. Not touristy, and the place we had was really nice.
[07:50] <seb128> great
[07:50] <seb128> willcooke, I've a 6410 but it's intel only so I guess not good enough to test that bug
[07:51] <seb128> willcooke, why did they flag it "oem priority" if they can't even test it?
[07:51] <willcooke> seb128, No worries. I'm not sure what we do in this case,  the OP (I think) says he hasnt got the hardware, OEM dont have the hardware, so...
[07:51] <willcooke> indeed
[07:51] <willcooke> (brb, supermarket delivery)
[07:51] <seb128> we do validate that it has no regression I guess
[07:52] <seb128> the fix might not work but if it doesn't make things work
[07:52] <seb128> and it's supposed to work in theory...
[07:52] <oSoMoN> seb128, how would you feel about pushing LO 6.1.2 to cosmic now? (as opposed to SRUing it after release, which might end up being a SRU of 6.1.3, skipping 6.1.2)
[07:53] <oSoMoN> IIRC Bjoern used to play it safe and prepare a SRU for just after the release
[07:57] <seb128> oSoMoN, +1 from me for uploading now, I think Bjoern was over-cautious, especially for non LTS cycles
[07:58] <oSoMoN> ok, I'll prepare and upload today
[07:58] <seb128> great
[07:58] <oSoMoN> ricotz, FYI ^
[07:59] <ricotz> +1 :)
[07:59] <seb128> you also know libreoffice better than me, how is their testing/the stability of their stable serie updateS?
[08:01]  * Laney nods
[08:01] <willcooke> what up Laney
[08:04] <oSoMoN> hey Laney
[08:05] <oSoMoN> seb128, pretty good in my limited experience, stable series updates are really bugfix-only releases
[08:06] <seb128> hey Laney, how are you?
[08:06] <seb128> oSoMoN, good then :)
[08:07] <duflu> jibel, done and done
[08:08] <jibel> duflu, thanks
[08:09] <didrocks> popey: hey! do you mind adding jagger to the yaru / communitheme team? He did some good work on icons and the team +1 on his inclusino
[08:09] <didrocks> inclusion*
[08:14] <Laney> hi willcooke oSoMoN seb128
[08:15] <didrocks> even if he has some insane proposal sometimes: https://discourse.ubuntu.com/t/call-for-participation-an-ubuntu-default-theme-lead-by-the-community/1545/1798 (IMHO :p)
[08:15] <Laney> had an early night so i'm good today #thuglyf
[08:15] <Laney> sup
[08:15] <seb128> early night ftw!
[08:15] <seb128> (I did the same ;-)
[08:20] <willcooke> :)
[08:21]  * duflu looks forward to not being jet lagged
[08:21] <duflu> #hazylyf
[08:22] <Laney> coldlyf too
[08:22] <Laney> stupid autumn
[08:24] <didrocks> :(
[08:24]  * didrocks isn't completely out of it yet
[08:25] <seb128> of the jetlag between Lyon and Brussel? ;)
[08:25] <seb128> Lyon is so far south that it takes a while to adjust :p
[08:25] <didrocks> no, the cold :p
[08:25] <seb128> ah
[08:25] <seb128> :)
[08:25] <didrocks> still coughing
[08:26] <seb128> :(
[08:26] <seb128> get better!
[08:26] <seb128> the kid started sneezing this morning, it's that season again. I hope I'm not next on the list :/
[08:27] <didrocks> thx! yeah, good luck :(
[08:39] <jibel> does ubuntu-bug xserver-xorg works for anyone on cosmic?
[08:42] <didrocks> jibel: got the password prompt twice, but I'm on the send/don't send dialog
[08:42] <didrocks> and it seems the included info are correct
[08:42] <jibel> hm, it hangs forever here
[08:44] <jibel> didrocks, did you accept to attach DM logs?
[08:44] <didrocks> jibel: yes, I accepted both
[08:45] <jibel> weird, it's blocked on the execution of pkexec /usr/share/apport/root_info_wrapper /tmp/tmpo_kbx2jf/:script:
[08:45] <jibel> and :script: is empty
[08:45] <didrocks> DM logs is the first prompt, correct?
[08:45] <didrocks> (I have 2)
[08:47] <didrocks> so, first prompt -> yes -> password; second prompt (for nvidia) -> yes -> password
[08:48] <jibel> k, seems to be just me then. i'll search a bit
[08:48] <jibel> thx
[08:49] <didrocks> yw
[09:39] <willcooke> Suddenly my Cosmic machine wont boot to a greeter
[09:40] <ogra> it wants to be a server but is too shy to tell you
[09:40] <willcooke> :)
[10:08] <willcooke> Reinstall sorted
[10:08] <willcooke> I will do more testing
[10:12] <Trevinho> jibel: as per https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292 have you been able to reproduce this again? As I can't anymore it seems now while I lost my /var/crash file :-(
[10:13] <jibel> Trevinho, I haven't tried since last week. Let me start a VM with latest cosmic
[10:14] <jibel> Trevinho, I explained cypher_mox yesterday how to reproduce it but no news since then
[10:21] <willcooke> jibel, I'm seeing a segfault in network manager on Cosmic at start up - did you ever see that?
[10:23] <willcooke> it restarts and then seems ok
[10:23] <jibel> willcooke, no, I didn't
[10:24] <willcooke> different topic, why is colord lookin for MIB files?!
[10:37] <RAOF> willcooke: If I had to guess, it would be libsane doing something not quite.
[10:38]  * willcooke digs in the logs
[10:38] <tjaalton> didrocks: replied to vulkan review
[10:40] <Trevinho> jibel: ah, I got it again
[10:46] <jibel> Trevinho, me too
[10:47] <jibel> gnome-initial-setup is broken
[10:48] <jibel> it shows the online account page and skip or next buttons do nothinh
[10:48] <jibel> g
[10:48] <jibel> is it known?
[10:49] <jibel> andyrock, ^
[10:49] <andyrock> jibel: let me check
[10:50] <andyrock> jibel: last iso?
[10:50] <jibel> andyrock, fresh installation
[10:50] <jibel> andyrock, yes
[10:51] <Trevinho> jibel: also got it...
[10:52] <andyrock> jibel: i'll take a look
[10:52] <andyrock> works here when tested on a vm
[10:52] <andyrock> but not from the last iso
[10:54] <Trevinho> jibel: also found the issue :)
[11:01] <willcooke> heh, when I could finally get in to a working session g-i-s worked ok for me.  Odd.
[11:02] <willcooke> However, I can't get to a log in screen in a normal boot.
[11:02] <willcooke> jibel - before I do digging, you think that is known?  I boot and just get a flashing cursor
[11:02] <willcooke> tty on 2
[11:07] <willcooke> ok, I think that network manager issues was just a thing.  It looks ok now
[11:10] <willcooke> seb128, do you have your Inspiron to hand?
[11:11] <willcooke> Here's what I'm seeing:  Installed daily from yesterday  - all fine.  Boot machine, get to a black screen with a flashing cursor.  Got to tty2 look at syslog, all seems OK.  Got to tty<something between 3 and 7> a mouse pointer appears.  Go back to 1 and there is gdm.
[11:11] <andyrock> jibel: works fine here
[11:11] <willcooke> Without moving ttys, I just stick at the black screen
[11:12] <andyrock> jibel: I installed the last iso on a VM
[11:12] <willcooke> logout gets back to gdm
[11:12] <willcooke> andyrock, g-i-s working fine here too
[11:13]  * willcooke -> sandwich
[11:13] <willcooke> <- sandwich
[11:14] <andyrock> jibel: maybe something is preventing the click to go through?
[11:14] <andyrock> jibel: otherwise I'm happy to debug the issue if you send me the vm image
[11:23] <popey> didrocks: did you ping me somewhere? I saw it when on the train this morning, but can't find it now
[11:28] <dupondje> network-manager-gnome broke since the update this morning :(
[11:28] <dupondje> anyone e noticed this already? :)
[11:31] <willcooke> dupondje, ah, I noticed a segfault in n-m
[11:31] <willcooke> but might be unrelated.
[11:31] <willcooke> How is it broken for you?
[11:32] <dupondje> willcooke: dropdown doesn't show wifi networks anymore
[11:32] <willcooke> checking
[11:32] <willcooke> huh, and this time when I booted my machine I did get to gdm
[11:32] <dupondje> and I have VPN connections for example, those show, but if I click on one, it suddenly connected to another wifi network
[11:32] <dupondje> seems like something got randomized :D
[11:32] <popey> oSoMoN: fixed, no borders round images now. how does that look? :) https://community.ubuntu.com/t/monday-1st-october-2018/8203/10?u=popey
[11:33] <dupondje> neither it does show that I'm connected to a VPN, while I am (connected via the settings)
[11:33] <willcooke> dupondje, drop down not showing wifi networks - in GNOME Shell?
[11:33] <willcooke> 'cos I dont think the drop down ever did
[11:34] <dupondje> willcooke: gnome-shell / wayland yes :)
[11:34] <dupondje> well you can connect to another wifi via the dropdown ... ?
[11:35] <willcooke> From the indicator?
[11:41] <dupondje> willcooke: ofcourse? like https://i.stack.imgur.com/QVr1V.png
[11:41] <dupondje> https://dflinux.frama.io/thebeginnershandbook/img/deb9-wifi-gnome-1.png
[11:42] <dupondje> WiFi is gone now here :) in the indicator
[11:44] <willcooke> dupondje, can you check the logs and see if network manager crashed?
[11:44] <willcooke> I saw a seg fault this morning, but it seems OK now, and the indicator is working as expected
[11:45] <dupondje> willcooke: NetworkManager[1826]: corrupted double-linked list
[11:45] <dupondje> but it restarted afterwise :)
[11:46] <dupondje> seems to be something else. Yesterday it was fine, today its broken. Seems like only network-manager-gnome package could be the cause?
[11:47] <willcooke> I need to get my cosmic machine booting to gdm again and then I can look at this a bit more
[11:48] <willcooke> bear with me
[11:51] <Laney> dupondje: which version of gnome-shell?
[11:52] <dupondje> http://ubuntu.dupondje.be/bug.jpg -> this it how it looks like here :)
[11:53] <dupondje> Laney: 3.30.0-1ubuntu2
[11:53] <Laney> there were some fixes to network status reporting in 3.30.0-3ubuntu1
[11:53] <oSoMoN> popey, perfect, thanks!
[11:55] <dupondje> Laney: still in proposed I guess?
[11:55] <Laney> it'll migrate shortly
[11:56] <andyrock> can I propose a branch to only show desktop file from session-shortcut only in Unity?
[11:57] <andyrock> seb128, Laney ^^^
[11:59] <Laney> gnome-shell has its own versinos of those right?
[11:59] <dupondje> Laney: confirmed that resolved it! thx
[11:59] <dupondje> willcooke: ^
[11:59] <andyrock> Laney: yep, they got an-all-in-one button
[12:00] <Laney> ok with me then
[12:00] <Laney> dupondje: nice
[12:03] <seb128> andyrock, unity only sounds fine to me yes
[12:03] <andyrock> kk preparing a debdiff
[12:03] <seb128> willcooke, I do have the inspiron, I'm going to download the daily iso and do test installs on it
[12:04] <seb128> willcooke, that sounds a timing bug from what you describe, might have to do/be a bug in the new gdm which is stopping the greeter when not needed now (to not have another session in memory for nothing)
[12:04] <seb128> Trevinho, you got a fix for that plymouth issue? well done!
[12:04] <jibel> andyrock, I cannot send a VM image
[12:05] <jibel> it's several GB and will take days to upload
[12:05] <seb128> do you get any error on the command line if you start it manually?
[12:07] <jibel> andyrock, actually it seems to be a problem with xorg, the screen is not refreshing completely
[12:08] <jibel> if I minimize/restore the window it's as expected
[12:08] <andyrock> jibel: ah, yeah I wrote before that maybe something was preventing the click to go through
[12:09] <andyrock> try also to just move the window around
[12:12] <willcooke> seb128, yeah switching to tty2 and then back to tty1 brings up gdm
[12:13] <Laney> a debug log would be good (turn it on in /etc/gdm3/custom.conf, reproduce the bug and then grab the journal)
[12:13] <seb128> willcooke, can you maybe enable Debug=true in /etc/gdm3/gdm.conf, reboot, get the issue and open a bug with ubuntu-bug gdm3?
[12:13] <Laney> IW IN
[12:13] <seb128> or what Laney said for the filename :p
[12:13] <Laney> AHAHAHAH
[12:13] <seb128> :)
[12:14] <willcooke> dupondje, Laney @ n-m: ack, thanks
[12:14] <Laney> that sounds related to this work in 3.30 though
[12:15] <Laney> if so it'll be one to file upstream as well probably, for halfline to have a look at
[12:15] <Laney> we already fixed a few like that
[12:15]  * Laney sammich
[12:15] <seb128> willcooke, bonus point if you file the bug with log on gitlab: )
[12:15]  * willcooke gives it a go
[12:24] <willcooke> hm, I dont see anything obvious in the logs
[12:29] <didrocks> popey: yeah, I was asking if you can add jaggers to the communitheme/yaru team group please
[12:36] <seb128> willcooke, no need for it to be obvious, it should be verbose is the debug=true worked and hopefully include the details upstream needs
[12:59] <willcooke> k, updating to proposed seems to have fixed it
[12:59] <willcooke> sorry
[12:59] <willcooke> I will retest a few times
[13:07]  * didrocks is fighting still on gsconnect…
[13:08] <jbicha> willcooke: I'm unable to reply to the team report community thread
[13:09] <jbicha> I have a concern about the tracker MIR
[13:12] <didrocks> tseliot: you could have written that in the description :/
[13:12] <didrocks> tseliot: so basically I've spent the whole morning reviewing the MIR for nothing?
[13:13] <tseliot> didrocks: wrong ping?
[13:13] <didrocks> tseliot: sorry, was for tjaalton :)
[13:13] <tseliot> good :)
[13:13] <didrocks> too many t*
[13:14] <didrocks> tjaalton: please have a look ^ and you didn't explain why the split (I requested this) and the difference: what would be in vulkan vs vulkan-loaders, what the MIR will use then
[13:14] <didrocks> and as long as it's not NEWed, I don't think I'm going to rereview it, as those questions aren't answered :/
[13:15] <popey> @didrocks done
[13:15] <didrocks> (if I understand correctly, vulkan is going to be an empty package, split in 4 sources, but only -loader would need a MIR)
[13:15] <didrocks> popey: thanks!
[13:15] <didrocks> would like a confirmation still, quite unclear
[13:17] <seb128> jbicha, the hub topic is not supposed to be for discussion, that's by design
[13:17] <seb128> we discuss topics on IRC during the meeting
[13:17] <seb128> or we said we would have a "discussion" post for comments
[13:19] <jbicha> so I should just start a regular desktop topic for the tracker issue?
[13:19] <seb128> or raise it to discuss during the IRC meeting
[13:19] <seb128> as you prefer
[13:19] <seb128> or talk about it here now
[13:19] <jbicha> opening a topic since it's easier to read there
[13:19] <seb128> good
[13:21] <jbicha> https://community.ubuntu.com/t/tracker-stuck-in-cosmic-proposed/8224
[13:21] <tjaalton> didrocks: the split was mentioned in the description
[13:21] <willcooke> jbicha, ah.  My bad.  popey please could you grant jbicha permission to post to the weekly updates topic?
[13:21] <tjaalton> didrocks: only loader will need the MIR
[13:21] <jbicha> we can discuss elsewhere but that gives background easier
[13:22] <tjaalton> didrocks: upstream did the split, so it had to be repackaged
[13:22] <didrocks> tjaalton: right, but you could have said to not review vulkan then
[13:23] <didrocks> MIR is already unfun, we were supposed to have 2 people from the desktop team but seems the plan was cancelled, and I'm not really fond of loosing a morning on things like that :/
[13:23] <willcooke> jbicha, caught up with backlog now - so yeah, that list is for weekly updates, which you might still want to post to,  so we should still sort that, but as seb said, discussion should be in a new topic and/or the meeting
[13:23] <didrocks> tjaalton: so, basically, only -loaders, once NEWed will need a MIR review?
[13:23] <didrocks> which is a subpart of vulkan
[13:23] <didrocks> correct?
[13:23] <jbicha> I didn't prepare an update for this week so unless I type really fast…
[13:24] <tjaalton> didrocks: correct
[13:24] <popey> willcooke: done
[13:24] <willcooke> thanks popey
[13:24] <didrocks> tjaalton: ok, and as you said, the vendoring will not be part of the package anymore
[13:24] <willcooke> jbicha, you can add it later if you like
[13:24] <tjaalton> no way to file it against vulkan-loader before it's in the archive, my mistake for subscribing ubuntu-mir then, it was meant to be a placeholder
[13:24] <didrocks> tjaalton: so, I suggest that you look at my comments, and already fix some I had if that applied to the new package
[13:25] <didrocks> so that already this is done and we win a loop
[13:25] <didrocks> however, we'll need someone to NEW the package first
[13:25] <tjaalton> I've tried
[13:26] <didrocks> (I don't want to cumulate NEWing and MIRing, better having someone else having a look)
[13:28] <didrocks> jbicha: the tracker code is very different than the one we used to have in main
[13:28] <didrocks> and as I have written, I already have doubt security-wise on file permissions
[13:28] <didrocks> I don't think telling "double guessing what the MIR team applied and bypass security" is a good option
[13:29] <seb128> it's too late in the cycle to promote/add to default install anyway
[13:29] <willcooke> It's meeting time
[13:29] <willcooke> Do you want a few mins to wrap that up? ^
[13:30] <willcooke> Or we can do it in the meetnig
[13:31] <didrocks> I guess in meeting if needed is good
[13:31] <willcooke> Laney, seb128, just before we start - now running proposed at I've got gdm up 4 times out of 4 so far
[13:31] <willcooke> going for #5 now
[13:31] <willcooke> ok, goingt to start then
[13:31] <willcooke> #startmeeting Desktop Team Weekly Meeting - 2018-10-02
[13:32] <meetingology> Meeting started Tue Oct  2 13:31:59 2018 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:32] <meetingology> Available commands: action commands idea info link nick
[13:32] <seb128> :)
[13:32] <willcooke> Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out), tjaalton, tseliot
[13:32] <seb128> hey
[13:32] <andyrock> o/
[13:32] <didrocks> o/
[13:32] <kenvandine> \o
[13:32] <tseliot> o/
[13:32] <oSoMoN> o/
[13:32] <jibel> o/
[13:32] <willcooke> New format this week then everyone.  You should have had a chance to review people's updates.  I've had no messages for anyone in far away places that they want to raise any topics.
[13:33] <heber> o/
[13:33] <jbicha> o/
[13:33] <willcooke> #topic Round table
[13:33] <willcooke> By a show of hands, does anyone have anything they want to raise based on the updates from the rest of the team, or otherwise?
[13:33] <willcooke> i.e. if no one wants to talk about anything, then we can move on to rls bugs
[13:33] <tjaalton> o/
[13:34] <didrocks> just that I'm fighting with gsconnect extension
[13:34] <didrocks> upstream is really responsive
[13:34] <didrocks> I hope to upload a new snapshot soon
[13:34] <willcooke> tjaalton, is that "I want to talk about something" or just a "I'm here!"?
[13:34] <didrocks> it will still be in universe, but if people want to give a test
[13:34] <willcooke> didrocks, that's great to hear, thanks!
[13:34] <tjaalton> willcooke: I'm here :)
[13:34] <didrocks> the idea is that the code will be close to what we want to ship by default next cycle
[13:34] <Laney> better
[13:35] <didrocks> so, the earlier you test with your phone, the better :)
[13:35] <seb128> just for next time, maybe standardize on a round of "o/ I've a topic"
[13:35] <didrocks> that's it for me
[13:35] <seb128> then we can go round between those who said that
[13:35] <seb128> with the chair giving the turn to each
[13:35] <seb128> otherwise it's going to be cahos
[13:35] <willcooke> that's what I was going for here
[13:35] <didrocks> seb128: +1
[13:35] <seb128> willcooke, right
[13:35] <Laney> NM's definitely being crashy here too, took me a while to get online after rebooting just then
[13:35] <seb128> but tjaalton did an unclear o/
[13:35] <seb128> and didrocks just wrote
[13:36] <didrocks> yeah, better to standardize
[13:36] <jbicha> o/
[13:36] <seb128> lol
[13:36] <seb128> see jbicha also :p
[13:36] <willcooke> I have a question as well
[13:36] <willcooke> ok, let's start with jbicha
[13:36] <willcooke> #topic jbicha
[13:36] <seb128> was that a raise of hand or an "hey"?
[13:36] <jbicha> I had a tracker question but it was late so maybe discuss that on the community site?
[13:37] <seb128> we can discuss it now
[13:37] <seb128> imho
[13:37] <jbicha> ok: https://community.ubuntu.com/t/tracker-stuck-in-cosmic-proposed/8224
[13:37] <jbicha> can we fast track the tracker mir?
[13:38] <seb128> no
[13:38] <didrocks> didn't we just discuss how bad the idea of fast tracking the tracker mir ?
[13:38] <kenvandine> gotta track the tracker
[13:38] <seb128> security team has some backlog, we have no impact on that, and in fact we are more import MIRs we want to get through (portals)
[13:38] <jbicha> didrocks: sorry, I might have missed that discussion
[13:38] <seb128> and it's not a good idea to add a feature that late
[13:39] <didrocks> on the MIRing side, this is my view:
[13:39] <didrocks> jbicha: the tracker code is very different than the one we used to have in main
[13:39] <didrocks> and as I have written, I already have doubt security-wise on file permissions
[13:39] <jbicha> ok, maybe I'll talk to mbiebl about letting the package split in
[13:39] <didrocks> I don't think telling "double guessing what the MIR team applied and bypass security" is a good option
[13:39] <seb128> would need a ffe at least
[13:39] <seb128> I would be fine deleting the new tracker from cosmic-proposed
[13:39] <seb128> it didn't migrate out and we don't need that update
[13:39] <seb128> but if you have an easy fix that works too
[13:40] <seb128> it's getting a bit late to land a new version now (having it not migrated out of proposed yet means it virtually haven't landed/got testing)
[13:40] <jbicha> let's see if the split works, otherwise I'm fine with dropping it from -proposed
[13:40] <seb128> wfm
[13:40] <jbicha>  /next topic
[13:40] <willcooke> cool, thanks. We know where we're going then
[13:40] <willcooke> #topic willcooke
[13:41] <willcooke> tjaalton, I'm keen to hear if you're any closer to understanding why virtualbox machines won't start without nomodeset
[13:41] <willcooke> That's a release blocker for me
[13:42] <tjaalton> willcooke: the kernel driver init takes 25-30s on initial boot, probably because the driver is not in the installer initrd
[13:42] <tjaalton> this triggers a weird race in xserver which has been there for some time already
[13:42] <seb128> "probably because the driver is not in the installer initrd"
[13:43] <seb128> how can we get that "probably" out of the sentence?
[13:43] <jibel> has the vbox driver already been in the installer initrd?
[13:43] <seb128> that
[13:43] <seb128> and if it was, when/why has it been removed?
[13:43] <Trevinho> seb128: is not according to lsinitrd
[13:43] <jibel> and if it was not why is it failing now?
[13:43] <Trevinho> lsinitramfs
[13:44] <Trevinho> maybe we're faster in doing something else and thus....
[13:44] <Trevinho> the issue.
[13:44] <Trevinho> like we try to start x when things are not ready yet, while before this was delayed by something else. This sometimes happen.
[13:44] <seb128> $ lsinitramfs /boot/initrd.img-4.4.0-116-generic | grep virtual
[13:44] <seb128> lib/modules/4.4.0-116-generic/kernel/drivers/regulator/virtual.ko
[13:44] <seb128> on xenial
[13:45] <seb128> so it was in the initramfs
[13:45] <Trevinho> as per listing initrd there's no x11 related video drivers there
[13:45] <seb128> or is that a different one?
[13:45] <didrocks> lib/modules/4.18.0-8-generic/kernel/drivers/regulator/virtual.ko
[13:45] <didrocks> it's still in the initramfs
[13:45] <tjaalton> seb128: vboxvideo
[13:45] <seb128> didrocks, wrong name, sorry :p
[13:45] <seb128> tjaalton, that was not in xenial either
[13:45] <didrocks> this one is not, was it in xenial?
[13:45] <didrocks> ok
[13:45] <Trevinho> yeah, no video driver is there iirc
[13:45] <andyrock> is it possible to add it and test  if it works?
[13:46] <tjaalton> seb128: maybe X started later then
[13:46] <Trevinho> ah, some are.
[13:46] <seb128> tjaalton, but the foundamental issue is an xorg one right?
[13:46] <Trevinho> but just lowlevel fb stuff
[13:46] <tjaalton> there's a window of like 3s.. X starts at 25s (here), vboxvideo init done at 27s
[13:47] <tjaalton> Trevinho: huh? my initrd has all from drivers/gpu/drm
[13:47] <Trevinho> tjaalton: oh, yeah... sorry. Not vbox though
[13:47] <tjaalton> vbox is in staging
[13:48] <seb128> I'm not sure that discussion is actually productive working toward a resolution
[13:48] <willcooke> tjaalton, is this issue on your radar? Are you activly looking in to it?
[13:48] <seb128> tjaalton, is a team owning the problem/actively working on resolving it?
[13:48] <willcooke> Do you need something from us to help?
[13:49] <seb128> and which team does/should own it
[13:49] <tjaalton> I don't know how to fix this
[13:49] <seb128> ?
[13:49] <seb128> well, what changed compared to bionic
[13:49] <seb128> is the vboxvideo init slower?
[13:49] <Trevinho> Also, this is related also to the one on kvm with std driver, isn't it?
[13:49] <Trevinho> while it has a different way of applying, but might be related to the same xorg issue in not trying better to reload or what?
[13:50] <seb128> tjaalton, is that a kernel regression? like does it work using the bionic kernel?
[13:50] <tjaalton> Trevinho: somewhat, but it's fixable by enabling drm/bochs
[13:50] <tjaalton> seb128: I don't know
[13:50] <Trevinho> gdm-wise we could change something as trying to load things for more time or what?
[13:50] <Trevinho> reload*
[13:50] <seb128> k
[13:51] <seb128> I suggest that's not a topic that's going to be resolved in the meeting
[13:51] <seb128> it needs actual debugging and understanding of the problem
[13:51] <Trevinho> well, at least to have a pointer I mean...
[13:51] <Trevinho> not details, but a direction.
[13:51] <willcooke> Yeah, seb128, jibel - lets chat about how we can try and get more of an understanding about what's going on later on
[13:51] <seb128> that's 10 min we are on the topic and I don't feel like we got anything useful out of it
[13:51] <willcooke>  /next topic
[13:52] <tjaalton> seb128: testing an older kernel would mean building the installer image with cosmic userland
[13:52] <willcooke> tjaalton, we can chat more about this after the meeting
[13:53] <tjaalton> sure
[13:53] <willcooke> We're not going to solve it now
[13:53] <willcooke> thanks
[13:53] <willcooke> I dont think anyone else had any topics, so we can move on to rls bugs
[13:53] <Trevinho> well
[13:53] <Trevinho> I've few branches for review and I'd like to get the SRU on XUbuntuCancel for search provider in, so reviews would be appreciated. There's also a silo to test and in case to publish in seconds if all fine
[13:54] <Trevinho> so... just an heads up on that. Ah, and also a gnome-calculator fix.
[13:54] <willcooke> Links are in your post on the hub right Trevinho?
[13:54] <Trevinho> yep
[13:54] <willcooke> thx
[13:54] <seb128> k
[13:54] <Trevinho> I wanted to mention in the 1st part but I didn't know how things were organized yet :)
[13:55] <Trevinho> and suddently topic changed :)
[13:55] <willcooke> ok, any more before we review rls bugs?
[13:55] <andyrock> o/
[13:55] <willcooke> #topic andyrock
[13:56] <andyrock> I got 2-3 MPs in salsa
[13:56] <andyrock> they have been there for a while
[13:56] <andyrock> is anyone willing to review them?
[13:56] <andyrock> not sure it fit here
[13:56] <seb128> I can help with some
[13:56] <andyrock> kk thanks I'll send you the links later
[13:56] <willcooke> thx
[13:56] <Laney> two things
[13:57] <Laney> #debian-gnome is better for debian sponsoring
[13:57] <Laney> and I don't know that using this round for "please review my stuff" is good
[13:57] <Laney> (that is feedback)
[13:57] <andyrock> kk thanks
[13:57] <seb128> andyrock, duflu usually list the things he's waiting for sponsoring in his update, I think that's a good place
[13:57] <seb128> I try to unblock things he has listed
[13:57] <andyrock> makes sense
[13:57] <andyrock> thanks for the feedback
[13:57] <seb128> I would have done the same for yours (in fact I spotted the g-c-c one and have a tab opened on it)
[13:57] <seb128> yw
[13:57] <seb128> Trevinho, ^ you as well
[13:58] <Trevinho> indeed
[13:58] <seb128> but yeah, similar to Laney
[13:58] <seb128> I think we derailed the purpose
[13:58] <seb128> those "those needs <...>" should be in the summaries
[13:58] <willcooke> +1
[13:58] <seb128> or we recreate a round table of updates on IRC
[13:58] <willcooke> let's do that for next week
[13:58] <willcooke>  /next topic
[13:58] <Trevinho> no, no... that's fine to define a strategy here and then we follow in the updates.
[13:58] <willcooke> any one else?
[13:58] <seb128> can we do rls now? ;)
[13:59] <willcooke> yes
[13:59] <seb128> thx :)
[13:59] <Trevinho> Since we had not, better to define one
[13:59] <willcooke> #topic Release Bugs
[13:59] <seb128> right
[13:59] <willcooke> Ok, we're going to skip the rls-bb-tracking bugs this week only, because the list is very long and Seb wants to spend some time tidying it up before we review
[14:00] <willcooke> rls-bb-incoming is empty (enough)
[14:00] <willcooke> so rls-cc-incoming first, why not
[14:00] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[14:00] <willcooke> 1 issue: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795421
[14:01] <willcooke> Nice to have but not a blocker IMO
[14:01] <seb128> rls-cc-notfixing imho
[14:01] <seb128> it's a minor cosmic issue
[14:02] <seb128> we should fix it but it's not a release blocker
[14:02] <willcooke> 2 votes for notfixing
[14:02] <willcooke> anyone opposed?
[14:02] <willcooke> going once
[14:02] <willcooke> twice
[14:03] <willcooke> gone
[14:03] <willcooke> bug updated and commented
[14:03] <willcooke> rls-cc-tracking now:
[14:03] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html
[14:04] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280
[14:04] <didrocks> this is the vbox issue?
[14:04]  * didrocks opens
[14:04] <willcooke> I think that might be the same bug I saw earlier and is fixed in proposed afaict
[14:04] <willcooke> didrocks, no, different thing
[14:04] <Trevinho> didrocks: not only, also on kvm..
[14:04] <jibel> this is qemu and hw
[14:04] <Laney> Marco got assigned that bug last week, it's a different task on the same one
[14:05] <Trevinho> yep, I've spent time in debugging, but something gdm specific, is as the vbox one something related to the init
[14:05] <willcooke> Trevinho, so WIP still?
[14:05] <Trevinho> so... not much desktop stuff, unless we decide to change gdm way of starting up
[14:05] <seb128> Trevinho, on https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/comments/11 (which is linked) you wrote "the patch should be fine", what patch is that?
[14:06] <Laney> different bug?
[14:06] <Trevinho> seb128: as per https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/comments/10
[14:06] <seb128> that doesn't have a patch :p
[14:07] <Trevinho> seb128: https://launchpad.net/ubuntu/+source/plymouth/0.9.3-1ubuntu9
[14:07] <seb128> Laney, could be, it's unclear to me, sounds like we are conflicting vbox/plymouth/other issues
[14:07] <Trevinho> yep... these are two different things
[14:07] <seb128> anyway
[14:07] <seb128> that should be assigned to Trevinho, as Laney said that was the outcome from the previous meeting
[14:07] <seb128> so let's do that and move on?
[14:07] <willcooke> Trevinho, can you update the bug pls?
[14:07] <seb128> we can discuss technical details after the meeting if needed
[14:07] <Trevinho> seb128: as said, not really much i can do on that...
[14:08] <willcooke> k, lets talk about it more later
[14:08] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1794951
[14:08] <Trevinho> I had this assigned, but I marked the gdm as invalid. So I can assign to myself if you want me to look at other places I don't know exaclty
[14:08] <willcooke> I raised that one, but having spoken to Ken earlier today there are other more important things and that issue is probably not a release blocker
[14:08] <Laney> looks like that one skipped the process :P
[14:09] <willcooke> so I'm happy to untag
[14:09] <willcooke> Laney, yeah I should have incoming that one, sorry
[14:09] <Trevinho> willcooke: fixing that would be quite easy though, it's just few lines of snapcraft if he's busy It takes few minutes.
[14:09] <willcooke> kenvandine, could you chat to Trevinho about that? ^
[14:09] <kenvandine> yeah
[14:09] <willcooke> Trevinho, I'm not so sure, but would be interesting to see
[14:10] <willcooke> next:
[14:10] <willcooke> http://launchpad.net/bugs/1792932
[14:10] <willcooke> Thats the virtualbox bug which we already talked about
[14:10] <willcooke> next: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1743216
[14:10]  * Trevinho is pretty sure this and 1794292 are two different faces of the same medal
[14:10] <willcooke> Looks like it might be fixed already, but is in progresss
[14:10] <Trevinho> [previous one]
[14:11] <seb128> the fix is in the queue yes
[14:11] <seb128> needs to be approved by someone from r-t (other than L_aney)
[14:11] <willcooke> I can validiate that one I think
[14:11] <willcooke> next: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1785240
[14:11] <Laney> it's fine, that one is on track
[14:11] <andyrock> is this really a release blocker?
[14:11] <andyrock> :)
[14:12] <andyrock> btw the fix is upstream (both in gnome-software, snapd-glib, and snapd)
[14:12] <andyrock> in cosmic Robert needs to take care of gnome-software
[14:12] <andyrock> the rest has already been uploaded
[14:13] <willcooke> yeah not a release blocker
[14:13] <andyrock> not so much I can do also because I don't understand how Robert deals with gnome-software uploading
[14:13] <willcooke> the last one is a security issue:
[14:13] <willcooke> https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1788929
[14:13] <willcooke> and that's the end of the list
[14:13] <seb128> looks like jd_strand is on it
[14:14] <willcooke> Any comments on rls bugs before we move on?
[14:14] <didrocks> nope
[14:14] <seb128> no
[14:14] <willcooke> ok, moving on
[14:14] <willcooke> #topic Trevinho
[14:14] <willcooke> Trevinho, you had something you wanted to raise
[14:15] <Trevinho> yeah, as per SRU of mutter/gnome-shell to bionic... despite the upstream pings it looks like a point version for 2.28 is taking ages
[14:15] <Trevinho> there are still some relevant issues like http://launchpad.net/bugs/1727356 that should be pushed
[14:15] <Trevinho> but waiting for a stable...
[14:15] <seb128> I'm not sure that's a team topic?
[14:16] <Trevinho> I'm happy to cherry-pick, but... should I go with that or what?
[14:16] <seb128> like it's fine to have as a channel discussion with me/your usual sponsors at any time
[14:16] <seb128> no?
[14:16] <Trevinho> I want to know how to proceed...
[14:16] <seb128> right
[14:16] <seb128> I'm just saying you don't need the full team attention for that
[14:16] <seb128> let's discuss it out of the meeting?
[14:16] <Trevinho> ok, as you prefer.
[14:17] <willcooke> ok, last topic:
[14:17] <willcooke> #topic AOB
[14:17] <willcooke> Anyone got anything?
[14:17] <Laney> I'd be interested to know who is still watching now
[14:17] <andyrock> o/
[14:17] <Laney> after all this format was less boring
[14:17] <Laney> :-)
[14:17] <didrocks> o/
[14:17] <jibel> I am
[14:17] <Nafallo> I'm mostly confused :-)
[14:18] <Trevinho> 👀
[14:18] <seb128> o/
[14:18] <willcooke> Comment: we need to find a better way than waiting for "anyone... anyone... Bueller"
[14:18] <seb128> less boring, but that one didn't feel as smooth as I was expecting
[14:18] <oSoMoN> o/
[14:18] <Laney> yes indeed
[14:18] <seb128> I guess that's normal for a first try though
[14:18] <Laney> where can we give our Useful Feedback™?
[14:18] <didrocks> seb128: agreed
[14:19] <oSoMoN> gotta get used to the new format, I like the new format with a post on the hub a lot more
[14:19] <didrocks> (is it time to list those who didn't answer that they are following? :p)
[14:19] <seb128> same
[14:19] <seb128> Laney, feedback here or by reply to willcooke's email I would say?
[14:19] <seb128> willcooke, ^ wdyt?
[14:20] <andyrock> lol
[14:20] <Laney> ok
[14:20] <Laney> I'd prefer rls tracking updates in the status posts themselves
[14:20] <Laney> that bit disrupted the flow a lot for me and I think could have been done offline
[14:20] <seb128> me too, at least for the -tracking review part
[14:20] <willcooke> was just typing, yeah, I think email is right, then we dont generate noise here waiting for everyone's feedback
[14:20] <seb128> I didn't really understand why we did/did it this way
[14:20] <Laney> and getting into the discussion of bug details should be avoided more imho, but that's not a new issue
[14:20] <Laney> otherwise I like it more
[14:21] <seb128> like most are assigned, post ff we used to just have people listing their bugs in a section with the status of each
[14:21] <willcooke> ok, please summarise your feedback via email and next meeting will the FTW
[14:21] <willcooke> *be
[14:21] <seb128> Laney, yeah, we keep falling back into discussing the issues :/
[14:21] <seb128> :)
[14:21] <seb128> thx!
[14:22] <willcooke> So we still need to talk more about the virtualbox issue
[14:22] <Laney> eom?
[14:22] <seb128> wrap?
[14:22] <seb128> we also need to talk to Trevinho about his SRUs :)
[14:22] <willcooke> just checking if there was anything else we still need to talk about
[14:22] <willcooke> that
[14:22] <willcooke> ok, EOM
[14:22] <willcooke> #endmeeting
[14:22] <meetingology> Meeting ended Tue Oct  2 14:22:46 2018 UTC.
[14:22] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-10-02-13.31.moin.txt
[14:22] <Trevinho> honestly I don't see that as a problem. Or maybe we should also add a post-section were we analyze the things
[14:22] <andyrock> thanks lunch time for me
[14:22] <kenvandine> 👍
[14:22] <didrocks> thx!
[14:23] <oSoMoN> thanks everyone!
[14:23] <Laney> too late kenvandine
[14:23] <Laney> BUSTED
[14:23] <seb128> andyrock, enjoy!
[14:23] <Trevinho> as this is the moment where more eyes are around and so easier to have better ideas. More than just a 1:1 thing
[14:23] <seb128> Trevinho, what are you refering to?
[14:23] <oSoMoN> andyrock, man, it's almost dinner time in the UK, you're terribly jet-lagged ;)
[14:23] <Trevinho> discussing the issues
[14:23] <Trevinho> so that who's interested can check the details...
[14:24] <willcooke> Next week's post is here: https://discourse.ubuntu.com/t/monday-8th-october-2018/8221
[14:24] <Trevinho> like... issue #12345678, need more talking... -> #aftermeeting.
[14:24] <Trevinho> so we do it know, but having this as a procedure.
[14:24] <seb128> Trevinho, it's fine to discuss work like the vbox one imho, but it's not useful to try to discuss bugs we didn't read/try to understand yet (the incoming list) or that are being handled and don't need discussion
[14:24] <Trevinho> thanks willcooke
[14:25] <Trevinho> eh, so there's no much point in even trying to assing them in the meeting imho.
[14:25] <seb128> Trevinho, if you want to discuss a bug & it's solution I would expect you to raise an hand in the roundtable section at the start
[14:25] <seb128> and add it as a topic
[14:25] <Trevinho> if we don't go into details it's generally not always 1/0 decision.
[14:27] <Trevinho> yeah, that was the idea when asking how to solve things (both tecnically speaking or from managemen point of view), indeed there might be things where not all the team is interested, but there are topics where more than two people are and this might be the moment. At least to define when to talk about it.
[14:27] <seb128> we usually manage to decide on most bugs
[14:28] <seb128> well it's always fine to raise a topic
[14:28] <seb128> worth thing you get told that it's better to discuss after the meeting
[14:28] <seb128> and the people interested can stick for that
[14:28] <Trevinho> anyway, just it's ok. let's now get into the deep of the remaining tasks.
[14:28] <seb128> right
[14:29] <seb128> so vbox/init/xserver
[14:29] <seb128> tjaalton, I'm unclear how much you investigated/figured out and how much is guessing that needs to be backed up by fact at this point?
[14:30] <Laney> willcooke: how did you notice that you got network-manager crashing?
[14:30] <willcooke> I need to go to another meeting, I will follow along and post when I can
[14:30] <seb128> tjaalton, you said the vbox driver got dropped from the initramfs and it's creating the issue, was that guess or fact? (it didn't seem to be included in xenial?)
[14:30] <Laney> I tried searching on errors but there's 0 crashes in 18.10 for n-m apparently
[14:30] <Laney> which is suspicious to me
[14:30] <seb128> Laney, willcooke, n-m didn't change recently
[14:30] <Laney> so?
[14:30] <willcooke> Laney, it was in syslog, but it went away. I'll try and reproduce
[14:30] <seb128> Laney, don't trust errors :p
[14:30] <seb128> it could just fail to retrace by missing symbols or something
[14:31] <Laney> right...
[14:31] <tjaalton> seb128: I'd need to boot in windows to check vbox, my guess is that the building the initrd adds vboxvideo if the system is vbox. otherwise it'll just have all the normal drm drivers
[14:31] <seb128> Laney, well, I was typing, sorry I hit enter too fast ... n-m didn't change so it's not the obvious candidate for a regression (unless the issue is not new), having a bt would be useful if one of you still have the .crash
[14:32] <Laney> If the crash was in network-manager that's where it would be bucketed on errors - this is the question I was asking.
[14:32] <Laney> I'm not really trying to investigate it (yet).
[14:32] <seb128> tjaalton, but the initrd is not built on the fly is it?
[14:32] <tjaalton> sure is
[14:32] <seb128> ah
[14:33] <seb128> I don't know that part of the boot well
[14:33] <tjaalton> not on the fly
[14:33] <Laney> It's bug #1794966 though
[14:33] <Laney> Or at least my one is
[14:33] <tjaalton> but for the installed system it'll build one
[14:33] <seb128> tjaalton, did you try to get foundations in the loop for that discussion?
[14:33] <tjaalton> kernel doesn't ship one, it's built on the system
[14:34] <tjaalton> seb128: no, spent more on the qemu thing and tried to get bochs enabled again. compared it with debian and they have it all working
[14:34] <tjaalton> but I guess the kernel is frozen now as of yesterday
[14:35] <seb128> Laney, from experience, e.u.c can missing a bucket can be due to failing retracings or apport failing to write/send the report (we had case when custom handlers would hijack apport, unsure if n-m does that)
[14:36] <seb128> tjaalton, jibel, willcooke, what's the reference bug for that vbox issue?
[14:36] <Laney> OK thanks, I really just wanted to know if w_illcooke had tried to submit it to errors, but thanks for the extra information.
[14:36] <seb128> np
[14:36] <tjaalton> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1792932
[14:40] <didrocks> Laney: https://launchpad.net/ubuntu/+source/nautilus/1:3.26.4-0ubuntu4
[14:40] <willcooke> Laney, is this any use?  https://paste.ubuntu.com/p/6TGCkW48XX
[14:40] <didrocks> nautilus-folder-handler.desktop is still used, as least associated to default mime type for inode/directory
[14:40] <didrocks> xdg-mime query default inode/directory
[14:40] <didrocks> nautilus-folder-handler.desktop
[14:42] <seb128> willcooke, do you have a .crash in /var/crash?
[14:42] <willcooke> seb128, nope, sorry.  I've rebooted a lot since then
[14:42] <willcooke> I'll do a fresh install
[14:43] <jbicha> willcooke: sorry I didn't follow context or know the details but there was some kind of network fix in today's gnome-shell update
[14:43] <oSoMoN> I just filed bug #1795674, is that a known issue by any chance?
[14:43] <jbicha> ^
[14:43] <willcooke> oSoMoN, could that be a theme issue?
[14:44] <jbicha> maybe try with tomorrow's iso?
[14:45] <jibel> it's there on hw
[14:46] <didrocks> Laney: I'm fine setting nautilus.desktop as the default if needed and it's a good fit
[14:46] <Laney> jbicha: it's a crash in network-manager itself (so no)
[14:46] <Laney> didrocks: ah, sorry, that should be org.gnome.Nautilus.desktop, I thought that was the case already
[14:47] <jbicha> ok
[14:47] <Laney> where does it come from can you remember?
[14:47] <seb128> Laney, https://bazaar.launchpad.net/~ubuntu-desktop/desktop-file-utils/ubuntu/view/head:/debian/defaults.list#L195
[14:47] <didrocks> Laney: no worry, I'll do it :) it's in desktop-file-utils (/usr/share/applications/defaults.list)
[14:47] <Laney> thx
[14:47] <Laney> I forgot the details of that thing
[14:47] <didrocks> easy to spot
[14:47] <willcooke> back from meeting
[14:47] <Laney> I checked the default list in gnome-session
[14:47] <didrocks> was blaming the software with "open in folder" first :p
[14:47] <Laney> gnome-mimeapps.list
[14:47] <seb128> Laney, that's a Debian thing
[14:48] <Laney> ok
[14:48] <didrocks> but their fault, no log it's failing ;)
[14:48] <seb128> well, we have a diff, ours is in desktop-file-utils
[14:48] <seb128> we should maybe look at getting ride of that delta
[14:48] <didrocks> yeah, gnome-mimeapps.list vs defaults.list vs gio mimetype…
[14:48] <kenvandine> Trevinho: so what was your theory
[14:48] <didrocks> ETOOMANYPLACES
[14:48] <seb128> we put it there because it's a component easier to rebuild and less likely to break things on a rebuild
[14:48] <Trevinho> kenvandine: this works fine https://github.com/3v1n0/telegram-snap/blob/master/snapcraft.yaml#L158
[14:49] <jdstrand> willcooke, seb128, et al: I'm working on https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1788929
[14:49] <willcooke> jdstrand, thanks!
[14:49] <seb128> jdstrand, ah, good, thanks
[14:49] <jdstrand> I uploaded to cosmic already. wanted to see if people ran into anything first
[14:50] <kenvandine> Trevinho: so the slowness is updating the icon cache or mime database?
[14:50] <jdstrand> I also did submittodebian on it
[14:52] <Trevinho> kenvandine: yeah, takes the most of it
[14:52] <kenvandine> Trevinho: why is that different for 18.10 though?
[14:52] <Trevinho> ah, mh,.. I thought it was always like that even before.
[14:53] <Trevinho> So, I didn't profile cosmic differently though.
[14:53] <Trevinho> So i might be wrong. I just thought it was the same issue
[14:53] <kenvandine> no, this issue is the same snap is much slower to start fresh on 18.10 than 18.04
[14:53] <jbicha> jdstrand: Debian GNOME accepts merge requests now. I don't know if that's easier or harder for you than submittodebian https://salsa.debian.org/gnome-team/evince
[14:56] <didrocks> ah, "opening folder" works way better now :)
[14:56] <Laney> :3
[14:57] <jdstrand> jbicha: in that moment submittodebian was, but noted
[14:58] <Trevinho> kenvandine: I see... Mh, we should profile the launching script then. For sure that operation was the one taking the most of the times
[14:58] <Trevinho> also parsing the fonts was, but might be different.
[14:58] <kenvandine> we fixed the font issue
[14:58] <Trevinho> seb128: as per those SRU what would you suggest?
[14:59] <kenvandine> at least for snaps built with the gnome backports PPA run on bionic hosts
[14:59] <kenvandine> Trevinho: that was the slowdown
[14:59] <oSoMoN> the welcome page of the installer slideshow is a beaver, not a cuttlefish, are we waiting on design to provide the screenshot?
[14:59] <kenvandine> but cosmic should have the same fontconfig cache version
[14:59] <seb128> Trevinho, I'm not sure to understand the issue. Waiting for an incoming upstream point release when there is one coming makes sense, if there is none coming or if it's taking to long it's fine to cherry pick or do a git snapshot tarball imho
[15:01] <Trevinho> seb128: well, it was said to be soon, but still it's not coming. And so cherry-picking everything would make the verification harder I guess
[15:01] <Trevinho> same for a git snapshot, no?
[15:01] <Trevinho> but at least that fix for mutter imho is something we should land asap. We waited for a point release even too much imho.
[15:02] <willcooke> oSoMoN, @ installer slideshow - I did new graphics the other day.  jibel approved the merge. https://code.launchpad.net/~willcooke/ubiquity-slideshow-ubuntu/ubiquity-slideshow-ubuntu
[15:03] <seb128> Trevinho, I would do a snapshot of the stable branch and handle it as if it was a point update SRU
[15:03] <oSoMoN> willcooke, cool, so it's just pending an upload?
[15:03] <willcooke> oSoMoN, yeah I think so.
[15:04] <Trevinho> seb128: is that something we can do in the same way? In terms of SRU handling... I dindn't know...
[15:05] <oSoMoN> willcooke, but we're way past UI freeze, does this require a UIFe ?
[15:05] <willcooke> oSoMoN, quite possibly.  I need to make one fix now, so I'll sort it
[15:05] <seb128> Trevinho, up to the SRU team to be fine or not but I think we can make our case for it
[15:06] <oSoMoN> willcooke, ack, thanks
[15:07] <Trevinho> I'll ping upstream again btw
[15:07] <seb128> andyrock, I sponsored g-c-c to Debian, did you plan to handle the Ubuntu rebase/update as well?
[15:08] <andyrock> seb128: yep :)
[15:08] <seb128> great, thx
[15:08] <andyrock> I looked at it because it contains the fix for a crash I sent upstream
[15:08] <seb128> and you are supposed to lunch :p
[15:08] <seb128> k
[15:08] <seb128> well let me know when the Ubuntu side is ready and I can sponsor that as well
[15:08] <andyrock> kk thanks :)
[15:10] <seb128> stepping back for a bit, bbl
[15:11] <oSoMoN> seb128, remembered that bug we looked into at the beginning of the week in Brussels, where the shell menu was only partially localized in French? I'm still seeing it but can't find the bug number, it was a language pack thing, right?
[15:11] <oSoMoN> ah, too late… that can wait till you're back though
[15:31] <willcooke> Laney, fresh install, no segfaults
[15:31] <willcooke> Laney, red herring I think
[15:31] <willcooke> re: n-m that is
[15:36] <Laney> ok, thanks, I'm still seeing it a bit though
[15:36] <Laney> some kind of memory management problem
[15:46] <willcooke> Laney, anything I can do to confirm/test?  How can I reproduce?
[15:46] <Trevinho> 17:08:10 <Trevinho> fmuellner: hey, any free slot for a point 3.28 release? :)
[15:46] <Trevinho> 17:08:47 <fmuellner> Trevinho: yeah, but as it's the last one, I'd like to take a look on what might be a good idea to include still
[15:46] <Trevinho> I guess we should go for git snapshots later... (seb128)
[15:47] <Laney> willcooke: dunno yet, don't worry about it
[15:52] <willcooke> Laney, ack
[15:53] <Trevinho> seb128: also for that gdm crash on kvm, what can I do? I mean, if you want me to poke around gdm to see if we can make it try harder, its something I can check, but if I should look at lower levels, I need to study things a bit. Not sure if someone else can be faster, then.
[15:54] <Laney> think it happens more when I'm on the usb ethernet thing maybe
[15:54] <Laney> Tue 2018-10-02 16:53:43 BST   24566     0     0   6 error     /usr/sbin/NetworkManager
[15:54] <Laney> just hotplugged it and then NM crashed
[15:54] <willcooke> erk
[16:05]  * willcooke takes his laptop for a walk.  
[16:05] <willcooke> I wonder if going out of range of the wifi is what crashed it
[16:13] <willcooke> Laney, ok, got some more crashes
[16:16] <Laney> nod
[16:17] <Laney> some wonkiness here
[16:17] <andyrock> didrocks: I'm preparing the update to gnome-control-center. Do we still need the "ubuntu-volume-amplification-to-gnome" migration thing?
[16:18] <didrocks> andyrock: I think not, but let me look
[16:19] <andyrock> was the switch from com.ubuntu.sound to org.gnome.desktop.sound
[16:19] <didrocks> yeah, just checking that was done in bionic
[16:20] <didrocks> andyrock: 1:3.29.90-1~ubuntu1 in cosmic
[16:20] <didrocks> so we need it until next LTS
[16:21] <didrocks> (included)
[16:21] <andyrock> not sure I'm following you but I trust you :D
[16:21] <didrocks> well, we need people to migrate their old settings to the new one
[16:21] <didrocks> and people on bionic have the old settings
[16:21] <andyrock> I guess to allow migration from lts to lts ?
[16:21] <didrocks> so whatever bionic -> <distro version> upgrade needs the migration scripts
[16:21] <didrocks> which are:
[16:22] <didrocks> 1. bionic -> cosmic
[16:22] <didrocks> 2. bionic -> next LTS
[16:22] <andyrock> kk thanks :)
[16:22] <didrocks> yw! :)
[16:22] <Laney> the patch could get a note, sounds like that's not obvious
[16:22] <didrocks> we should maybe add a "can be removed…"
[16:22] <didrocks> yeah, whatever Laney told
[16:22] <Laney> HIGH FIVE
[16:22]  * didrocks high five back
[16:22] <andyrock> I'll add it in the upload
[16:23] <didrocks> andyrock: you can say post f* (if f* is the next LTS)
[16:23] <didrocks> just add that to the migration script, would be a lot of *f*un :p
[16:34] <Laney> willcooke: want to see if 1.12.4 is better? https://people.canonical.com/~laney/package-junkyard/
[16:34] <Laney> at least I didn't make it crash yet
[16:34] <willcooke> Laney, wack.  Installing
[16:35] <Laney> super sick safe solid sound
[16:36] <Laney> even if not this is a better basis for a bug report
[16:36] <willcooke> ruh roh.  My gdm issue is back, even with proposed
[16:40] <Laney> if you could, https://gitlab.gnome.org/GNOME/gdm/issues would be good w/the journal from a failed situation
[16:40] <willcooke> Laney, will do.  Just installing the n-m stuff
[16:40] <Laney> thx
[16:40] <willcooke> and then will do more on that one
[16:41] <willcooke> (it's possible that enabling debug is what fixed it :) )
[16:41] <willcooke> k, nm installed
[16:43]  * Laney does 20 minutes of queue reviews
[16:49] <willcooke> Laney, anecdotally, it seems to restore network connectivity from resume faster
[16:49]  * willcooke takes his laptop for another walk
[16:49] <willcooke> it gets out more than I do
[16:55] <willcooke> Laney, well, same tests as earlier, suspend/resume when in range of different access points now doesnt segfault, and yeah, it does feel faster to reconnect on resume.
[16:55] <willcooke> ship it
[16:55] <willcooke> I'll keep an eye on it
[16:56] <willcooke> now, gdm3....
[16:56] <Laney> kool
[16:57] <willcooke> ohhhh, and now I think I see why I wasnt seeing more useful logging from gdm3
[16:57] <willcooke> More verbose logs
[16:57] <willcooke> I thought that was just a comment, but I think that's the actual config
[16:58] <Laney> it's Enable=true or something
[17:01] <Laney> climbing -> pub quiz -> bed -> breakfast -> IRC
[17:01] <Laney> LATERS!
[17:03] <willcooke> l8r Laney
[17:18] <willcooke> gdm3 upstream bug: https://gitlab.gnome.org/GNOME/gdm/issues/428
[17:19] <gitbot> GNOME issue 428 in gdm "Ubuntu 18.10 boots to black screen with flashing cursor, no gdm. Switching to tty2 and back to 1 fixes it." [Opened]
[17:19] <willcooke> <- dinner
[17:37] <andyrock> Laney: I just built gnome-control-center and I got the python-script-but-no-python-dep from the lintian, should I fix it using the way suggested here? https://lintian.debian.org/tags/python-script-but-no-python-dep.html
[17:37] <andyrock> it has been ignored for a while, that's why I'm asking
[17:40] <andyrock> as a side-note I noticied that 08_lowercase_user_names.patch ( Disallow upper-case letters in user names for compliance with adduser) has never been ported to debian, so I'm planning to do so, if that's ok
[17:43] <Trevinho> willcooke: in that gdm issue, you get also a crash, or just doesn't show up?
[17:44] <Trevinho> Also maybe xorg logs might help or the ones in `/var/lib/gdm3/.local/share/xorg/`
[17:44] <Trevinho> while might be the same of /var/log, but... just to check..
[17:45] <xnox> somehow i have different gdm3 bugs too
[17:45] <xnox> not as severe, but somehow my tty1 is left in framebuffer mode and gdm3 cannot handle that
[17:45] <xnox> whatever that means
[17:45] <tjaalton> so echoing here too, that the xserver crash is due to mesa enabling a feature on the software fallback driver, which makes glamor init pass now (didn't succeed in bionic), so adding a patch to the xserver should fix the vbox/qemu issues
[17:46] <andyrock> \o/
[17:47] <tjaalton> hmm
[17:47] <Trevinho> tjaalton: lovely
[17:49] <tjaalton> hmm hang on, need to verify it
[17:49] <willcooke> tjaalton, \o/
[17:49] <willcooke> (well, potentially \o/)
[17:50] <willcooke> Trevinho, no crash that I can see, just doesnt seem to start
[17:50] <Trevinho> mh, I see... willcooke also jouralctl log might help so that we can also see gnome-shell logs in case
[17:51] <willcooke> Trevinho, in case it's useful I just added the log for when I switch to tty1 and things kick in to life: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637
[17:51] <willcooke> I can attach that to the upstream bug if you think it's useful
[17:51] <willcooke> I'll get the other log now
[17:51] <Trevinho> let me see
[17:52] <willcooke> damn ittttttttttttttttttt
[17:52] <Trevinho> even 1st log was with debugging enabled, right?
[17:52] <willcooke> now it's bloody working again
[17:52] <Trevinho> haha
[17:52] <willcooke> Trevinho, yeah,
[17:52] <willcooke> it was enabled
[17:52] <Trevinho> races are racy!
[17:52] <willcooke> :))
[17:52] <jbicha> andyrock: we don't need or want to use dh_python for gnome-control-center but you can add python3 to Depends
[17:53] <andyrock> jbicha: the problem is that the offending python script is a migrations cript
[17:53] <andyrock> *script
[17:53] <andyrock> how to handle this case?
[17:53] <jbicha> andyrock: or just ignore the lintian error since we already indirectly depend on python3 (via system-config-printer at least)
[17:54] <andyrock> kk I'll ignore for the moment but would be nice to get rid of it
[17:54] <jbicha> we'll get rid of it in F ;)
[17:55] <andyrock> :(
[17:58] <jbicha> I said you can add the python3 depends if the lintian error bothers you
[18:00] <willcooke> Trevinho, do you think that gdm issue could be related to https://gitlab.freedesktop.org/xorg/xserver/commit/0a9415cf793babed1f28c61f8047d51de04f1528 (the one t_jaalton mentions might fix vbox)
[18:02] <Trevinho> mh, don't think so as in real hw you should be able to use proper driver, not llvmpipe (sw emulation)
[18:04] <willcooke> ah of course
[18:28] <willcooke> calling it a night, see you tomorrow
[18:33] <tjaalton> hmm I'll add that patch to xserver anyway, even though I couldn't find which commit in newer mesa made glamor init succeed
[18:59] <seb128> oSoMoN, that was bug #1793476
[19:00] <seb128> oSoMoN, unsure we got a langpack update since g-s was rebuilt with that version though
[19:00] <seb128> Trevinho, let's talk tomorrow about the kvm one, I'm not sure to understand the details
[19:13] <jbicha> oSoMoN: there were some issues with gnome-shell 3.30.0 translation handling, should be fixed whenever they do a 3.30.1. here are some links:
[19:13] <jbicha> https://lists.ubuntu.com/archives/ubuntu-translators/2018-October/007517.html
[19:13] <jbicha> https://gitlab.gnome.org/GNOME/gnome-shell/issues/537
[19:13] <gitbot> GNOME issue 537 in gnome-shell "Strings are no longer extracted by gettext" [1. Bug, 8. Translation, Closed]
[19:13] <jbicha> https://gitlab.gnome.org/GNOME/gnome-shell/issues/614
[19:13] <gitbot> GNOME issue 614 in gnome-shell "Badly unused strings in pofiles" [Opened]
[20:12] <oSoMoN> seb128, jbicha: thanks for the links!