/srv/irclogs.ubuntu.com/2018/11/20/#ubuntu-desktop.txt

dufluRAOF: Another report of colour profiles being applied as too green has come in. Seems to be an issue consistently visible with whites appearing as lime green (bug 1803840)02:28
ubot5bug 1803840 in colord (Ubuntu) "color calibration with huey pro greenish" [High,Confirmed] https://launchpad.net/bugs/180384002:28
dufluIt was previously reported by mpt and robert_ancell02:29
dufluAnnoyingly, with all the hardware I own, I've never seen that bug myself02:30
robert_ancellweird02:31
RAOFHm.02:34
RAOFI don't think night mode *is* a colour profile, though?02:35
RAOFPretty sure that's just changing the gamma LUT.02:35
RAOFWhich won't appear as a colour profile to applications.02:35
dufluRAOF: It's not about night mode...(?)02:37
RAOFThe linked bug (that robert_ancell and mpt were on) talked about night mode.02:38
dufluRAOF: That's a true statement, but not relevant.02:38
duflurobert_ancell, what machine model did you experience that on?02:39
robert_ancellduflu, that was on mpts laptop which I believe was an old Lenovo!?02:40
dufluYeah, still the same one I think. I will need to scroll back a lot to find his answer02:41
* RAOF might need to acquire another colourhug, as his seems to have dropped off the USB.02:46
dufluRAOF: I seem to have had a couple of dicky USB cables. Took a while to find one that was reliable with it02:47
dufluCan't remember if it was Kmart cables that caused the problem or solved it :)02:53
Trevinhohi duflu02:57
dufluhola Trevinho02:57
Trevinhoand hey RAOF... Do you know a bit the transformation code for Xorg?02:57
TrevinhoRAOF: as I was hitting and looking at https://gitlab.freedesktop.org/xorg/xserver/issues/1402:57
gitbotxorg issue 14 in xserver "Xorg crashes when it tries to resume a scale transformation after that it has been closed" [Opened]02:57
* duflu knows nothing if you're talking about the Xorg internals there02:58
RAOFUrgh, vtable chains!02:58
TrevinhoRAOF: well, not either too much related to vtables as it's probably like the server tries to destroy something (the filters) earlier than the server is shut down02:59
TrevinhoI mean, I whish there was a XSerever destroyed thing, more than a CloseScreen02:59
RAOFWhy not break the ABI?03:00
dufluIt is a Tuesday after all03:00
* RAOF is reading the MR03:00
duflufor some03:00
TrevinhoRAOF: not really a MR yet, just a commit03:00
RAOFThe Xorg ABI is pretty fluid :)03:01
TrevinhoRAOF: well, that would imply rebuilding all the drivers, but..03:01
Trevinhoah ok :)03:01
RAOFAt least it was last I checked.03:01
RAOFAt least a couple of years ago the ABI broke once per Xserver release, so rebuilding all the drivers is not really a blocking issue :)03:01
Trevinhoyou can do the reviewing or you know who point me for that? As depending on that we can discuss it03:01
Trevinholike, if you can review / approve, and if breaking the ABI is feasible, we can do that :)03:02
dufluSpeaking of which... I have a theory that those Xorg crashes triggered by some snaps might be related to shipping ABI incompatibilities that Xorg isn't robust enough to handle03:02
Trevinhomh, client side would be weird, isn't it?03:03
TrevinhoRAOF: ^03:09
RAOFSnaps wouldn't be breaking on Xorg ABI changes.03:11
RAOFI can't actually review, sorry; I've been out of the mainline of Xorg development for a while.03:12
dufluRAOF: It's not the snaps breaking, but doing the breaking (bug 1754693)03:14
ubot5bug 1754693 in xorg-server (Ubuntu) "Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]" [High,Confirmed] https://launchpad.net/bugs/175469303:14
RAOF<freenode_duf "Speaking of which... I have a th"> Snaps can't interact with the Xorg loader at all. They *might* be sending messages unknown to the server, but that code is pretty robust.03:14
dufluActually, maybe same theory but Mesa not Xorg03:15
TrevinhoRAOF: ok, thanks anyways :)03:16
RAOFSnaps *also* can't interact with GNOME Shell's dri loader 😀03:17
RAOFI'd expect that it's unrelated to snaps and the Skype client just makes the correct sequence of requests to trigger a common-or-garden Xserver bug.03:19
RAOF(a way to test this hypothesis would involve using Xtrace to dump the protocol interactions)03:20
RAOFOr maybe a llvmpipe bug.03:21
sarnoldduflu: thanks for joining together the gdm/plymouth bugs, I missed that you had asked for he new bug. :) thanks!03:44
duflusarnold, I actually went looking for the bug he said he created today, but did not find it because of "Private Security"03:44
sarnoldduflu: yeah.. I wish the new bug form made it easier to mark a bug security without making it private03:45
dufluTrevinho, do you know how to make the Ubuntu Dock appear in a local build of gnome-shell? I can't get it to appear any more. Only the upstream dock03:47
duflu--mode=ubuntu doesn't do it03:47
Trevinhoduflu: are you using that in your home or different home?03:48
dufluTrevinho, a local build from home03:48
Trevinhoduflu: ok in any case you'd need this https://github.com/micheleg/dash-to-dock/pull/825/03:49
dufluOh. I guess it needs to find extensions in a home-like location ?03:49
gitbotmicheleg issue (Pull request) 825 in dash-to-dock "dash, docking: remove Shell.GenericContainer" [Open]03:49
Trevinhoduflu: so basically, install that in your home03:49
Trevinhothat's for latest gnome-shell03:49
dufluTrevinho, thanks. I should have thought of the API break03:49
Trevinhoduflu: I think the log was showing that03:50
Trevinhoduflu: anyway, just apply that diff to the ubuntu-branch in case, and put that in your ~/.local/share/gnome-shell/extensions/<extension-id>03:51
Trevinhogenerally I also use a different home for such stuff though03:51
dufluYes, the log says that's the error03:51
Trevinhojust passing env HOME, not really to use a different user03:51
dufluMaybe I'll just defer Ubuntu Dock work till it's all fixed in disco03:52
Trevinhoduflu: well, as you wish it's not really a problem once you've set thungs up04:11
Trevinhoduflu: I've something like this04:12
Trevinho`ls -l /data/GNOME/JHBUILD_HOME/.local/share/gnome-shell/extensions/ -l`04:12
Trevinho`lrwxrwxrwx 1 marco marco 18 ago 29 22:03 dash-to-dock@micxgx.gmail.com -> /data/dash-to-dock`04:12
Trevinhoso basically /dat/dash-to-dock is the git repo of it, while I launch gnome-shell with `HOME=/data/GNOME/JHBUILD_HOME`04:13
dufluTrevinho, thanks. I haven't worked on dash-to-dock since switching to local builds. So I will do something like that next time I do04:17
Trevinhoduflu: really, you should use jhbuild though :)04:20
Trevinhoduflu: just add something like this as config (setting your paths) https://pastebin.com/tZXYfXnL04:20
dufluThen I wouldn't find all the build bugs before everyone else04:20
Trevinhoonce you've that you can just do `jhbuild build gnome-shell` and since there you've things set up, and you can also manually `ninja install` or whatever you prefer04:21
Trevinhobut at least you've all upstream stuff setup in your prefix, without having to care much about things and being able to track things if you need to install04:21
Trevinhoor uninstall04:21
dufluI think I can handle typing --prefix=04:22
dufluand env PKG_CONFIG_PATH=04:22
Trevinhoduflu: well, it's not just that especially for stuff that needs particular GIR stuff...04:28
Trevinhoduflu: these should be the envs actually https://paste.ubuntu.com/p/cth7dKB6Yr/04:29
Trevinhowell a part from my local ones :04:29
Trevinhowell better this04:31
Trevinhohttps://www.irccloud.com/pastebin/f3RfExzG/runner.sh04:31
Trevinhobut well, that's for example to run gdm from that build installation, with a local gnome-shell or things like that04:33
=== Class7_ is now known as Class7
seb128good morning desktopers!06:27
seb128tkamppeter, jamesh, hey, don't forget your weekly update on the hub06:29
jibelgood morning06:35
dufluHi seb128, jibel07:12
jibelHi duflu07:20
didrocksgood morning07:22
oSoMoNgood morning desktoppers07:24
didrockssalut oSoMoN07:24
oSoMoNsalut didrocks, ça va?07:25
duflu'lo oSoMoN07:28
duflu'lu oSoMoN :)07:28
oSoMoNhey duflu, how goes?07:28
dufluoSoMoN, was going well but today the barber accidentally removed too much of my eyebrows. Otherwise good. You?07:29
didrocksoSoMoN: ça va, et toi ?07:29
oSoMoNI'm good, it was a short night but I feel rested and hopeful that this will be a productive day07:30
oSoMoNsorry for your eyebrows duflu. luckily those things tend to grow again07:32
dufluYes, they were needing combing, which is too long07:32
=== pstolowski|afk is now known as pstolowski
dufluMorning willcooke08:50
dufluMorning mpt. Can you remind me what model laptop had the colour profile issue?08:50
willcookemorning duflu, all08:56
seb128hey willcooke08:56
willcookehi seb128, how goes?08:56
seb128good! you?08:56
seb128done with the post-holidays catch? no surprise in there? ;)08:56
willcookeemail firehose, but pretty much caught up.  Yeah, no fires, thank you!08:57
willcookeIn other news, I have carpet and paint in my office08:57
willcookeand a new monitor08:57
willcookeNo more squinting at a tiny screen \o/08:57
dufluwillcooke, are those two things also applied? :)08:58
willcookeha!  Yes, they are in the right place08:58
willcookeno paint on the carpet08:58
willcookeI've seen rather too much of Ikea in the last week though08:58
seb128jamesh, tkamppeter, weekly summary reminder?08:59
seb128willcooke, nice :) which one did you pick? 26"?08:59
* willcooke -> meeting. Will send reminder after that08:59
seb128enjoy!08:59
willcookeseb128, 24" Dell ultrasharp.08:59
willcookeit's lovely08:59
seb128good to know08:59
* duflu highfives willcooke08:59
dufluPremierColor FTW09:00
willcookeIt's got this awesome audio-pass-through feature, so depending on which input is selected, thats the audio which comes out the speakers09:00
dufluI think DisplayPort does that as well as HDMI09:01
willcookeyeah09:01
Laneyhey09:01
dufluhey Laney09:01
seb128hey Laney, how are you?09:02
dufluIt's nice not needing to calibrate a monitor, because then you avoid bug 178576409:02
ubot5bug 1785764 in gnome-control-center (Ubuntu) "Chrome/Chromium and Image Viewer distort colours if a colour profile is enabled." [High,Confirmed] https://launchpad.net/bugs/178576409:02
seb128I though that there was a default/computed profile so users would hit that problem even without doing calibration?09:03
dufluseb128, Yes... but what I mean is with a factory calibrated monitor the workaround of not having a custom profile in software doesn't matter09:05
mptduflu, a MacBook 2008 vintage09:06
seb128k09:06
dufluAh. Ta mpt09:07
Laneyhey duflu seb12809:08
Laneyseb128: i'm good, got to meet the transport guy from the council last night and ask him about cycling09:09
Laney...not much is coming...09:09
Laneyyou?09:09
seb128:(09:09
seb128I'm good! slept well, but I got up early, it feels like middle of the night now at 6:30 :/09:09
Laney:<09:13
Laneyits cold this week too09:13
seb128yeah, near 0°C here and windy brrrr09:18
cpaelzerHi, I'm experimenting with virtual gpus and wonder where to check best for what is actually used atm10:34
cpaelzerI see in lspci that I ahve both (qxl by kvm and an intel HD card passed through) in the guest10:34
cpaelzerand I see Xorg.0.log mentioning qxl and i965 drivers10:34
cpaelzerwhat would be the best place to verify which e.g. xrandr outputs are of which driver and stuff like that?10:35
duflucpaelzer, if you have multiple GPUs then each app is free to choose which one it uses. Do you have one or multiple?10:35
dufluIn that case, only the app can answer the question. To see what the default one is, install mesa-utils and then run 'glxinfo'10:36
cpaelzerthe guest has multiple gpus now10:37
cpaelzerthanks checking out glxinfo ...10:37
duflucpaelzer, you can also use standard Unix tools like lsof and fuser to find which GPU each process has open (/dev/dri/card*). You can also look at the outputs that are directly wired to each card in /sys/class/drm/...10:41
dufluAlthough those are cards, vs render nodes. I think it would still answer your questions10:42
cpaelzerduflu: yeah that clearly got me further10:43
cpaelzerglxinfo was a lot of output and nothing clear - I assume I'd see multiple "Device" entries there if it fully initializes10:43
cpaelzerbut there is only one entry for a virtual device10:43
cpaelzeryet the /dev/dri/card has both entries, so that is good at leas10:44
cpaelzert10:44
duflucpaelzer, I think a GL/EGL/GLX context is only ever bound to one GPU. So 'glxinfo' will only ever give one answer10:44
cpaelzerah ok that would be ok for glxinfo then10:44
cpaelzeralso the /sys/class/drm looks good, essentially card0 (the virtual one) has 4 virtual outputs and the card1 (passthrough) has exactly the external port config of my system10:45
cpaelzerduflu: do you know how I know could make an application use card1-hdmi1 for example?10:45
cpaelzerif that makes any sense10:45
cpaelzerthe UI itself seems on card0 with output "virtual0"10:45
duflucpaelzer, it kind of makes sense. You have to tell the app (and the app must support) manual selection of a /dev/dri/cardN. Then once the card is selected you choose the output10:46
dufluHowever... APPS only use /dev/dri/cardN. The display server is fixed to whatever card you are physically plugged into, in the least10:47
dufluHmm. Or do apps get away with just using render nodes? I'm not sure now10:48
duflucpaelzer, one more tip before I log off. This will show you active monitors:   grep . /sys/class/drm/*/enabled10:53
duflugrep . /sys/class/drm/*/enabled10:53
dufluor just:  grep enabled /sys/class/drm/*/enabled10:54
cpaelzerthanks10:55
cpaelzerall seem enabled except a virtual port - I think that would only exist in a docking station, but that is fine10:57
oSoMoNseb128, re https://bugzilla.gnome.org/show_bug.cgi?id=746422#c60, do you reckon it would be acceptable to SRU n-m 1.10.14 to bionic11:20
ubot5Gnome bug 746422 in IP and DNS config "[CVE-2018-1000135] Unencrypted DNS queries leaked outside full-tunnel VPN" [Normal,Resolved: fixed]11:20
oSoMoN?11:20
willcookeI would like to see that too, but will see what seb says11:23
seb128oSoMoN, willcooke, the shorter/easier the diff the better I feel about a SRU, that one is non trivial but should be doable with proper testing I guess... depends how important we consider the issue to be and how risky the change is12:27
oSoMoNseb128, I can prepare test packages in a PPA to give it a solid round of testing before we decide what to do13:29
seb128oSoMoN, wfm, we can also give it a solid round of testing once it's in proposed13:45
willcookeoSoMoN, hit me up with the ppa and I will start testing13:55
willcooke#startmeeting Desktop Team Weekly Meeting 2018-11-2014:30
meetingologyMeeting started Tue Nov 20 14:30:37 2018 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.14:30
meetingologyAvailable commands: action commands idea info link nick14: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/RHiGQXZJ/ubuntu-desktop-1904-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting 2018-11-20 | Current topic:
tselioto/14:30
seb128hey14:31
Nafalloo/14:31
willcookeRoll call: andyrock, dgadomski, didrocks, duflu (out), jbicha, jamesh (out), jibel, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)14:31
didrockshey14:31
oSoMoN🐵/14:31
andyrocko/14:31
kenvandine\o14:31
* willcooke tries to remember how to do this14:31
willcookeLets review the rls bugs14:31
willcookeLooks like everyone has updated their bugs (based on the hub post)14:32
willcookebb-incoming : http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html14:32
willcookenothing for us atm14:32
willcookerls-bb-tracking: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html14:33
willcookeEverything is assigned14:33
willcookecorrection14:34
willcookeL_aney assigned this to tjaalton https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/171417814:34
ubot5Ubuntu bug 1714178 in xorg-server (Ubuntu) "Triple 4K monitor display failed (modesetting driver limited to 8192x8192)" [Medium,Triaged]14:34
willcookeand this: https://bugs.launchpad.net/amd/+bug/177027114:35
ubot5Ubuntu bug 1770271 in mesa (Ubuntu Bionic) "VegaM support" [Undecided,New]14:35
willcookeand this: https://bugs.launchpad.net/ubuntu/bionic/+source/mesa/+bug/179859714:35
ubot5Ubuntu bug 1798597 in xorg-server (Ubuntu Bionic) "Backport packages for 18.04.2 HWE stack" [Undecided,New]14:35
seb128sounds good14:35
willcookecc incoming: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html14:36
seb128willcooke, on -bb you forgot https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/180013514:36
ubot5Ubuntu bug 1800135 in libssh (Ubuntu Bionic) "libssh-dev is missing cmake find module" [Undecided,Confirmed]14:36
seb128L_aney in his email recommends -notfixing14:36
seb128which I'm +1 with14:36
willcookeah, I didnt think that was one for us14:37
willcookeah, kk14:37
seb128it doesn't impact Ubuntu Desktop14:37
willcookeyeah14:37
willcooke+1 from me14:37
seb128let's do that then :)14:37
willcookelooks like the tag is already gone14:37
seb128right, because it's nomination accepted14:37
seb128I wonder if rls-bb-notfixing works for those case?14:38
willcookeI added it anyway14:38
seb128thx14:38
willcookecc-incoming: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html14:38
willcookehttps://bugs.launchpad.net/ubuntu/+source/mesa/+bug/175469314:39
ubot5Ubuntu bug 1754693 in xorg-server (Ubuntu) "Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]" [High,Confirmed]14:39
willcookeIMO we should try and fix that one14:39
seb128+114:39
willcookebut... it's wayland, so less important14:39
willcookehrm14:39
willcookeI still think we need to, because it will be broken elsewhere14:39
seb128yeah, also it makes those snap not work as good14:40
seb128and wayland is default on some other distros14:40
willcookeyeah14:40
willcookeoki, +1 to fix14:40
seb128we need an assignee though14:40
willcooketjaalton, would you be able to take a look at it? ^14:40
seb128tjaalton can you ... what will said :)14:40
willcookewhile we wait, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/179929314:41
ubot5Ubuntu bug 1799293 in gnome-shell (Ubuntu) "gnome session: Must ask twice to lock the screen" [High,Confirmed]14:41
seb128+1 to accept the nomination14:41
willcookeL_aney said it's pretty rare and edge-casey.  I agree notfixing, but we work on it as time allows anyway14:42
andyrockwell it's a security issue if you close your laptop14:42
andyrockand the lockscreen is no there when you re-open it14:42
willcookethen dont enable auto login :)14:42
andyrockI mean you suspend it14:42
seb128it's not only autologin14:42
willcookeoh14:42
willcookeahhh14:43
andyrockI'm pretty sure it has the same root case of dash-to-dock over lockscreen14:43
willcookethis could be related to the problems that you were having jibel14:43
andyrockat least in one varaint14:43
willcookeandyrock, yeah14:43
seb128one of the comments mentions bg setting14:43
seb128I was going to say that14:43
tjaaltonwillcooke: okay14:43
willcookethank you tjaalton14:43
seb128andyrock, do you want to take on that?14:43
andyrockthe main variant of the dash-to-dock over lockscreen is that both are enabled14:43
andyrockand I'm fixing it14:43
seb128+1 from me on nominating based on the fact that's it's screen failing to lock which is border security14:44
willcookein which case, thanks andyrock14:44
andyrockthan there is the other variant (and I think it shares the same main cause)14:44
andyrockno idea what's the cause but it needs to be fixed14:44
willcookeassigned it and targetted to C14:45
willcookeit wouldnt let me target D14:45
andyrockthx14:45
willcookeand the next one is: http://launchpad.net/bugs/176938314:45
ubot5Ubuntu bug 1769383 in gnome-shell-extension-ubuntu-dock (Ubuntu Disco) "Ubuntu dock/launcher is shown on the lock screen" [High,In progress]14:45
willcookewhich we covered above and is assigned14:45
seb128right14:45
willcookedd incoming: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html14:46
andyrockI would target bionic for 1769383 too14:46
willcookeandyrock, done14:47
willcookedd has the same bug as we already talked about14:47
willcookek, that's the end of the list I think14:47
willcookeanyone want to talk about those before we move on to AOB14:47
willcookeif they do, we can come back round again14:48
willcooke#topic AOB14:48
=== 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/RHiGQXZJ/ubuntu-desktop-1904-cycle | Amaterasu watches over you benevolently | Desktop Team Weekly Meeting 2018-11-20 | Current topic: AOB
willcookeI remember there being a question from the hub14:48
willcookedidrocks I think you suggested someone come and ask something, can you remember what?14:49
didrocksyes, I don't remember the question though :p14:49
willcookeI'll look14:49
didrocksah, it's something that clobrano already asked14:49
didrocksIIRC14:49
didrocksso, that's settled :)14:49
willcookein the meantime, do you think we will get the new d-2-d in D?  With the window preview ordering "fixes"?14:50
clobranohey :D14:50
didrockshey clobrano :)14:50
willcookehey clobrano14:50
didrocksunsure I have time currently with the installer work14:50
clobranohi willcooke , didrocks14:50
didrocksso, probably in a quieter time, if no-one beats me to do the upload14:50
willcookedidrocks, ack, thx14:50
didrockssame for Yaru btw, would be need if someone cut a new release14:50
didrocksnice*14:51
willcookenod14:51
clobranodidrocks: what question? :)14:51
didrocksclobrano: willcooke will have a look again14:51
willcookecant find it, I'll look it out after the meeting14:53
willcookeanyone got anything else?14:53
willcookeguess not.14:53
willcooke#endmeeting14:53
=== 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/RHiGQXZJ/ubuntu-desktop-1904-cycle | Amaterasu watches over you benevolently
meetingologyMeeting ended Tue Nov 20 14:53:50 2018 UTC.14:53
meetingologyMinutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2018/ubuntu-desktop.2018-11-20-14.30.moin.txt14:53
willcookethanks all14:53
oSoMoNthanks14:53
willcookeAh, I found it - but it was from 5 months ago, and someone just replied now :)14:54
willcookeso ignore me14:54
andyrockthx14:55
tseliotsorry, I missed the chance to update you on nvidia14:56
seb128thx14:56
willcooketseliot, np, now is good14:56
seb128tseliot, you can still do now :)14:56
tseliotwillcooke: just FYI, I uploaded nvidia 410.78 in disco. It will be an additional flavour, in addition to 390, which will be a legacy driver. And I plan to backport 410 to Bionic.14:56
willcookenice!14:56
didrocksthx14:56
tseliotthe new nvidia is still in NEW, so it might take a while14:56
tseliotthat's all I have14:57
willcookethanks tseliot14:57
tseliot:)14:57
Laney added: rls-cc-tracking15:29
Laneythat's not a tag btw15:29
* Laney nominates https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1754693 and makes sure tasks on other bugs have assignees :-)15:32
* Laney the bug janitor15:32
ubot5Ubuntu bug 1754693 in xorg-server (Ubuntu) "Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]" [High,Confirmed]15:32
willcookethanks Laney15:40
Laneyanything for #ubuntu-desktop 😘15:40
andyrockdidrocks: https://github.com/micheleg/dash-to-dock/pull/84316:04
gitbotmicheleg issue (Pull request) 843 in dash-to-dock " extension: Ensure signal disconnection " [Open]16:04
andyrockcould you take a look?16:04
didrocksandyrock: will do tomorrow morning. Still in installer build16:25
andyrockkk16:25
oSoMoNwillcooke, https://launchpad.net/~osomon/+archive/ubuntu/nm-lp1754671/+packages just built, I haven't actually tested, hopefully this doesn't break the internet badly17:18
willcookethanks oSoMoN, I will install it tomorrow and report back17:20
willcookeor not17:20
willcookedepending :)17:20
oSoMoN:)17:21
=== pstolowski is now known as pstolowski|afk
* oSoMoN calls it a day17:36
oSoMoNhave a good evening everyone17:36
willcookedinner time, night all18:01
popeyI <3 the update posts on discourse. Especially all the lovely icons and emoji! :D18:46
andyrockseb128: still here? do you mind creating the ubuntu/cosmic branch for gnome-control-center ?21:26
andyrockI want to prepare the SRU21:26
seb128andyrock, k, I can do that21:54
seb128andyrock, k, done, I created it from the 1:3.30.1-1ubuntu2  tag which is the current cosmic version22:01
seb128on that note, calling it a day, night desktopers22:02
robert_ancellRAOF, I have a gnome-software 3.28.1-0ubuntu4.18.04.7 SRU which has one of the bugs as failed on the pending-sru page - this bug was in the .6 SRU and removed in .7 - do you know if this is holding back the SRU from being verified?22:39
RAOFrobert_ancell: That probably would be holding back the verification (or, at least, would be preventing people from acting on it). Why is it still marked as failed?22:40
robert_ancellRAOF, the fix caused another issue so was abandoned. So it shouldn't be considered part of the SRU anymore.22:40
RAOFOk, there's something weird with that SRU.22:51
RAOFrobert_ancell: Aaah! I think someone accidentally accepted it into -proposed without a complete .changes list.23:18
robert_ancellRAOF, yeah, I think I missed the -v when building the source package23:19
RAOFOr maybe not? I'm not entirely sure how to read this launchpad output.23:19
robert_ancellSo it is in proposed, but I wonder if the bug being marked red means it will stay there23:20
RAOFrobert_ancell: Right, which is why the bug tracking is screwy.23:20
RAOFrobert_ancell: And why it hasn't actually been verified.23:20
RAOFOnly one of the green bugs on the pending-sru page has actually been verified against the version of the upload in -proposed.23:20
robert_ancellRAOF, ok, I'll chase up the verifiers to reconfirm.23:24
RAOFrobert_ancell: I'm not entirely sure how to proceed here; the *simplest* thing for me would be to ask you to upload again with a correct .changes file, accept that, and it will trigger all the necessary “please verify” requests.23:24
robert_ancellRAOF, can I re-use the .7 version?23:25
RAOFNope, it'd need to be .823:25
robert_ancell*sigh*23:25
RAOFLaunchpad has seen the .7 version, and what Launchpad sees cannot be unseen!23:25
robert_ancellRAOF, so would you like me to do that then?23:25
RAOFI think that would be simplest, yes. Please do so.23:26
robert_ancellAnd the .changes should have changes from .5 .6 .7 and .8 in it right?23:26
RAOFCorrect. Everything since the current version in -updates23:26
RAOFThat will leave #1754864 incorrectly marked as fixed, I think, but I'll manually fix the status post-acceptance.23:30
robert_ancellRAOF, uploaded23:32
RAOFTa. RAOF23:35
RAOFSorry about the faffing.23:42

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