/srv/irclogs.ubuntu.com/2018/10/23/#ubuntu-desktop.txt

dufluRAOF: I just noticed in some user logs the SNMP/MIB/OID errors from colord. Is a fix planned for that?01:21
RAOFduflu: As soon as sane is fixed, sure.01:22
dufluKay, ta01:22
RAOFOr, rather, those errors aren't from colord; they're from libsane (or, likely, from one of the absolute garbage plugins that it loads).01:22
RAOFYou'll also see those errors should you start `simple-scan` from a terminal :)01:23
=== pstolowski|afk is now known as pstolowski
didrocksgood morning07:18
seb128hey didrocks :)07:18
dufluHi didrocks07:26
didrockshey hey! :)07:27
oSoMoNgood morning desktoppers07:32
dufluMorning oSoMoN07:36
didrockssalut oSoMoN07:38
oSoMoNgood afternoon duflu07:38
oSoMoNsalut didrocks07:38
dufluI 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 release07:44
dufluOr maybe they do, and the news sparks their interest07:44
jibelduflu, where do you see this spike?07:44
duflujibel, in my bug mail07:45
jibelduflu, you mean lp bug reports?07:45
dufluYes. And people commenting "me too" on old bugs07:45
jibelI don't see any particular spike in the installer bugs07:45
dufluOK. My experience is not a scientific measurement07:46
oSoMoNduflu, 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.0407:46
dufluYeah07:46
oSoMoNthat's broken UX07:46
jibeland ubuntu-report doesn't show more installations of 18.0407:47
jibeloSoMoN, ah right, you want to submit a bug report? otherwise I'll do07:48
oSoMoNjibel, can do, do you know where I should file that?07:48
jibeloSoMoN, 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
seb128lut jibel oSoMoN, en forme?07:49
TrevinhoMorning..07:51
oSoMoNsalut seb128, ça va, et toi?07:51
jibelseb128, ça va bien et toi?07:51
oSoMoNbuon giorno Trevinho07:51
oSoMoNneat, there's a "Report a bug on this site" link, I hadn't noticed…07:52
seb128ça va bien :)07:53
seb128good morning Trevinho!07:53
TrevinhooSoMoN: salut!07:53
Trevinhoy à tois, seb07:54
didrockshello Trevinho07:54
oSoMoNjibel, https://github.com/canonical-websites/www.ubuntu.com/issues/426707:55
gitbotcanonical-websites issue 4267 in www.ubuntu.com ""Download 18.10 now" directs to a generic download page which offers 18.04 first" [Open]07:55
Trevinhodidrocks: bonjour!07:56
Trevinhokenvandine: might it https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/179349607:56
ubot5Ubuntu bug 1793496 in mutter (Ubuntu) "scaling changes when closing/re-opening the lid" [Medium,Triaged]07:56
Laneypew08:02
didrockshey Laney08:03
oSoMoNgood morning Laney08:04
Laneyhi didrocks oSoMoN08:04
seb128howdy Laney08:05
seb128& robert_ancell08:05
seb128lol08:05
Laneymoin seb12808:07
dufluMorning Trevinho and Laney08:09
* Laney nods solemnly in the direction of duflu 08:16
tjaaltonI'm seeing issues with the shell where returning from the "screensaver" shows the launcher panel but the desktop just remains purple08:28
tjaaltononly way to get around that is to suspend/resume08:29
tjaaltonbut the next time it'll do the same thing again08:29
seb128Trevinho, Laney, duflu, ^ do you have an idea about that?08:32
TrevinhoMHMH08:33
Trevinhotjaalton: is nautilus-desktop running properly there?08:33
Laneynot sure why I would in particular, so no08:33
Laneyjournal?08:33
duflutjaalton, I saw the launcher on top of the lock screen once this year... and only once08:33
Laneynever seen anything like that personally08:33
seb128k08:33
Trevinhonope, I mean just at unity times we had something like that08:34
seb128sorry, ping was a bit random but I though those were the people who fiddled a bit with gnome-shell/rendering issues08:34
tjaaltonTrevinho: seems to be08:34
duflutjaalton, maybe a bug report with a photo/screenshot would help08:34
Trevinhotjaalton: killing restarting that helps ?08:35
seb128Laney, 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
gitbotGNOME issue (Merge request) 18 in totem "Gallery correct options" [Opened]08:35
tjaaltonTrevinho: haven't tried that yet.. I'll try get a screenshot first08:35
seb128oh08:35
seb128"The source branch is 1 commit behind the target branch"08:35
seb128hum08:35
seb128oh, maybe I didn't pull before doing my fix08:35
seb128Laney, Trevinho, unping :p08:35
Trevinhoseb128: pull --rebase is your friend :)08:36
seb128let's see how that works08:36
seb128$ git pull --rebase08:36
seb128La branche courante gallery-correct-options est à jour.08:36
Trevinhoor use the web ui and reset to that, but, well better to do it locally first08:36
dufluseb128, 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 you08:36
Trevinhoand then ofc push -f to your remote08:36
seb128Trevinho, the pull --rebase didn't bring that new commit in08:37
dufluIt's really just giving permission to rebase and change the final commit's hash08:37
seb128do I need to "origin gnome-3-30" to it?08:37
Trevinhoseb128: pull --rebase origin master eh08:37
Laneygnome-3-3008:37
Trevinhoor well the branch name08:37
seb128$ git pull --rebase origin gnome-3-3008:38
seb128Depuis gitlab.gnome.org:seb128/totem08:38
seb128 * branch            gnome-3-30 -> FETCH_HEAD08:38
seb128La branche courante gallery-correct-options est à jour.08:38
seb128"git log" still doesn't have the missing commit though08:38
seb128ah08:39
seb128it's because my origin is my fork08:39
seb128not master08:39
Trevinhoah, right08:39
Trevinhoso use the gitlab url instead08:39
seb128yeah, doing so08:39
Trevinhonot sure if you made an alias, but you might add gnome:totem as shorturl if you setup gnome as an insteadof url08:40
seb128better :)08:40
Laneytjaalton: dunno if you missed my "journal?" but I suggest attaching that08:40
tjaaltonLaney: got it, thanks08:40
duflutjaalton, 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:46
tjaaltonduflu: best to ask tseliot09:50
tjaaltonso I just restarted shell and it crashed09:51
dufluCrash files please :)09:52
dufluOr crash reports.09:53
tjaaltonI don't think apport is enabled anymore09:53
tjaaltonat least there wasn't a dialog to file it09:53
duflutjaalton, ;)  https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment09:54
tjaaltonyeah, ubuntu-bug works09:54
duflutseliot, 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:55
duflu(this is now a purely Nvidia system since I disabled the integrated GPU)09:56
tjaaltonhttps://errors.ubuntu.com/oops/c745da6c-d6a9-11e8-949a-fa163ee63de609:56
duflutjaalton, which is bug 179660709:56
ubot5bug 1796607 in gnome-shell (Ubuntu) "gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_display_new → meta_display_open" [Undecided,New] https://launchpad.net/bugs/179660709:56
tjaaltonalright, subscribed09:57
dufluWait, that's only in my dev build and in someone else's bug report. My main installation is working. I wonder how10:00
dufluI guess gdm fallback to X must be working. Just not for everyone10:03
dufluYes. I must stop trying to do 3 things at once10:07
=== ecloud_wfh is now known as ecloud
tseliotduflu: 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 use10:50
tseliotat least until I have the time to see what's wrong in gdm10:51
duflutseliot, 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.,10:52
zygahey11:11
zygais there anyone from the desktop team, I could talk to to escalate an issue11:12
zygain absence of willcooke11:12
jibelzyga, what is the issue?11:12
zygajibel: https://launchpad.net/bugs/1799433 <- but Nvidia not really needed11:13
ubot5Ubuntu bug 1799433 in snapd "GNOME desktop on nvidia crashes when exiting nsenter" [Undecided,New]11:13
zygajust run:11:13
zygasudo udevadm trigger; sudo udevadm settle;11:14
zygathen ^D in terminal to kill stuff11:14
zygaaffects popey, I reproduced this on cosmic easily now11:14
jibelwhat does "Desktop explodes" exactly means? I hope no one has been injured by this bug11:15
jibelpopey, ^11:15
popeyhttps://bugs.launchpad.net/snapd/+bug/179943311:16
ubot5Ubuntu bug 1799433 in snapd "GNOME desktop on nvidia crashes when exiting nsenter" [Undecided,New]11:16
popeyoh, you have that, duh11:16
zygajibel: X crashes (nvidia) or some parts of shell crash (intel)11:16
popeyall applications and the desktop dies11:16
popeyblack screen11:16
zygajibel: I'm going through logs on my system now11:16
jibelzyga, popey can one of you please reproduce and attach the journal?11:17
zygapopey: can you please do that11:17
zygaI will follow up with non-nvidia one11:17
popeyreproduce what? I filed the bug! :)11:17
zygaI think the outcome is different, Nvidia dies "harder"11:18
zygain my case gdm crashes, I think11:18
zygabut let me double check11:18
popeyI've already had my entire desktop explode twice today. I kinda need to do some work so I'd rather not explode it again11:19
popeywhat journal am I attaching?11:19
jibeljournalctl -b11:20
jibelafter the crash11:20
popeyi have since rebooted, can I still get the journal from the previous crash?11:20
jibelyes11:20
jibeljournalctl --list-boots to identify which boot11:21
zyganote, after rebooting I cannot reproduce this - perhaps there is more "state" required somehow11:21
jibelthen journalctl -b <id>11:21
zygalet me look at the past case like jibel suggests11:21
popeysorry, this journalctl thing is obtuse, how do I get the full log, not a pager?11:22
zygaOct 08 12:20:54 fyke gdm3[1257]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed11:22
jibelwhere does nsenter comes from? I cannot find a package in the archive11:22
zygaOct 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
popeyok, http://paste.ubuntu.com/p/jcqYz593px/ attached to bug11:22
zygautil-linux11:22
zygaI think doing "udevadm trigger" makes gdm unhappy11:23
zygaall kinds of bad stuff is logged11:23
zygahmmm11:26
zygaI wonder why I cannot reproduce it anymore11:26
zygajibel, popey, mborzecki: I cannot reproduce this again, it failed once on VMware though (not Nvidia)11:32
zygalooking 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:34
zygaalso11:35
zygaOct 23 13:12:27 fyke systemd-logind[1424]: Session c1 logged out. Waiting for processes to exit.11:35
zygaOct 23 13:12:27 fyke at-spi-bus-launcher[78191]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":1024"11:35
jibelI cannot reproduce on a fresh install of cosmic. The nsenter command fails with: /usr/bin/locale-check: No such file or directory11:48
zygajibel: that's bash11:48
zygabut it is inside already11:48
zygahmmm11:48
zygaso whatever is causing it is more complex11:48
zygathis machine was otherwise through a few suspend resume cycles11:48
zygaand countless app runs11:48
zygaso the good thing is that it doesn't happen all the time11:48
zygajibel: perhaps related: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/176010411:53
ubot5Ubuntu bug 1760104 in nvidia-graphics-drivers (Ubuntu) "Xorg crashed with SIGSEGV in InputReady() from ospoll_wait() from InputThreadDoWork()" [Medium,Confirmed]11:53
jibelzyga, no apparently it's gdm that decides to restart the session when the session of root is closed12:02
zygaoh12:02
zygathat's interesting12:02
zygawhat is the meaning of session in this case?12:02
zygaand how does gdm know?12:02
* zyga would like to understand the current desktop stack more 12:02
jibelzyga, the sudo session12:02
zygaaha12:03
zygasudo creates a session?12:03
zygaactually, what I meant is that session has many meanings12:03
zygaso not sure what type of session is this12:06
GunnarHjHi didrocks, are we now talking about approximately the same things? :)12:54
didrocksGunnarHj: sounds like it :)13:00
zygapstolowski: hey, standup time13:02
GunnarHjdidrocks: I think it's highly desirable to involve someone who is reasonably familiar with the Ubiquity code. Would that be you these days?13:06
pstolowskizyga: oh13:08
didrocksGunnarHj: what I told, depending on the potential new installer, we might or not change ubiquity13:08
didrocksotherwise, there is no point in investing into ubiquity if we are going with another solution in the coming cycle(s)13:08
GunnarHjdidrocks: That makes sense, of course. Does it mean that those things are currently not first in the queue?13:09
didrocksGunnarHj: 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:11
didrocksI guess we have a clear understand13:12
didrocksunderstanding now*13:12
didrocksI would be interested to try your patch though, the one liner13:12
didrockslet's see for d*13:12
GunnarHjdidrocks: Yeah, it would be interesting to see if that does what I hope.13:13
didrocksyep :)13:15
* zyga gets back to reviews but first needs to make coffee13:24
seb128ok, meeting time13:30
seb128#startmeeting Desktop Team Weekly Meeting 23 October 201813:30
meetingologyMeeting started Tue Oct 23 13:30:27 2018 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.13:30
meetingologyAvailable commands: action commands idea info link nick13:30
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting 23 October 2018 | Current topic:
seb128Roll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel, heber, kenvandine (out), laney, oSoMoN, tkamppeter, trevinho, robert_ancell (out), tjaalton, tseliot13:30
Trevinhoo/13:30
seb128Happy post-cosmic & no-d-name-yet meeting!13:30
hebero/13:30
jibelhi13:30
andyrocko/13:30
didrockshey!13:31
oSoMoN\o13:31
Laneysup13:31
tjaaltonyo13:31
seb128k, let's get started13:31
seb128I 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-bugs13:32
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting 23 October 2018 | Current topic: rls-bugs
seb128http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html13:32
seb128bug #1798053 is the only one there13:32
ubot5bug 1798053 in gnome-software (Ubuntu) "Click on the back icon in gnome-software don't work" [High,Confirmed] https://launchpad.net/bugs/179805313:32
andyrockis it easy to reproduce?13:32
seb128That got several duplicates, we have a team member (osomon) who can reproduce13:33
oSoMoNyes, 100% reproducible13:33
seb128it's a key app and it's not reflecting good13:33
seb128I would +1 to target it13:33
didrockswell, looks like easy to reproduce, worth fixing, °113:33
didrocks+1*13:33
seb128oSoMoN, 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:33
seb128get->take13:34
oSoMoNI can have a quick look and if I can't figure it out I'll pass it to Robert13:34
seb128k, thx13:34
seb128next13:34
seb128let's review http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html quickly13:35
seb128https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/179428013:35
ubot5Ubuntu bug 1794280 in xorg-server (Ubuntu Cosmic) "gdm doesn't start on a fresh installation of Cosmic Desktop" [Critical,Confirmed]13:35
TrevinhoI'm on properly fixing it13:35
andyrockI  lost connection on the pc13:35
seb128it's fixed for gdm3/fbdev ... do we consider it fixed with the xorg-server line to close?13:35
seb128Trevinho, in xserver? because the gdm part is closed13:36
Trevinhoseb128: well, gdm3 part is workarounded :)13:36
seb128tjaalton, is there a fix in xorg needed there is should that line be invalid? ^13:36
Laneythe rls part is fixed13:36
Laneyat least in gdm13:36
seb128Trevinho, k, please open another bug for your improvement13:36
Laneyreplacing it is not rls13:36
seb128makes sense13:36
Trevinhoagree13:36
seb128thx Laney Trevinho13:36
Laneydunno about xorg, as far as I know that is invalid at least for cosmic13:37
seb128I guess https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1796822 is fixed as well13:37
ubot5Ubuntu bug 1796822 in xorg-server (Ubuntu Cosmic) "Desktop live cd boots corrupted screen in Virtualbox on Bionic" [Critical,Confirmed]13:37
seb128or same situation13:37
seb128the initramfs change fixed the release issue13:37
seb128xorg line might be to close or not, but not needed to be targetted at this point13:37
TrevinhoLaney: x side isn't invalid when using kvm + std driver. But for lower level issues I think. tjaalton knows better.13:37
Trevinholow prio though13:37
seb128https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/179495113:37
ubot5Ubuntu bug 1794951 in gnome-calculator (Ubuntu Cosmic) "Calculator (snap) is slow to start on a freshly installed Cosmic machine" [High,Confirmed]13:37
Laneyshould be assigned then if it's being fixed.13:37
seb128is fixed according to will's comment, I'm going to wait for him to confirm and close13:38
seb128the other ones seem assigned/on track and don't need discussion13:38
seb128http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html13:39
seb128that has a bug with a patch https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/179760413:39
ubot5Ubuntu bug 1797604 in xserver-xorg-video-intel (Ubuntu) "Xserver opengl problems on i5-8259U" [Undecided,Confirmed]13:39
mdeslaurjbicha: I think you added a bad shebang here: https://salsa.debian.org/gnome-team/gnome-screensaver/commit/eee80254cec8af6c8f66e3307b4b61a639f22e2e13:39
seb128mdeslaur, hey, we are in the middle of a meeting :)13:40
mdeslauroh, whoops13:40
seb128so that intel bug, it makes some video card work better, I would +1 to accept the nomination13:40
seb128tjaalton, ^ can you have a look at getting that into bionic?13:41
tjaaltonchecking13:41
seb128anyway, if nobody disagree I accept it for bionic13:42
tjaalton-intel isn't used by default13:43
seb128http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html13:43
seb128tjaalton, k, needs to be looked at more into details then I guess13:43
seb128the bb tracking list is still out of shape, I'm starting cleaning it now but let's kip for this week again13:44
seb128sorry about that13:44
seb128that's it from the rls bugs13:44
seb128#topic AOB13:44
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting 23 October 2018 | Current topic: AOB
seb128any other topic?13:44
andyrocknone from me13:45
didrocksneither13:45
Trevinhofine here too, I'd have some SRU shell question, but I guess not whole team related :)13:45
seb128k, short and efficient then (the bug section still felt a bit cahotic to me though, unsure why)13:45
seb128let's wrap13:45
andyrockit would be nice to discuss bugs to upset La_ney13:46
seb128thanks everyone!13:46
seb128#endmeeting13:46
=== meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/3VYBPFaR/ubuntu-desktop-1810-cycle | Amaterasu watches over you benevolently
meetingologyMeeting ended Tue Oct 23 13:46:05 2018 UTC.13:46
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-10-23-13.30.moin.txt13:46
seb128andyrock, haha13:46
didrocksthx!13:46
oSoMoNthanks13:46
Trevinhothx13:46
seb128Trevinho, what are your g-s SRU questions?13:48
seb128we should get a SRU going to cosmic, at least to get the keyboard layout switch fix from andyrock/garnacho13:49
Trevinhowell, 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
Trevinhowell, I was speaking mostly for bionic here13:49
kenvandineTrevinho: symptom sounds right, but he said it was fine on bionic.  It started after upgrading to cosmic.  That bug says bionic.14:19
kenvandineTrevinho: i'll point him at that14:19
Trevinhokenvandine: I don't remember much changes on that side in mutter, but I might be wrong.14:19
jbichamdeslaur: it came that way from Ubuntu. Do you think it's better to remove the gnome-screensaver apport shebang completely?14:20
kenvandineTrevinho: i'll point him at that bug though, thanks14:20
mdeslaurjbicha: 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:21
seb128hey kenvandine, how is SLC going?14:22
seb128kenvandine, 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 meeting14:22
ubot5Ubuntu bug 1794951 in gnome-calculator (Ubuntu Cosmic) "Calculator (snap) is slow to start on a freshly installed Cosmic machine" [High,Confirmed]14:22
seb128jbicha, mdeslaur, the error was added in http://launchpadlibrarian.net/350649809/gnome-screensaver_3.6.1-7ubuntu6_3.6.1-8ubuntu1.diff.gz14:24
* mdeslaur nods14:25
seb128jbicha, seems like you did that when you renamed/added to Debian?14:25
* didrocks has a vm ready, trying refreshing to latest gnome-platform14:26
didrocksgnome-3-26-1604 rev 74 is still slow to me for first app startup14:27
seb128didrocks, thx for testing14:29
didrocksyw (commented)14:29
seb128kenvandine, ^14:30
seb128didrocks, current revision is 75 though?14:31
didrocksah, not what snap refresh refreshed here14:32
didrocksseb128: http://paste.ubuntu.com/p/3PQyKPGSnb/14:33
didrocksdo you see something different?14:33
seb128didrocks, yes,14:37
seb128channels:14:37
seb128  stable:    3.26.0 (75) 153MB -14:37
seb128  candidate: 3.26.0 (75) 153MB -14:37
seb128but that partition is still i386, so probably a mismatch between archs14:38
Laney74 here14:38
seb128which I don't know if expected, or if it means 75 failed to publish on amd64?14:38
didrocksseb128: ah, the rev is a build #14:38
Laneythat makes sense14:38
didrocksno14:38
didrocksbuild 74 is amd6414:38
didrocksbuild 75 is i38614:38
seb128how do we know it's the current build?14:38
seb128sometime the store fails to accept updates14:38
seb128maybe the fix is in 75 that failed to upload?14:39
seb128or do you say the change is in 74?14:39
didrocksah, so you mean, build 76 failed?14:39
seb128I don't know how to check14:39
didrocksjust that the "rev" is a build number14:39
didrocksmeaning, on 2 archs, you won't have the same "rev", ever never14:39
seb128right, but how do we know if 74 include the change we want to see?N14:39
didrocksso yeah, maybe there was an upload, kicking off build 75 and 7614:39
willcooke74 should have the font cache fix14:39
didrocksand 76 failed14:39
didrocksThere is no way to know that rev 74 and 75 have the same source code14:40
willcooke76 might have been arm14:40
didrocksalso, yeah14:40
didrocksbut 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
seb128k14:41
seb128willcooke, hey, how is SLC?14:41
seb128willcooke, so yeah, seems like that fix isn't good enough for everyone then :/14:41
didrockswillcooke: doesn't work for me, are you sure you removed the snap cache?14:41
seb128didrocks, it wfm14:41
didrocksweird, this vm is fairly vanilla14:42
seb128the other day "rm -rf ~/snap/gnome-calculator; time /snap/bin/gnome-calculator" was taking 35s and not it takes 3s14:42
didrocksseb128: once you removed ~/snap/gnome-calculator/…14:42
seb128not->now14:42
willcookeseb128, hey!  I can't remember exactly now, but I'm pretty sure I tested it properly14:42
didrockslet me revert between the 214:43
willcookeI'm installing a new Vbox now14:43
didrocksit's from a vm, so a little it less stable ofc…14:43
seb128willcooke, 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 have14:43
didrockswait, I'm in the GNOME vanilla session on this VM14:44
didrocksjust in case…14:44
didrocksmaybe it's font-cantarell or such14:44
kenvandineseb128: good, i'll handle it14:44
seb128kenvandine, thx14:44
seb128didrocks, that should be in the system or user cache though :/14:44
didrocksindeed, switched session, let's time14:45
kenvandineseb128, didrocks:  rev 74 is the right build for amd6414:46
kenvandineand the revision that both willcooke and i tested14:46
didrockshttp://paste.ubuntu.com/p/8KFqHv6g4S/14:46
kenvandinei did a fresh install, refreshed gnome-3-26-1604 and it was fast to start14:47
didrockskenvandine: doesn't seem to be really good in my VM ^14:47
didrocksI ctrl+C once gnome-calculator appears14:47
didrockstried twice with downgrading + upgrading again14:47
kenvandine:/14:47
didrocks(qemu, but I don't think that should impact)14:47
didrocksfresh install in the VM, only hacked on GNOME Shell in it + installed gnome-session package14:47
didrocks(and pastebinit… :p)14:47
kenvandinewillcooke: do you have the iso locally and can do a fresh VM install?14:48
willcookekenvandine, doing it right now14:48
kenvandinethanks14:48
didrocksis there a way I can trigger some timing debug log?14:48
kenvandineSNAP_DESKTOP_DEBUG=114:48
kenvandinethat will give you times for desktop-launch14:49
didrockslet me see if I can spawn some useful info for you14:49
kenvandineunfortunately the fontconfig slow down is after desktop-launch is done14:49
didrocksah :/14:49
didrocksyeah14:49
didrocksdesktop-launch elapsed time:  0.32164046614:49
didrocksNow running: exec gnome-calculator14:49
didrocksthen, it waits…14:49
didrocksso probably triggering fontconfig14:49
kenvandineapproximately how long?14:49
didrocks1às14:50
didrocks10s*14:50
didrocksbefore showing ** (gnome-calculator:6823): WARNING **: 16:50:18.525: currency.vala:412: Currency VEF is not provided by IMF or ECB14:50
willcookeerm, got an installer crash in vbox14:50
didrockswillcooke: enough mem allowed?14:51
willcooke1.7GB14:51
willcookemaybe not14:51
didrocksyeah, should be good14:51
willcookeThis is the same vm config I used last week, so odd.14:51
willcookedidrocks, 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 cache14:52
didrocksI guess the 10s is rebuilding the font cache14:53
didrocksso why on that config? odd14:53
willcookewoah, this is odd14:53
willcookeit is still intsalling14:53
willcookebut it's reported a crash14:53
kenvandinedidrocks: the fontconfig slowdown was ~25s14:53
kenvandinemaybe the 10s is just from slow disk access in qemu?14:54
kenvandine10s seems way too fast14:54
didrockskenvandine: why then rev 70 has the same startup time?14:54
didrocks"relatively fast" ;)14:54
didrocksor did rev 70 already had the fix?14:54
kenvandineno...14:55
kenvandineweird14:55
* didrocks puzzled as well14:55
seb128time depends of the disk/cpu though14:59
=== Class7_ is now known as Class7
didrocksright, but we should see a difference between rev 70 and 7415:04
didrockswhich is why I started by comparing both15:04
oSoMoNseb128, bug #1798053 is fixed upstream in the 3.30 branch, the fix is trivial, shall I go ahead and prepare a SRU ?15:06
ubot5bug 1798053 in gnome-software (Ubuntu) "Click on the back icon in gnome-software don't work" [High,Confirmed] https://launchpad.net/bugs/179805315:06
seb128oSoMoN, yes please, I can do sponsoring15:07
oSoMoNok15:07
willcookeI installed that new vm and manually refreshed the gnome-3-26-1604 snap15:15
willcookeand it started in 3 seconds15:15
willcookeso it could be a different issue15:16
oSoMoNseb128, 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.gz15:23
oSoMoNI'll SRUify the bug report now15:24
seb128oSoMoN, thx15:25
kenvandinedidrocks no idea, all very weird16:33
=== pstolowski is now known as pstolowski|afk
oSoMoNI'm done for today, have a good evening everyone17:14
seb128andyrock, 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:37
ubot5bug 1799293 in gnome-shell (Ubuntu) "gnome session: Must ask twice to lock the screen when user has auto-login enabled" [Undecided,New] https://launchpad.net/bugs/179929321:37
Trevinhoseb128: looking...21:38
seb128Trevinho, thx, doesn't need to be today and the bug probably lacks details/log you would need21:38
seb128feel free to "incomplete" it and ask details21:38
Trevinhomh, doesn't seem needed logs, let me see if I reprodue21:39
Trevinhoce*21:39
seb128thx21:40
Trevinhoseb128: mh, I can't reproduce in my vm here... hmmh21:43
seb128right, I expect we would have heard more about it if it impacted all auto login configs21:46
seb128could be due to an extension or something...21:46
Trevinhoseb128: you can?21:47
seb128no...21:47
seb128don't worry about it for now21:47
seb128thx for testing21:47
seb128and you should go to bed at this time :)21:48
TrevinhoI was playing with something... :P21:48
seb128hehe21:48
seb128that said I'm calling it a day!21:48
seb128have a good night Trevinho & desktopers21:48
Trevinhogood night21:48
Trevinhothanks21:49

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!