[06:39] <handsome_feng> Hi, Please could anyone help to upload ukui-greeter which fix LP: #1822014 before beta release? Thanks in advance!
[06:39] <ubot5`> Launchpad bug 1822014 in Ubuntu Kylin "ukui-greeter failed to launch on ubuntukylin 19.04 beta iso" [Critical,Confirmed] https://launchpad.net/bugs/1822014
[06:42] <handsome_feng> It is kept at: https://launchpad.net/~ubuntukylin-members/+archive/ubuntu/1904updates
[07:54] <oSoMoN> good morning desktoppers
[08:11] <duflu> Morning oSoMoN
[08:11] <oSoMoN> hi duflu
[08:51] <willcooke> good morning
[08:55] <marcustomlinson> morning!
[08:57] <oSoMoN> good morning willcooke, marcustomlinson
[08:58] <willcooke> oSoMoN, thank you for looking at the wallpapers last night
[08:59] <oSoMoN> willcooke, you're welcome! Please test https://launchpad.net/~osomon/+archive/ubuntu/disco-wallpapers/+packages and let me know if that looks good, before I request sponsorship
[09:00] <oSoMoN> I did test and it looks fine to my untrained eye
[09:00] <willcooke> will do, just installing the daily Disco and then I'll give it a go
[09:08] <handsome_feng> Hi, When will Disco beta release? I'm still waiting someone to sponsor my ukui-greeter which fix LP: #1822014
[09:08] <ubot5`> Launchpad bug 1822014 in Ubuntu Kylin "ukui-greeter failed to launch on ubuntukylin 19.04 beta iso" [Critical,Confirmed] https://launchpad.net/bugs/1822014
[09:09] <willcooke> handsome_feng, freeze was Monday, beta should be out today.  Then things will unfreeze and things can land again
[09:10] <willcooke> clobrano, hi!  Do you know... is it expected that the circle around the little person icon on the login screen has gone away?
[09:11] <clobrano> handsome_feng: Hi, yes, the circle is gone by design :)
[09:11] <willcooke> clobrano, got it, thanks!
[09:11] <clobrano> oops, wrong nick, sorry handsome_feng
[09:12] <duflu> Morning willcooke, marcustomlinson, clobrano, world
[09:12] <clobrano> and good morning all o/ :D
[09:12] <handsome_feng> willcooke: emmm, without this fix, ubuntukylin can't login to the desktop...
[09:12] <willcooke> ahoy duflu
[09:12] <oSoMoN> good morning clobrano
[09:14] <willcooke> handsome_feng, that's bad luck :(  It's very unlikely that they will respin today, but you should go in #ubuntu-release and ping the release team and see if they can help.
[09:14] <willcooke> laney is on holiday, infinity won't be online yet
[09:14] <willcooke> sil2100 is out by the looks of things
[09:15]  * acheronuk was just doing that ping ^
[09:15] <handsome_feng> willcooke: Thank you, I'm talking with acheronuk now, and he is help to find the release team
[09:15] <willcooke> just saw, cool!
[09:17] <acheronuk> I'll keep half an eye out for sil2000 coming online
[09:31] <willcooke> oSoMoN, wallpapers look good, thank you!  I'm testing the slideshow now, but it will take a few hours, I looked at the xml and it looks about right
[09:31] <willcooke> so +1
[09:32] <oSoMoN> willcooke, in my tests I hand-edited the xml after installation to change the duration of each image to 5 secs
[09:32] <oSoMoN> that worked, so assuming it will work with 30min for each image too
[09:33] <willcooke> I'll do the same, just to see it cycle round
[09:33] <willcooke> Ha, I **LOVE** it that you can have fractions of a second for the duration of an image in the slideshow, but until now you could only scale the screen in integers
[09:34] <willcooke> #priorities
[09:34] <oSoMoN> heh
[09:46] <willcooke> oSoMoN, looks good +1
[09:46] <willcooke> thanks a lot
[09:46] <willcooke> I think all our sponsors are out, so we can pick it up next week when the archive opens again
[09:46] <willcooke> meanwhile, I think I've found a new bug
[09:47] <willcooke> in gfm
[09:47] <willcooke> gdm
[09:47] <oSoMoN> willcooke, thanks
[10:00] <willcooke> hi sparkiegeek
[10:01] <sparkiegeek> hi, I'm having issues convincing GNOME on 18.04 LTS to switch default sound output to my Bluetooth headphones, they are showing as connected and appear in the Sound tab of GNOME Control Centre, but when I click them, the setting doesn't seem to "stick"
[10:01] <sparkiegeek> sound still comes out of the previously selected sink (the rubbish speakers built into the monitor connected via HDMI)
[10:03] <willcooke> sparkiegeek, have you tried with pavucontrol - it would be interesting to see if that works.  If it does then it's a problem with g-c-centre.  If it doesn't then it could be a Pulse issue
[10:06] <sparkiegeek> willcooke: hmm, so with pavucontrol I don't see them as listed as an output device. In Configuration tab, I see that the profile is set to "Off", If I set it to A2DP, then close pavucontrol and re-enter, it again doesn't seem to 'stick'
[10:06]  * willcooke looks for a bluetooth speaker
[10:08] <sparkiegeek> ho hum, more fun - by disconnecting and reconnecting, it all "works"
[10:08] <sparkiegeek> i.e. g-c-centre behaves as I expect, they're listed in pavucontrol etc.
[10:09] <willcooke> sparkiegeek, what's your audio source here?  (I half expect you to say Google Chrome here)
[10:10] <sparkiegeek> willcooke: well it was Firefox with Google Meet, but I was using the "Front left", "Front right" to test
[10:10] <willcooke> kk
[10:10] <sparkiegeek> spotify is connected, but paused
[10:11] <willcooke> I just used Spotify and it worked
[10:11] <willcooke> hmm
[10:11] <sparkiegeek> (was listed as an application in pavucontrol)
[10:11] <willcooke> ok, so... if pavucontrol isnt working either, then it's probably not a g-c-c thing
[10:12] <sparkiegeek> suspect it's somehow related to ordering of things. Had it fail multiple times just before my regular morning Google Meet
[10:12] <sparkiegeek> ack, agree that g-c-c is out of the firing line
[10:12] <willcooke> has it been working fine previously?
[10:13] <willcooke> duflu, do you happen to know if we've pushed a new pulse out recently?
[10:13] <sparkiegeek> can't point to a particular regression, the headphones are new, and when connecting first "things just worked" but seem flaky after disconnecting and reconnecting etc.
[10:13] <willcooke> heh, Spotify on random picked The GLC.  Nice.
[10:13] <duflu> willcooke, someone was doing minor patches to support one specific headset, but in general no. It's unchanged since 18.10
[10:14] <willcooke> thx duflu
[10:14] <duflu> Which is very handy because this year I have been able to identify recent regressions as not Pulse's fault
[10:15] <willcooke> sparkiegeek, I think we need to speak to koza and do some Bluetooth debugging.
[10:15] <duflu> \o/ mutter menu fix written and landed, and still on time for dinner
[10:16] <willcooke> nice one duflu, enjoy
[10:16] <sparkiegeek> willcooke: ack
[10:16] <willcooke> sparkiegeek, it would be interesting to try a Disco live image and see if things are generally broken still
[10:17] <sparkiegeek> willcooke: yeah, was thinking of just jumping in and going to Disco
[10:17] <willcooke> and then open a bug against, erm, well open it against pulse and we can move it as needed
[10:17] <willcooke> and then I will ask Koza to advise on the BT debugging with wireshark and whathaveyou
[10:18] <willcooke> I think it's most likely a Bluez issue
[10:18] <duflu> Hang on a sec...
[10:18] <sparkiegeek> all feels a bit wooly at the moment, can't nail down a set of steps to reproduce
[10:20] <duflu> A couple of pairing problems were just fixed upstream, but it turns out at least one of them is only for mice... https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1773897/comments/50
[10:20] <ubot5`> Ubuntu bug 1773897 in OEM Priority Project "[regression] Logitech M337 mice are automatically disconnected after connected" [Critical,Confirmed]
[10:20] <duflu> The other is for Bluetooth in general but isn't documented at all :/
[10:22] <duflu> night...
[10:25] <willcooke> hm those changes look like pointing devices only, but might still help
[10:27] <sparkiegeek> i do see a scattering of 'Bluetooth: hci0: last event is not cmd complete (0x0f)' in dmesg
[10:27] <sparkiegeek>  
[10:27] <willcooke> we could try forcing the pin to 0000
[10:28] <willcooke> e.g. https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1773897/comments/48
[10:28] <ubot5`> Ubuntu bug 1773897 in OEM Priority Project "[regression] Logitech M337 mice are automatically disconnected after connected" [Critical,Confirmed]
[10:28] <willcooke> oh, no
[10:28] <willcooke> there is a generic headphones|headset rule
[10:29] <willcooke> so it should already be there
[10:29] <willcooke> sparkiegeek, which model of headphones?
[10:29] <sparkiegeek> and i can confirm that in my case both Ubuntu and the headset thinks it's connected (it speaks to me :D )
[10:30] <sparkiegeek> willcooke: Sony WH-1000X M3
[10:33] <sparkiegeek> ok, getting closer to reproducible steps - from a working setup, if I turn the headphones off, sound falls back to the default device (so far so good). Then I turn them back on again, and reconnect BT, but then pulse seems to default the profile to 'off', and I have to switch it to A2DP, and then disconnect/reconnect the headphones to get back to working again
[10:33] <sparkiegeek> will file bug now
[10:36] <sparkiegeek> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1283003 sounds familiar
[10:36] <ubot5`> Ubuntu bug 1283003 in gnome-bluetooth (Ubuntu) "Bluetooth headset/speakers listed but not selectable in Sound settings" [High,Confirmed]
[10:42] <sparkiegeek> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1822073 is what I filed
[10:42] <ubot5`> Ubuntu bug 1822073 in pulseaudio (Ubuntu) "Bluetooth headset profile forgotten after disconnection" [Undecided,New]
[10:44] <willcooke> nice one, thanks sparkiegeek
[10:45] <willcooke> I think we might need to send this one upstream, but we will take a look and see what we can do
[10:59] <jibel> oSoMoN, bug 1822075
[10:59] <ubot5`> bug 1822075 in gnome-shell (Ubuntu) "tooltips and combo boxes in webbrowsers are all garbage" [Undecided,New] https://launchpad.net/bugs/1822075
[10:59] <oSoMoN> jibel, is the chromium snap affected, too?
[11:00] <oSoMoN> (and/or firefox snap, if you can test)
[11:00] <jibel> let me check
[11:02] <jibel> oSoMoN, yes it is
[11:02] <jibel> I tried the tooltips in FF and the result is the same
[11:05] <oSoMoN> jibel, is that a recent regression?
[11:05] <willcooke> I'm going to flag the bug for rls review next week, if it's a general amd problem then it needs fixing imo
[11:05] <willcooke> oh, you already did
[11:05] <willcooke> :)
[11:06] <jibel> oSoMoN, yes it's recent and actually also affect any combo, not only in webbrowser
[11:06] <oSoMoN> aha
[11:06] <oSoMoN> jibel, there was a xorg update yesterday, can you try downgrading?
[11:07] <tjaalton> what update?
[11:10] <jibel> sure, I'll first try kernel 4.xx
[11:10] <jibel> it's just a reboot away
[11:10] <tjaalton> which X driver is being used?
[11:11] <oSoMoN> xorg:amd64 (1:7.7+19ubuntu11, 1:7.7+19ubuntu12) is the update I got yesterday, I didn't check what's in there tbh
[11:11] <tjaalton> might be a regression in the -ati pkg, upstream has a new bugfix release with some fixes and reverts
[11:11] <tjaalton> oSoMoN: it's just a metapackage
[11:12] <oSoMoN> right
[11:12] <jibel> I'll downgrade xorg
[11:13] <jibel> but lunch first
[11:13] <oSoMoN> first things first :)
[11:13] <tjaalton> no need to downgrade xorg..
[11:17] <tjaalton> jibel: pull xserver-xorg-video-ati/-radeon from ppa:canonical-x/x-staging once it has built
[13:03] <jibel> tjaalton, the version in the ppa fixes the issue
[13:08] <oSoMoN> cool
[13:16] <tjaalton> jibel: thanks
[16:41] <Eickmeyer> Hey everyone. Found a nasty UX bug in Ubiquity for Ubuntu Studio. (bug 1822134)
[16:41] <ubot5`> bug 1822134 in ubiquity (Ubuntu) "Ubuntu Studio Installation - Black Text on Dark Gray" [Undecided,New] https://launchpad.net/bugs/1822134
[16:42] <Eickmeyer> Not sure how to resolve this, but if someone could help me out here, that would be great.
[16:43] <Eickmeyer> We changed our GTK theme, and it's not behaving correctly with Ubiquity.
[16:50] <willcooke> Eickmeyer, perhaps clobrano might be able to help
[16:51] <Eickmeyer> Thanks willcooke! It's not a show-stopper for beta, but I'd like it to get resolved by final.
[16:52] <clobrano> hey Eickmeyer
[16:52] <Eickmeyer> clobrano: Hi!
[16:52]  * clobrano is looking at the issue ticket
[16:53] <Eickmeyer> cyphermox confirmed it on his own.
[16:53] <clobrano> Eickmeyer: has your theme anything to do with yaru/adwaita?
[16:53] <Eickmeyer> clobrano: Not at all. The theme is materia.
[16:54] <Eickmeyer> Used to be numix-blue, but we decided to drop that since we were maintaining it with our tiny little team.
[16:57] <clobrano> Eickmeyer: I see. In yaru we customized some details of ubiquity, but not the color. However you might have a look in our repo to see where to put your hands
[16:57] <clobrano> https://github.com/ubuntu/yaru/blob/6a4d98747160c9d28bb0fe1249d4117d37bb472c/gtk/src/light/gtk-3.20/_apps.scss#L576
[16:57] <clobrano> s/color/text color/
[16:59] <Eickmeyer> clobrano: Line #587 gives me a clue.
[16:59] <clobrano> :)
[17:00] <Eickmeyer> clobrano: Unfortunately, I have no idea what to do with that clue. :(
[17:01] <clobrano> Eickmeyer: :D, unfortunately I'm not familiar with materia theme, but I might save some time to look into it (not sure though)
[17:01] <Eickmeyer> clobrano: That would be much appreciated.
[17:01] <Eickmeyer> I linked the package in the bug report.
[17:02]  * clobrano added to backlog
[17:03] <Eickmeyer> clobrano: I'm calling the beta release good for now, but I hope we can get something fixed before RC or final.
[17:03] <clobrano> Eickmeyer: alright
[17:04] <Eickmeyer> The bug report is in the release notes.
[17:05] <clobrano> Eickmeyer: is materia repo this one https://github.com/nana-4/materia-theme ? I can't find anythig in code section for materia-gtk-theme
[17:06] <Eickmeyer> clobrano: Looks like it.
[17:10] <clobrano> Perfect
[18:53] <willcooke> night all
[22:22] <clobrano> Eickmeyer: https://github.com/nana-4/materia-theme/pull/369
[22:22] <gitbot> nana-4 issue (Pull request) 369 in materia-theme "gtk: tweak visibility of Ubiquity #label_page label" [Open]
[22:23] <Eickmeyer> clobrano: Nice! Then, since it would be a bug fix, would we be able to cherry-pick that into the materia-gtk-theme package, or.. how would that work?
[22:26] <Eickmeyer> clobrano: I just subscribed to that PR.
[22:27] <clobrano> Eickmeyer: this is just a pull request, let's see if it's accepted. After that, materia-gtk-theme package has to be updated by the ppa manager
[22:28] <clobrano> Eickmeyer: the only source code I've found is the github one, so I don't know how that's done :)
[22:29] <Eickmeyer> clobrano: If it were me, I'd pull the commit as a git patch and add it to debian/patches for quilt to take care of.
[22:31] <clobrano> Eickmeyer: this is a good idea
[22:32] <clobrano> Eickmeyer: the change is very specific, it won't cause any side effect
[22:32] <tsimonq2> jibel, etc.: For the Canary images, are those actually published somewhere, or are they just published squashfses that I have to manually inject into an ISO?
[22:32] <tsimonq2> ("those" meaning, published, usable ISOs)
[22:33] <tsimonq2> I don't see anything on cdimage.ubuntu.com, which implies the latter, however, it could just be not set up yet.
[23:15] <Eickmeyer> clobrano: It's pulled from upstream Debian. Luckily, I know a guy.
[23:15] <Eickmeyer> https://packages.debian.org/source/sid/materia-gtk-theme