[07:14] <didrocks> good morning
[07:22] <duflu> Morning didrocks
[07:24] <didrocks> hey duflu
[07:26] <didrocks> hum, 3 issues with new GNOME Shell in 2 minutes, let's reboot to see
[07:28] <didrocks> ok, just 2 now :) (open a terminal shortcut work after a restart after upgrading)
[07:28] <didrocks> unsure to file them, the top panel one is obviously known, just the release hasn't been coordinated
[07:29] <didrocks> I'll still file gnome-shell-extension-gsconnect not working with new G-S
[07:29] <didrocks> not targetting -incoming as not the default, but as we wanted to promote it…
[07:45]  * duflu isn't sure who didrocks is talking to
[07:45] <duflu> But yeah there are some hiccups in gnome-shell 3.31.9x
[07:46] <didrocks> duflu: the top panel is now always transparent with new G-S, no?
[07:46] <didrocks> I guessit needs a new Yaru release
[07:47] <duflu> didrocks, always opaque, never transparent you mean?
[07:47] <duflu> Yeah that was an upstream decision
[07:47] <didrocks> hum, it's always transparent here
[07:47] <didrocks> with Yaru
[07:47] <duflu> Weird
[07:47] <duflu> Upstream decided to make it always opaque
[07:47] <duflu> Sounds like you've got some old theme settings laying around
[07:47] <didrocks> yeah, but I guess the css property that is assigned is the one which was corresponding to the transparent color in Yaru
[07:48] <didrocks> or is it always opaque for you, with Yaru?
[07:48] <duflu> didrocks, sorry you are right. My Yaru login is always transparent now
[07:48] <didrocks> ah :)
[07:48] <duflu> I can't keep up with all the changes
[07:48] <didrocks> I guess it's just that the "fixed" value was the default property
[07:48] <didrocks> but we didn't change Yaru css
[07:49] <didrocks> or this is changed in upstream Yaru
[07:49] <didrocks> but not released yet
[07:49] <didrocks> (but yeah, I know upstream removed the dynamic transparency thingy)
[07:50] <duflu> Ironically one of the most popular branches is to add a new transparency method (https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/404)
[07:50] <gitbot> GNOME issue (Merge request) 404 in gnome-shell "Add transparent panel adapting to background image characteristics" [Opened]
[07:50] <didrocks> ahah ;)
[07:50] <didrocks> oh you got 404, congrats!
[07:50] <didrocks> and 404 for "transparent" is an easter egg in itself :p
[07:51] <duflu> #geekjoke
[07:52]  * duflu hugs didrocks to clarify that's not a bad thing
[07:52]  * didrocks hugs duflu back ;)
[07:53] <duflu> didrocks, oh so the dock is always opaque for similar reasons?
[07:56] <didrocks> yep
[07:57] <didrocks> I guess it was a discussion during the day, so you probably missed it, we decided to align
[07:57] <didrocks> I thought we decided for some slight transparency though
[07:57] <didrocks> unsure what happened to this, but Trevinho would know
[07:58] <duflu> Obviously the dock and panel don't match. So I assume someone will fix that
[07:58] <duflu> one way or the other
[07:59] <duflu> Actually that will solve an old bug where their transparencies were slightly different
=== pstolowski|afk is now known as pstolowski
[08:37] <tjaalton> duflu: you can reproduce bug 1767312?
[08:37] <ubot5> bug 1767312 in mesa (Ubuntu) "[radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos" [High,Confirmed] https://launchpad.net/bugs/1767312
[08:37] <duflu> tjaalton, it was on weird old hardware. I don't know where the hardware is but am confident it's in this house
[08:38] <tjaalton> old enough that it uses r600_dri.so and not radeonsi?
[08:38]  * duflu shrugs
[08:38] <tjaalton> 10bpc should be disabled in code for gallium drivers
[08:39] <duflu> tjaalton, I can make it an evening task to get to over the next week and retest. Which release would you like me to try?
[08:40] <tjaalton> bionic or newer
[08:40] <tjaalton> actually r300 and up are all using gallium
[08:41] <clobrano> good morning all o/
[08:41] <didrocks> hey clobrano
[08:42] <clobrano> hey didrocks, how are you?
[08:42] <didrocks> clobrano: good! Yourself?
[08:43] <clobrano> didrocks: mee too, thanks :)
[08:44] <clobrano> duflu, didrocks: I didn't know about that little transparency decision for the shell top panel. There's a PR about ready that will set it totally solid
[08:44] <clobrano> https://github.com/ubuntu/yaru/pull/1234
[08:44] <gitbot> ubuntu issue (Pull request) 1234 in yaru "sync Yaru gnome-shell against upstream" [Open]
[08:45] <didrocks> clobrano: the top panel is totally solid, only the dock should have slight transparency
[08:45] <didrocks> IIRC
[08:45] <didrocks> but that was Trevinho who would know more
[08:45] <duflu> clobrano, thanks :)
[08:46] <clobrano> didrocks: I see, as it was originally on 18.04 + ambiance then
[08:50] <didrocks> clobrano: exactly!
[08:56] <clobrano> out of curiosity, is there anyone using Matrix IRC bridge to chat here in ubuntu-desktop?
[08:56] <duflu> didrocks, do you need bug 1819126 to stay private?
[08:56] <ubot5> Error: Launchpad bug 1819126 could not be found
[09:02] <Laney> yo
[09:02] <acheronuk> clobrano: I see a few nicks here with the [m] suffix
[09:03] <acheronuk> testing it out on KDE channels, matrix is a bit of a pain still
[09:05] <duflu> Hi Laney
[09:06] <clobrano> acheronuk: I couldn't use it much, because  the IRC bridge for the ubuntu-desktop channel (or generally for freenode) seems read only. None of my messages passed through, while it works fine with #gnome channels
[09:13] <acheronuk> clobrano: just tried in here, and bridge hasn't forwarded the message yet :/
[09:14] <acheronuk> it is not perfect yet
[09:15] <acheronuk> or could be channel modes in here
[09:16] <didrocks> duflu: just rereviewed, nothing really private, let's open it
[09:17] <duflu> Done
[09:18] <didrocks> duflu: you know this is the "big icon size" bug which just went worse
[09:18] <clobrano> acheronuk: yep :(
[09:19] <duflu> didrocks, bug 1818246, bug 1818878 or something else?
[09:19] <ubot5> bug 1818246 in gnome-shell (Ubuntu) "update-notifier's notification is huge due to large icon" [High,Confirmed] https://launchpad.net/bugs/1818246
[09:19] <ubot5> bug 1818878 in yaru-theme (Ubuntu) "System menu user icon is bigger than others in 3.31.92" [High,Triaged] https://launchpad.net/bugs/1818878
[09:20] <didrocks> duflu: bug 1818246
[09:20] <acheronuk> clobrano: works in #kubuntu-devel and #kde chans, so I think that explanation makes sense. e.g. something like mode set in here so only ops see messages from users whos nicks are not registered
[09:20] <acheronuk> I recall a lot of ubuntu chans set that a while back when there was massive spam
[09:20] <clobrano> acheronuk: I see, hope this can be fixed
[09:21] <acheronuk> up to ops in this chan. which is not me
[09:22] <RAOF> <freenode_clo "acheronuk: I see, hope this can "> Have you got a registered IRC account associated with the Matrix bridge?
[09:23] <acheronuk> clobrano: https://community.kde.org/Matrix#How_do_I_join_an_IRC_channel_that_requires_registered_nicknames.3F
[09:24] <acheronuk> ^^ for KDE matrix, but should be generic
[09:24] <clobrano> acheronuk: thanks! I'll have a look
[09:32] <oSoMoN> good morning desktoppers
[09:35] <seb128> good morning desktopers
[09:38] <Laney> hey oSoMoN seb128
[09:40] <seb128> hey Laney, how are you?
[09:40] <seb128> happy friday!
[09:40] <didrocks> hey oSoMoN, Laney, seb128
[09:41] <seb128> lut didrocks, en forme ?
[09:41] <didrocks> manque de sommeil cette nuit
[09:41] <didrocks> Martin a fait des siennes, mais bon, ça va :p
[09:44] <seb128> :(
[09:45] <Laney> I'm alright, but feeling tired today, happy it's the weekend soon
[09:45] <Laney> hey didrocks!
[09:45] <seb128> :)
[09:45] <seb128> Laney: I've a feeling you are not going to like that one...
[09:47] <didrocks> hey hey Laney
[09:47] <Laney> 😳
[09:48] <seb128> we have a new ubuntu-font version to package
[09:48] <seb128> I've heard you did deal with that once
[09:48] <Laney> come on
[09:48] <seb128> so you might remember some of the details on how that's done?
[09:48] <seb128> :(
[09:48] <Laney> there's loads of weird shit to check
[09:48] <Laney> you need to sync with sladen on it imho
[09:49] <seb128> we can try at least
[09:54] <duflu> Oh, morning oSoMoN and seb128
[09:54] <seb128> hey duflu, how are you?
[09:54] <duflu> andyrock, bug 1712122 looks out of date...?
[09:54] <ubot5> bug 1712122 in gnome-shell (Ubuntu) "Desktop keyboard shortcuts autorepeat (probably shouldn't)" [Low,Triaged] https://launchpad.net/bugs/1712122
[09:54] <duflu> seb128, going well. And about to end the week. You?
[09:55] <seb128> duflu: I'm good thanks :)
[09:55] <seb128> duflu: any plan for the w.e yet?
[09:55] <duflu> seb128, a family dinner, plus infinite home improvements/chores
[09:55] <duflu> fun fun
[09:55] <duflu> You seb128?
[09:56] <seb128> we have friends over for dinner on saturday, otherwise nothing planned yet
[09:57] <duflu> sounds similar
[09:59] <seb128> yeah
[09:59] <duflu> seb128, BTW your crash from yesterday is now formalised in bug 1819126
[09:59] <ubot5> bug 1819126 in gnome-shell (Ubuntu) "gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image-content.c:155:st_image_content_get_preferred_size: assertion failed (priv->width > -1): (-1 > -1)]" [Medium,Confirmed] https://launchpad.net/bugs/1819126
[10:00] <duflu> which doesn't look like what I said I thought it looked like
[10:01] <seb128> duflu: thx
[10:01] <duflu> Night
[10:02] <seb128> Laney: k, font bug opened and sladen pinged, le('s see how that goes
[10:02] <seb128> duflu: have a nice w.e!
[10:02] <Laney> thx
[10:02] <seb128> oh, didrocks opened it but with different scenario that I had
[10:03] <seb128> it segfault that way when unlocking the screen here
[10:03] <didrocks> I guess this is triggered by any notifications from an application that doesn't have appinfo
[10:03] <didrocks> and so when size = -1
[10:03] <didrocks> ironically, this is now hiding the bug of "too large icon size"
[10:03] <didrocks> so, it was only a warning, but it seems Marco turned it into a segfault in mutter now
[10:04] <seb128> improvement!
[10:04] <didrocks> well
[10:04] <didrocks> I can claim the bug I was looking at is "fixed" :p
[10:04] <seb128> well, Marco fixed your issue :p
[10:04] <didrocks> exactly
[10:05] <didrocks> I guess we'll discuss this next Tuesday anyway
[10:05]  * didrocks goes back to ubuntu-cdimage
[10:05] <seb128> I'm rls-dd-incoming it
[10:05] <Laney> the upstream bug has a merge proposal linked, does that fix it?
[10:06] <Laney> probably not, just a random mention
[10:06] <seb128> Jonas said it's not likely but I didn't try yet
[10:07] <seb128> going to wait for Trevinho to comment
[10:07] <Laney> k whatever
[10:10] <Trevinho> morning
[10:10] <Trevinho> Ah, I also got an email about this crash...
[10:10] <Trevinho> well, I wouldn't have been so strong in asserting it, but Jonas suggested me to assert it so I did xD
[10:14] <Trevinho> didrocks: the reason why size -1 was considered wrong is that we can't then have a proper resource scale on it, so we decided to not allow them. And well, the crash is a good way to know about these cases xD
[10:14] <Trevinho> while I prefer to be more conservative, there are different ideas :)
[10:17] <didrocks> yeah, I would be on your side of more conservative
[10:17] <didrocks> but anyway, at least, now, it's surfaced :p
[10:17] <Trevinho> you see :)
[10:17] <didrocks> I hope the test case helps triggering it
[10:17]  * Trevinho relocates to coworking
[10:18] <didrocks> funny that I spent some hours in finding a good reproducer + debug to find that was the float casting
[10:23] <seb128> good morning Trevinho
[11:06] <Trevinho> hi seb128
[11:07] <oSoMoN> ricotz, hey, in case you hadn't noticed, there are packages for gcc-mozilla (trusty and xenial) in ppa:ubuntu-mozilla-security/ppa that fix building firefox 65 on arm*
[11:10] <oSoMoN> ricotz, hopefully that's also enough to build firefox 66
[11:10] <oSoMoN> are you looking at the armhf failures for 66, btw?
[11:50] <ricotz> oSoMoN, hi, you are kidding me?
[11:51] <ricotz> oSoMoN, I told you several times that there are gcc-mozilla 6.5.0 packages available since december, e.g. also here https://launchpad.net/~mozillateam/+archive/ubuntu/build-support
[11:52] <ricotz> the firefox 66 failures are not gcc related
[11:52] <oSoMoN> ricotz, I know, but backporting 6.5.0 in its entirety is not needed 6.4.0 + that patch is enough
[11:54] <ricotz> I see, do as you like
[11:55] <ricotz> I am currently not looking into the 66 failures
[11:56] <oSoMoN> ok, I'll have a look at those, then
[11:58] <ricotz> thanks
[11:59] <seb128> Laney: could you look at bug #1819103? I had it to check on my backlog because I saw it mentioned on other reports/forums before but now we have a proper report
[12:00] <ubot5> bug 1819103 in indicator-application (Ubuntu) "Indicator Application and indicator-applet does not show indicators" [Undecided,New] https://launchpad.net/bugs/1819103
[12:00] <seb128> it looks like having indicator-application installed on the system somewhat conflicts with the gnome-shell extension
[12:00] <seb128> dunno if they fight for the same dbus name or what
[12:02] <Laney> guess so, I don't know how that stuff works but I can look if you want
[12:03] <seb128> that would be nice, thx
[12:10] <Laney> something wrong with using rls process for that one, ooi?
[12:11] <seb128> I guess we can
[12:11] <seb128> it's one of those bugs where I don't know if it's important enough to be rls handled
[12:11] <Laney> no need, just wondering if there is some case for skipping it
[12:11] <seb128> but I guess if it's important enough for me to ask you to own it, then it's important enough to be tracked by our process
[12:14] <Laney> I don't reproduce this on disco
[12:14] <Laney> do you?
[12:16] <seb128> let me try
[12:17] <Laney> https://people.canonical.com/~laney/weird-things/wfm.png
[12:19] <seb128> I installed it and did a shell reload, it's still there
[12:19] <seb128> let me restart my session
[12:26] <seb128> Laney: after installing indicator-application and restarting my session I don't get the transmission icon anymore
[12:26] <Laney> disco?
[12:26] <seb128> yes
[12:27] <seb128> journal has
[12:27] <seb128> gnome-shell[15942]: [AppIndicatorSupport-WARN] Failed to acquire org.kde.StatusNotifierWatcher
[12:27] <seb128> which I guess is the issue
[12:27] <seb128> it's a race who owns the dbus name first
[12:27] <Laney> sounds like it could be racy
[12:27] <seb128> unsure how we can fix it, out of renaming out or making them conflct :/
[12:29] <Laney> just don't make indicator-application autostart in gnome
[12:32] <seb128> oh, good point, I though it would be dbus activated or something but there is an autostart
[12:33] <seb128> having in OnlyShowIn=Unity makes sense I guess
[12:33] <Laney> can't be dbus-activated, otherwise they would conflict over the .service file
[12:33] <seb128> right
[12:34] <Laney> does it have GNOME in there because of gnome-panel?
[12:36] <seb128> I don't remember the specifics now :/
[12:36] <seb128> AutostartCondition=GNOME3 unless-session gnome
[12:37] <seb128> how does that work again?
[12:38] <Laney> $DESKTOP_SESSION
[12:38] <Laney> could add a second one with ubuntu there
[12:38] <Laney> (probably)
[12:45] <seb128> but then the first on would still trigger?
[12:47] <Laney> dunno, need to see
[13:07] <Laney> NotShowIn=ubuntu; it is
[13:09] <seb128> ah, makes sense now that you say it
[13:09] <seb128> thx Laney :)
[13:10] <seb128> on that note, lunch!
[15:35] <kenvandine> mvo: did you look into the help url issue?
[15:44] <mvo> kenvandine: I haven't yet, let me do so now
[15:44] <mvo> kenvandine: whats the easiest way for me to reproduce?
[15:45] <kenvandine> mvo: well i actually can't reproduce it today :)
[15:45] <kenvandine> on disco, as we no longer have the menu in the panel
[15:45] <seb128> the lcy wifi is crap, keeps required you to reauth
[15:45] <kenvandine> i was seeing it on the seeded snaps
[15:45] <kenvandine> mvo: if you are on cosmic or bionic, open gnome-calculator and click help in the menu
[15:47] <kenvandine> mvo: the core18 snaps actually seem fine
[15:47] <kenvandine> but  we haven't published core18 versions of the seeded snaps yet
[15:49] <mvo> kenvandine: oh, interessting. so core18 works as expected but not "core" ?
[15:50] <kenvandine> yeah, apparently :)
[15:50] <kenvandine> i was only testing the seeded snaps the other day
[15:50] <mvo> kenvandine: is clicking on "help" on e.g. stable edit enough?
[15:50] <mvo> *stable gedit
[15:50] <kenvandine> and now the version of gnome-shell in disco doesn't provide a menu in the panel
[15:51] <kenvandine> gedit is core18
[15:51] <kenvandine> gnome-calculator from stable should be a good test
[15:52] <kenvandine> mvo: the only snaps we have that haven't been updated to core18 are the seeded ones
[15:53] <jbicha> kenvandine: what version of snapd of whatever do I need to use to try the core18 help feature?
[15:54] <kenvandine> mvo: which version was that released in? 2.37.4 maybe?
[15:55] <jbicha> 'cause I'm on disco and it doesn't seem to work
[15:55] <kenvandine> oh, interesting
[15:55] <kenvandine> maybe it has something to do with me running edge
[15:55] <jbicha> edge of what? :)
[15:56] <kenvandine> core
[15:56] <seb128> reading the irc log from earlier, didrocks your gs-connect if it's a segfault is probably bug #1816415 fixed by andyrock which is just waiting for the fixes to land in the packaging now
[15:56] <ubot5> bug 1816415 in glib2.0 (Ubuntu) "gjs-console crashed with SIGSEGV in g_socket_receive_message_with_timeout()" [High,In progress] https://launchpad.net/bugs/1816415
[15:56] <kenvandine> jbicha: what version are you running?
[15:56] <mvo> kenvandine: it should work with edge/core - I will update disco RSN not too
[15:57] <jbicha> I was using stable core & core18, snapd is 2.37.4+19.04
[15:58] <andyrock> didrocks: https://trello.com/c/OxxvEMgt/263-gjs-console-crashed-with-sigsegv-in-gsocketreceivemessagewithtimeout if you want to track the status of the fix
[15:59] <didrocks> seb128: andyrock: oh nice! Ok, I'll keep the extension enabled thus to confirm it's back on track
[15:59] <didrocks> thx for the head's up
[16:00] <jbicha> yeah, help still doesn't work with core and core18 upgraded to edge
[16:01] <kenvandine> they are all working for me now
[16:01] <kenvandine> but weren't before
[16:01] <kenvandine> maybe a reboot?
[16:01] <jbicha> trying…
[16:01] <kenvandine> i hadn't rebooted in weeks
[16:01] <kenvandine> until this morning
[16:02] <kenvandine> shouldn't need a reboot... but that's all i can think of
[16:07] <jbicha> still didn't work
[16:10] <kenvandine> weird
[16:10] <kenvandine> anything on the console?
[16:18] <seb128> kenvandine, jbicha: , I justtried on stock disco and that errros with
[16:18] <seb128> user-open error: Supplied URL scheme "help" is not allowed
[16:18] <seb128> on that note boarding, bbl, have a nice w.e desktopers
[16:19] <willcooke> see you seb128
[16:19] <kenvandine> yeah, that's the old code
[16:19] <kenvandine> bye seb128
[16:19] <seb128> willcooke: btw the font uopdate with the new ttf is in disco now, let me know how it goes if you try it
[16:20] <willcooke> thanks seb128
[16:20] <jbicha> seb128: I'll upload fonts-ubuntu to Debian (experimental) too
[16:21] <willcooke> thanks jbicha
[16:21] <seb128> k; as you wish
[16:22] <seb128> you might want to update to 0.84 there? ;)
[16:22] <seb128> (but then dont sync to ubuntu)
[16:24] <jbicha> bye :)
[16:30] <Laney> ah I forgot about bileto's stupid changelog trailers that it generates for me
[16:31] <seb128> hehe
[16:31] <Laney> robru blamed my configuration but I forgot in what way and I remember that I didn't agree with him
[16:33] <didrocks> you just didn't remember in which way you disagreed
[16:34] <Laney> he was WRONG on the INTERNET
[16:34] <Laney> could have been irl tbh
[16:36] <didrocks> worse, it could be both!
[16:37]  * Laney hulk smash
[16:37] <didrocks> ;)
[17:58] <willcooke> night all, have a good weekend
[18:00] <Laney> laterz
[18:00]  * Laney is off to climb a big hill (tomorrow)
[18:24] <oSoMoN> have a good week-end everyone