[00:29] <jbicha> fossfreedom: gnome-shell/gdm3 is back on your iso because of notification-daemon this time
[01:58] <RAOF> /msg robert_ancell Hey, could you kindly ping me on telegram? I'd like to make sure I can actually receive messages before arriving at the sprint :)
[02:01] <sarnold> /msg RAOF I'm not sure your irc client is your friend :)
[02:01] <RAOF> sarnold: The perils of bridging to Matrix ☺
[02:02] <sarnold> RAOF: curious, I didn't expect that..
[02:03] <RAOF> It's possible that a more mature client than Fractal would have picked the /msg up and translated it.
[02:07] <JanC> is matrix or any matrix client supposed to interpret IRC commands at all?
[02:08] <ahayzen> https://riot.im/app does interpret some commands
[02:08] <RAOF> Riot has its own set of commands.
[02:08] <RAOF> Yeah,
[02:08] <JanC> I mean, the fact that matrix bridges to IRC doesn't mean it has to have the same UI
[02:34] <jbicha> lol
[02:35] <jbicha> I'm just glad that it wasn't anything more sensitive!
[02:53] <RAOF> I'd be checking more thorourgly for something more sensitive than “give us a ping to test my notification settings” ☺
[07:42] <didrocks> good morning
[07:45] <jibel> Salut didrocks
[07:46] <didrocks> salut jibel
[07:46] <didrocks> good semi-off day? :)
[07:50] <jibel> didrocks, I don't think that driving to Paris can be described as "good" :) Kids were taking the train for holidays
[07:56] <didrocks> oh, indeed :p
[09:00] <seb128> good morning desktopers
[09:01] <didrocks> hey seb128
[09:01] <seb128> lut didrocks, en forme ?
[09:02] <Laney> sup
[09:02] <didrocks> seb128: ça va, et toi ?
[09:02] <didrocks> Laney: hey hey
[09:02] <seb128> ça va bien
[09:03] <oSoMoN> good morning desktoppers
[09:08] <didrocks> salut oSoMoN
[09:08] <oSoMoN> salut didrocks
[09:14] <seb128> lut oSoMoN, en forme ?
[09:14] <seb128> hey Laney
[09:14] <oSoMoN> salut seb128, fatigué mais ce soir je suis en week-end
[09:14] <oSoMoN> et toi?
[09:14] <seb128> bon courage alors :)
[09:14] <seb128> ça va, mais un peu mal à la gorge depuis hier
[09:14] <Laney> hey didrocks seb128 oSoMoN
[09:14] <seb128> j'espère m'en débarrasser avant dimanche
[09:15] <oSoMoN> hey Laney
[09:15] <Laney> omg someone's encrypted the channel again
[09:15] <oSoMoN> seb128, en effet il vaut mieux être en pleine forme pour attaquer un sprint
[09:17] <seb128> Laney, the key is public, you can decrypt!
[09:17]  * seb128 hands Laney un dictionnaire de la langue française
[09:18] <Laney> if it comes with croissant, I'm happy
[09:18] <seb128> au chocolat?
[09:18]  * seb128 hides from Didier
[09:19] <Laney> :D
[09:19] <didrocks> pfffff
[09:19] <didrocks> pffffff
[09:19] <didrocks> pfffffff
[09:19] <didrocks> pffffffff
[09:19] <didrocks> pfffffffff!
[09:20] <didrocks> Laney: how did you decipher what seb128 told btw? That was encrypted as well :p
[09:20] <seb128> lalala
[09:20] <Laney> $ gpg --list-secret-keys
[09:20] <Laney> [ tasty food here ]
[09:53] <jibel> the UX of the new version of control-center is terrible
[09:53] <jibel> and it crashes when I click on details
[09:54] <jibel> then I cannot launch it again meh :(
[10:01] <Laney> the second part is https://gitlab.gnome.org/GNOME/gnome-control-center/issues/285, which is fixed upstream and the bug also contains a command you can use to be able to run it again
[10:01] <gitbot> GNOME issue 285 in gnome-control-center "crash in the info panel" [1. Crash, 6. Component: Info, Closed]
[10:05] <seb128> bug #1814949 on the launchpad side
[10:05] <seb128> what's the problem with the UX?
[10:07]  * Laney wonders what the point of rls-dd-incoming on that is when jbicha has the ability to fix it
[10:14] <jibel> main panel is almost empty until you resize the window depending on the panel, when you go to applications you cannot go package, sound panel has too many items, that's 2 min of using it before it crashes and I cannot open it anymore
[10:22] <jibel> go back*
[10:22] <seb128> I'm not sure ot understand the resize thing, applications is a new panel and probably not that useful atm for us since it's flatpak centric (though Robert has a card o make it work iwth snaps)
[10:23] <seb128> the crash is an unfornate regression from the new glib, those happens in the unstable cycle
[10:23] <seb128> & it's being handled
[10:24] <seb128> if you find the new sound panel design too 'busy' please report upstream, I'm sure they welcome feedback
[10:24] <seb128> it fits better than the old design imho, doesn't mean it's perfect
[10:24] <jibel> in this case the release should have been postponed until glib is fixed
[10:24] <jibel> or whatever is broken between glib and g-c-c
[10:25] <seb128> it's not like the "details" panel was an essential feature and worth revertingglib over
[10:25] <seb128> we don't block stabilization of important OS pieces over things noone really needs
[10:25] <seb128> like I don't think arguing that glib should be blocked over/revert because the info panel of settings is having an issue
[10:26] <seb128> + makes sense
[10:26] <seb128> it would be detrimental to the release quality imho and conterproductive
[10:26] <seb128> you loose days/weeks of important testing for a panel which has no issue, come on
[10:27] <jibel> the problem is not the panel, you cannot launch g-c-c again after it crashes
[10:27] <seb128> the workaround is easy
[10:27] <seb128> "gnome-control-center sound" for example
[10:27] <andyrock> do you know if it's possible to make read-only a page on wiki.ubuntu.com ?
[10:27] <jibel> nope, it doesn't work
[10:27] <seb128> andyrock, I dont know, maybe popey does?
[10:28] <seb128> jibel, ?
[10:28] <jibel> the workaround doesn't work
[10:28] <seb128> what does it say?
[10:28] <jibel> j-lallement@sark:~/Downloads$ gnome-control-center sound
[10:28] <jibel> Segmentation fault (core dumped)
[10:28] <jibel> just try on disco
[10:28] <seb128> can you get a bt?
[10:29] <seb128> I can confirm that info crashes
[10:29] <Laney> that's not the workaround from the bug
[10:29] <Laney> it's a gsettings reset
[10:29] <seb128> opening another panel should work though no?
[10:30] <Laney> apparently not
[10:30] <seb128> it worked for me, weird, maybe timing or something
[10:31] <seb128> jibel, gsettings reset org.gnome.ControlCenter last-panel
[10:31] <seb128> then?
[10:32] <jibel> this works
[10:32] <seb128> good
[10:32] <seb128> let me cherry pick that upstream patch also
[10:32] <seb128> so we can stop arguing for good
[10:33] <seb128> can you please give details on the reiszing issue and report the "sound panel is too busy" on https://gitlab.gnome.org/GNOME/gnome-control-center/issues as well?
[10:36] <jibel> yeah but still, things should be tested before begin uploaded and hold the release if there is an obvious crash. It was simple-scan last week, g-c-c this week and it took less than 2 min to make them crash
[10:36] <jibel> being*
[10:38] <seb128> come on
[10:38] <seb128> things are tested
[10:38] <seb128> the problem is coming from the glib update and not the g-c-c update
[10:38] <seb128> even if do one hour of starting everything I can think of using glib I might not think about going to the settings->info panel
[10:39] <jibel> simple-scan crash last week?
[10:39] <seb128> different case
[10:39] <jibel> same case, most basic tests have not been done
[10:58] <seb128> bah, I don't understand git again :/
[11:12] <Laney> seb128: want help or?
[11:13] <seb128> Laney, no, thanks, I was about to ask but decided to try on a fresh checkout and then back in my working tree and now it works
[11:13] <seb128> I had
[11:13] <seb128> gnome-control-center$ gbp pq rebase
[11:13] <seb128> ...
[11:13] <seb128> CONFLIT (contenu) : Conflit de fusion dans panels/mouse/gnome-mouse-properties.c
[11:14] <seb128> but it went away
[11:14] <seb128> maybe I was in the wrong branch or something
[11:14] <Wimpress> jibel: Just doing some 18.04.2 iso testing.
[11:14] <Laney> okey
[11:14] <seb128> then pq export would fail saying I had unstashed changed but I figured it out
[11:14] <Wimpress> Neither virtualbox-guest-x11 or virtualbox-guest-x11-hwe can be installed.
[11:14] <seb128> I needed to rebase --continue after resolving the conflict
[11:15] <seb128> anyway, thanks for asking Laney :)
[11:17] <Laney> if someone else has done the rebase before (if you're just pulling and adding a patch for e.g.) you can also drop/import
[11:17] <Laney> np
[11:18] <seb128> Laney, I was trying to follow https://wiki.ubuntu.com/DesktopTeam/git#Pick_some_upstream_commits
[11:19] <seb128> instead of just dumping a .patch in debian/patches manually (would have been easier)
[11:20] <Laney> ok, just wanted to give you a tip
[11:21] <seb128> thx, I'm not sure ot understand git/gbp enough to understand the tip though
[11:21] <seb128> if I don't use 'gbp pq rebase', then what command does the job?
[11:21] <Laney> rebase rebases the branch
[11:22] <seb128> oir you meant to just copy the .patch the old way?
[11:22] <Laney> but you can re-create it
[11:22] <Laney> if you just want to add a patch, that is what drop and import does
[11:25] <seb128> ah, right, I remember now, Marco mentioned that in the past :)
[11:25] <seb128> thx Laney
[11:25] <seb128> (also tried, indeed it works and avoid some of the 'noise' rebase is creating)
[11:29] <Laney> that recipe is also not going to make a patch with dep3 headers ;-)
[11:29]  * Laney edits it to add '-e' at least
[11:35] <seb128> shrug
[11:36] <seb128> gbp push fails with
[11:36] <seb128> gbp:error: Error running git push: To git+ssh://seb128@git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-control-center
[11:36] <seb128>  ! [rejected]        b3ab4d31841d2009c9d8930437acd3c6eeb63f0e -> pristine-tar (non-fast-forward)
[11:36] <seb128> hint: Updates were rejected because a pushed branch tip is behind its remote
[11:37] <seb128> but git branch -v/git pull tell me pristine-tar is up-to-dat
[11:37] <seb128> I can just ignore that gbp push error since I don't need to push anything at this point
[11:37] <seb128> but it's puzzling :/
[11:41] <Wimpress> tseliot: The doesn't appear to be a HWE nvidia driver for 18.04.2 in the archive.
[12:17] <jbicha> Laney: I didn't want to step on your toes by cherry-picking the g-c-c patch if you were planning to do it today
[12:18] <jbicha> jibel: I don't have a scanner so I wasn't able to do the basic simple-scan test. It did run without a scanner…
[12:19] <jbicha> good morning
[12:20] <Laney> jbicha: Alright, it was mostly that rls-dd-incoming seems like an unusual way to express that (you could have asked me)
[12:20] <Laney> anyway, seb128 did it so all good
[12:20] <jbicha> I was probably going to ask today. Silly timezones :)
[12:21] <Laney> feel free to ping me any time, I'll just reply when I get online next
[12:22] <jbicha> ok
[12:22] <Laney> :>
[12:26] <jbicha> I guess the most useful part of the new g-c-c Applications panel is that you can now disable file associations
[12:26]  * Laney likes that
[12:26] <jbicha> the rest is like an alternative way of browsing the Search and Notifications panel (this way you navigate by app instead of by feature)
[12:44] <Laney> jibel: I just filed https://gitlab.gnome.org/GNOME/gnome-control-center/issues/377, not sure if that's what you were trying to describe but it seemed worth reporting to me
[12:44] <gitbot> GNOME issue 377 in gnome-control-center "Sound panel shows duplicate and irrelevant entries" [6. Component: Sound, Opened]
[12:51] <jibel> Laney, thanks for reporting it, it's the issue and the main input and output volumes are not visible
[12:51] <jibel> you have to scroll
[12:54] <Laney> right, the order of the components is in the design
[12:54] <Laney> it's a bit weird when there are a lot of streams
[12:59] <jibel> Laney, do you see this too https://i.imgur.com/g53CLAd.png ?
[12:59] <jbicha> seb128: the new g-c-c patch isn't listed in d/p/series :(
[13:00] <Laney> jibel: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/375
[13:00] <gitbot> GNOME issue 375 in gnome-control-center "Some panels (Background, Sound, Printers) cause the sidebar to disappear when visited" [Opened]
[13:01] <jibel> it's slightly different, in this case only the sidebar is visible with a wide empty space
[13:02] <jibel> and another issue is this where you cannot go back from applications https://i.imgur.com/R7WCZLC.png
[13:03] <Wimpress> tjaalton: nvidia driver are uninstallable in 18.04.2. Is this a known issue?
[13:03] <Laney> first part is part of the same bug, watch the screencast
[13:03] <tjaalton> Wimpress: you mean tseliot? I think it's being fixed
[13:03] <Laney> didn't see the other thing, please file it
[13:04] <Wimpress> Yeah, I pinged tseliot earlier. Thank for the update.
[13:21] <ricotz> hi, g-c-c 1:3.31.90-1ubuntu2 is not working -- $ gnome-control-center
[13:21] <ricotz> gnome-control-center: symbol lookup error: gnome-control-center: undefined symbol: gnome_get_all_languages
[13:27] <ricotz> ah, never mind, although it still crashes
[13:32] <ricotz> seb128, Laney, hi, the udisks patch in g-c-c is not applied aka not in the series file
[13:33] <jbicha> seb128: I'll go ahead and do this g-c-c upload since I have another fix to add
[13:35] <ricotz> jbicha, thanks
[14:04] <seb128> jbicha, thx for pointing that out, I got bitten by the gbp workflow again :/
[14:05] <tseliot> Wimpress: yes, I'm working on it.
[14:05] <seb128> ricotz, that symbol issue is weird, can you give a ldd of the binary?
[14:05] <seb128> jbicha, k, thx
[14:09] <seb128> jbicha, also do you review the diff of every upload others do?
[14:13] <Laney> just got a usb bluetooth adapter
[14:13] <Laney> hoping for ZERO BUGS!
[14:13] <Laney> let's try ;-)
[14:14] <seb128> haha
[14:15] <Laney> ok it's recognised by the kernel, good first step
[14:15] <ricotz> seb128, seems some intermediate problem, the root cause was the missing patch as said
[14:16] <seb128> ricotz, k, good
[14:16] <ricotz> seb128, I tend to look at the diff if I got bitten by a bug myself
[14:17] <seb128> yeah, makes sense
[14:17] <Laney> k managed to pair with my phone and send a file, good start
[14:18] <seb128> woot
[14:18] <Laney> now let me try the headset
[14:20] <seb128> tseliot, is there a bug about the nvidia problem? is #r-t aware of the problem?
[14:20] <Laney> k, close but no cigar, it paired fine but they're not listed in the sound panel as an output
[14:26] <tseliot> seb128: I don't think so, I noticed yesterday, and I asked tjaalton (who uploaded the new hwe stack)
[14:26] <seb128> tseliot, tjaalton, can we get a bug tracking and r-t notified?
[14:28] <jbicha> tseliot: since you're here, did you see bug 1815374?
[14:30] <tseliot> jbicha: no, but I promise I'll have a look soon, thanks
[14:31] <tseliot> seb128: sure
[14:34] <seb128> tseliot, thx
[14:54] <tseliot> seb128: it seems that we already have a bug report about it: LP: #1815579
[14:55] <seb128> tseliot, thx
[15:37] <seb128> kenvandine, jbicha, so we got a stack of snap failing to build errors in the moderation queue from the desktop list around jan 30, is that something you know about? can I just discard those or is the info useful?
[15:38] <seb128> things like
[15:38] <seb128>  	[Snap build #447603] amd64 build of gedit snap package in ubuntu bionic-backports
[15:38] <seb128> Store upload failed for gnome-calculator-candidate
[15:38] <jbicha> seb128: those have generally been taken care of
[15:38] <seb128> [Snap build #447889] i386 build of gnome-clocks-master snap package (gnome-clocks) in ubuntu bionic-updates
[15:38] <seb128> k
[15:38] <kenvandine> discard ;)
[15:38] <seb128> thx
[15:39] <seb128> I'm always unsure if those reach the uploader/right people as well
[15:39] <seb128> or just the list
[15:39] <jbicha> there are probably a few that will still ping until the Snap Store manual reviews are done for changed D-Bus app id's for GNOME 3.32
[15:39] <seb128> k
[15:40] <kenvandine> jbicha: do you know which ones haven't been ack'd yet?
[15:40] <kenvandine> i can chase them down
[15:40] <seb128> there was a few ' 	Store authorization failed for ...'
[15:40] <seb128> unsure what those are
[15:40] <kenvandine> i fixed those already
[15:40] <kenvandine> well
[15:40] <kenvandine> jbicha made sure i did :)
[15:40] <jbicha> some of those emails are because Launchpad periodically requires reauthorization for it to automatically upload to the Store
[15:40] <seb128> k
[15:40] <kenvandine> the token expires from time to time
[15:40] <kenvandine> annoying :)
[15:40] <jbicha> it's a bit annoying for what we do :(
[15:44] <jbicha> kenvandine: it looks like glade is the only one I see with the dbus rename now
[15:45] <kenvandine> ok
[15:45] <kenvandine> jdstrand: can you look at that?  glade is stuck in review because of the dbus slot
[15:47] <jdstrand> kenvandine: r32 - r35 (the latest) are all approved. they need to be released though (I did this yesterday or sometime). am I missing something?
[15:47] <kenvandine> jdstrand: oh... they are :)
[15:48] <kenvandine> sorry about that
[15:48] <kenvandine> jbicha: ^^ all good
[15:48] <jdstrand> np
[15:50] <cyphermox> hey, on the desktop daily-live, I see the icon for ubiquity changed to some kind of weird circle and line thing, anybody know whether that's on purpose?
[15:55] <kenvandine> jbicha: i've released glade-master to edge and glade to candidate
[16:11] <kenvandine> jbicha: they have a fix for the gedit git mirror, just waiting for a sysadmin to roll it out
[16:11] <kenvandine> been in their queue for a couple days now
[16:13] <tomreyn> hey, i installed using the desktop daily-live, kept the default setting of "install updates during installation", chose minimal install, and ended up with 297 pending upgrades.
[16:14] <tomreyn> (maybe this is already known or even expected at this time)
[16:20] <kenvandine> tomreyn: that's not surprising.  The latest daily-live is nearly 2 weeks old now.
[16:20] <kenvandine> tomreyn: there are newer ones in pending
[16:22] <k_alam> jbicha: Hi, in nm-applet dependency can it be "policykit-1-gnome | gnome-shell" instead of "gnome-shell | policykit-1-gnome" ?
[16:23] <tomreyn> kenvandine: i see. but isn't it more of a conceptual issue then? being just a dumb user i am i would assume that keeping the "install updates during installation" option would, whether the installer is old or new, make me end up with exactly 0 pending updates after the install is done.
[16:24] <tomreyn> kenvandine: anyways, i don'T want to delay any work, or waste anyone's time, just thought this may be relevant.
[16:24] <kenvandine> tomreyn: generally that number should be small.  With the current development release there are quite a few packages updated every day
[16:24] <kenvandine> and the goal is to have a new daily live image everyday, something is holding that back right now
[16:24] <kenvandine> not the norm
[16:24] <kenvandine> tomreyn: no worries, it was worth mentioning :)
[16:25] <tomreyn> we seem to be discussing different things. my point is that i'd expect the installer to check for and install any pending updates, no matter when the installer was generated.
[16:26] <kenvandine> oh...
[16:26] <kenvandine> no it doesn't do that
[16:26] <kenvandine> it downloads them though
[16:26] <kenvandine> so when you first boot up they can be applied if you wish
[16:26] <kenvandine> without needing to download them
[16:26] <tomreyn> that was not the case here
[16:26] <seb128> kenvandine, tomreyn, that's sort of bug #1802337
[16:26] <seb128> the option/description is a bit misleading also
[16:26] <kenvandine> yeah
[16:28] <kenvandine> oSoMoN: looking at your diff it surprised me to see we still have a meson part.  I thought I had removed that now that snapcraft can fetch the latest meson with pip
[16:28] <tomreyn> thanks seb128. maybe that's a dupe of  https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1798992 then
[16:28] <tomreyn> (and thank you as well, kenvandine)
[16:29] <kenvandine> tomreyn: no worries
[16:29] <kenvandine> oSoMoN: in theory you should be able to just remove that part
[17:06] <oSoMoN> kenvandine, I'll try that
[19:28] <seb128> kenvandine, bug #1815941 is interesting, from the screenshot on https://gitlab.gnome.org/GNOME/gnome-software/uploads/ce3b0d852457daa6b03ec06d6015c462/Screenshot_from_2019-01-16_16-09-40.png gnome-software can display sources, would be nice to have that enabled for snaps. What's the best way to have that on the backlog for this cycle? trello board card?
[19:42] <kenvandine> seb128: that is interesting
[19:43] <kenvandine> seb128: i think gnome-software now has a selector on the app page when the same appId is available from multiple sources
[19:43] <kenvandine> or at least there is a recent design for that