[02:52] <handsome_feng> Hi, could someone here handle my request? Thanks! https://answers.launchpad.net/launchpad/+question/670540
[02:55] <tsimonq2> handsome_feng: Hello :)
[02:55] <tsimonq2> handsome_feng: It would probably be better for you to ask in #launchpad.
[02:55] <tsimonq2> iirc wgrant is in Australia, so there's a possibility that he is lurking.
[02:56] <handsome_feng> tsimonq2: Oh, Thank you for your important information!
[02:57] <tsimonq2> handsome_feng: No problem, have a great day :)
[02:58] <handsome_feng> tsimonq2: you too :)
[05:41] <didrocks> good morning
[05:45] <duflu> Morning didrocks
[05:48] <jibel> Good morning
[05:58] <duflu> Hi jibel
[06:35] <ricotz> hey desktopers
[06:48] <duflu> Hi ricotz
[07:20] <seb128> good morning desktopers
[07:21] <jibel> didrocks, hi, I'm reviewing bug 1778697. How do you set apport to never report report errors from g-c-c?
[07:22] <jibel> didrocks, in privacy I've auto or manual
[07:23] <seb128> https://launchpad.net/ubuntu/+source/gnome-control-center/1:3.28.1-0ubuntu1.18.04.2
[07:29] <didrocks> jibel: that should be in the g-c-c sru, you should have a secondary dialog with an option box and checkbox, you don't see this?
[07:29] <didrocks> hey seb128
[07:29] <jibel> didrocks, well, I tried update-notifier alone, there is no mention of it depending on the newer version of g-c-c
[07:30] <jibel> didrocks, also when set to manual with current version of g-c-c I don't get any dialog and the crash is not uploaded automatically
[07:30] <didrocks> jibel: ah, right, I was assuming newer g-c-c would be released in -updates already as I've uploaded it some time ago
[07:30] <didrocks> jibel: well, you know about crash not being uploaded with what we found on Thursday…
[07:30] <didrocks> which will be in newer apport
[07:31] <didrocks> so, unfortunately, we can also check the status right now, as the existing API is lying
[07:31] <seb128> lut didrocks
[07:31] <seb128> 'can't?
[07:32] <seb128> didrocks, g-c-c is 6 days old on the SRU page so I guess it's going to be aged enough only today, also it's not verified yet
[07:33] <didrocks> seb128: no, we can check the status reported by whoopsie API
[07:33] <didrocks> isntead of automatically reporting bugs
[07:34] <didrocks> the status will say that it's set to automatically upload even if it won't do it
[07:34] <didrocks> g-c-c has been uploaded way more than 6 days ago, that's why I didn't track if it was releasde or not in -ugdates
[07:34] <didrocks> updates*
[07:34] <seb128> ah, I see
[07:34] <seb128> delay to have it reviewed/accepted
[07:34] <didrocks> yeah
[07:35] <seb128> also nevermind the +not comment, the syntax construction was looking weird to me "unfortunatly, we can, as the it's lying"
[07:36] <seb128> the unfortatly and lying bits made it sounds like the middle part should be negactive as well
[07:36] <didrocks> yeahn, sorry, I'm doing 2 things at the same time, looking at why apport autopkgtests are failing when passing locally…
[07:36] <jibel> didrocks, there is something weird going on with g-c-c from proposed
[07:36] <didrocks> this whole stack is a PITA :/
[07:36] <seb128> shame that you touched it enough to be the new maintainer :p
[07:36]  * seb128 hides
[07:37] <didrocks> clearly not
[07:37] <didrocks> I would just rewrite the whole 3 things in one if that was the case :p
[07:37] <seb128> haha
[07:37] <jibel> didrocks, set reporting to auto, close the dialog and minimize g-c-c, generate a crash (sh -c 'kill -SEGV $$'), restore g-c-c, reporting is set to never
[07:38] <didrocks> jibel: this isn't related to the crash, but whoopsie give an invalid signal to g-c-c before stopping
[07:38] <didrocks> if you just close g-c-c
[07:38] <didrocks> (without keeping it on that page)
[07:38] <didrocks> restart it
[07:38] <didrocks> it will always reflect the correct value
[07:38] <didrocks> but whoopse-preferences is a activated dbus service
[07:38] <didrocks> which close on idle
[07:38] <didrocks> in a minute
[07:38] <didrocks> and send this invalid signal before shutting down
[07:39] <didrocks> that's next to fix on my list :/
[07:39] <ricotz> hi :), is there some hold up in processing gnome stable updates?
[07:40] <didrocks> jibel: most of users will just tweaks the options, close the window anyway, so, shouldn't be noticeable
[07:42] <seb128> hey ricotz, doesn't look like it, https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=gnome ?
[07:42] <ricotz> I am wondering because vala is still at 0.40.4 (latest 0.40.7), an update is also wanted for bionic, while it is synced from debian I already tried to ask there
[07:42] <seb128> ricotz, do you have a specific one in mind?
[07:42] <didrocks> Ran 29 tests in 81.807s
[07:42] <didrocks> OK
[07:42] <didrocks> :/
[07:43] <didrocks> in a vm…
[07:43] <ricotz> seb128, hi :), "hold up" as in not picking up upstream releases
[07:43] <seb128> ricotz, same old lack of resources/help needed, if you are interested why not contributing that SRU?
[07:45] <ricotz> seb128, I am kind of busy with other things and vala upstream itself, and my membership request for gnome on debian salsa wasn't processed
[07:45] <seb128> ricotz, k, well I guess welcome to the club :)
[07:46] <ricotz> I see, j_bicha was picking them up pretty fast, I guess he is taking some break
[07:46] <seb128> yeah, he has not been around recently
[07:46] <ricotz> ok
[07:46] <seb128> and none of us has the free cycles to work on those updates
[07:46] <seb128> especially the ones which don't have specific reported issues our customers/users are asking to see resolved
[07:47] <ricotz> toolchain updates are kind of important ;)
[07:47] <seb128> vala typically is not really user facing
[07:47] <jibel> didrocks, another issue, I've reporting set to never and got a crash dialog
[07:47] <seb128> yes, they are, as is other work
[07:48] <seb128> ricotz, sorry, I just don't have a good answer for you, we have too much to do and not enough people
[07:48] <ricotz> seb128, ok, I see that
[07:49] <ricotz> will have to try more on the debian side first anyway
[07:49] <ricotz> seb128, thanks
[07:49] <seb128> yw!
[07:50] <didrocks> jibel: with latest update-notifier?
[07:51] <jibel> didrocks, yes
[07:51] <didrocks> ah, that one is more annoying…
[07:51] <didrocks> I've tested is a lot on Friday
[07:51] <didrocks> it*
[07:51] <didrocks> and didn't get into that situation
[07:52] <didrocks> so, when you have g-c-c, set to never report crash, install the new update-notifier, ensure that version is running (logout/login)
[07:52] <didrocks> you still get an UI?
[07:53] <jibel> didrocks, I killed u-n and started it manually
[07:53] <didrocks> :( I did try this more than once before uploading u-n :/
[07:54] <didrocks> the auto use-case is fixed by apport
[07:54] <didrocks> the never use-case is fixed by u-n
[07:55] <jibel> didrocks, I'll approve g-c-c because it's behaving correctly and whoopsie is stopped/started according to the reporting mode.
[07:56] <willcooke> morning
[07:56] <didrocks> jibel: yeah, I guess it's the only piece working currently of the stack :/
[07:56] <didrocks> hey willcooke
[07:56] <jibel> bonjour willcooke
[08:00] <seb128> hey willcooke, how are you?
[08:02] <duflu> Morning willcooke
[08:02] <Laney> morning
[08:02] <duflu> And morning Laney
[08:02] <seb128> hey Laney, how are you?
[08:02] <seb128> had a good trip back? did you recover from the crazy week?
[08:04] <willcooke> seb128, good thanks!  The sun is still shining.  How is your cold?
[08:04] <didrocks> hey Laney
[08:05] <seb128> willcooke, not great, I've been feeling tired whole w.e and the cought has been quite annoying since yesterday and woke me up a bunch of time during the night :/
[08:05] <seb128> but otherwise it's sunny here as well!
[08:12] <Laney> hey duflu seb128 didrocks willcooke
[08:12] <Laney> seb128: delayed by like 2.5 hours but otherwise was alright, managed to make a quick change at st pancras
[08:13] <seb128> italians, always laaaate :)
[08:13] <Laney> back at like 1am, then I got up at 7.45 to go do the parkrun /o\
[08:13] <Laney> heh
[08:13] <Laney> the pilot blamed the londons
[08:13] <Laney> london air traffic controllers*
[08:13] <seb128> lol
[08:17] <Laney> https://nats.aero/blog/2018/06/final-excds-transition/
[08:22] <Laney> LocutusOfBorg: thx for sponsoring gtk - can you make sure that the branches are updated please?
[08:35]  * didrocks understands now the apport autopkgtests failure
[08:35] <didrocks> and why it's passing locally
[08:35] <didrocks> so, basically, I have to really acknoledge this time that you can't disable apport if you don't have whoopsie installed
[08:35] <didrocks> (which was already the case, disabling apport was made by a whoopsie configuration file)
[08:35] <didrocks> (that whoopsie wasn't even creating/reading…) :/
[08:36] <didrocks> and you was setting apport to "never" but whoopsie was still uploading your traces (and automatically)
[08:37] <didrocks> I guess this is ok, let me try then to ack that, people can still disable apport anyway without whoopsie install by uninstalling it
[08:37] <didrocks> seb128: making sense to you? ^
[08:47] <didrocks> seb128: that can be summarized as https://bazaar.launchpad.net/~didrocks/apport/whoopsie-auto-ui/revision/3208 (see commit message as well)
[08:47]  * didrocks tests that in autopkgtests suite now
[08:48] <didrocks> (which doesn't have whoopsie installed, that's why it was passing locally)
[08:48] <seb128> didrocks, reading
[08:49] <seb128> wfm
[08:49] <didrocks> let me confirm that autopkgtests pass with it :)
[08:49] <didrocks> I'll do a followup upload
[08:50] <didrocks> meanwhile j_ibel found the issue in u-n (grrrr crash report spawing after 5 minutes or more… I probably haven't waited enough in the "never" case :/)
[08:51] <Trevinho> morning
[08:51] <didrocks> hey Trevinho
[08:51] <Trevinho> hi didrocks
[08:51] <Trevinho> thanks for the SRU
[08:51] <didrocks> yw ;)
[08:51] <didrocks> thanks for making them
[08:51] <andyrock> morning
[08:52] <didrocks> hey andyrock!
[08:52] <andyrock> seb128: I got a fix for https://gitlab.gnome.org/GNOME/gnome-shell/issues/109
[08:52] <gitlab-bot> GNOME issue 109 in gnome-shell "Extended characters in OSK don't get entered" (comments: 16) [Opened]
[08:52] <andyrock> at least a way to fix it
[08:53] <andyrock> working on a clean MP
[08:55] <didrocks> Ran 29 tests in 12.114s
[08:55] <didrocks> seb128: ok, autopkgtests fixed, mind commenting on https://code.launchpad.net/~didrocks/apport/whoopsie-auto-ui/+merge/348479 as there is an additional commit since you approved?
[08:56] <seb128> andyrock, hey, happy monday! great :)
[08:56] <seb128> hey Trevinho, how are you?
[08:57] <Trevinho> hi seb128 all good, sun sprint is continuing for two days more here :)
[08:57] <seb128> didrocks, done
[08:57] <Trevinho> seb128: you?
[08:57] <didrocks> seb128: thanks!
[08:57] <seb128> Trevinho, I'm ok, got a cold after coming back which is has been kicking my ass a bit :l/
[08:57] <Trevinho> damn...
[08:57] <Trevinho> I've also a cold :-(
[08:58] <Trevinho> now it's 30ish
[08:58] <seb128> blocked nosed at first and it turned into caughing this w.e which made my night a bit difficult
[08:58] <didrocks> get better before you come to GUADEC! :)
[08:58] <seb128> should be fine by then
[08:58] <didrocks> 38°C yesterday here :(
[08:59] <Trevinho> yesterday pool was a must :)
[08:59] <seb128> hehe
[09:01] <didrocks> apport 2.20.10-0ubuntu5 uploaded
[09:02] <seb128> \o/
[09:02] <didrocks> hoping that one will pass proposed, once there, we can envision SRUing
[09:05] <didrocks> j_ibel confirms the u-n scheduler is weird, sometimes you get a crash and nothing happens even after 8 minutes…
[09:05] <didrocks> so I guess that's why my tests were skewed, he found the issue (no absolute path to call systemctl)
[09:06] <didrocks> I don't think it's worth fixing update-notifier scheduler (which seems stuck in some cases) as we'll move in cosmic to systemd user session hopefully?
[09:06] <seb128> I'm not sure to understand what bit is buggy and why
[09:06] <seb128> no absolute path means it fails to find the command?
[09:06] <seb128> then it shouldn't work at all?
[09:07] <didrocks> right, but it's a call to systemctl
[09:07] <didrocks> to check if the service is up or not
[09:08] <seb128> that sounds like worth fixing in the LTS, it's a nicer experience if you get the report dialog without delay
[09:08] <didrocks> hum
[09:08] <didrocks> no, we didn't find a fix for that
[09:08] <seb128> that doesn't need to be you fixing it though
[09:08] <seb128> just report it and give me the bug number
[09:08] <didrocks> just so that "never" really works (fixing the previous patch)
[09:08] <didrocks> ok
[09:08] <seb128> thx
[09:08] <didrocks> by default, there is a 3 minutes delay
[09:08] <didrocks> (from the start)
[09:08] <didrocks> I guess to accumulate the "crashes" dialog if multiple happens
[09:08] <seb128> that's to not load the system on login?
[09:09] <didrocks> maybe… but it's still the case way even after the first 3 minutes
[09:09] <didrocks> basically, the whole concept of "show the crash dialog" immediately to explain why something doesn't work was never behaving like that :p
[09:10] <seb128> that stack could really do with a good review/bug fixing round
[09:10] <didrocks> clearly
[09:10] <didrocks> too many projects interleaving
[09:10] <seb128> I'm going to have a look to those 3 minutes thing
[09:10] <didrocks> update-notifier/apport/whoopsie/whoopsie-preferences
[09:10] <seb128> that must have been done for a reason
[09:10] <didrocks> seb128: changing the timer will be easy, the issue is that sometimes, it's stuck and miss the window
[09:10] <didrocks> and you have to create a new inotify in /var/crash to "unstuck" it
[09:11] <seb128> let's get that reported and the foundations list
[09:11] <didrocks> (which was why I thought my patch was working)
[09:11] <didrocks> yes
[09:12] <jibel> didrocks, i'll file the bug
[09:12] <didrocks> thanks jibel!
[09:12]  * didrocks uploads u-n fix in cosmic and bionic
[09:14] <duflu> Trevinho, thinking about patching mutter!117 ?
[09:40] <LocutusOfBorg> Laney, I already asked @tsimonq2 to do it :)
[09:56] <Laney> LocutusOfBorg: if he could have pushed then he could probably have uploaded no?
[09:56] <Laney> or you didn't work from a branch to sponsor it for some reason?
[10:00] <LocutusOfBorg> not sure if he has access, let me push them
[10:03] <Laney> ta
[10:04] <duflu> Ugh, multiple branch dependencies in a system that can't handle single branch dependencies
[10:05]  * duflu gives up and goes to dinner
[10:06] <LocutusOfBorg> done! @tsimonq2 please comment if you have write access
[10:06] <Laney> LocutusOfBorg: ~ubuntu-desktop is an uploading team
[10:32] <LocutusOfBorg> so Laney he can't unless somebody PPU it for him
[10:35] <Laney> more or less
[11:25] <willcooke> Should this bug be fixe released for Bionic now?  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261
[11:27] <Laney> in proposed
[11:29] <Laney> (which is Fix Committed in SRU speak)
[12:29] <willcooke> Laney, ah thanks
[14:06] <Trevinho> LocutusOfBorg: you should push the bzr tags on the lp: branches for gtk
[14:21] <LocutusOfBorg> Trevinho, ack!
[14:22] <Trevinho> LocutusOfBorg: good, I've fixed them while creating the git branches, but better to fix bzr too
[14:23] <LocutusOfBorg> I think I did it
[14:23] <LocutusOfBorg> please let me know if I made any mistake
[14:23] <LocutusOfBorg> (I ran bzr tag and push)
[14:26] <Laney> going to move Trevinho's branches from https://code.launchpad.net/~canonical-desktop-team/+git to ~ubuntu-desktop, then we can start using them
[14:26] <Laney> unless anybody wants to tell me not to
[14:26] <Laney> didrocks: ^^^^^^^^^^^^^^
[14:27] <Trevinho> once done that, lp branches should probably be edited to remove the whole content addoing a file that says where code is now?
[14:27] <Laney> yep
[14:28] <Laney> sounds like hard work though ._.
[14:28] <Trevinho> I can script that if you want, then you push it
[14:28] <Trevinho> no... few lines, you know :)
[14:29] <Laney> this guy loves shell scripting
[14:29] <didrocks> Laney: please go ahead :)
[14:29] <Laney> will do
[14:29] <Laney> thx!
[14:29] <didrocks> Laney: wait, I can push it
[14:29] <Laney> this is a lot of clicking though, I should write an API script for that
[14:29] <didrocks> Laney: I have some "finalise changelog" commit
[14:30] <Laney> you can change the owner
[14:30] <Laney> e.g. on https://code.launchpad.net/~canonical-desktop-team/ubuntu/+source/gnome-calculator/+git/gnome-calculator/+editV
[14:30] <Laney> https://code.launchpad.net/~canonical-desktop-team/ubuntu/+source/gnome-calculator/+git/gnome-calculator/+edit
[14:30]  * Laney was going to do that
[14:30] <didrocks> Laney: ah, I let you do that, I change the remote meanwhile to push latest commits
[14:30] <Laney> ok
[14:30] <didrocks> sounds like there are branches where we already have history though there
[14:31] <Trevinho> ah, also I've to change them to point to ubuntu/master
[14:31] <Trevinho> didrocks: yeah, some like gdm3 needs to be merged with current ones
[14:31] <Trevinho> so don't move the ones we 've already
[14:31] <Trevinho> ye
[14:31] <Trevinho> t*
[14:31] <Laney> ye those are for merging
[14:32] <didrocks> Laney: so, for g-s, I've already pushed it a long time ago, that one doesn't need to be move thus
[14:33] <didrocks> even if I'm surprised it's been reprocessed with new commits an hour ago by Trevinho, reimporting
[14:33] <Trevinho> didrocks: it's just an automated script doing that
[14:33] <didrocks> Trevinho: please exclude the ones we already migrated :p
[14:33] <Laney> shell? session? screensaver? software?
[14:33] <didrocks> Laney: Shell
[14:34] <Laney> thx
[14:34] <Trevinho> was this btw https://pastebin.ubuntu.com/p/KRxTXHVsdf/
[14:34] <didrocks> I hope somebody is checking the result makes sense before moving the ownership
[14:34] <Trevinho> didrocks: and I'm not excluding per se, since for these I'll just merge them with current, so we'll preserve history and that's it.
[14:34] <Laney> not individually no
[14:34] <didrocks> Trevinho: remerge gnome shell? why?
[14:35] <Trevinho> didrocks: gnome-shell no
[14:35] <didrocks> ok
[14:35] <Trevinho> didrocks: it was just a for which caused it to be pushed again :)
[14:35] <didrocks> Laney: ok, you will be responsible if weird debian/control* :p
[14:37] <Laney> :/
[15:03] <Laney> Trevinho: done, ones left need merging
[15:04] <Laney> it would be good if we could get ~ubuntu-desktop emails working
[15:04] <Laney> so people see MPs coming in
[15:05] <Laney> they probably get eaten by the mailing list now?
[15:08] <seb128> they do in the moderation queue
[15:08] <seb128> do->go
[15:08] <seb128> I'm  unsure if we want to "spam" the list with them
[15:08] <Laney> well if the list is dead we could use it now for code review stuff
[15:08] <seb128> though that now the list has been superseeded by the hub for real human discussions we could
[15:09] <Laney> I always feel a bit 🙈 when someone pings about a thing and it was proposed to ~ubuntu-desktop some time before
[15:10] <Laney> so doing that gets my vote
[15:11] <Laney> If you can whitelist by header, "X-Launchpad-Notification-Type: code-review" would be a good one
[15:12] <Laney> so we don't get bug spam since people sometimes subscribe the team to bugs
[15:13] <seb128> right let me see
[15:16] <Laney> 🙌
[15:16] <Laney> which is called "Person Raising Both Hands in Celebration"
[15:16] <Laney> GNOME is teaching me Semantic Emoji
[15:20] <seb128> haha
[15:31] <ricotz> seb128, would you be available to upload a vala package?
[15:31] <ricotz> what is the preferred version suffix for syncs from debian git?
[15:44] <ricotz> http://people.ubuntu.com/~ricotz/ubuntu/
[15:45] <ricotz> based on https://salsa.debian.org/gnome-team/vala
[16:08] <xnox> Laney, willcooke, seb128 - https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1779569
[16:08] <xnox> input appreciated as to, where/how is this to fix. I fear there is "browser engines" in the way
[16:08] <xnox> works fine in gnome-terminal, gedit, hexchat, etc.
[16:13] <Laney> It sounds like a duplicate of the listed bug, which is supposedly fixed in thunderbird 60 (not out yet afaics).
[16:42] <Laney> snapd.service just blocked startup on a VM for 3min 1.756s
[17:16] <willcooke> night all
[17:57] <seb128> Laney, sounds like something worth reporting to the snapd team, what other services were blocked?
[19:11] <tsimonq2> Laney, LocutusOfBorg: Thanks.
[19:32] <Laney> seb128: GDM didn't come up until it finally came alive
[19:32] <Laney> will do