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