[01:21] <duflu> RAOF: I just noticed in some user logs the SNMP/MIB/OID errors from colord. Is a fix planned for that?
[01:22] <RAOF> duflu: As soon as sane is fixed, sure.
[01:22] <duflu> Kay, ta
[01:22] <RAOF> Or, rather, those errors aren't from colord; they're from libsane (or, likely, from one of the absolute garbage plugins that it loads).
[01:23] <RAOF> You'll also see those errors should you start `simple-scan` from a terminal :)
[07:18] <didrocks> good morning
[07:18] <seb128> hey didrocks :)
[07:26] <duflu> Hi didrocks
[07:27] <didrocks> hey hey! :)
[07:32] <oSoMoN> good morning desktoppers
[07:36] <duflu> Morning oSoMoN
[07:38] <didrocks> salut oSoMoN
[07:38] <oSoMoN> good afternoon duflu
[07:38] <oSoMoN> salut didrocks
[07:44] <duflu> I don't think all users know what version of Ubuntu they are downloading. Every time we announce a new release I see a spike of users installing the last LTS and not the most recent release
[07:44] <duflu> Or maybe they do, and the news sparks their interest
[07:44] <jibel> duflu, where do you see this spike?
[07:45] <duflu> jibel, in my bug mail
[07:45] <jibel> duflu, you mean lp bug reports?
[07:45] <duflu> Yes. And people commenting "me too" on old bugs
[07:45] <jibel> I don't see any particular spike in the installer bugs
[07:46] <duflu> OK. My experience is not a scientific measurement
[07:46] <oSoMoN> duflu, to be fair, the "Download 18.10 now" link on https://ubuntu.com takes you to https://www.ubuntu.com/download, where you can go to https://www.ubuntu.com/download/desktop, and the first, most prominent option there is to download 18.04
[07:46] <duflu> Yeah
[07:46] <oSoMoN> that's broken UX
[07:47] <jibel> and ubuntu-report doesn't show more installations of 18.04
[07:48] <jibel> oSoMoN, ah right, you want to submit a bug report? otherwise I'll do
[07:48] <oSoMoN> jibel, can do, do you know where I should file that?
[07:49] <jibel> oSoMoN, https://github.com/canonical-websites/www.ubuntu.com/issues/new?body=%0a%0a%0a---%0a*Reported%20from:%20https://www.ubuntu.com/download/desktop*
[07:49] <seb128> lut jibel oSoMoN, en forme?
[07:51] <Trevinho> Morning..
[07:51] <oSoMoN> salut seb128, ça va, et toi?
[07:51] <jibel> seb128, ça va bien et toi?
[07:51] <oSoMoN> buon giorno Trevinho
[07:52] <oSoMoN> neat, there's a "Report a bug on this site" link, I hadn't noticed…
[07:53] <seb128> ça va bien :)
[07:53] <seb128> good morning Trevinho!
[07:53] <Trevinho> oSoMoN: salut!
[07:54] <Trevinho> y à tois, seb
[07:54] <didrocks> hello Trevinho
[07:55] <oSoMoN> jibel, https://github.com/canonical-websites/www.ubuntu.com/issues/4267
[07:55] <gitbot> canonical-websites issue 4267 in www.ubuntu.com ""Download 18.10 now" directs to a generic download page which offers 18.04 first" [Open]
[07:56] <Trevinho> didrocks: bonjour!
[07:56] <Trevinho> kenvandine: might it https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1793496
[08:02] <Laney> pew
[08:03] <didrocks> hey Laney
[08:04] <oSoMoN> good morning Laney
[08:04] <Laney> hi didrocks oSoMoN
[08:05] <seb128> howdy Laney
[08:05] <seb128> & robert_ancell
[08:05] <seb128> lol
[08:07] <Laney> moin seb128
[08:09] <duflu> Morning Trevinho and Laney
[08:16]  * Laney nods solemnly in the direction of duflu 
[08:28] <tjaalton> I'm seeing issues with the shell where returning from the "screensaver" shows the launcher panel but the desktop just remains purple
[08:29] <tjaalton> only way to get around that is to suspend/resume
[08:29] <tjaalton> but the next time it'll do the same thing again
[08:32] <seb128> Trevinho, Laney, duflu, ^ do you have an idea about that?
[08:33] <Trevinho> MHMH
[08:33] <Trevinho> tjaalton: is nautilus-desktop running properly there?
[08:33] <Laney> not sure why I would in particular, so no
[08:33] <Laney> journal?
[08:33] <duflu> tjaalton, I saw the launcher on top of the lock screen once this year... and only once
[08:33] <Laney> never seen anything like that personally
[08:33] <seb128> k
[08:34] <Trevinho> nope, I mean just at unity times we had something like that
[08:34] <seb128> sorry, ping was a bit random but I though those were the people who fiddled a bit with gnome-shell/rendering issues
[08:34] <tjaalton> Trevinho: seems to be
[08:34] <duflu> tjaalton, maybe a bug report with a photo/screenshot would help
[08:35] <Trevinho> tjaalton: killing restarting that helps ?
[08:35] <seb128> Laney, Trevinho, do you understand why bastien asked me to "rebase" on https://gitlab.gnome.org/GNOME/totem/merge_requests/18 ? there is no commit in gnome-3-30 since I created my branch off it, unsure what rebase would do/how it would be useful then?
[08:35] <gitbot> GNOME issue (Merge request) 18 in totem "Gallery correct options" [Opened]
[08:35] <tjaalton> Trevinho: haven't tried that yet.. I'll try get a screenshot first
[08:35] <seb128> oh
[08:35] <seb128> "The source branch is 1 commit behind the target branch"
[08:35] <seb128> hum
[08:35] <seb128> oh, maybe I didn't pull before doing my fix
[08:35] <seb128> Laney, Trevinho, unping :p
[08:36] <Trevinho> seb128: pull --rebase is your friend :)
[08:36] <seb128> let's see how that works
[08:36] <seb128> $ git pull --rebase
[08:36] <seb128> La branche courante gallery-correct-options est à jour.
[08:36] <Trevinho> or use the web ui and reset to that, but, well better to do it locally first
[08:36] <duflu> seb128, try ticking "Allow commits from members who can merge to the target branch" so that the committer is able to do it themselves without needing you
[08:36] <Trevinho> and then ofc push -f to your remote
[08:37] <seb128> Trevinho, the pull --rebase didn't bring that new commit in
[08:37] <duflu> It's really just giving permission to rebase and change the final commit's hash
[08:37] <seb128> do I need to "origin gnome-3-30" to it?
[08:37] <Trevinho> seb128: pull --rebase origin master eh
[08:37] <Laney> gnome-3-30
[08:37] <Trevinho> or well the branch name
[08:38] <seb128> $ git pull --rebase origin gnome-3-30
[08:38] <seb128> Depuis gitlab.gnome.org:seb128/totem
[08:38] <seb128>  * branch            gnome-3-30 -> FETCH_HEAD
[08:38] <seb128> La branche courante gallery-correct-options est à jour.
[08:38] <seb128> "git log" still doesn't have the missing commit though
[08:39] <seb128> ah
[08:39] <seb128> it's because my origin is my fork
[08:39] <seb128> not master
[08:39] <Trevinho> ah, right
[08:39] <Trevinho> so use the gitlab url instead
[08:39] <seb128> yeah, doing so
[08:40] <Trevinho> not sure if you made an alias, but you might add gnome:totem as shorturl if you setup gnome as an insteadof url
[08:40] <seb128> better :)
[08:40] <Laney> tjaalton: dunno if you missed my "journal?" but I suggest attaching that
[08:40] <tjaalton> Laney: got it, thanks
[09:46] <duflu> tjaalton, I am playing with nvidia-390 today. I assume the missing KMS support by default is by design. What's the correct way to enable it?
[09:50] <tjaalton> duflu: best to ask tseliot
[09:51] <tjaalton> so I just restarted shell and it crashed
[09:52] <duflu> Crash files please :)
[09:53] <duflu> Or crash reports.
[09:53] <tjaalton> I don't think apport is enabled anymore
[09:53] <tjaalton> at least there wasn't a dialog to file it
[09:54] <duflu> tjaalton, ;)  https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
[09:54] <tjaalton> yeah, ubuntu-bug works
[09:55] <duflu> tseliot, I just tried nvidia-390 in cosmic for the first time. Surprised to find it makes the machine unbootable because KMS is still enabled in the kernel but absent in the driver. Not a good user experience. Is that known?
[09:56] <duflu> (this is now a purely Nvidia system since I disabled the integrated GPU)
[09:56] <tjaalton> https://errors.ubuntu.com/oops/c745da6c-d6a9-11e8-949a-fa163ee63de6
[09:56] <duflu> tjaalton, which is bug 1796607
[09:57] <tjaalton> alright, subscribed
[10:00] <duflu> Wait, that's only in my dev build and in someone else's bug report. My main installation is working. I wonder how
[10:03] <duflu> I guess gdm fallback to X must be working. Just not for everyone
[10:07] <duflu> Yes. I must stop trying to do 3 things at once
[10:50] <tseliot> duflu: when KMS is enabled (which it is on hybrid graphics), Gdm causes problems on some machines. Lightdm doesn't. I'm thinking of disabling KMS again if gdm is in use
[10:51] <tseliot> at least until I have the time to see what's wrong in gdm
[10:52] <duflu> tseliot, I noticed that too. But I was confused by doing 3 things at once. In the end it was only one user's machine where gdm3 is failing to fall back from Wayland to X11. Although the upstream bug reports about similar are numerous. It's a gdm3 bug so ignore me, and good night.,
[11:11] <zyga> hey
[11:12] <zyga> is there anyone from the desktop team, I could talk to to escalate an issue
[11:12] <zyga> in absence of willcooke
[11:12] <jibel> zyga, what is the issue?
[11:13] <zyga> jibel: https://launchpad.net/bugs/1799433 <- but Nvidia not really needed
[11:13] <zyga> just run:
[11:14] <zyga> sudo udevadm trigger; sudo udevadm settle;
[11:14] <zyga> then ^D in terminal to kill stuff
[11:14] <zyga> affects popey, I reproduced this on cosmic easily now
[11:15] <jibel> what does "Desktop explodes" exactly means? I hope no one has been injured by this bug
[11:15] <jibel> popey, ^
[11:16] <popey> https://bugs.launchpad.net/snapd/+bug/1799433
[11:16] <popey> oh, you have that, duh
[11:16] <zyga> jibel: X crashes (nvidia) or some parts of shell crash (intel)
[11:16] <popey> all applications and the desktop dies
[11:16] <popey> black screen
[11:16] <zyga> jibel: I'm going through logs on my system now
[11:17] <jibel> zyga, popey can one of you please reproduce and attach the journal?
[11:17] <zyga> popey: can you please do that
[11:17] <zyga> I will follow up with non-nvidia one
[11:17] <popey> reproduce what? I filed the bug! :)
[11:18] <zyga> I think the outcome is different, Nvidia dies "harder"
[11:18] <zyga> in my case gdm crashes, I think
[11:18] <zyga> but let me double check
[11:19] <popey> I've already had my entire desktop explode twice today. I kinda need to do some work so I'd rather not explode it again
[11:19] <popey> what journal am I attaching?
[11:20] <jibel> journalctl -b
[11:20] <jibel> after the crash
[11:20] <popey> i have since rebooted, can I still get the journal from the previous crash?
[11:20] <jibel> yes
[11:21] <jibel> journalctl --list-boots to identify which boot
[11:21] <zyga> note, after rebooting I cannot reproduce this - perhaps there is more "state" required somehow
[11:21] <jibel> then journalctl -b <id>
[11:21] <zyga> let me look at the past case like jibel suggests
[11:22] <popey> sorry, this journalctl thing is obtuse, how do I get the full log, not a pager?
[11:22] <zyga> Oct 08 12:20:54 fyke gdm3[1257]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
[11:22] <jibel> where does nsenter comes from? I cannot find a package in the archive
[11:22] <zyga> Oct 08 12:20:54 fyke gnome-session-binary[1557]: CRITICAL: We failed, but the fail whale is dead. Sorry....
[11:22] <zyga> (going backwards)
[11:22] <popey> ok, http://paste.ubuntu.com/p/jcqYz593px/ attached to bug
[11:22] <zyga> util-linux
[11:23] <zyga> I think doing "udevadm trigger" makes gdm unhappy
[11:23] <zyga> all kinds of bad stuff is logged
[11:26] <zyga> hmmm
[11:26] <zyga> I wonder why I cannot reproduce it anymore
[11:32] <zyga> jibel, popey, mborzecki: I cannot reproduce this again, it failed once on VMware though (not Nvidia)
[11:34] <zyga> looking at my logs from that boot I found: Oct 23 13:10:39 fyke kernel: [drm:vmw_stdu_crtc_page_flip [vmwgfx]] *ERROR* Page flip error -16.
[11:35] <zyga> also
[11:35] <zyga> Oct 23 13:12:27 fyke systemd-logind[1424]: Session c1 logged out. Waiting for processes to exit.
[11:35] <zyga> Oct 23 13:12:27 fyke at-spi-bus-launcher[78191]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1024"
[11:48] <jibel> I cannot reproduce on a fresh install of cosmic. The nsenter command fails with: /usr/bin/locale-check: No such file or directory
[11:48] <zyga> jibel: that's bash
[11:48] <zyga> but it is inside already
[11:48] <zyga> hmmm
[11:48] <zyga> so whatever is causing it is more complex
[11:48] <zyga> this machine was otherwise through a few suspend resume cycles
[11:48] <zyga> and countless app runs
[11:48] <zyga> so the good thing is that it doesn't happen all the time
[11:53] <zyga> jibel: perhaps related: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1760104
[12:02] <jibel> zyga, no apparently it's gdm that decides to restart the session when the session of root is closed
[12:02] <zyga> oh
[12:02] <zyga> that's interesting
[12:02] <zyga> what is the meaning of session in this case?
[12:02] <zyga> and how does gdm know?
[12:02]  * zyga would like to understand the current desktop stack more 
[12:02] <jibel> zyga, the sudo session
[12:03] <zyga> aha
[12:03] <zyga> sudo creates a session?
[12:03] <zyga> actually, what I meant is that session has many meanings
[12:06] <zyga> so not sure what type of session is this
[12:54] <GunnarHj> Hi didrocks, are we now talking about approximately the same things? :)
[13:00] <didrocks> GunnarHj: sounds like it :)
[13:02] <zyga> pstolowski: hey, standup time
[13:06] <GunnarHj> didrocks: I think it's highly desirable to involve someone who is reasonably familiar with the Ubiquity code. Would that be you these days?
[13:08] <pstolowski> zyga: oh
[13:08] <didrocks> GunnarHj: what I told, depending on the potential new installer, we might or not change ubiquity
[13:08] <didrocks> otherwise, there is no point in investing into ubiquity if we are going with another solution in the coming cycle(s)
[13:09] <GunnarHj> didrocks: That makes sense, of course. Does it mean that those things are currently not first in the queue?
[13:11] <didrocks> GunnarHj: right, it's more as we looked at those issue during cosmic release, we thought at first it was a regression, then, the goal was to understand the intent and what we might want to change in a new architecture (if we go for it)
[13:12] <didrocks> I guess we have a clear understand
[13:12] <didrocks> understanding now*
[13:12] <didrocks> I would be interested to try your patch though, the one liner
[13:12] <didrocks> let's see for d*
[13:13] <GunnarHj> didrocks: Yeah, it would be interesting to see if that does what I hope.
[13:15] <didrocks> yep :)
[13:24]  * zyga gets back to reviews but first needs to make coffee
[13:30] <seb128> ok, meeting time
[13:30] <seb128> #startmeeting Desktop Team Weekly Meeting 23 October 2018
[13:30] <meetingology> Meeting started Tue Oct 23 13:30:27 2018 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
[13:30] <seb128> Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel, heber, kenvandine (out), laney, oSoMoN, tkamppeter, trevinho, robert_ancell (out), tjaalton, tseliot
[13:30] <Trevinho> o/
[13:30] <seb128> Happy post-cosmic & no-d-name-yet meeting!
[13:30] <heber> o/
[13:30] <jibel> hi
[13:30] <andyrock> o/
[13:31] <didrocks> hey!
[13:31] <oSoMoN> \o
[13:31] <Laney> sup
[13:31] <tjaalton> yo
[13:31] <seb128> k, let's get started
[13:32] <seb128> I don't expect that one to be long, there has been less tagged bugs that I though we would have, which is probably good sign :)
[13:32] <seb128> #topic rls-bugs
[13:32] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[13:32] <seb128> bug #1798053 is the only one there
[13:32] <andyrock> is it easy to reproduce?
[13:33] <seb128> That got several duplicates, we have a team member (osomon) who can reproduce
[13:33] <oSoMoN> yes, 100% reproducible
[13:33] <seb128> it's a key app and it's not reflecting good
[13:33] <seb128> I would +1 to target it
[13:33] <didrocks> well, looks like easy to reproduce, worth fixing, °1
[13:33] <didrocks> +1*
[13:33] <seb128> oSoMoN, do you want to have a look since you can reproduce or you are too busy with other things and prefer Robert to get it?
[13:34] <seb128> get->take
[13:34] <oSoMoN> I can have a quick look and if I can't figure it out I'll pass it to Robert
[13:34] <seb128> k, thx
[13:34] <seb128> next
[13:35] <seb128> let's review http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html quickly
[13:35] <seb128> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280
[13:35] <Trevinho> I'm on properly fixing it
[13:35] <andyrock> I  lost connection on the pc
[13:35] <seb128> it's fixed for gdm3/fbdev ... do we consider it fixed with the xorg-server line to close?
[13:36] <seb128> Trevinho, in xserver? because the gdm part is closed
[13:36] <Trevinho> seb128: well, gdm3 part is workarounded :)
[13:36] <seb128> tjaalton, is there a fix in xorg needed there is should that line be invalid? ^
[13:36] <Laney> the rls part is fixed
[13:36] <Laney> at least in gdm
[13:36] <seb128> Trevinho, k, please open another bug for your improvement
[13:36] <Laney> replacing it is not rls
[13:36] <seb128> makes sense
[13:36] <Trevinho> agree
[13:36] <seb128> thx Laney Trevinho
[13:37] <Laney> dunno about xorg, as far as I know that is invalid at least for cosmic
[13:37] <seb128> I guess https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1796822 is fixed as well
[13:37] <seb128> or same situation
[13:37] <seb128> the initramfs change fixed the release issue
[13:37] <seb128> xorg line might be to close or not, but not needed to be targetted at this point
[13:37] <Trevinho> Laney: x side isn't invalid when using kvm + std driver. But for lower level issues I think. tjaalton knows better.
[13:37] <Trevinho> low prio though
[13:37] <seb128> https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1794951
[13:37] <Laney> should be assigned then if it's being fixed.
[13:38] <seb128> is fixed according to will's comment, I'm going to wait for him to confirm and close
[13:38] <seb128> the other ones seem assigned/on track and don't need discussion
[13:39] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:39] <seb128> that has a bug with a patch https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1797604
[13:39] <mdeslaur> jbicha: I think you added a bad shebang here: https://salsa.debian.org/gnome-team/gnome-screensaver/commit/eee80254cec8af6c8f66e3307b4b61a639f22e2e
[13:40] <seb128> mdeslaur, hey, we are in the middle of a meeting :)
[13:40] <mdeslaur> oh, whoops
[13:40] <seb128> so that intel bug, it makes some video card work better, I would +1 to accept the nomination
[13:41] <seb128> tjaalton, ^ can you have a look at getting that into bionic?
[13:41] <tjaalton> checking
[13:42] <seb128> anyway, if nobody disagree I accept it for bionic
[13:43] <tjaalton> -intel isn't used by default
[13:43] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[13:43] <seb128> tjaalton, k, needs to be looked at more into details then I guess
[13:44] <seb128> the bb tracking list is still out of shape, I'm starting cleaning it now but let's kip for this week again
[13:44] <seb128> sorry about that
[13:44] <seb128> that's it from the rls bugs
[13:44] <seb128> #topic AOB
[13:44] <seb128> any other topic?
[13:45] <andyrock> none from me
[13:45] <didrocks> neither
[13:45] <Trevinho> fine here too, I'd have some SRU shell question, but I guess not whole team related :)
[13:45] <seb128> k, short and efficient then (the bug section still felt a bit cahotic to me though, unsure why)
[13:45] <seb128> let's wrap
[13:46] <andyrock> it would be nice to discuss bugs to upset La_ney
[13:46] <seb128> thanks everyone!
[13:46] <seb128> #endmeeting
[13:46] <meetingology> Meeting ended Tue Oct 23 13:46:05 2018 UTC.
[13:46] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-10-23-13.30.moin.txt
[13:46] <seb128> andyrock, haha
[13:46] <didrocks> thx!
[13:46] <oSoMoN> thanks
[13:46] <Trevinho> thx
[13:48] <seb128> Trevinho, what are your g-s SRU questions?
[13:49] <seb128> we should get a SRU going to cosmic, at least to get the keyboard layout switch fix from andyrock/garnacho
[13:49] <Trevinho> well, nothing much new... I asked already few weeks ago for a point release, but still nothing... So I'd say when we define a deadline for "ok, we go for a git snapshot" instead? :-/
[13:49] <Trevinho> well, I was speaking mostly for bionic here
[14:19] <kenvandine> Trevinho: symptom sounds right, but he said it was fine on bionic.  It started after upgrading to cosmic.  That bug says bionic.
[14:19] <kenvandine> Trevinho: i'll point him at that
[14:19] <Trevinho> kenvandine: I don't remember much changes on that side in mutter, but I might be wrong.
[14:20] <jbicha> mdeslaur: it came that way from Ubuntu. Do you think it's better to remove the gnome-screensaver apport shebang completely?
[14:20] <kenvandine> Trevinho: i'll point him at that bug though, thanks
[14:21] <mdeslaur> jbicha: it wasn't like that in the previous ubuntu version. Just remove the two + signs, as it's causing the hook to fail now.
[14:22] <seb128> hey kenvandine, how is SLC going?
[14:22] <seb128> kenvandine, can you check if https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1794951 should be closed? we were not sure what to do with it during the meeting
[14:24] <seb128> jbicha, mdeslaur, the error was added in http://launchpadlibrarian.net/350649809/gnome-screensaver_3.6.1-7ubuntu6_3.6.1-8ubuntu1.diff.gz
[14:25]  * mdeslaur nods
[14:25] <seb128> jbicha, seems like you did that when you renamed/added to Debian?
[14:26]  * didrocks has a vm ready, trying refreshing to latest gnome-platform
[14:27] <didrocks> gnome-3-26-1604 rev 74 is still slow to me for first app startup
[14:29] <seb128> didrocks, thx for testing
[14:29] <didrocks> yw (commented)
[14:30] <seb128> kenvandine, ^
[14:31] <seb128> didrocks, current revision is 75 though?
[14:32] <didrocks> ah, not what snap refresh refreshed here
[14:33] <didrocks> seb128: http://paste.ubuntu.com/p/3PQyKPGSnb/
[14:33] <didrocks> do you see something different?
[14:37] <seb128> didrocks, yes,
[14:37] <seb128> channels:
[14:37] <seb128>   stable:    3.26.0 (75) 153MB -
[14:37] <seb128>   candidate: 3.26.0 (75) 153MB -
[14:38] <seb128> but that partition is still i386, so probably a mismatch between archs
[14:38] <Laney> 74 here
[14:38] <seb128> which I don't know if expected, or if it means 75 failed to publish on amd64?
[14:38] <didrocks> seb128: ah, the rev is a build #
[14:38] <Laney> that makes sense
[14:38] <didrocks> no
[14:38] <didrocks> build 74 is amd64
[14:38] <didrocks> build 75 is i386
[14:38] <seb128> how do we know it's the current build?
[14:38] <seb128> sometime the store fails to accept updates
[14:39] <seb128> maybe the fix is in 75 that failed to upload?
[14:39] <seb128> or do you say the change is in 74?
[14:39] <didrocks> ah, so you mean, build 76 failed?
[14:39] <seb128> I don't know how to check
[14:39] <didrocks> just that the "rev" is a build number
[14:39] <didrocks> meaning, on 2 archs, you won't have the same "rev", ever never
[14:39] <seb128> right, but how do we know if 74 include the change we want to see?N
[14:39] <didrocks> so yeah, maybe there was an upload, kicking off build 75 and 76
[14:39] <willcooke> 74 should have the font cache fix
[14:39] <didrocks> and 76 failed
[14:40] <didrocks> There is no way to know that rev 74 and 75 have the same source code
[14:40] <willcooke> 76 might have been arm
[14:40] <didrocks> also, yeah
[14:41] <didrocks> but yeah, apart from trusting "latest release stuff" from snap info, there is no way to know (or have access to the backend of snapcraft.io)
[14:41] <seb128> k
[14:41] <seb128> willcooke, hey, how is SLC?
[14:41] <seb128> willcooke, so yeah, seems like that fix isn't good enough for everyone then :/
[14:41] <didrocks> willcooke: doesn't work for me, are you sure you removed the snap cache?
[14:41] <seb128> didrocks, it wfm
[14:42] <didrocks> weird, this vm is fairly vanilla
[14:42] <seb128> the other day "rm -rf ~/snap/gnome-calculator; time /snap/bin/gnome-calculator" was taking 35s and not it takes 3s
[14:42] <didrocks> seb128: once you removed ~/snap/gnome-calculator/…
[14:42] <seb128> not->now
[14:42] <willcooke> seb128, hey!  I can't remember exactly now, but I'm pretty sure I tested it properly
[14:43] <didrocks> let me revert between the 2
[14:43] <willcooke> I'm installing a new Vbox now
[14:43] <didrocks> it's from a vm, so a little it less stable ofc…
[14:43] <seb128> willcooke, right, it works for me as well, but if it doesn't for didrocks it might mean it still depends of the local config you have
[14:44] <didrocks> wait, I'm in the GNOME vanilla session on this VM
[14:44] <didrocks> just in case…
[14:44] <didrocks> maybe it's font-cantarell or such
[14:44] <kenvandine> seb128: good, i'll handle it
[14:44] <seb128> kenvandine, thx
[14:44] <seb128> didrocks, that should be in the system or user cache though :/
[14:45] <didrocks> indeed, switched session, let's time
[14:46] <kenvandine> seb128, didrocks:  rev 74 is the right build for amd64
[14:46] <kenvandine> and the revision that both willcooke and i tested
[14:46] <didrocks> http://paste.ubuntu.com/p/8KFqHv6g4S/
[14:47] <kenvandine> i did a fresh install, refreshed gnome-3-26-1604 and it was fast to start
[14:47] <didrocks> kenvandine: doesn't seem to be really good in my VM ^
[14:47] <didrocks> I ctrl+C once gnome-calculator appears
[14:47] <didrocks> tried twice with downgrading + upgrading again
[14:47] <kenvandine> :/
[14:47] <didrocks> (qemu, but I don't think that should impact)
[14:47] <didrocks> fresh install in the VM, only hacked on GNOME Shell in it + installed gnome-session package
[14:47] <didrocks> (and pastebinit… :p)
[14:48] <kenvandine> willcooke: do you have the iso locally and can do a fresh VM install?
[14:48] <willcooke> kenvandine, doing it right now
[14:48] <kenvandine> thanks
[14:48] <didrocks> is there a way I can trigger some timing debug log?
[14:48] <kenvandine> SNAP_DESKTOP_DEBUG=1
[14:49] <kenvandine> that will give you times for desktop-launch
[14:49] <didrocks> let me see if I can spawn some useful info for you
[14:49] <kenvandine> unfortunately the fontconfig slow down is after desktop-launch is done
[14:49] <didrocks> ah :/
[14:49] <didrocks> yeah
[14:49] <didrocks> desktop-launch elapsed time:  0.321640466
[14:49] <didrocks> Now running: exec gnome-calculator
[14:49] <didrocks> then, it waits…
[14:49] <didrocks> so probably triggering fontconfig
[14:49] <kenvandine> approximately how long?
[14:50] <didrocks> 1às
[14:50] <didrocks> 10s*
[14:50] <didrocks> before showing ** (gnome-calculator:6823): WARNING **: 16:50:18.525: currency.vala:412: Currency VEF is not provided by IMF or ECB
[14:50] <willcooke> erm, got an installer crash in vbox
[14:51] <didrocks> willcooke: enough mem allowed?
[14:51] <willcooke> 1.7GB
[14:51] <willcooke> maybe not
[14:51] <didrocks> yeah, should be good
[14:51] <willcooke> This is the same vm config I used last week, so odd.
[14:52] <willcooke> didrocks, I found a good indicator for the start up issue was to look at the disk light.  If it was on a lot, then probably rebuilding font cache
[14:53] <didrocks> I guess the 10s is rebuilding the font cache
[14:53] <didrocks> so why on that config? odd
[14:53] <willcooke> woah, this is odd
[14:53] <willcooke> it is still intsalling
[14:53] <willcooke> but it's reported a crash
[14:53] <kenvandine> didrocks: the fontconfig slowdown was ~25s
[14:54] <kenvandine> maybe the 10s is just from slow disk access in qemu?
[14:54] <kenvandine> 10s seems way too fast
[14:54] <didrocks> kenvandine: why then rev 70 has the same startup time?
[14:54] <didrocks> "relatively fast" ;)
[14:54] <didrocks> or did rev 70 already had the fix?
[14:55] <kenvandine> no...
[14:55] <kenvandine> weird
[14:55]  * didrocks puzzled as well
[14:59] <seb128> time depends of the disk/cpu though
[15:04] <didrocks> right, but we should see a difference between rev 70 and 74
[15:04] <didrocks> which is why I started by comparing both
[15:06] <oSoMoN> seb128, bug #1798053 is fixed upstream in the 3.30 branch, the fix is trivial, shall I go ahead and prepare a SRU ?
[15:07] <seb128> oSoMoN, yes please, I can do sponsoring
[15:07] <oSoMoN> ok
[15:15] <willcooke> I installed that new vm and manually refreshed the gnome-3-26-1604 snap
[15:15] <willcooke> and it started in 3 seconds
[15:16] <willcooke> so it could be a different issue
[15:23] <oSoMoN> seb128, gnome-software 3.30.2-0ubuntu8 is in the unapproved queue: http://launchpadlibrarian.net/394533482/gnome-software_3.30.2-0ubuntu7_3.30.2-0ubuntu8.diff.gz
[15:24] <oSoMoN> I'll SRUify the bug report now
[15:25] <seb128> oSoMoN, thx
[16:33] <kenvandine> didrocks no idea, all very weird
[17:14] <oSoMoN> I'm done for today, have a good evening everyone
[21:37] <seb128> andyrock, Trevinho, could one of you add bug #1799293 to their backlog? jibel had that one as well in London (unsure if he's using auto login)
[21:38] <Trevinho> seb128: looking...
[21:38] <seb128> Trevinho, thx, doesn't need to be today and the bug probably lacks details/log you would need
[21:38] <seb128> feel free to "incomplete" it and ask details
[21:39] <Trevinho> mh, doesn't seem needed logs, let me see if I reprodue
[21:39] <Trevinho> ce*
[21:40] <seb128> thx
[21:43] <Trevinho> seb128: mh, I can't reproduce in my vm here... hmmh
[21:46] <seb128> right, I expect we would have heard more about it if it impacted all auto login configs
[21:46] <seb128> could be due to an extension or something...
[21:47] <Trevinho> seb128: you can?
[21:47] <seb128> no...
[21:47] <seb128> don't worry about it for now
[21:47] <seb128> thx for testing
[21:48] <seb128> and you should go to bed at this time :)
[21:48] <Trevinho> I was playing with something... :P
[21:48] <seb128> hehe
[21:48] <seb128> that said I'm calling it a day!
[21:48] <seb128> have a good night Trevinho & desktopers
[21:48] <Trevinho> good night
[21:49] <Trevinho> thanks