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

=== cpaelzer_ is now known as cpaelzer
Trevinhomorning...06:31
TrevinhoLaney: I've been using latest version, but I agree it wasn't the case here to look at. But I tried that branch in kms and simply it will stop ubuntu running forever in kms, as  CanGraphical never goes to 'yes'.06:32
Trevinhoso indeed I think is a lower level thing, just speaking of the effect here06:33
dufluMorning Trevinho06:59
dufluWait. Trevinho is first online.07:02
* duflu suspects he hasn't gone to bed yet07:02
TrevinhoxD07:02
Trevinhoahaha, I did, but I had to drive a friend to the airport, so I had an early alarm :(07:03
didrocksgood morning07:18
Trevinhohi didrocks07:18
didrockshey Trevinho07:18
dufluHello didrocks07:29
didrocksmorning duflu07:32
seb128k, back!07:36
seb128hey didrocks Trevinho duflu07:36
seb128good morning desktopers07:36
dufluHi seb12807:37
seb128how is everyone today?07:38
oSoMoNgood morning desktoppers07:42
didrockssalut seb128, hey oSoMoN07:44
acheronukLP: #179800507:44
ubot5Launchpad bug 1798005 in ubiquity (Ubuntu) "Installer crashed on the "Who Are You?" panel." [Undecided,New] https://launchpad.net/bugs/179800507:44
acheronukcan anyone check ubuntu main for that bug?07:44
acheronukI have to walk out the door in a few mins07:44
oSoMoNsalut didrocks, seb12807:45
acheronuklog: https://paste.ubuntu.com/p/kbzDFYpCBT/07:45
seb128lut oSoMoN; en forme ?07:46
didrocksseb128: on the "how is everyone" -> doing another yack shaving it seems :p07:46
didrocksand you?07:46
oSoMoNseb128, ça va, et toi?07:47
dufluMorning oSoMoN07:50
seb128oSoMoN, ça va bien!07:50
seb128didrocks, poor yack, winter is coming they need to keep warm :p the installer/screen reader one?07:50
* duflu was briefly distracted by spider killing... Happy spring07:50
didrocksseb128: yeah, the whole a11y stack basically07:51
seb128:(07:51
seb128do you have a clue what's the issue is?07:51
didrocksyep07:51
seb128how do you ubiquity carry over the config to the installed system?07:51
didrocksit's using… a11y-profile-manager07:51
seb128lol07:52
didrockswhich isn't seeded anymore07:52
seb128that explains :)07:52
didrockssame, isolinux is using a11y-profile-manager07:52
seb128shrug, I did revert some of that when I fixed other a11y problems in previous cycle07:52
didrockswhich has a lot of vulneravities07:52
seb128I should have done a full revert to the codebase before that component was added :/07:52
didrockslike well-known names owned by root in /tmp07:52
seb128but a11y-profile-manager isn't used/on the iso anymore, is it?07:52
didrocksalso, this thingy doesn't really know about GNOME07:53
didrocksit's not on the iso07:53
didrocksbut isolinux set the profile you select based on it07:53
seb128ah :/07:53
seb128shrug, we should have reverted those changes07:53
didrocksand ubiquity, at install time, runs a hook which triggers it07:53
seb128that component was added not so long ago07:53
didrocksI like as well the usage of:07:53
didrocksfunction_witout_parameter() {07:53
didrocks  … read global variables …07:54
didrocks}07:54
didrocks…set global variables… with "if profile"07:54
didrocksfunction_witout_parameter()07:54
didrocksthe whole code is like that :/07:54
willcookemorning08:05
seb128hey willcooke08:06
didrockshey willcooke08:06
seb128at the office again today?08:07
dufluMorning willcooke08:13
Laneyyo08:15
seb128hey Laney, how are you? enjoy the great London?08:16
didrocksmorning Laney08:16
seb128and the citizenM?08:17
willcookeseb128, not yet, but might go in a little later on.  Got some meetings this mirning08:17
seb128willcooke, you didn't send the traditional "who is where this week" and "meeting reminder" btw :p08:17
willcookedarn08:17
willcookeI'll do it no08:18
willcookenow08:18
Laneyseb128: it's good! nice cappuccino this morning :>08:20
Laney& hey didrocks willcooke08:20
LaneyI forgot to do a status update08:20
seb128bad Laney :p08:24
Laneyprobably do it after we fix the installer that we broke :-)08:33
seb128haha08:34
Laneyrelease traditions08:34
seb128with Didier we decided to stay away from doing late changes to fix a11y this cycle08:34
seb128the "onscreen reader is not enabled after installation if selected during install" is there since 17.10 :/ (casper still uses a11y-profile-manager than we killed from the iso/main when we switched to GNOME)08:35
Trevinhohi guyz08:35
Laneywhoops!08:35
Laneygood that it's not new though08:35
didrocksyeah, and we know what happens when we fix a11y in the installer, right?08:36
didrockswe can create a new tradition, but I'm not in :p08:36
Laneyyou could try elif finished_step == 'ubiquity.components.partman_commit':08:38
LaneyWHAT08:38
Laneyhttps://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/179786108:38
Laneythat08:38
ubot5Ubuntu bug 1797861 in ubiquity (Ubuntu) "Screen reader doesn't read installer's GUI during a live session installation" [Undecided,New]08:38
Laneyguessing that's not covered by previous statements about a11y-thingy08:38
didrocksNo, it's not related on that one08:39
didrocks(we are only talking about getting options from isolinux and setting them on the final installed system)08:39
seb128right, I'm going to give a try to that one08:41
Laneythanks!08:43
didrocksLaney: stupid question, but how do you trigger maybe-ubiquity using Boxes/kvm?08:48
didrocksLaney: I always have isolinux popping up08:48
didrocksand so, no way to have maybe-ubiquity08:49
Laneyyou can add it to the kernel cmdline08:51
didrocksdo you have the exact syntax handy?08:51
didrocksotherwise, I can look08:51
Laneyjust add maybe-ubiquity somewhere in there08:52
didrocksI guess replacing only-ubiquity by maybe-ubiquity08:52
didrocksk! thanks Laney08:52
didrockstrying to reproduce the issue as well (can't when booting directly to a live session or install session)08:52
didrocksconfirmed with maybe-ubiquity -> try ubuntu -> enable a11y -> start ubiquity08:53
didrocksindeed, no root apps are read by the screen reader under that config08:54
seb128so only when going through maybe ubiquity?08:54
seb128or "luck" on that boot?08:54
didrocks100% on one try for both right now ;)08:54
didrocksdoing more run to confirm or deny08:54
didrocksah, have reproduced in only-ubiquity08:57
seb128I wonder if orca gets confused by having the same apps register 2 times or something08:57
seb128k, guess not then08:57
didrockshum08:59
didrocksit's weird08:59
didrocksin that session, it "sometimes work"09:00
didrockslike selecting the language list, I get one on fourth selection read09:00
didrocks(even if I go very slowly)09:00
seb128I'm on the maybe-ubiquity screen and I've activated it but it fails to read anything e.g when I change language09:01
didrockstry keyboard09:01
seb128oh, yes, I was just doing that09:02
didrocks(I didn't try activating a11y on maybe-ubiquity itself)09:02
didrocksah ok09:02
didrocksbecause on the fuzzy results before, I got 100% working with keyboard, but not mouse…09:02
seb128so yeah, I picked "try ubuntu"09:02
seb128right, same here09:02
didrockssomething is fishy09:02
seb128I was trying the mouse09:02
seb128well, keyboard is what makes sense09:03
didrocksindeed09:03
seb128blind users can probably not use the mouse09:03
didrocksbut still, don't really like that :)09:03
seb128yeah09:03
didrocksit's going to hit us back because we don't understand it fully09:03
seb128so the reader is working on the live session for me on first try going through maybe-ubiquity09:04
didrocksdoesn't for me on this second try09:04
didrocksmaybe-ubiquity -> enabled a11y -> live session -> (a11y enabled already) ubiquity -> nothing (nor mouse or keyboard)09:05
seb128k, try 209:05
seb128my first one was09:06
seb128"wait to boot to maybe-ubiquity -> alt-super-S, it reads something -> click "try" -> start ubiquity from the launcher -> it reads the ubiquity dialog buttons ("continuer")09:06
didrocksI started it from the desktop icon09:07
didrocksbut apart from that, same…09:07
didrocksyou selected french on maybe-ubiquity?09:07
seb128yes09:07
didrockslet's try09:07
didrockswaow09:08
didrocksit reads the list in maybe-ubiquity09:08
didrocksbut with an initial lag of at least 5s09:08
didrocksbut then, nothing in live session…09:09
=== cpaelzer_ is now known as cpaelzer
didrockswe should call release week "look at a11y installer issue week"09:10
seb128second try, working as well in live09:12
seb128"continuer button" is spoken when I start ubiquity once in live09:12
didrockscould be racy, but how come…09:12
didrocksand if you sudo gedit?09:12
seb128does it work for you if you stop/start the screenreader?09:12
seb128any error in the journal?09:12
seb128sudo gedit speaks "document sans titre...309:13
didrocksnothing failing looking for a11y in the journal09:13
didrocksI tried to stop/start it again09:13
didrocksnot better09:13
seb128you have sound if you use aplay or something?09:13
seb128or the test audio from g-c-c?09:13
didrocksoh a11y is working09:13
didrocksfor everything which !root09:13
seb128:(09:13
didrocksorca has a stacktrace09:14
didrockson shutdown09:14
didrocksbut nothing when starting…09:14
didrocksyeah, all windows which aren't root are working09:14
didrockslet me confirm again (I'm sure I've done that) that booting a live session right away works09:15
didrocksyeah09:16
didrocksapps as root works in that case09:16
didrocksnice sudo apt install pastebinit -> plymouth screen -> exit09:16
didrocksit switched vt!09:17
didrocksbut the session is still running09:17
didrockshttp://paste.ubuntu.com/p/g97MHJdCYr/ <- working env09:17
didrockslet's reboot in maybe-ubiquity + session switch and see09:17
seb128wfm on another try :/09:18
didrocksvirtualbox, not kvm?09:19
Trevinhosooooooo (Laney), for what I think is also willcooke's issue I think that more than gdm itself, is the way gdm is started. So right now we start it once we've a tty. and for the daemon is probably fine. Problem is that that point there might be no drm card (yet).09:19
TrevinhoA way to fix this is changing gdm3.service so that it wants a drm card / fb to be there09:19
didrocksseb128: ah, even better, in that session, no a11y working at all…09:20
seb128:(09:20
seb128didrocks, right, virtualbox here09:20
didrockshttp://paste.ubuntu.com/p/X46nG3RPFj/ -> failing session (after maybe-ubiquity, enable a11y, try ubuntu)09:21
Trevinhobut not sure if this is a general rule... As in pure fb scenarios I guess X would start without any FB device in... So maybe gdm should wait for a drm device if trying with wayland, while on X could go without.. .But again even X should wait if there's a fb but there's no X driver for it... So quite a mess :)09:21
didrocksnothing fancy diffing the logs, apart from IDs changing…09:22
seb128:/09:22
didrocksah!09:22
didrocksoct. 16 09:22:28 ubuntu orca-autostart.desktop[8065]: Une autre instance du lecteur d’écran est déjà lancée pour cette session.09:22
didrocksoct. 16 09:22:28 ubuntu orca-autostart.desktop[8065]: Lancez « orca --replace » pour remplacer ce processus par un nouveau.09:22
didrocksin that session09:22
seb128ah!09:22
didrocksif I disable/reenable screen reader09:22
didrocksmaybe there is a race + something else with sudo?09:23
seb128another bug I guess09:23
seb128the desactivate not working09:23
didrocksyeah09:23
didrocksorca is 4 minutes old09:23
didrocksunder ubuntu user09:23
didrocksno log on shutdown request though :/09:23
seb128works everytime here/on virtualbox09:23
Trevinhowillcooke: your laptop is still with Andrea?09:24
seb128I need to step out for early lunch but I try with kvm once I'm back09:24
seb128bbl09:24
didrocksseb128: enjoy!09:24
seb128thx09:24
willcookeTrevinho, hey, yes09:28
willcookeunless he sold it09:28
Trevinhoahaha09:28
Trevinhoyou know... you trusted an Italian..09:28
willcooke:)09:29
willcookeWith the money he got, he could have bought a milkshake09:29
willcookeTrevinho, reading backscroll09:29
didrocksseb128: second time I'm reproducing the "no a11y working at all", I have to kill orca, then I'm in the "orca works with all but root apps"09:32
Trevinhoin general I think for making things working in any normal scenario, I think there are multiple options... 1) udev rules + systemd service updates for gdm waiting drm cards (what I've done locally, seems to work properly) | 2) making gdm daemon to monitor udev so that if a main drm card is added it tries to create again a display. As right now it fires once, then if it fails, it just doesn't try again.09:32
willcookeTrevinho, yeah, so the problem with waiting for a drm device is, as you said, there might not be one in headless mode09:32
willcookeTrevinho, from ISO testing some of the flavours I think that some of them do retry the greeter later on09:33
willcookeIf we could make the systemd service retry, say, three times before giving up, would that do it?09:33
Trevinhowillcooke: the daemon itself starts properly. it's more a gnome-session thing of not retrying again I think.09:34
willcookeah, kk09:34
willcookeso let's just put the sleep statement back in again then09:34
Trevinhowillcooke: as gdm starts the daemon, then it launches various subdaemons09:34
willcookegot ya09:35
Trevinhowell it's better to use udev anyway...09:35
Trevinholike wait for a drm for time, if it doesn't work, then just try.09:35
willcookeI was joking about the sleep statement btw :)  Just in case...09:35
Trevinhothis is the faster and easier fix09:35
willcookesounds good09:35
Trevinhowell, like having a "max timeout" for headless versions where there might be weird setups with no dri cards, but... well for 99% of ubuntu targets things should actually work09:36
willcookewe should get jibel to confirm that it will work for his automated testing. He'll be in London in a few hours09:36
Trevinhosooo... eventually I think our main issue is this one: loginctl starts as soon as we've a fb... but having a fb doesn't always mean we've a gfx (dri) card ready to go. So it starts and then fails... CanGraphical doesn't seem to reflect this properly even (as because CanGraphical if is connected to `master-of-seat`, that one is also not safe to use since might be there when fb is set, not when also dri card is there). So for a proper fix10:13
Trevinhowe've multiple possibilities, for a fix for release I'd go with udev + systemd checks.10:13
willcookeTrevinho, +110:33
* willcooke -> train10:33
popeyJust did an install of cosmic daily 20181016 in virtualbox with 3d acceleration on and ubiquity died bug 179806510:51
ubot5bug 1798065 in ubiquity (Ubuntu) "Installer crashed :(" [Undecided,New] https://launchpad.net/bugs/179806510:51
popeyI suspect this may be a dupe of bug 179805010:52
ubot5bug 1798050 in ubiquity (Ubuntu) "Installation crashed after Continue clicked after presentation of the time Zone" [Undecided,New] https://launchpad.net/bugs/179805010:52
popeyI switched off 3d acceleration in virtualbox and the install seems to be progressing further.10:52
willcookepopey, can you tell me the specs of the VM?  Especially RAM and VRAM11:11
willcookeDoing a quick test from the train of some old ISOs I have11:11
willcookesee if I can easily find when it broke11:11
popeywillcooke: 4GB RAM, 128MB VRAM11:11
willcookethx11:11
willcookeand did you do a "try" or go direct to install?11:12
popeyjust install11:12
willcookeack11:12
popeyi just left it till i got the gui with two buttons11:12
willcookepopey, and was it on a cosmic host?11:14
willcookei.e. cosmic on cosmic11:15
willcookeyes, looks like it was11:15
willcookeRTFB11:15
popeyno11:15
willcookeoh11:15
popeycosmic vm on bionic host11:15
willcookeah, ok, that data was from inside the VM11:16
popeyyeah, i filed the bug in the vm using the popup from ubiquity11:16
seb128popey, was it a one time thing? or can you reproduce with the same setup?11:16
seb128also ubiquity issues at this point of the cycle might be worth raising in #ubuntu-release11:17
popeyi will attempt to reproduce it now11:17
seb128thx11:17
willcookemy ISO from Friday worked here11:18
seb128Oct 16 10:38:06 ubuntu ubiquity: AssertionError: Failed to mount the target: /target11:18
seb128it's similar to bug #1798050 reported earlier11:19
ubot5bug 1798050 in ubiquity (Ubuntu) "Installation crashed after Continue clicked after presentation of the time Zone" [Undecided,New] https://launchpad.net/bugs/179805011:19
willcookeI'll retry using the existing diks11:19
seb128or bug #179800511:19
ubot5bug 1798005 in ubiquity (Ubuntu) "Installer crashed on the "Who Are You?" panel." [Critical,Triaged] https://launchpad.net/bugs/179800511:19
seb128ah11:19
seb128^11:19
willcookeyeah11:19
seb128willcooke, popey, ^ that's the regression L_aney was mention earlier this morning11:19
seb128so "known issue/being worked on" it seems11:19
willcookewoot11:20
willcookethanks seb128 popey11:20
willcookeI'll be in the office in 30 mins, so will report back to the channel11:20
popeydidnt do it on this run11:20
popeythanks seb12811:20
seb128popey, it's racy so pretty sure it's that issue, looks like L_aney as a candidate fix in https://git.launchpad.net/ubiquity/commit/?id=d78495811:21
popey\o/11:21
popeygreat success11:21
Laneyyeah feel free to try it if you want11:25
Laneyyou can patch that from the live session11:25
Trevinhoso... I'm going with the conditional-wait workaround for gdm now, I think is saner (wait drm a bit, otherwise continue how it is). For upstream i've various other ideas. Might be both systemd that would need to do a similar thing or gdm instead to be more robust. As Systemd right now advertize a CanGraphical as soon a there's a /dev/fb0 around, but this is not true if the drm device takes some time to initialize after the fb. And so when12:07
Trevinhothe drmdevice has been finally added it can't advertize again a CanGraphical change. That's why the fix propsed upstream might help but doesn't fix the problem in all the cases.12:07
Trevinhoprobably lunch first though :P12:07
dgadomskihi12:21
willcookehi dgadomski12:21
jbichaTrevinho: btw did you see my comment in LP: #1796822 that I get the corrupted screen when I enable autologin12:21
dgadomskicould anybody please take a look at the merge request for bug #1755490?12:21
ubot5Launchpad bug 1796822 in xorg-server (Ubuntu Cosmic) "Desktop live cd boots corrupted screen in Virtualbox on Bionic" [Critical,Confirmed] https://launchpad.net/bugs/179682212:21
ubot5bug 1755490 in unity-settings-daemon (Ubuntu) "Incorrect information about display shown in unity-control-center" [Undecided,In progress] https://launchpad.net/bugs/175549012:21
Trevinhojbicha: mh didn't see no, but I think it all might be related to the same issue12:22
willcookedgadomski, is that especially urgent?12:22
jbichayes, I'm commenting because I think there were some indications we fixed the problem but that one still is easily reproducible for me12:23
Trevinhojbicha: run with this systemd unity (add a .service and enable it):12:23
Trevinhohttps://www.irccloud.com/pastebin/6gNvcnai/12:23
Trevinhoattach the log after that please12:23
dgadomskiwillcooke: nope, not super urgent, it's just there for some time12:23
willcookedgadomski, oki, I propose that we look at it after release then, if that's good for you12:24
dgadomskiwillcooke: yep, completely, thanks12:24
willcookecool12:24
willcookeI'll add a trello card12:24
TrevinhoI mean all these bugs are speed dependent, and because gdm starts too early basically :)12:26
jbichaTrevinho: log attached to the bug12:29
Trevinhothanks12:39
Trevinhojbicha: was udevadm service running?12:40
Trevinhojbicha: did you systemctl enable it?12:40
jbichaTrevinho: ok, new attachment, thanks!12:45
Trevinhota12:59
Trevinhoseems to be the same issue13:00
Nafallohmm. remind me what URL the meeting updates lives on again? :-)13:29
Nafallonever mind. found it :-)13:29
willcookesorry folks13:30
willcookebear with me13:30
willcookeunprepared13:30
willcooke#startmeeting Desktop Team Weekly Meeting 16 October 201813:31
meetingologyMeeting started Tue Oct 16 13:31:07 2018 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.13:31
meetingologyAvailable commands: action commands idea info link nick13:31
=== 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 16 October 2018 | Current topic:
willcookeRoll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel/heber, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)13:31
didrockshey!13:31
Trevinhoo/13:31
hebero/13:31
seb128hey13:31
jibelhi o/13:31
oSoMoNhey13:31
Nafallohi there13:31
willcookeLaney, andyrock and jibel are here in London13:31
willcookeEveryone is very busy with release work, so let's keep this short13:32
willcookeWe haven't had chance to review the rls bugs, so we will have to do it live13:32
willcookeTracking first:  http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html13:33
willcookehttp://launchpad.net/bugs/179428013:33
ubot5Ubuntu bug 1794280 in xorg-server (Ubuntu Cosmic) "gdm doesn't start on a fresh installation of Cosmic Desktop" [Critical,Confirmed]13:33
willcookeWe're working on that one, happy its in hand.  Could have a fix/work around soon13:33
willcookehttp://launchpad.net/bugs/179682213:33
ubot5Ubuntu bug 1796822 in xorg-server (Ubuntu Cosmic) "Desktop live cd boots corrupted screen in Virtualbox on Bionic" [Critical,Confirmed]13:33
willcookeInitial indications are that this is the same bug13:34
willcookeShould know for sure soon13:34
willcookehttp://launchpad.net/bugs/179495113:34
ubot5Ubuntu bug 1794951 in gnome-calculator (Ubuntu Cosmic) "Calculator (snap) is slow to start on a freshly installed Cosmic machine" [High,Confirmed]13:34
willcookeKen will look at that tomorrow.  Can be fixed with out affecting release13:34
willcookehttp://launchpad.net/bugs/179754313:34
ubot5Ubuntu bug 1797543 in gnome-software (Ubuntu Cosmic) "Unable to update software - Button Restart & Update, restarts no updates applied" [High,Fix released]13:34
willcookefixed13:34
willcookehttp://launchpad.net/bugs/179605613:34
ubot5Ubuntu bug 1796056 in xorg-server (Ubuntu Cosmic) "Xorg crashed with SIGSEGV in __strstr_sse2_unaligned() from glamor_egl_init() from try_enable_glamor()" [Medium,Confirmed]13:34
willcookeI think we've worked around that mostly.  tjaalton anything more needed there ^ ?13:35
willcookeEOL13:36
tjaaltonwillcooke: nope13:36
seb128there is an upstream patch that has been merged to error out "properly", unsure if that's good enough though if the erroring out still means screwed systems?13:36
tjaaltonupstream released 1.20.2 with that, too late for cosmic anyway13:37
willcooketjaalton, will it get an SRU?13:37
tjaaltonwillcooke: maybe13:37
willcookeFWIW I havent seen that specific bug in recent testing, so I think all the other fixes we've done are masking it13:37
seb128yeah, probably not worth targetting at this point13:38
willcookeok, lets untarget13:38
willcooketjaalton ok with you?13:38
tjaaltonsure13:38
willcookeoki, I will do that in a mo13:38
willcookeIncoming:13:38
willcookehttp://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html13:38
willcookehttp://launchpad.net/bugs/179754313:39
willcookefixed13:39
ubot5Ubuntu bug 1797543 in gnome-software (Ubuntu Cosmic) "Unable to update software - Button Restart & Update, restarts no updates applied" [High,Fix released]13:39
willcookehttp://launchpad.net/bugs/179654813:39
ubot5Ubuntu bug 1796548 in gnome-shell (Ubuntu) "[regression] New windows are all centred" [Medium,New]13:39
willcookeFeature not a bug13:39
willcooke+1s to reject?13:39
Trevinhoyep13:39
didrocksyep, changed on purpose13:39
willcookehttps://bugs.launchpad.net/ubuntu/+source/upower/+bug/179655013:40
ubot5Ubuntu bug 1796550 in upower (Ubuntu) "[regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)" [Medium,Triaged]13:40
willcookenot a release blocker IMO.  There is a simple fix, but in the spirit of this meeting, notfixing?13:41
seb128that sounds like a good SRU13:41
seb128right13:41
didrocks+113:41
seb128I'm going to add it to my SRU list13:41
didrocks(and don't impact everyone btw, just tried)13:41
willcookehttps://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/179157413:42
ubot5Ubuntu bug 1791574 in gnome-shell (Ubuntu) "gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage" [Medium,In progress]13:42
Trevinhosru too13:42
willcookeack13:42
Trevinhoseb128: list that too plz13:42
seb128?13:42
willcookehttps://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/179157413:42
didrocks(on the SRU list, I guess)13:42
Trevinho[not if it's "yours"]13:42
willcookenot a release blocker for 179157413:43
seb128ah, SRU seems fine13:43
seb128if that's the question13:43
seb128dunno what you mean by "list that too"13:43
willcookehttps://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/177072513:44
ubot5Ubuntu bug 1770725 in gstreamer-vaapi (Ubuntu) "Totem window is all black in Wayland sessions on Sandy Bridge CPUs" [Medium,Confirmed]13:44
willcookeSince wayland is not the default, I say -1 for rls13:44
seb128rls-notfix since it's waylabd13:44
willcookedone13:44
willcookeok, that was more like it13:45
willcooke:)13:45
seb128did we skip over mais il était pas trop ouvert, sa réponse ?13:45
seb128wth?13:45
Trevinhoseb128: add that to the list (if it's a team sru list) I meant13:45
seb128https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/178935613:45
ubot5Ubuntu bug 1789356 in yaru-theme (Ubuntu) "Dark purple (noise) background flashes up briefly during the login animation" [Low,New]13:45
didrocksdoesn't seem a release blocker, I can have a look for SRU though for bionic-cosmic-eye-users ;)13:45
willcookeok, I already notfixing that one13:45
seb128thx13:45
willcookemight have been a copy & paste error13:45
willcookeany more on the rls bugs?13:46
didrockswe had enough of them :p13:46
willcooke#topic AOB13: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 | Desktop Team Weekly Meeting 16 October 2018 | Current topic: AOB
willcookeBon chance for release all13:46
jbichaplease update https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes13:46
willcookeOh, good call jbicha13:46
willcookeI'll take a look at that this afternoon13:46
willcookeany more?13:47
jbichaif you worked on cool features this cycle, please do add it to the Release Notes so people know about it :)13:47
willcookeI have some stuff semi prepared, I can add it13:48
willcookewhich should call out most of it13:48
willcookeok, ending meeting then13:48
willcookethanks13:48
didrocksthx!13:48
seb128thx!13:49
willcooke#endmeeting13:49
=== 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 16 13:49:33 2018 UTC.13:49
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-10-16-13.31.moin.txt13:49
willcooke19 mins13:49
oSoMoNthanks13:50
tkamppeterSorry I am late, have posted my week (Mentor Summit) now.13:51
jbichatkamppeter: hi, I blogged about https://jeremy.bicha.net/2018/10/14/google-cloud-print-in-ubuntu/13:52
seb128jbicha, that only works in libreoffice no?13:54
jbichaseb128: it works in other apps13:54
seb128or how does it integrate to the gtk print dialog?13:54
jbichayes13:54
seb128"how"13:55
jbichadunno :)13:55
seb128I mean gtk doesn't use the lib13:55
jbichamagic?13:55
tkamppeterJbicha, this is really strange, as the part for the GTK print dialog to support the Common Print Dialog Backends (cpdb-...) is not finished yet.13:55
seb128are you sure it's just not gnome-online-accounts doing it?13:55
seb128like GNOME upstream feature13:55
jbichahmm13:56
seb128https://bugzilla.gnome.org/show_bug.cgi?id=72336813:56
ubot5Gnome bug 723368 in Printing "GTK+ print module for Google Cloud Print" [Enhancement,Resolved: fixed]13:56
jbichaoh, I guess it is GOA not gcp after all13:56
jbichasorry13:56
seb128that makes more sense :)13:57
jbichamaybe I should have checked with Till before posting13:57
tkamppeterI have a GSoC 2018 (the GSoC which ended in August of this year) student who was supposed to do the GTK dialog support, but he did not finish and wants to finish after the summer. I did not yet get this work.13:57
jbichaoh13:57
jbichaI don't have a printer actually. less headache 😉13:58
seb128tkamppeter, btw what's the status of the issue that is/Was blocking https://bugs.launchpad.net/ubuntu/+source/cpdb-libs/+bug/1747759 ?13:58
ubot5Ubuntu bug 1747759 in cpdb-libs (Ubuntu) "[MIR] cpdb-libs" [High,Incomplete]13:58
jbichais it only LibreOffice that would support that then?13:58
tkamppeterjbicha, by the way, can you compare my user name here in the IRC with the name as you have written in the blog?13:58
jbichasure, sorry about that13:59
tkamppeterseb128, not yet solved I must return to get this stuff running on the porter box.14:00
tkamppeterat least I have a way again to log into the porter box.14:00
tkamppeterseb128, next problem is that I cannot simply run stuff as root or at least privileged printing (lpadmin group) user.14:01
tkamppeterjbicha, yes, only LO currently, the rest I hope to get together for the next release.14:01
juliankHeya desktop folks, I'm seeing gnome-software prompting me for system updates (reboot&upgrade) on cosmic recently. That seems a bit wrong given that we use update-manager?14:03
seb128juliank, https://launchpad.net/ubuntu/+source/gnome-software/3.30.2-0ubuntu4 ?14:03
juliankah, thanks, seems I'm out of date14:04
seb128np14:04
jbichatkamppeter: I updated my post. I hope it's more accurate now14:08
tkamppeterjbicha,  and the GSoC where these projects were done is 2017, not 2007 (I actually started in 2008 with GSoC, and also it is not that easy to integrate 10-year old software into our GUIs).14:10
jbichaok14:12
seb128on screenreader issues, https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/179786814:28
ubot5Ubuntu bug 1797868 in gnome-initial-setup (Ubuntu) "Screen reader doesn't read gnome-initial-setup windows properly" [Undecided,New]14:28
=== Class7_ is now known as Class7
willcookedesktoppers I've updated the release notes with a bullet list.  Please add to and expand where you can:  https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes16:48
seb128k16:50
Laneygggggggdmmmmmmmmmmmmmmmmmmmmm19:12
LaneyTrevinho: it's up19:49
TrevinhoLaney: great, thanks a lot19:49
willcookethanks Trevinho Laney19:50

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