[02:46]  * duflu spies Intel 10th gen CPUs in bug reports from OEM people and gets excited
[04:17] <duflu> Jet lagged jamesh?
[04:17] <duflu> Or flying out soon?
[04:23] <jamesh> flying home later today
[04:24] <jamesh> and apparently with a 7.5 hour layover in Doha :-(
[05:38] <oSoMoN> good morning desktoppers
[05:39] <duflu> Morning oSoMoN
[05:42] <oSoMoN> hey duflu
[05:46] <didrocks> good morning
[05:53] <jibel> hi didrocks
[05:53] <duflu> Morning didrocks
[05:53] <duflu> and good morning jibel
[05:53] <oSoMoN> salut didrocks, jibel
[05:53] <jibel> hi all
[05:55] <didrocks> hey jibel, duflu, oSoMoN
[06:25] <clobrano> good morning 0/
[06:31] <didrocks> hey clobrano
[06:31] <ricotz> good morning desktoppers
[06:31] <oSoMoN> good morning clobrano, ricotz
[06:31] <didrocks> hey ricotz
[06:31] <ricotz> oSoMoN, didrocks, hey
[06:33] <ricotz> oSoMoN, hi, is there some reasoning for switching to clang for ff69?
[06:34] <oSoMoN> ricotz, yes, the ppc64el builds would fail or fail to run in all sorts of ways with gcc
[06:34] <ricotz> oSoMoN, does this correspond to the build policy between mozilla and canonical?
[06:34] <oSoMoN> I would have preferred to anticipate that and do the switch in the beta branches
[06:35] <oSoMoN> ricotz, also clang is used by upstream to produce official builds, so this better aligns with them
[06:35] <ricotz> I see, and yes, switching it now it quite something
[06:37] <ricotz> oSoMoN, still the changelog must provide some information about why doing this
[06:37] <ricotz> or some bug report
[06:37] <ricotz> did you try to build it with llvm-9 on eaon yet?
[06:38] <oSoMoN> not yet, no
[06:39] <oSoMoN> ricotz, your help is welcome if you want to test that
[06:39] <ricotz> oSoMoN, hmm, I can follow this with 70, but as you said it is a quite late invasive change for 69
[06:45] <duflu> Morning ricotz
[06:45] <ricotz> hey duflu
[06:55] <Wimpress> Morning o/
[06:56] <oSoMoN> hey Wimpress
[07:04] <jibel> is night mode gone from gnome-shell?
[07:04] <jibel> I'm stuck with a red-ish display
[07:06] <duflu> jibel, sometimes colour profiles stick. Try just toggling the colour profile in settings
[07:06] <jibel> duflu, I've no color profile
[07:06] <duflu> And if you don't need one then delete the default, which fixes a bug
[07:07] <jibel> duflu, there use to be a mode to shift to red based on time of the day
[07:07] <jibel> duflu, and I'm block in night mode
[07:07] <seb128> goood morning desktopers
[07:07] <duflu> Morning seb128
[07:07] <oSoMoN> good morning seb128
[07:08] <seb128> the night mode is in the display settings panel
[07:08] <duflu> jibel, I can't find the setting. Might just be gnome-control-center though. To fix it you might need to hack gsettings
[07:08] <seb128> it's in the control center yes
[07:08] <duflu> seb128, not in 3.33
[07:09] <seb128> it's a page in display
[07:09] <duflu> For at least two of us
[07:09] <duflu> Nope
[07:10] <seb128> well it is
[07:10] <seb128> maybe it's not working for you
[07:10] <seb128> but by design/code that's where it's supposed to be
[07:10] <duflu> Probably the feature still exists, but the GUI is strangely gone
[07:10] <seb128> it was moved in https://gitlab.gnome.org/GNOME/gnome-control-center/commit/50be7b13c
[07:11] <duflu> Ah! Bad design
[07:11] <seb128> it's supposed to be  a row on the page
[07:11] <duflu> jibel, it was moved to a button in the titlebar
[07:11] <duflu> No wonder we couldn't find it
[07:12] <seb128> that
[07:12] <RAOF> Oooooh.
[07:12] <RAOF> My screen blanks each time the AMD gpu gets (temporarily) turned on!
[07:12] <seb128> hey RAOF
[07:12]  * RAOF notices this because opening the Display tab causes the discrete GPU to be turned on.
[07:12] <RAOF> Hey seb128!
[07:13] <duflu> I don't consider the titlebar "in a page"
[07:13] <duflu> Plus the colour makes it less obvious
[07:14] <seb128> is it better in Adwaita?
[07:14] <seb128> could be a theme problem...
[07:14] <duflu> Not sure, but that wouldn't move it
[07:14] <seb128> right, but that is not a new problem
[07:14] <seb128> even fileselector widgets have actions in the tittlebar
[07:15] <seb128> I don't like that design decision of GNOME either...
[07:27] <duflu> seb128, I think the problem is more g-c-c-specific. If you select a panel then you don't expect the contents of that panel to be outside of it
[07:28] <seb128> duflu, you should open a bug on gitlab as design feedback
[07:28] <duflu> seb128, design bugs are hard and slow, but more to the point I already had a heated discussion with its author yesterday
[07:28] <duflu> So no more comments for a while
[07:29] <seb128> :(
[07:29] <seb128> George again?
[07:29] <seb128> was it on gitlab/about the revert?
[07:29] <duflu> No, not related
[07:29] <duflu> They are keen to land geometric-picking but apparently intend to rewrite it. Just never said so in the MR
[07:29] <duflu> And still haven't said so publically
[07:30] <duflu> So I just ended up saying, yeah fine
[07:30] <duflu> Or publicly
[07:35] <duflu> In better news, mutter 3.33.91 brings one frame lower output latency to Xorg, as well as lower input latency for touchpad scrolling
[07:36] <duflu> Feels good, but there's more yet to land for smoother rendering
[07:37] <seb128> lut oSoMoN, désolé j'ai oublié de répondre avec les discussions, en forme ? :)
[07:37] <seb128> duflu, getting there! slow, but still :)
[07:42] <oSoMoN> seb128, ça va, hâte d’être en vacances et encore 10000 trucs à faire avant
[07:42] <oSoMoN> et toi?
[07:42] <seb128> un peu pareil :)
[07:46] <jibel> duflu, thanks. I didn't see it at all. buttons in the title bar are really a bad choice
[07:47] <jibel> however the feature is broken somehow. enabling/disabling it doesn't change the color and my display is still red
[07:48] <jibel> août 29 09:48:01 sark gsd-color[21255]: could not find device: property match 'XRANDR_name'='HDMI-0' does not exist
[07:48] <jibel> août 29 09:48:01 sark gsd-color[21255]: could not find device: property match 'XRANDR_name'='HDMI-0' does not exist
[07:48] <jibel> I suppose this is why
[07:48]  * jibel files a bug
[07:49] <seb128> file it upstream please
[07:49] <seb128> we don't have anyone downstream to deal with that atm I think
[07:56] <jibel> I cannot adjust the system volume in gnome-control-center, there is no cursor on the slider. Is anyone else seeing that?
[07:57] <duflu> jibel, yeah it's broken. Needs a bug. Though the shell menu works
[07:58] <jibel> I'll file a bug for that too
[07:58] <willcooke> morning
[07:59] <duflu> jibel, actually for me that's because sound isn't working
[07:59] <duflu> I can select the device though
[07:59] <duflu> Morning willcooke
[08:00] <Laney> hello
[08:01] <duflu> Hi Laney
[08:06] <Laney> hi duflu
[08:07] <Laney> seb128: did you see https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg ?
[08:07] <Laney> umm https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[08:08] <seb128> Laney, yes, doko commented about it on the rygel MIR, thx
[08:08] <Laney> cool
[08:15] <ricotz> seb128, hi :), how is it going with vala 0.46?
[08:15] <ricotz> Laney, hey
[08:17] <Laney> hi ricotz
[08:17] <seb128> ricotz, hey, we got busy getting the main part of the desktop updated and missed feature freeze, we would need a ffe now
[08:17] <seb128> also I'm on holidays tonight for a week so probably not something I'm going to be able to help with until I'm back
[08:18] <ricotz> seb128, I see, too bad, I am hoping for it getting into eoan
[08:18] <seb128> you could file the ffe :)
[08:21] <ricotz> seb128, this would lead to a lot of work :(
[08:22] <seb128> the ffe bug? it's only a few lines of rational, you have a test rebuild ppa ready
[08:22] <ricotz> time which is better invested upstream
[08:22] <seb128> k, as you prefer
[08:22] <ricotz> the ppa is outdated already, I guess
[08:22] <seb128> we will likely not have 0.46 this cycle is no-one is wanting to help with it though
[08:22] <seb128> right but it gives an indication
[08:23] <ricotz> with work, I mean fixing those those failures for ancient packages
[08:24] <seb128> yeah, well it's the deal if we want to update
[08:26] <ricotz> correct
[09:30] <ginggs> did something break unity desktop yesterday?
[09:31] <seb128> specifics?
[09:51] <willcooke> On E?  L_aney commented on discourse that it's likely related to the systemd work
[10:06] <ginggs> yes, on eoan.  k_alam asked yesterday "There is some issue with recent gnome-session update, if I try to update, it tries to uninstall unity-session ?"
[10:07] <ginggs> my unity-session didn't get removed, but whenever I try to log in, the screen goes blank, and after a few seconds I end up at the login screen again
[10:10] <seb128> ginggs, see https://discourse.ubuntu.com/t/testing-unity-session-in-eoan-ubuntu-19-10/10690/64
[10:10] <seb128> L_aney uploaded a fix now it
[10:11] <ginggs> seb128: thank you!
[10:11] <seb128> Laney, no upload on eoan-changes/launchpad, in case it failed to upload and you didn't notice
[10:22] <seb128> (worked now)
[10:23] <Laney> I'm having some connection issues with the Canonical network
[10:56] <didrocks> Trevinho: hey, did you try to new Shell with the "autohide" behavior for the dock? I wonder if this is what is making it crashing
[10:56] <didrocks> I have weird "push here" behavior (like the dock is hiding/showing/hiding/showing very quickly)
[10:57] <didrocks> so, there is at least this bug
[10:57] <didrocks> and I'm unsure if the crash is related or not yet
[10:57] <didrocks> (apport is collecting the trace)
[10:57] <seb128> let me try to turn that on, I've been on the new stack since before GUADEC and got 0 crash here
[10:57] <didrocks> seb128: not 100% hit
[10:57] <seb128> (but also intel where I expect you have nvidia?)
[10:57] <didrocks> yep
[10:58] <didrocks> at least the "autohide bug" shouldn't be (or would it?) card-specific
[10:58] <didrocks> but right now, the dock is showing up properly :/
[10:58] <didrocks> oh, I have 2 monitors now that I'm back home
[10:58] <didrocks> and the dock is between the 2 monitors
[10:58] <didrocks> maybe that's what triggering the issue
[10:59] <didrocks> (but again, can't get back the "show" bug that I already got 3 times)
[11:02] <didrocks> Trevinho: seb128: I subscribed you both on https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841921, let's see once retraced
[11:02] <didrocks> "503 (Service Unavailable). Failed to subscribe Marco Trevisan (Treviño)." I see how some people are doing on their bug strategy :p
[11:03] <seb128> didrocks, thx, autohide on single screen and no segfault so far here
[11:04] <didrocks> seb128: yeah, didn't get a new one either, but 3 in a raw is concerning
[11:04] <didrocks> and my setup didn't change: 2 monitors, dock in between since the crash :p
[11:04] <didrocks> at least, we have a stracktrace, let's see once retraced
[11:05] <didrocks> and once launchpad will let me subcribe Trevinho to the bug…
[11:07] <Trevinho> Ahahaha.... Bugwalled!
[11:08]  * didrocks checks launchpad commits from Trevinho
[11:10] <didrocks> ahhhhhhhhhhhh, you are now subscribed, mwahahahahaha
[11:10] <seb128> hey Trevinho, did you have a safe trip back?
[11:13] <didrocks> lalala, crash again :/
[11:14] <didrocks> seems definitively related to revealing the dock
[11:14] <Trevinho> seb128: yes, got home quite late (3am) as there was half hour delay and I had to drive one hour to get home (and thank God I took the car or I would have been stuck in the airport or forced to taxi to an hotel)
[11:14]  * didrocks turns autohide off for now
[11:14] <Trevinho> so I swapped today to help dayana in her last full day here
[11:15] <didrocks> Trevinho: waow, 3am, was it scheduled like that or you got delayed?
[11:16] <seb128> Trevinho, stop being on the computer then :)
[11:18] <didrocks> so, duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841794
[11:18] <didrocks> (and already 3 duplicates)
[11:18] <Trevinho> didrocks: was 00.35, then luggage, delay + car home from Bologna to Florence
[11:18] <didrocks> Trevinho: ah, from Bologna… yeah, that explains
[11:18] <didrocks> take some rest! :)
[11:25] <Trevinho> didrocks: yeah direct flights were only by Ryanair in Italy so I preferred to move to get the fight than doing changes and pay a flight to Greece 500€
[11:29] <didrocks> make sense
[11:30] <didrocks> hum, no more repeated key with my integrated volume up/down key on my keyboard
[11:30] <didrocks> (long press -> only one tick)
[11:31] <didrocks> seb128: do you reproduce this as well? ^ (keep volume up pressed for instance, I just have one volume increase)
[11:32] <Laney> nope, works for me
[11:32] <didrocks> doesn't on my internal & external keyboard (only for volume, works for brightness)
[11:34] <seb128> didrocks, key repeat doesn't work for me either
[11:34] <seb128> Laney, you and your wayland session :p
[11:34] <didrocks> cking: thanks for answering! That was my bet, but I preferred getting an authoritative answer
[11:35] <cking> didrocks, no problem :-)
[11:36] <Laney> could be
[11:36] <seb128> didrocks, Laney, key repeat works (and play sounds which I think it didn't do before) when under wayland
[11:36] <seb128> also I got the segfault playing a bit with the dock on autohide between monitors
[11:36] <didrocks> ok, so xorg-specific, let me file a bug
[11:36] <seb128> so no nvidia specific
[11:36] <seb128> upstream please :)
[11:36] <didrocks> sure
[11:37] <seb128> thx
[11:37] <didrocks> but still one on our side for tracking?
[11:38] <seb128> if you believe it's rls-ee material sure, otherwise unsure it's very useful
[11:38] <seb128> but doesn't hurt either
[11:39] <seb128> the segfault seems to happen easily when playing with the dock and doing some dnd of icons when e.g nautilus is over it
[11:40] <didrocks> yeah, seeing that we got 1 bug + 3 duplicates in one day, sounds like it will be popular
[11:41] <seb128> it's a real bug, I can't trigger it in single monitor
[11:42] <didrocks> which explains why I didn't see it either before getting back home
[11:43] <seb128> likely one for Trevinho once he's back to work, tomorrow or next week
[12:18] <seb128> Laney, thx for upstreaming that gcc sound issue :-)
[12:19] <Laney> np
[13:04] <Wimpress> Afternoon Laney.
[13:04] <Wimpress> Th Ubuntu MATE 19.10 daily image is exhibiting an interesting feature.
[13:04] <Wimpress> It boots GNOME Shell.
[13:05] <seb128> wooot
[13:06] <seb128> is it loading in french at least? ;)
[13:06] <Wimpress> I know you've all just been to GUADEC and are feeling super enthusiatic, but... ;-)
[13:06] <Laney> have you done some investigation that led you to ping me?
[13:07] <seb128> give it at least  a few days before jugging if you like it or not!
[13:09] <Laney> Probably some dependency change
[13:09] <Wimpress> GNOME Shell is being pulled in via update-notifier, which is seeded by Ubuntu MATE.
[13:10] <Wimpress> update-notifier Recommends: gnome-shell | notification-daemon
[13:10] <Wimpress> mate-notification-daemon Provides: notification-daemon.
[13:10] <Wimpress> It's been that way for years.
[13:11] <Laney> Something must have changed.
[13:11] <Wimpress> in the last 24 hours, GNOME Shell is now pulled in to Ubuntu MATE.
[13:11] <Laney> There are multiple chains, that's not going to be the oen.
[13:11] <Laney> one.
[13:12] <seb128> Wimpress, does 'aptitude why gnome-shell' is helpful?
[13:13] <Wimpress> Yeah, that ^ is what led me to update-notifier.
[13:13] <Wimpress> I was just asking in case it prompted anything regarding system and user session.
[13:13] <Wimpress> Clearly not, I'll go hunting...
[13:14] <Wimpress> *systemd and user session
[13:14] <Laney> You shouldn't have gnome-shell on the ISO, that's orthogonal to the systemd stuff
[13:14] <Laney> it'll be a packaging level thing
[13:14] <RikMills> Wimpress: kylin mentioned the same thing the other day. i.e. gnome-shell getting pulled in
[13:15] <seb128> update-notifier didn't change since aug 1st
[13:15] <seb128> so not likely it
[13:16] <RikMills> * Chose ubuntu-session to satisfy gnome-shell
[13:16] <RikMills> * Chose gnome-shell to satisfy libnotify4
[13:16] <RikMills> ^^ from kylins germninate
[13:22] <Wimpress> RikMills: Thanks. I'll take a look.
[13:25] <Laney> Good luck /o\
[14:12] <Laney> Wimpress: had a look and I can't immediately see what's going on
[14:14] <Laney> it does look like it's pulling gnome-shell due to libnotify4, but mate-notification-daemon ought to be satisfying that recommends too, so I'm not quite sure
[14:49] <Wimpress> Laney: Yeah, I'm just testing what happends if I add libnotify4 to the Ubuntu MATE core seed and meta packages.
[14:50] <Wimpress> This germinate output is also "interesting"
[14:50] <Wimpress> * Chose gnome-shell to satisfy screen-resolution-extra
[16:14]  * oSoMoN logs off for 10 days, see ya all in a while!
[16:15] <didrocks> see you oSoMoN
[18:17] <willcooke> night all