[06:00] <jibel> duflu, hi
[06:00] <duflu> Hello hikiko
[06:00] <duflu> Hello jibel :)
[06:00] <duflu> Autocomplete fail
[06:00] <jibel> duflu, I frequently get bug 1748450 when I resume from suspend
[06:00] <ubot5`> bug 1748450 in gnome-shell (Ubuntu Bionic) "gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from <bug 1505409>" [High,Triaged] https://launchpad.net/bugs/1748450
[06:01] <jibel> duflu, is there anything I can do to debug it further?
[06:01] <duflu> jibel, I put a status update in the master bug https://bugs.launchpad.net/bugs/1505409
[06:01] <ubot5`> Ubuntu bug 1505409 in GNOME Shell "gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]" [Critical,Confirmed]
[06:03] <jibel> I saw your comment. is there anything I can do to help?
[06:04] <duflu> jibel, not sure. My mind is on the gjs major leak and crashes today
[06:05] <duflu> jibel, maybe... can we ensure crash reports get the _old_ Xorg log from when they happened rather when they were reported? That would help, but might be hard
[06:08] <duflu> jibel, if the problem is Xwayland bouncing itself on an "X error" then gnome-shell will crash and Xwayland would live on. If we could turn X errors into crashes for Xwayland, and not try to recover from them, then I think that would help
[06:09] <duflu> Then we'll actually get useful crash reports about the root cause, somewhere in Xwayland
[06:32] <oSoMoN> good morning desktoppers
[06:36] <Nafallo> morning o/
[06:37] <didrocks> good morning
[06:42] <oSoMoN> hey Nafallo, salut didrocks
[06:45] <duflu> Morning oSoMoN, Nafallo, didrocks
[06:45] <oSoMoN> hey duflu
[06:50] <didrocks> salut oSoMoN, duflu
[07:54] <willcooke> morning
[07:55] <didrocks> hey willcooke!
[08:03] <Laney> URGH I'M SICK
[08:03] <Laney> HI
[08:03] <didrocks> :( Laney
[08:04] <didrocks> stayed at home this week-end?
[08:05] <Laney> hey didrocks
[08:05] <Laney> nah, did lots of stuff!
[08:05] <Laney> including the 5k run ;-)
[08:06] <duflu> Morning willcooke and Laney
[08:07] <duflu> willcooke, here's the main (unchanged, mature) leak fix: https://bugs.launchpad.net/gnome-shell/+bug/1672297 But upstream are apparently working on additional fixes, even over the weekend. None of them have landed though.
[08:07] <ubot5`> Ubuntu bug 1672297 in gjs (Ubuntu Bionic) "gnome-shell uses lots of memory, and grows over time" [Critical,In progress]
[08:07] <didrocks> Laney: nice ;) but urgh being sick now
[08:12] <Laney> indeed
[08:12] <Laney> anyway how are you?
[08:12] <Laney> and hey duflu
[08:14] <willcooke> thx duflu
[08:14] <willcooke> bad luck Laney
[08:14] <willcooke> I painted the bathroom.  I ache all over now
[08:19] <didrocks> Laney: I plan to restart doing some exercise today :)
[08:24] <seb128> duflu, hey, I read your concerns about the gjs update, can you made a summary of the problems?
[08:25] <duflu> seb128, it's all fine now I understand the bugs. They have fixes coming and no revert is required
[08:25] <seb128> duflu, great, thx
[08:26] <duflu> I was just stressed and annoyed I have to squash 200+ bug emails in the morning
[08:26] <duflu> But they're fully triaged now
[08:26] <duflu> I *had*
[08:26] <seb128> urg, that seems a lot
[08:27] <duflu> Yeah I guess someone wrote news about a final beta :)
[08:27] <seb128> how did we end up with that number? we don't get quite that many reports on other days
[08:27] <seb128> haha
[08:27] <seb128> I'm just through emails, I didn't do launchpad backlog yet
[08:27] <duflu> seb128, that number is hidden in (bugs_opened - bugs_closed)... I only report the final number each week, which is tiny
[08:28] <duflu> Also I can't report the opened/closed numbers without trawling my emails
[08:28] <seb128> well I do go through 'most recently changed bugs in main" daily
[08:28] <seb128> so I've an idea about how many bugs are "active" on a daily basis
[08:29] <seb128> that number just seemed high compared to the activity we had previous week
[08:29] <seb128> btw did you figure out the "can't be retraced" issue?
[08:29] <seb128> is/was that just dbgsym missing or lagging behind?
[08:29] <duflu> seb128, yes the hint was in errors.ubuntu.com which told me the name of the missing binary
[08:29] <duflu> It was just a glib2.0 upgrade
[08:30] <duflu> Once everyone upgrades they will be retraceable again
[08:30] <nhaines> Hi everyone!  I was asked to ping someone in here about updating the example-content package for bionic.  A merge request is here: https://code.launchpad.net/~nhaines/example-content/bionic-fcs/+merge/343295
[08:30] <duflu> seb128, interesting that ubuntu-bug reports don't tell you the binary name, only "??"
[08:30] <seb128> hey nhaines
[08:30] <nhaines> seb128: hey  :)
[08:30] <seb128> duflu, you mean? do you have an example?
[08:31] <seb128> willcooke, ^ interested in the example-content update, seems like your sort of job? ;)
[08:31]  * willcooke reads
[08:32] <willcooke> ack, I can review, but I can't merge
[08:32] <willcooke> I usually bribe L_aney
[08:32] <duflu> seb128, for example, bug 1764173, bug 1764059, bug 1764050
[08:32] <ubot5`> Error: Launchpad bug 1764173 could not be found
[08:32] <ubot5`> Error: Launchpad bug 1764059 could not be found
[08:32] <ubot5`> Error: Launchpad bug 1764050 could not be found
[08:32] <willcooke> ooh, nice one mardy
[08:32] <duflu> (private)
[08:33] <didrocks> briber!
[08:34] <seb128> duflu, ah, apport is just using gdb afaik, so probably at this level. At least we have the procmaps and the addresses can be matched
[08:34] <seb128> but yeah, procmaps in the first one is
[08:34] <seb128> 7f012e0bb000-7f012e1ce000 r-xp 00000000 08:01 15335474                   /lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.0 (deleted)
[08:34] <duflu> seb128, yeah it's all fine
[08:34] <seb128> so basically the process was using old glib, glib got updated, lib removed from disk
[08:34] <seb128> so the dump is pointing to a missing lib
[08:34] <seb128> right
[08:36] <duflu> That kind of problem with ?? probably happens all the time. It's only an emergency when it happens with duplicates of a massively-duplicated crash
[08:39] <seb128> yeah, it's often during unstable cycles when components are moving often
[08:39] <seb128> ideally apport/retracers would be able to fetch the dbgsym corresponding to the version in use and not to the current one
[08:43] <willcooke> didrocks, looks like you are in the right team for the FCS merge.  I've checked the content and it's fine, and the licence looks correct, but I can't merge it, can you?
[08:44] <willcooke> didrocks should change his nick to z_didrocks
[08:44] <willcooke> :)
[08:47]  * didrocks would even love zzzzz_didrocks :)
[08:47]  * didrocks does
[08:51] <didrocks> willcooke: I guess you want an upload in addition to the merge?
[08:53] <duflu> seb128, would you be able to help sponsor this patch? https://launchpad.net/bugs/1672297
[08:53] <ubot5`> Ubuntu bug 1672297 in gjs (Ubuntu Bionic) "gnome-shell uses lots of memory, and grows over time" [Critical,In progress]
[08:55] <seb128> duflu, I can have a look, do you know what's blocking them to land in upstream master? is there any disagreement on the solution?
[08:55] <duflu> seb128, no disagreement, just apathy. The fix I picked is dated March
[08:56] <duflu> and hasn't needed changing since
[08:59] <seb128> k, we should at least get Trevinho to review/ack that
[08:59] <seb128> Trevinho, ^ what do you think about including the changes in https://launchpadlibrarian.net/365705963/gjs_1.52.1-1ubuntu1.debdiff ?
[08:59] <seb128> jbicha, darkxst, ^ would you be interested in having that in debian/sync over?
[08:59] <duflu> Wrong timezone? :)
[09:02] <willcooke> didrocks, yes please
[09:04] <didrocks> willcooke: and done!
[09:04] <willcooke> thank you didrocks!  (cc nhaines)
[09:04] <seb128> duflu, backlog for later!
[09:04] <nhaines> seb128, willcooke, didrocks: thanks!  :D
[09:06] <didrocks> yw ;)
[09:36] <seb128> oSoMoN, chromium osk & vaapi, is any of those likely for 18.04 at this point? or rather .1/SRU now?
[09:36] <seb128> oSoMoN, I'm asking because I'm moving items to a new ".1" column on the trello board
[09:37] <seb128> andyrock, hey, can you proposed package updates for the gnome-calendar & gtk segfault fixes you made recently?
[09:45] <oSoMoN> seb128, I need to add latest developments on the card, not happening for 18.04 indeed
[09:46] <seb128> oSoMoN, I move them to .1 then,t hx
[09:46] <oSoMoN> cheers
[09:57] <darkxst> seb128, maybe, but probably not in time for final freeze, they still seem rather experimental and haven't had an upstream review
[09:57] <darkxst> what are the performance effects of spamming the GC?
[09:57] <seb128> duflu, ^
[09:58] <duflu> darkxst, over the past few weeks no performance hit has been noticed
[09:58] <seb128> duflu, darkxst, we should at least get the cairo issue/revert in and sycned, I tend to agree that the other changes are more SRU material at this point where they have time to be properly tested
[09:59] <duflu> seb128, the main leak fix is not SRU material, it's much more important than the cairo fix
[10:01] <duflu> willcooke, seb128, if you guys ^ want to wait for upstream before committing to any leak fixes then your decision. I was doing it because both willcooke and community members asked for it
[10:01] <duflu> It's certainly a bigger deal than that cairo crash
[10:02] <seb128> duflu, I don't think wes hould wait for upstream, but I also think such changes can have side effect and a week before release is late to land them
[10:02] <seb128> it gives little margin to gauge the impact and decide to revert if needed
[10:06] <duflu> seb128, I would agree but CPU concerns are moot if your system is slowing down and crashing from memory exhaustion. So fixing that is more important than performance concerns (which are presently zero).
[10:07] <duflu> seb128, also I only chose the one leak fix that is several weeks mature. I ignored the others
[10:08] <darkxst> seb128, duflu I am fine with cairo patch
[10:08] <duflu> darkxst, that's lower priority. Please forget it for now
[10:08] <seb128> duflu, right, it's just going against the rules of lowering the complexicity of changes as we get closed from release
[10:08] <seb128> duflu, it's lower priority but it's easier to review/approve
[10:09] <darkxst> duflu I have not seen any major leaks here, under "normal use"
[10:09] <darkxst> yes gnome-shell is using a but more memory
[10:09] <duflu> darkxst, seriously. Please read the bug and OMG too.
[10:09] <seb128> the reports make it clear there are users that see leak issues
[10:09] <duflu> I can leak 1MB per second
[10:09] <seb128> it's difficult to estimate how many users are impacted though
[10:09] <seb128> it depends how you use the shell also
[10:10] <duflu> seb128, all users
[10:10] <darkxst> duflu, under normal use? or spamming functions that are knowm to build up in GC?
[10:10] <duflu> seb128, you can measure the impact within 2 seconds of login
[10:10] <seb128> by doing specific steps
[10:10] <duflu> By measuring memory usage, and doing nothing. It's huge
[10:11] <seb128> I'm not denying that
[10:11] <seb128> but I never had to close a session due to those leak eithers
[10:11] <seb128> (I do turn my computer off at night though, so I don't have sessions ongoing for days)
[10:11] <seb128> I'm just trying to ponderate the impact
[10:11] <seb128> yes it's an issue
[10:11] <seb128> yes it bites lot of users
[10:11] <duflu> seb128, don't shoot the messenger. If you're going to argue about the issue then please do so with the users who are passionate about the bug report.
[10:12] <darkxst> is gjs not running GJS under memory pressure?
[10:12] <seb128> but it's not a stopper for every single user
[10:12] <darkxst> s/GJS/GC/
[10:12] <duflu> darkxst, GJS isn't EVER running GC for many classes of object. EVER
[10:12] <seb128> duflu, I'm not arguing against the issue or shooting the messenger, I just think you overstate the proper by making it sounds like it makes GNOME unusable for everyone
[10:13] <duflu> seb128, please tell the users that. In the bug
[10:13] <duflu> seb128, please also tell OMGubuntu who continue to write about it
[10:13] <seb128> shrug
[10:13] <duflu> I didn't ask to own this bug
[10:13] <seb128> I'm not denying it's an important issue
[10:15] <duflu> In the mornings I get abused by users for not having fixed it and in the evening I get questioned for trying to fix it.
[10:15] <duflu> I'm going to EOD in a sec
[10:15] <darkxst> duflu, it may not trigger GC for certain objects but they would get cleaned up next time it runs
[10:15] <duflu> darkxst, no they don't. EVER
[10:15] <duflu> That's the bug
[10:16] <duflu> GJS simply doesn't work for GObject even when the JS and GObject is perfect
[10:17] <duflu> I know. I found it hard to believe but it explains everything, and the fix provides a noticeable impact as soon as you log in
[10:18] <seb128> duflu, don't take it that personal, I was not questioning your work or position
[10:18] <duflu> seb128, also willcooke specifically asked me to get it done this week
[10:18] <seb128> duflu, I'm just saying that by release/freeze rules it's difficult to get a "non trivial" change like that approved that late
[10:18] <seb128> we need confidence it can't create new problems
[10:18] <duflu> I know. I was waiting and hoping upstream would land something by now
[10:19] <darkxst> and the fix is hacky at best, lets spam GC so gobjects get deleted on at a time? anyway I do have time to look through the patches tonight, but will try and do a proper review tomorrow. I would however be hesistant to upload those changes days before final freeze, even too ubuntu.
[10:19] <seb128> I asked Trevinho to follow up on some of his similar fixes weeks ago that didn't happen either
[10:19] <seb128> we are stucked in a non optimal situation now
[10:19] <seb128> it's getting late but at the same time we need to do something :/
[10:19] <duflu> darkxst, OK. Please direct reviews here: https://gitlab.gnome.org/GNOME/gjs/merge_requests/114
[10:19] <ubot5-ng> GNOME bug (Merge request) 114 in gjs "Queue a GC when a toggle reference goes from >1 to 1" (comments: 15) [Opened]
[10:20] <seb128> duflu, thanks for the work you put into those fixes and sorry if it sounded like I was questioning what you did, I was not
[10:20] <seb128> duflu, I hope you are still able to enjoy your evening after that discussion :/
[10:21] <duflu> seb128, yeah I reduced my VAAPI fix to a one liner. Now uploading
[10:21] <darkxst> duflu, I am not an upstream maintainer, but have done a lot of work on gjs over the years
[10:22] <duflu> darkxst, still that's the place to add any thoughts
[10:24] <duflu> seb128, willcooke specifically requested that leak fix. So I suggest you just decide with him
[10:24] <seb128> duflu, I'm going to talk to him, but I'm not deciding anything here
[10:25] <seb128> duflu, I'm not in the release team and it's not in my power to decide if that can go in
[10:25] <seb128> duflu, I'm just used to work with them and I know it's going to require to be convincing to upload a behaviour change to the gc that late
[10:25] <seb128> so I'm trying to see what we can do and have the arguments we need ready for that discussion
[10:26] <seb128> duflu, anyway you did your side of the work so don't worry too much
[10:45] <willcooke> didrocks, jamiebennett tested the data collection this morning and his monitor which is connected via usb c wasn't picked up.
[10:48]  * Laney cries at the remaining volume_key failure
[11:10] <Laney> helps if you spell DEB_BUILD_OPTIONS right
[11:15] <jbicha> seb128: fyi, I have mutter and gnome-shell 3.28.1 tarballs, waiting for Tre_vinho to gather the extra patches for them he wants later today
[11:15] <jbicha> good morning
[11:20] <seb128> jbicha, hey, nice
[11:37] <k_alam> jbicha: [ftbfs] https://code.launchpad.net/~khurshid-alam/indicator-sound/lp-1737834/+merge/343023
[11:38] <k_alam> and this: https://code.launchpad.net/~khurshid-alam/indicator-sound/lp-1700680/+merge/343022
[11:40] <jbicha> k_alam: please subscribe ubuntu-sponsors to bugs with stuff that needs sponsoring
[11:43] <jbicha> your 1700680 merge has an obvious typo (the package is named -schemas instead of -schema). I haven't investigated but I suspect that fix is wrong anyway
[11:43] <jbicha> Ubuntu Touch hasn't been supported in Ubuntu for a year so I suggest looking whether that support can be dropped from indicator-sound instead
[11:44] <jbicha> anyway, you already pinged Tre_vinho about indicator-sound so I'll let him take care of the reviews there
[11:47] <k_alam> jbicha: Ah right...I will rectify it.....But that package provide com.ubuntu.AccountsService.Sound interface along with various com.ubuntu.touch interfaces. Touch related things can be dropped.
[11:51] <jbicha> please investigate what com.ubuntu.AcccountsService.Sound does and if it's still needed
[11:53] <jbicha> k_alam: for bug 1741027 Please add FFe explanation so that the Release Team can review. See https://wiki.ubuntu.com/FreezeExceptionProcess
[11:53] <ubot5`> bug 1741027 in unity-control-center (Ubuntu) "[FFE] screen sharing panels abort using an unexistant vino gsettings key" [High,Confirmed] https://launchpad.net/bugs/1741027
[12:00] <ricotz> hey desktopers
[12:00] <k_alam> jbicha: alright.
[12:04] <ricotz> jbicha, hi, I noticed a problem with vte2.91 in ubuntu, the revert-pcre2.patch reverts some unrelated g-i annotation changes and therefore breaking the gir/vapi compared to upstream in unnecessary ways
[12:06] <jbicha> ricotz: could you talk to Egmont about that? he is part of vte upstream and he did the latest pcre patch update
[12:07] <ricotz> jbicha, could you point me to an irc channel?
[12:07] <didrocks> willcooke: was he running on wayland by any chance?
[12:07] <didrocks> willcooke: remember that we only supports Xorg for getting monitor info
[12:09] <jbicha> ricotz: I've always just used email or bug reports with Egmont
[12:09] <ricotz> jbicha, I see
[12:10] <Laney> Status: successful
[12:10] <Laney> YEAH
[12:11] <jbicha> 🎉
[12:11] <Laney> tests needed a writable home 🙄
[12:12] <Laney> /root existed which is why it worked when I ran as root
[12:14] <jbicha> ok, we have a few other packages like that
[12:15] <jbicha> Laney: oh I did that actually but the tests still didn't pass when I tried https://salsa.debian.org/utopia-team/volume-key/commit/42207b3dbc
[12:16] <jbicha> I guess you had some other fixes too though?
[12:17] <Laney> yes
[12:17] <Laney> I fixed the actual bug first
[12:17] <jbicha> :)
[12:17] <Laney> you know about debian/clean?
[12:17] <Wimpress> oSoMoN: Which source repo is the Chromium snapcraft.yaml in?
[12:18] <jbicha> Laney: yes, for some reason we don't use it as often
[12:18] <Laney> royal we?
[12:19] <Laney> I mean, that's a weird sentence construction when talking about one of your own commits
[12:19] <jbicha> I copied that home thing from other GNOME packages
[12:19] <jbicha> I guess debian/clean is uh … cleaner
[12:20] <Laney> you could save an override
[12:21] <Laney> now I get to fight with pagure
[12:23] <jbicha> you have upload rights to that salsa repo so feel free to make the clean change there :)
[12:24] <ricotz> jbicha, https://launchpad.net/~ricotz/+archive/ubuntu/staging/+sourcepub/8991295/+listing-archive-extra
[12:24] <Laney> laney@bionic (master↑1|…)> git push ssh://git@pagure.io/forks/laney/volume_key.git                                                                                                                ~/dev/canonical/random/volume_key
[12:24] <Laney> git@pagure.io: Permission denied (publickey).
[12:24] <Laney> this thing :|
[12:25] <Laney> oh it has a separate SSH key configuration to the thing that I filled in when I made the account
[12:27] <jbicha> ricotz: ok, yes, please ask Egmont about vte since he was the one that did that part recently
[12:27] <ricotz> will do
[12:56] <Laney> jibel: yo, would you be able to test https://launchpad.net/~laney/+archive/ubuntu/ppa/+build/14767038 with your encrypted usb key pls?
[12:56] <Laney> amazingly I don't seem to have a usb key :/
[12:57] <Laney> so the patch I made to fix the tests is not tested in actual use
[13:18] <didrocks> first communitheme interview posted! Just as 5 of them… like, a week then ;)
[13:31] <willcooke> didrocks, yay
[13:34] <didrocks> willcooke: so "known", didn't get the time to inspect what to do yet on the wayland session
[13:35] <jibel> Laney, what do you want me to test exactly?
[13:37] <willcooke> didrocks, ack thanks
[13:38] <jibel> Laney, just install the package and check if I can still access my encrypted drive?
[13:38] <seb128> jbicha, I don't think we really replied to that the other time, but are we sure a ffe is not needed to remove packages?
[13:39] <jbicha> seb128: you're the Archive Admin, you tell me :) It is very common for AAs to remove packages at the very last moment
[13:40] <jbicha> I emailed ubuntu-devel because I expect this particular one to be a bit annoying for some people (I haven't gotten much hate mail yet from Debian though)
[13:43] <jbicha> gksu was already unseeded at Feature Freeze until a ffe managed to (accidentally) get it back in the Kylin install
[13:44] <seb128> sysadmins or such might still use it
[13:44] <seb128> I don't like to remove thing just before release like that
[13:44] <seb128> you might screw people
[13:44] <seb128> removals should be done early in the cycle/by ff imho
[13:45] <seb128> not that I care especially about gksu
[13:45] <seb128> just I don't like the idea to do changes without letting some time for users to give feedback/adjust to the change
[13:45] <jbicha> seb128: I don't disagree with you about the ideal of doing removals by say, FF. That just isn't the way AAs do their job
[13:45] <jbicha> they want until the end of the cycle to get around to processing removal bugs that were filed months sooner
[13:45] <seb128> well some packages are buggy and need to be removed for valid reasons
[13:45] <jbicha> *wait*
[13:45] <seb128> your seem to be more "want to kill cruft"'
[13:48] <seb128> andyrock, hey, I see you reply to emails ... did you see my IRC ping earlier?
[14:15] <andyrock> seb128: nope
[14:15] <andyrock> looking for it
[14:15] <andyrock> seb128: kk I'll try to do that by the end of today
[14:15] <andyrock> debdiff right?
[14:16] <seb128> andyrock, yes, thx
[14:22] <Laney> jibel: yeah
[14:22] <seb128> tjaalton, hey, could you have a look at / upstream https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1754693 ?
[14:22] <ubot5`> Ubuntu bug 1754693 in xorg-server (Ubuntu) "Xwayland crashed with SIGABRT in st_renderbuffer_delete()" [High,Confirmed]
[14:23] <ricotz> is there a schedule for the bionic point releases already? I am curious about the date for 18.04.1
[14:27] <seb128> ricotz, that's a question for -release more than desktop, https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule doesn't have it so I expect it's not decided yet
[14:28] <seb128> ricotz, it's probably somewhere in July
[14:28] <seb128> willcooke, Laney might know?
[14:28] <Laney> umm
[14:28] <ricotz> seb128, thanks, judging from the past it might be July 19th
[14:35] <didrocks> if you have access to some hardware with nvidia, I would be interested into you running xrand on your machine (wich some connected monitors) and print the output
[14:35] <didrocks> jibel: maybe? ^
[14:38] <jibel> didrocks, intel or amd here
[14:39] <didrocks> ok, thanks :)
[14:43] <Laney> didrocks: https://paste.ubuntu.com/p/xQr7tN4DKQ/
[14:43] <didrocks> Laney: thanks! That's what I expected :)
[14:48] <seb128> didrocks, is it different from intel machines?
[14:48] <seb128> jibel, did you look at the keyboard selection bug in ubiquity yet?
[14:49] <didrocks> seb128: it's not, but for the selected element, there are multiple frequencies support (where I have a duplicated line here), so my regexp needs more work
[14:49] <seb128> ah ok
[14:49] <didrocks> I was a little bit restrictive, let me ensure it's better supported + tested
[14:49] <seb128> is that the usb-c monitor not listed issue?
[14:49] <didrocks> yeah
[14:49] <seb128> great
[14:49] <seb128> thx
[14:50] <didrocks> Laney: do you have any tool to select the freq? like, can you get 1920x1080@50hz?
[14:50] <Laney> uh
[14:50] <didrocks> (for DVI-I)
[14:51] <Laney> don't know
[14:51] <Laney> I just use g-c-c
[14:51] <Laney> some nvidia tool exists doesn't it?
[14:51] <didrocks> I think the syntax would be: 1920x1080     60.00  59.94    50.00*+    60.05    60.00    50.04
[14:51] <didrocks> but unsure
[14:51] <didrocks> yeah, nvidia-config or such?
[14:51] <didrocks> or nvidia-settings
[14:52] <Laney> dunno
[14:52] <Laney> I'm not on that computer, it is remote to me
[14:52] <Laney> so can't check
[14:52] <Laney> ts_eliot could probably help you
[14:53] <didrocks> hum, good idea, tseliot: do you know in case you have multiple freqs available for a given resolution what is the xrandr syntax if you don't select the first one?
[14:53] <didrocks> like instead of    1920x1080     60.00*+  59.94    50.00    60.05    60.00    50.04
[14:53] <didrocks> what is the output if I select 1920x1080@50.00
[14:54] <didrocks> I don't see anything in g-c-c to select the freq…
[14:57] <Laney> I don't think I've ever done that
[14:57]  * didrocks tried some naïve xrandr command and needed to reset it via g-c-c :p
[14:57] <didrocks> me neither ;)
[14:58] <didrocks> I would like to avoid betting on a syntax
[15:02] <tseliot> didrocks: the rate followed by "+" is the preferred one. I think that's the one that is applied if you don't specify it
[15:03] <didrocks> ah, I get it!
[15:03] <didrocks> was able to reproduce it :)
[15:03] <didrocks> so, you can have:
[15:03] <didrocks>    1366x768      60.02 +
[15:03] <didrocks> but selected is:
[15:03] <didrocks>    1280x720      60.00    59.99    59.86*   59.74
[15:03]  * didrocks reverts, it's too blurry to cope with it :)
[15:03] <didrocks> I have what I needed, thanks tseliot
[15:03] <Laney> this sounds unfun
[15:04] <Laney> no good API to get this stuff?
[15:04] <didrocks> Laney: note that I found
[15:04] <didrocks> not*
[15:04] <tseliot> didrocks: np
[15:04] <Laney> :(
[15:04] <Laney> what does g-c-c do?
[15:04] <didrocks> Laney: oh, btw, g-c-c enable you to select the rate if you onlly have one monitor
[15:05] <didrocks> just noticed that
[15:05] <didrocks> well, only if you manually set a refresh rate which isn't the preferred one
[15:08] <oSoMoN> Wimpress, sorry I was out for a while, dunno if your question was answered, in case it wasn't: https://code.launchpad.net/~chromium-team/chromium-browser/+git/snappy-packaging
[15:08] <Wimpress> oSoMoN: Thanks.
[15:09] <Wimpress> In a meeting but I have some questions for you. I'll be in touch tomorrow.
[15:11] <oSoMoN> sure
[15:19] <Trevinho> Morning
[15:19] <Laney> this cold sucks
[15:20]  * Laney is leaking everywhere
[15:20] <Laney> hey Trevinho!
[15:20] <Laney> how's it going?
[15:20] <Trevinho> Hi Laney
[15:20] <didrocks> poor Laney, get some hot drink!
[15:20] <tjaalton> seb128: ok, moved it to mesa for now
[15:20] <didrocks> hey Trevinho
[15:20] <Trevinho> Good... You?
[15:20] <Laney> good
[15:20] <Trevinho> Didrocks hey
[15:20] <Laney> are you on your phone or something?
[15:20]  * Laney doesn't believe you are typing these words manually :P
[15:21] <seb128> tjaalton, thx
[15:22] <Trevinho> Laney: switching between the two
[15:33] <xclaesse> is it known that ssh-agent is broken in 18.04 ?
[15:34] <xclaesse> anyone knows how to fix it ?
[15:39] <Laney> works fine here, so it's not broken
[15:39] <Laney> jibel: did you get to try volume-key?
[15:40] <Laney> If we can upload this then hopefully the MIR will go through
[15:41] <Trevinho> Laney: can you please publish https://bileto.ubuntu.com/#/ticket/3223 ?
[15:48] <Laney> Trevinho: looks like it needs a bit of a review, so can't do right now
[15:54] <Trevinho> Laney: mh, ok seb128 already review part of the code so could also do it if has time? :)
[16:05] <didrocks> jdstrand: hey, do you have any idea when you will be able to review my apparmor fix for evince?
[16:44] <jbicha> Trevinho: sorry to ping again, but you're going to be giving me patches to apply against mutter & gnome-shell 3.28.1, right?
[16:49] <Trevinho> jbicha: yeah, I'll do it later today
[16:50] <Trevinho> I'll prepare PR for salsa and one for ~ubuntu-team
[16:50] <jbicha> we don't use ubuntu-team so um…
[16:52] <Trevinho> didrocks: can you reabase https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/70 again (Or add the flag to allow project devs to edit the branch)?
[16:52] <ubot5-ng> GNOME bug (Merge request) 70 in gnome-shell "ui: Theme lookup should respect XDG_DATA_DIRS" (comments: 10) [Opened]
[16:52]  * Trevinho loves his bot
[17:07] <didrocks> Trevinho: I don't think you can allow editafter the fact (and I think I did)
[17:09] <didrocks> Trevinho: rebased
[17:10] <Trevinho> ah ok
[17:10] <Trevinho> thakns
[17:10] <Trevinho> thanks*
[17:12] <didrocks> thanks Trevinho :)
[17:13] <Trevinho> :)
[17:19] <jibel> willcooke, FYI the job which promotes the images has been fixed and 20180916 is now in current
[17:19] <jibel> 20180416 :)
[17:33] <willcooke> thanks jibel
[17:44] <Laney> We can sync volume-key once LP picks it up and j_ibel or someone gives the thumbs up that I didn't break it
[17:44]  * Laney is uploading to Debian
[17:46] <Laney> I forgot to actually say "run the tests fatally" in the changelog
[17:46] <Laney> #oops
[17:51] <sarnold> oh swet
[17:51] <sarnold> sweet, too. :) thanks Laney
[17:52] <Laney> sarnold: sweat would be OK too
[17:52] <Laney> :-)
[17:52] <sarnold> :D
[17:53] <Laney> you had to set --pinentry-mode=loopback basically
[19:44] <Trevinho> jbicha: mhmh
[19:44] <Trevinho> marco@tricky:/data/GNOME/mutter (debian/master):✗ $ gbp pq export
[19:44] <Trevinho> gbp:info: Generating patches from git (debian/master..patch-queue/debian/master)
[19:44] <Trevinho> gbp:error: patch-queue/debian/master not a valid tree-ish
[19:56] <Trevinho> nm I wanted to import and actually picked the wrong bash completion
[20:37] <oSoMoN> good night everyone
[20:46] <seb128> LocutusOfBorg, could you commit your gtk 3ubuntu1 update to the vcs?
[20:47] <seb128> 'night desktopers
[21:50] <jbicha> ximion: hi, I guess we want https://salsa.debian.org/gnome-team/gnome-software/commit/e52d2fa5 in bionic and it should be harmless?
[21:51] <jbicha> and I'm assuming the other icon sizes won't work until appstream.ubuntu.com gets a newer asgen?
[21:53] <ximion> yes and yes
[21:53] <ximion> the 128x128px version should work though
[21:53] <ximion> the change is completely harmless
[21:54] <ximion> for the asgen update we are battling a very weird crash when the garbage collector marks a memory region, that appears to only happen on Ubuntu at the moment
[21:57] <ximion> jbicha: ^