[00:24] <pieq> Morning!
[01:34] <callmepk> Good morning
[01:40] <jamesh> morning callmepk 
[01:40] <callmepk> Hi jamesh 
[03:56] <pieq> the Ubuntu Software icon is absent from the left panel after installing 20.04 beta. Is it a choice or a bug?
[03:56] <pieq> (and I still don't understand the difference between what's called "Ubuntu Software" in a new install, and the "Snap Store")
[04:13] <duflu> pieq_, I don't know. I tend to use the command line for everything myself
[04:13] <duflu> robert_ancell, ^ ?
[04:14] <robert_ancell> pieq_, I believe it should be in the panel by default, so that sounds like a bug if it's not there.
[04:15] <robert_ancell> pieq_, Ubuntu Software and the Snap Store are the same thing. It's a snap, that when run on Ubuntu has all the functionality we had with the .deb, and when run on other distros just shows the Snap functionality.
[04:26] <pieq_> duflu, yeah me too, but I wanted to give it a try cause I have friends who don't
[04:27] <pieq_> robert_ancell, thanks for the clarification, I'll raise a bug then. In what project should I do so?
[04:27] <robert_ancell> pieq_, raise it against https://launchpad.net/ubuntu/+source/gnome-software
[04:28] <robert_ancell> The shortcut might be from somewhere else, but start there.
[06:08] <oSoMoN> good morning desktoppers
[06:15] <didrocks> good morning
[06:15] <pieq_> hi didrocks and oSoMoN 
[06:15] <duflu> Hi oSoMoN and didrocks 
[06:25] <didrocks> salut pieq, oSoMoN, hey duflu 
[06:27] <seb128> lut didrocks, pieq, oSoMoN, comment ça va aujourd'hui ?
[06:27] <seb128> hey duflu, how are you?
[06:28] <pieq> seb128, pas trop mal, merci ! Et toi ?
[06:28] <seb128> ça va bien !
[06:28] <pieq> raising bugs like there's no tomorrow!
[06:32] <duflu> Hi seb128, busy and stressed still but I don't think there are any emergencies still
[06:32] <duflu> You?
[06:32] <seb128> duflu, a bit tired but good otherwise
[06:33] <seb128> duflu, let me know if I can help you reducing the stress level
[06:33] <duflu> Well, the 4 day weekend should help. Let's see how that goes
[06:33] <seb128> right, almost there!
[06:35] <pieq> seb128, every time I start my freshly installed 20.04 laptop, I see a message telling me to press Ctrl+C to cancel disk checking
[06:35] <pieq> But I think actually no disk checking is going on, cause if I don't do anything, the system boots up normally in a few secs, as usual
[06:35] <pieq> seb128, could it be a regression related to #1870018 ?
[06:35] <duflu> I think that's a new *feature*
[06:36] <pieq> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1870018
[06:36] <seb128> duflu, on installed systems?
[06:37] <duflu> Oh. No.
[06:38] <seb128> pieq, ubuntu-bug plymouth , add the 'journalctl -b 0' log and boot with plymouth:debug on the grub cmdline and then add /var/log/plymouth-debug.log 
[06:38] <seb128> https://wiki.ubuntu.com/Plymouth#Enabling_Debugging
[06:40] <pieq> seb128, doing...
[06:41] <duflu> seb128, it's not a plymouth issue. Plymouth does not request anything; it's just a GUI. Something else would be causing that
[06:41] <seb128> pieq, thx
[06:41] <seb128> duflu, right, what I would expect as well
[06:41] <didrocks> salut seb128, fatigué, mais ça va
[06:41] <seb128> didrocks, mauvaise nuit?
[06:42] <didrocks> seb128: ouais, donc forcément, ça impacte les oreilles, etc. etc.
[06:42] <seb128> :-(
[06:42] <seb128> force pas aujourd'hui, repose toi un peu
[06:44] <didrocks> merci! on va essayer si j’arrive à avancer comme je le souhaite
[06:44] <pieq> hm... ubuntu-bug plymouth shows me the Launchpad message "Please wait while bug data is processed. This page will refresh every 10 seconds until processing is complete." but it never gets to the next screen
[06:45] <pieq> and just before clickin "Send", I can see there is a permission error to retrieve the boot log
[06:45] <oSoMoN> hey duflu, salut pieq, seb128, didrocks 
[06:45] <oSoMoN> seb128, ça va bien, et toi?
[06:46] <seb128> pieq, try with sudo ?
[06:46] <seb128> oSoMoN, ça va, un peu fatigué et pas encore bien réveillé :)
[06:48] <pieq> seb128, now I can see the boot.log before clicking "Send", but I'm still stuck at Launchpad page
[06:49] <seb128> it can take a while, depending of your upload
[06:49] <seb128> do something else and see in a few minutes?
[06:49] <seb128> oSoMoN, you should be able to sync librsvg :)
[06:55] <oSoMoN> seb128, ack, thanks! (and thanks for the additional build-dep that I missed, I went a bit too fast)
[06:55] <seb128> np!
[06:55] <seb128> oSoMoN, where did you find tb 68.7? neither the download page nor https://archive.mozilla.org/pub/thunderbird/ has it from here
[06:56] <oSoMoN> seb128, it's an RC: https://ftp.mozilla.org/pub/thunderbird/candidates/68.7.0-candidates/
[06:56] <seb128> ah
[06:56] <seb128> thx
[06:57] <seb128> (I noticed your uploaded and wanted to update the snap)
[06:57] <oSoMoN> seb128, it's reasonable to wait for it to be released before accepting it into focal-proposed
[06:57] <seb128> I'm not a r-t member so not going to accept it
[06:57] <seb128> but thx for the info
[06:57] <oSoMoN> I know, just saying
[06:57] <seb128> I will wait for that to update the snap then :)
[06:58] <pieq> seb128, 8 minutes later, still on the same page, ahah
[06:58] <seb128> :(
[06:59] <seb128> pieq, well, otherwise open a bug manually and add the plymouth log and the journal one
[06:59] <pieq> seb128, how about I sosreport everything into an archive and manually open a bug?
[06:59] <pieq> ok, I have a meeting, will do after
[06:59] <seb128> thx
[07:02] <marcustomlinson> morning desktoppers
[07:02] <seb128> hey marcustomlinson, how are you?
[07:03] <marcustomlinson> seb128: good thanks :) yourself?
[07:03] <seb128> Trevinho, duflu, great that the nvidia/scaling/monitor bug was on the GNOME side and is fix commited upstream now, better than having to investigate closed source driver issues and getting those fixed
[07:03] <seb128> marcustomlinson, I'm good, just a bit tired, need some coffee :)
[07:04] <marcustomlinson> I've forgotten what it feels like to not be tired :P
[07:04] <duflu> seb128, not sure. In the process of verifying that's completely true....
[07:05] <duflu> Morning marcustomlinson 
[07:05] <marcustomlinson> hey duflu
[07:05] <seb128> duflu, the upstream bug seems similar so hopefully it's really resolved
[07:05] <duflu> seb128, the bug does not happen if I build vanilla upstream 3.36.0 so I am checking the patch they claim is relevant is really relevant
[07:06] <seb128> duflu, oh, I didn't know you were able to reproduce that bug
[07:06] <seb128> k
[07:06] <seb128> would be easy enough to apply that patch to our build and see if your machine is happier
[07:08] <duflu> Nope. The upstream patch does not work.
[07:08] <duflu> Next I will try removing xrandr scaling
[07:11] <oSoMoN> good morning marcustomlinson 
[07:11] <marcustomlinson> good morning oSoMoN
[07:17] <duflu> seb128, OK neither the upstream patch, nor removing our xrandr scaling patch fixes it. I guess maybe additional fixes from 3.36.1 might be needed
[07:18] <duflu> So maybe 3.36.1 is still the answer
[07:18] <seb128> we need to update to .1 anyway, Debian got it fix git patches on top
[07:18] <seb128> Trevinho, ^ 
[07:21] <oSoMoN> seb128, I can't sync librsvg, I'm missing upload rights
[07:21] <seb128> oSoMoN, ah, I keep forgetting that, doing it for you then :)
[07:22] <oSoMoN> thx
[07:23] <pieq> seb128, hm, false alarm, it's showing fsck message at boot time cause I had a USB drive plugged in. Do you know how fsck decides what drive has to be checked?
[07:25] <seb128> pieq, no idea
[07:25] <seb128> is that me or launchpad timeouts more than usual recently?
[07:27] <duflu> seb128, not much more than usual. 
[07:28] <duflu> But a little
[08:03] <Laney> morning
[08:04] <didrocks> hey Laney 
[08:11] <oSoMoN> good morning Laney 
[08:11] <duflu> Morning Laney
[08:13] <seb128> hey Laney, how are you today?
[08:15] <Laney> hey didrocks oSoMoN duflu seb128 
[08:15] <Laney> doing OK, hoping I can get that UI work uploaded today, tiny bit stressed about that
[08:16] <Laney> (then it's over to OEM guys to hook it up)
[08:16] <tseliot> duflu, hi, from what I can see the scaling issue with nvidia is fixed in upstream gnome. Correct?
[08:16] <duflu> tseliot, yes, maybe. I cannot verify the fix but all the discussion upstream says so
[08:17] <duflu> I can't reproduce the bug with the upstream code, and I can't reproduce the fix with the downstream code and upstream fix
[08:17] <duflu> So I just *hope* it is fixed
[08:17] <duflu> I also can't see how that patch unbreaks xrandr
[08:19] <duflu> tseliot, so we will release mutter 3.36.1 and if it's still not fixed then reopen
[08:23] <tseliot> duflu, it sounds like a plan
[08:25] <marcustomlinson> hey Laney
[08:26] <marcustomlinson> Laney: thanks for sorting out update-manager for me yesterday :)
[08:28] <duflu> tseliot, I am thinking the upstream bug report just hasn't linked to the correct patch that actually fixed it. But something fixed it by the sounds of it
[08:30] <jibel> since image 20200406, fresh installation, I cannot log in. anyone seeing this?
[08:31] <duflu> jibel, nvidia?
[08:31] <jibel> no VM
[08:31] <jibel> qemu
[08:31] <duflu> Hmm, might be reported already still
[08:31] <jibel> there is an xorg crash
[08:31] <tseliot> duflu, this, assuming that the fix was actually in mutter. I don't really remember if it's the only place where they deal with randr events
[08:32] <duflu> tseliot, yeah it should be
[08:32] <duflu> or maybe gnome-desktop too ;)
[08:32] <tseliot> fingers crossed then
[08:34] <duflu> jibel, got an assertion failure in your journal?
[08:35] <duflu> Hmm no changes in gnome-desktop look relevant beyond what's in focal
[08:40] <jibel> duflu, bug  1871578
[08:42] <duflu> jibel, deduplicated
[08:47] <jibel> duflu, this is new, it worked a couple of images ago
[08:47] <jibel> and rather critical
[08:47] <duflu> jibel, if it's a race then it will come and go randomly
[08:47] <jibel> cant test
[08:47] <duflu> it's not new
[08:47] <duflu> Try using Ubuntu on Wayland as a workaround
[08:47] <jibel> any workaround so I can start a session
[08:48] <duflu> jibel, Try using Ubuntu on Wayland as a workaround
[08:48] <duflu> Painful how many bugs using Xorg creates for us
[08:51] <jibel> we cannot just discard it this way. VM are a major share of installations and 20.04 doesn't start with the default session
[08:52] <seb128> duflu, it's not like wayland was bug free...
[08:52] <jibel> on the master bug several users are reporting this problem
[08:52] <seb128> jibel, that's not a new issue though
[08:52] <duflu> Well, I would get most of my life back right now if we didn't use Xorg, so it's significant
[08:52] <duflu> But Nvidia leaves us little choice
[08:59] <jibel> maybe but I didn't have this problem last week
[09:05]  * pieq chuckled at duflu's "I would get most of my life back right now if we didn't use Xorg" and feels a little bad about it.
[09:07] <pieq> the xorg/wayland situation is not optimal at the moment, it's true. I'd love to use Wayland as my daily driver, but mpv refuses to launch on it
[09:07] <pieq> because "there are too many Wayland issues right now", says the output log
[09:10] <seb128> jibel, wellll, either it's the same bug and it's random and you are just unlucky this week or it's a new issue that look similar and impact more people, it's not easy to tell from one report though
[09:16] <duflu> pieq, we have a fix for that coming... bug 1868520
[09:17] <duflu> Still under review in upstream Mesa
[09:22] <duflu> jibel, I had a brief exchange with tjaalton about that bug recently. He said it was a race. I don't know more than that
[09:22] <pieq> duflu, oh, that sounds great!
[09:22] <tjaalton> duflu: did we get new systemd?
[09:22] <duflu> Yes, 245?
[09:23] <pieq> I'll try my best to use Wayland as much as possible, since it's the way forward
[09:23] <tjaalton> aiui that should've fixed it
[09:23] <duflu> Not new enough?
[09:24] <tjaalton> X is started too soon
[09:25] <tjaalton> hm, not sure if they're the same
[09:27] <rbalint> tjaalton, duflu there is an even newer staging in ppa:ci-train-ppa-service/3801 if you want to give it a try, it should be accepted today to focal-proposed
[09:29] <duflu> pieq, I take it that's the mpv error you saw?
[09:31] <pieq> duflu, probably, can't remember now, I just remember a very clear reference to the fact that mpv developers prevented mpv from being launched in Wayland
[09:31] <duflu> pieq, yes they do like the server-side window decorations that Xwayland gives them
[09:31] <duflu> We patch around that
[09:33] <pieq> duflu, hm!
[09:35] <duflu> Though it's been years since I looked at that so I might be out of date
[09:40]  * pieq eod
[09:41] <pieq> see you tomorrow!
[09:55] <duflu> Bye pieq 
[10:06] <Wimpress> Morning desktoppers o/
[10:06] <didrocks> hey Wimpress 
[10:06] <marcustomlinson> hey Wimpress
[10:08] <duflu> Morning Wimpress 
[10:08] <Wimpress> Hello all. 
[10:08]  * duflu deflates
[10:08] <Wimpress> duflu: You're up late again.
[10:08] <duflu> Wimpress, no tonight is early actually. But I will run while I can
[10:09] <duflu> Just got a shallow pass through all my unresolved upstream work
[10:09] <duflu> Night...
[10:09] <Wimpress> Oooh. 
[10:09] <Wimpress> Upstream GNOME or PLymouth?
[10:10] <duflu> Both
[10:10] <duflu> o/
[10:10] <Wimpress> Excellent :-)
[10:10] <Wimpress> Goodnight
[10:28] <kokoye2007> hello
[10:28] <kokoye2007> i want to ask something for Ubuntu Installer 
[10:28] <kokoye2007> some one can help me 
[10:49] <seb128> kokoye2007, there is an #ubuntu-installer channel, also best to ask your question rather than wait for someone to give a reply to a non question
[10:55] <kokoye2007> thank seb128
[10:55] <kokoye2007> i think i send email 
[10:55] <kokoye2007> cc to you
[11:06] <cpaelzer> hiho - for a bug report - what is the component when I hit "meta" that shos the search box and preview of my search results
[11:06] <cpaelzer> like "meta" -> "enter a few chars" -> select an app from the list to start
[11:10] <cpaelzer> docs call it "activities overview"
[11:10] <cpaelzer> but for a bug I'd need a package name
[11:10] <cpaelzer> well I assume I'll start with gnome-shell and you can reasssign as needed
[11:13] <cpaelzer> Filed https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607
[11:13] <cpaelzer> let me know what you'd need on that ...
[11:14] <seb128> cpaelzer, what screen resolution/scaling factor/video card do you use?
[11:14] <seb128> cpaelzer, 'activity' is the right name
[11:15] <Laney> kenvandine: yelp fails to build with me with some message about gtk-doc
[11:17] <seb128> cpaelzer, bug #1869571 ... does the describe matches your setup?
[11:18] <cpaelzer> checking seb128
[11:18] <cpaelzer> where can I check my scaling factore these days?
[11:19] <cpaelzer> ah found it
[11:19] <seb128> cpaelzer, settings -> display, but see my most recent comment
[11:19] <seb128> do you use dual monitors stacked vertically?
[11:20] <seb128> if so that's a dup of the bug I just mentioned
[11:25] <cpaelzer> it is a dup, marked as such
[11:25] <cpaelzer> thanks seb128
[11:25] <seb128> cpaelzer, yw!
[11:27] <seb128> cpaelzer, I don't know how frequent the vertical stacking is used but I tagged rls-ff-incoming so we review it on our next team meeting
[11:28] <cpaelzer> what I can confirm (since my setup is more complex than those in the report already) is that any sort of vertical seems affected
[11:28] <cpaelzer> like my two row 3:2 setup
[11:29] <cpaelzer> I personally can live without UI for that, as I usually type and hit enter - but more visual people will consider this more critical
[11:29] <cpaelzer> I'm subscribed and will follow as bug updates get added
[11:30] <seb128> thanks for the details, impressive setup you have :)
[11:40] <cpaelzer> the hard part is to do it on my T580 laptop :-)
[11:45] <seb128> Laney, kenvandine, it builds fine on focal so probably some other component that changed/needs fixing in Debian
[11:46] <Laney> thanks for checking ...
[11:47]  * Laney tries focal
[11:51] <seb128> Laney, https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+build/19139160
[11:51] <seb128> tried in a ppa as well to make sure it's nothing local
[11:51] <Laney> yes but I want to know if it's anything in *my* local setup
[11:52] <seb128> not likely
[11:52] <seb128> https://buildd.debian.org/status/package.php?p=yelp&suite=unstable
[11:52] <Trevinho> seb128: oh great to read on that nvidia thing :)
[11:52] <Laney> ok thanks, seems you have a handle on it and want to take over
[11:52] <seb128> Trevinho, bonjourno, indeed :)
[11:52]  * Laney leaves it to seb128 and goes back to ubiquity
[11:53] <Trevinho> seb128: buondì! :)
[11:53] <seb128> Laney, not really, I just looked at the build logs since I uploaded yesterday, but I can try having a look later if you want
[11:53] <seb128> I was not going to debug it, just rulled out the problem to be in the yelp update
[11:54] <Laney> https://people.canonical.com/~laney/weird-things/rst.png
[11:54] <Laney> oooh yeahhhh nice UI
[11:55] <Laney> I didn't actually know it was uploaded to Debian
[11:55] <Laney> thought I was handling that sponsorship
[11:55] <Laney> but yeah happy not to :-)
[12:03] <Laney> . o O ( hope it's not new gtk that breaks it ... )
[12:30] <Wimpress> seb128 Laney Here is my testcase for GameMode.
[12:30] <Wimpress> https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1853830/comments/11
[12:30] <Wimpress> Works correctly here. I've asked community testers to test it as well.
[12:57] <seb128> Laney, nice!
[12:57] <seb128> Wimpress, sounds good
[13:22] <oSoMoN> seb128, the autopkgtest failures at https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#librsvg look worth retrying to me
[13:24] <seb128> oSoMoN, the sphinx ones look real from recent history
[13:24] <seb128> I retried the other one now
[13:27] <oSoMoN> seb128, you're right, I hadn't thought of looking at test history…
[13:27] <seb128> oSoMoN, it's a timeout in a wget, I looked a bit earlier, it's weird because if I read correctly the test it tries to wget a local file: uri...
[13:28] <oSoMoN> that sounds suspicious
[13:29] <oSoMoN> has there been any change in our autopkgtest infrastructure at the time this started failing?
[13:31] <seb128> I don't know
[13:31] <seb128> jamespage asked about that failure earlier on #ubuntu-devel
[13:31] <seb128> maybe they will debug it for us :)
[13:32] <oSoMoN> Laney, has there been any relevant change in the autopkgtest infra between 2020-03-25 and 2020-03-30 ?
[13:34] <mitya57> seb128, oSoMoN: wget is just a method name. Actually it tries to load a local file using WebKitGTK.
[13:34] <oSoMoN> aha
[13:35] <mitya57> I am not yet sure what broke it, but it also broke in Debian: https://ci.debian.net/packages/s/sphinx/unstable/amd64/
[13:35] <Laney> I doubt it
[13:36] <Laney> did you or anyone try running the test yourselves?
[13:36] <oSoMoN> no
[13:37] <oSoMoN> just poking in the dark, but it looks like people are already looking/have looked at it
[13:41] <mitya57> jamespage filed bug 1871610 which has some detail
[13:41] <mitya57> gi.repository.GLib.Error: WebKitJavascriptError: file:///usr/share/doc
[13:41] <mitya57> /sphinx-doc/html/search.html?q=example:1:80: TypeError: null is not an
[13:41] <mitya57> object (evaluating '$('#search-results > p:first').text().match(/found
[13:41] <mitya57> (\d+) page/)[1]') (699)
[13:42] <diddledan> Wimpress, I just pinged you in telegram, but I'll pop the image here 'cos it's a more appropriate venue. anyone else, feel free to chime-in with thoughts: is this a firefox bug? https://www.dropbox.com/s/0pjwlpa1ilcqqcm/ffbug.png?dl=0
[13:43] <diddledan> the corner of the window
[13:43] <diddledan> every firefox window has it
[13:44] <diddledan> this is FF 75.0 from Focal (20.04)
[13:46] <Laney> aside: AFAICS we shouldn't have migrated that sphinx
[13:46] <Laney> oh no lies
[13:47] <Laney> missed the previous result buried down in the history
[13:48] <oSoMoN> diddledan, I'm not seeing that here, is that X11 or wayland?
[13:48] <diddledan> wayland
[13:48] <diddledan> although I believe FF uses XWayland?
[13:48] <oSoMoN> diddledan, mind filing a bug?
[13:48] <diddledan> willdo
[13:48] <oSoMoN> thx
[13:53] <Laney> seb128: Wimpress: ooi, do you know if gamemoded quits after a period of inactivity?
[13:53] <diddledan> #1871644
[13:54] <diddledan> LP#1871644
[13:54] <diddledan> bah
[13:54] <diddledan> what's the right incantation to link Launchpad bugs?!
[13:54] <diddledan> :-p
[13:54] <diddledan> bug 1871644
[13:55] <diddledan> there we go!
[13:55] <diddledan> I know how to drive this thing, honest!
[13:59] <diddledan> seems to also affect X11 for me
[13:59] <diddledan> I've updated the bug
[14:01] <mitya57> seb128, oSoMoN, Laney: looks like a bug in WebKit. When opening that page in Epiphany I get this: https://mitya57.me/tmp/epiphany.png
[14:01] <mitya57> But line 51 is inside a <script>! It is:         if (sbh < win.innerHeight()) {
[14:02] <mitya57> Does it try to parse HTML as XML???
[14:10] <GunnarHj> Hi seb128!
[14:10] <GunnarHj> As regards all those ibus-ui-gtk3 crashes I'm thinking of the fact that Debian changed --libexec from /usr/lib/ibus to /usr/libexec:
[14:10] <GunnarHj> https://salsa.debian.org/debian/ibus/-/commit/2fccf6d2
[14:10] <GunnarHj> They also added a backwards compatibility fix since most ibus engines still install their things in /usr/lib/ibus:
[14:10] <GunnarHj> https://salsa.debian.org/debian/ibus/-/commit/e26a5620
[14:10] <GunnarHj> I'm thinking that if they missed something in connection with those changes, it might be one reason for the explosion of crash reports. Would it be worth the try to reverse those commits for now, or am I way off track?
[14:10] <seb128> GunnarHj, hey, how are you?
[14:11] <GunnarHj> It's fine here, and you?
[14:11] <seb128> I'm good
[14:11] <seb128> GunnarHj, I doubt a location change would result in crashes like those you triaged
[14:11] <seb128> it would rather be not found error or similar
[14:12] <GunnarHj> seb128: Yeah, sounds reasonable.
[14:12] <hellsworth> good morning desktopers
[14:13] <kenvandine> good morning hellsworth 
[14:13] <oSoMoN> good morning hellsworth, kenvandine 
[14:13] <kenvandine> hey oSoMoN 
[14:14] <hellsworth> hi oSoMoN , kenvandine 
[14:14] <diddledan> morning folks :-)
[14:14] <kenvandine> hey diddledan 
[14:14]  * diddledan checks their wrist for a watch, realises they aren't wearing one and then checks the computer... 15:14pm in the afternoon. that's far too early to be awake!
[14:15] <seb128> mitya57, you are sure? it's weird, https://ci.debian.net/packages/s/sphinx/unstable/amd64/ the last success and first failure have the same webkitgtk version
[14:15] <seb128> hey USers :)
[14:15] <hellsworth> hi europeans :)
[14:15] <diddledan> seb128, I fight for the Users!
[14:15] <kenvandine> :)
[14:15] <hellsworth> lol
[14:16] <seb128> heh
[14:16] <GunnarHj> seb128: I looked at the error tracker, and there weren't so many ibus-ui-gtk3 crashes as long as we had ibus 1.5.22-1~exp1ubuntu1. That's what made me speculate.
[14:16] <mitya57> seb128: definitely it is not specific to my python script as it happens in epiphany too. But I am still not sure what caused it, I am currently doing some debugging.
[14:16] <seb128> GunnarHj, there wasn't also not so many focal users until we hit beta :p
[14:16] <GunnarHj> seb128: True.
[14:16] <oSoMoN> diddledan, bug confirmed, although I'm seeing something slightly different, and it's affecting only wayland for me
[14:17] <diddledan> odd
[14:17] <oSoMoN> (tested in a focal VM, and commented on the bug)
[14:17] <diddledan> I am surmising that something in the Firefox UI is protruding from underneath the theme
[14:17] <seb128> mitya57, k, let us know if you figure something out, https://ci.debian.net/data/packages/unstable/amd64/s/sphinx/4705725.log doesn't have any obvious candidate
[14:17] <mitya57> I looked at that log too, yes, no candidate :(
[14:18] <oSoMoN> diddledan, this looks like https://bugzilla.mozilla.org/show_bug.cgi?id=1509931
[14:18] <diddledan> oSoMoN, aha! I found the incantation that prevents it - turning off the unified titlebar and menubar to have a separate bar for each fixes it
[14:19] <seb128> kenvandine, Laney, so yelp is failing due to webkit and that's fixed upstream in https://trac.webkit.org/changeset/259380/webkit
[14:19] <seb128> (we don't have the bug because we build without the wpe backend due to universe depends)
[14:19] <Laney> nice
[14:19] <Laney> webkit, sensing a theme here
[14:19] <seb128> also it doens't happen locally because there is a display
[14:19] <seb128> indeed :)
[14:20] <diddledan> oSoMoN, yep, that's the same bug I think
[14:20] <diddledan> let me link it to launchpad
[14:20] <oSoMoN> done already
[14:21] <diddledan> aha
[14:21] <diddledan> that'll be why it was moaning at me :-p
[14:21] <Laney> mitya57: might want to chat in #webkitgtk, could let you shortcut some steps
[14:25] <oSoMoN> diddledan, there's also https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1828728, which is X11-specific
[14:26] <seb128> Laney, I don't know offhand for gamemoded, I've added an item to check to my afternoon's backlog
[14:27] <Laney> seb128: ok, or you could hand that off to the driver of the feature ;-)
[14:27] <Laney> just did +1 the ffe btw
[14:29] <mitya57> Laney: thanks, asked
[14:32] <seb128> Laney, thanks!
[14:33] <mitya57> https://paste.ubuntu.com/p/wKjp9XX2jt/ — pasting here too, from that trace it seems to definitely parse it as XML
[14:36] <mitya57> Hmm, actually that file is XHTML, so maybe it's right…
[14:42] <GunnarHj> seb128: Bug #1871599 is weird. Can it be a regression from the POT update you did? Would it help to update the .po files also?
[14:44] <seb128> GunnarHj, shrug,  I guess it's a regression from my changes :/
[14:45] <GunnarHj> seb128: Nothing seems to be normal with the translations of that package. :(
[15:10] <kenvandine> I did a clean install of focal on my laptop this morning, so nice to have a fresh install :)
[15:10] <marcustomlinson> :)
[15:10] <seb128> kenvandine, zfs? ;)
[15:10] <kenvandine> yes
[15:10] <kenvandine> but with real swap this time :)
[15:11] <kenvandine> that's why i had to reinstall... living without swap and 8G is hard
[15:11] <seb128> right
[15:15] <Saviq> is unreadable text in gedit (white on light grey) known on Focal with Yaru-dark?
[15:15] <clobrano> Saviq, yep let me find the bug
[15:16] <clobrano> Saviq, https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1857191
[15:18] <Saviq> thanks clobrano
[15:19]  * Saviq should've looked in gedit's preferences..
[15:58] <marcustomlinson> Laney: help :/
[15:58] <marcustomlinson> I caused a new bug un update-manager. Bug #1871490
[15:59] <marcustomlinson> https://code.launchpad.net/~marcustomlinson/update-manager/update-manager/+merge/381937
[15:59] <Laney> whoops
[15:59] <Laney> sorry for missing that
[15:59] <marcustomlinson> not your fault!
[15:59] <Laney> will look in a minute, just polishing off a ubiquity upload
[16:06] <Laney> eek
[16:11] <Laney> jibel: have you tried an install on efi recently?
[16:11] <mitya57> seb128, Laney: looks like the sphinx error is related to new shared-mime-info
[16:11] <Laney> I just got an initramfs prompt
[16:12] <seb128> mitya57, I was thinking it might be something like when you said it was trying it as a wrong type
[16:12] <seb128> but I didn't have time to check yet and didn't see shared-mime-info in the env diff earlier
[16:12] <mitya57> Now I will try to find a particular commit
[16:12] <mitya57> In fact I created a chroot based on snapshot.debian.org and upgraded packages one by one.
[16:13] <Wimpress> Laney: I can test EFI install. 
[16:14] <Laney> Wimpress: good, this time I wasn't using the OEM kernel
[16:14] <Laney> same as what I was going on about yesterday though
[16:14] <mitya57> It may be https://gitlab.freedesktop.org/xdg/shared-mime-info/commit/3ba7920b6dfa0b28c400d302d070dbcad5d29824
[16:15] <seb128> mitya57, https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/8ae13a58 ?
[16:15] <seb128> or that
[16:15] <Laney> Wimpress: jibel: https://people.canonical.com/~laney/weird-things/argh.png
[16:16] <mitya57> seb128: that looks more related, let me try reverting it
[16:16] <Laney> /dev/vda5 totally does exist though
[16:18] <seb128> Laney, :-(
[16:18] <seb128> Laney, if you send me an update .pot I can upload to launchpad/warn translators, if you want to win some time having those strings up before the package is uploaded
[16:18] <seb128> or I can do the template refresh/upload if you give me the diff/mp
[16:19] <Laney> seb128: It's pushed to ubiquity master
[16:19] <Laney> not in the .pot though, how is that done?
[16:20] <seb128> Laney, debconf-updatepo iirc?
[16:20] <seb128> I can have a look in a bit if you want
[16:20] <Laney> that updates debian/real-po/*.po
[16:20] <seb128> ah
[16:21] <seb128> intltool-update -p in po/ ?
[16:22] <Laney> oh no wait, it is there
[16:22] <seb128> good
[16:22] <mitya57> seb128: reverting your commit helps :)
[16:23] <seb128> mitya57, great :)
[16:23] <mitya57> Should I upload it?
[16:23] <mitya57> Or better try to fix on sphinx side? (escaping < > & to &lt; &gt; &amp;)
[16:24] <Laney> sounds like that s-m-i commit was actually to fix a different problem with webkit
[16:25] <Laney> so I vote for a fix on the sphinx side if that's possible
[16:28] <mitya57> Laney: ok, I will try
[16:30] <Laney> Wimpress: happens without efi actually
[16:34] <seb128> mitya57, agreed with Laney, that commit sounds like it makes webkit does the right thing, the fact that it confuses the tests sound like maybe a bug on this side, I would investigatge fixing that first
[16:34] <mitya57> I will try to make Sphinx use HTML 5 :)
[16:44] <Laney> seb128: I'm going to upload ubiquity, still if you have time to manually push the pot that would be good
[16:44] <Laney> verified that install is still broken for me without the new installer pkg anyway, so I don't make it worse :/
[16:52]  * Laney looks at marcustomlinson's patch
[16:58] <Laney> (https://people.canonical.com/~laney/weird-things/battery.png lol)
[16:58] <Laney> (just saw that in the directory listing)
[17:00] <mitya57> Laney: https://xkcd.com/2289/
[17:00] <Laney> :D
[17:01] <Laney> oh the phone days, what good times we had
[17:02] <marcustomlinson> XD
[17:07] <mitya57> Fixed sphinx uploaded!
[17:09] <Laney> mitya57: nice one!
[17:24] <Laney> tkamppeter: can you check foomatic-db in the unapproved queue and let me know if you think it should be accepted please?
[17:34] <oSoMoN> mitya57, thanks!
[17:35] <mitya57> You are welcome!
[17:35] <mitya57> (It is currently in the unapproved queue)
[17:47] <jibel> Laney, not since beta.
[17:47] <jibel> (re have you tried efi recently)
[17:48] <jibel> Laney, did you file a bug?
[17:48] <jibel> is it on hw or vm?
[17:49] <jibel> vm from the name of the disk obviously
[17:55] <jibel> today's image doesn't even boot in a vm
[17:55] <jibel> qemu
[17:56] <jibel> ah it does, just be patient, with uefi there is no feedback during the integrity check.
[18:17] <seb128> jibel, plymouth isn't displayed during the integrety check on uefi systems?
[18:45] <jibel> seb128, not in qemu, on my test machine it was fine as of last week
[18:46] <jibel> but I see the nice shutdown message
[18:46] <seb128> jibel, I wonder if plymouth is failing there for some reason, but even so it should fallback to text mode and that shoul dhave messages as well
[18:47] <jibel> seb128, after installation it's fine, so it's just when booting the installation media
[18:47] <jibel> which is annoying still because that's where it spends time checking the iso
[18:47] <seb128> right
[18:47] <seb128> I need to check with qemu
[18:47] <seb128> do you use any wrapper around it?
[18:48] <jibel> Laney, no crash with the default installation on uefi, can you provide more details to reproduce it?
[18:49] <jibel> I don't have a vda5 which is expected 
[18:49] <jibel> seb128, just virt-manager
[18:49] <jibel> other than that it's pretty standard. I'm on focal 
[18:49] <seb128> k, I will try tomorrow
[18:49] <seb128> I usually use virtualbox
[18:49] <jibel> thanks
[18:50] <seb128> graphic drivers behave differently there
[19:14] <Laney> jibel: I'll file something tomorrow
[19:14] <Laney> but I just install and reboot, and get that initramfs prompt
[19:14] <Laney> actually happens on uefi and non uefi
[19:14] <Laney> I'll try on hw
[19:20] <Laney> seb128: thanks for the mail
[19:20] <seb128> Laney, np!
[21:48] <xnox> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1871717 is odd
[22:23] <xnox> looks like german translation is broken in bios boot https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1871724