[06:06] <didrocks> good morning
[06:07]  * didrocks reboot in a single monitor for Trevinho
[06:14] <didrocks> duflu: FYI, I rebooted without drm modeset=1 for nvidia. Let's see if I trigger slowness/freeze, but for now, nothing
[06:14] <didrocks> the scaling issue is still here though
[06:15] <duflu> didrocks, please also check you don't have something busily writing to the journal. Because journal flushing also happens every 5 seconds and will freeze a program
[06:15] <duflu> Morning didrocks :)
[06:16] <didrocks> duflu: hey! Well, possibly related to io. It's mostly when I'm opening/closing apps
[06:17] <didrocks> (most of the time, not necessary a rule)
[06:17] <duflu> didrocks, If you have a HDD LED to look at then that helps :)
[06:17] <duflu> Also strace
[06:17] <didrocks> duflu: unsure what to strace?
[06:17] <duflu> didrocks, write or fsync calls etc
[06:17] <didrocks> yeah, but which prog?
[06:18] <duflu> didrocks, gnome-shell maybe? But yeah it could be anything if kernel journal flushing is the issue
[06:18] <didrocks> and the question, is why it started for RAOF and I when it was ok beforehand and it seems it doesn't happen without drm modeset=1
[06:18] <didrocks> but my journal doesn't file up
[06:19] <didrocks> like, nothing is spamming it
[06:19] <RAOF> didrocks: Nah, it happens for me with nvidia_drm.modeset=0
[06:19] <didrocks> RAOF: argh, maybe it sounded only better here :/
[06:19] <duflu> That's fine. Unfortunately I'm being harassed in upstream work so I'll have to get to this bug next week
[06:19] <didrocks> final freeze is next Thursday
[06:19] <duflu> Unless I have a particularly lucky Friday
[06:20] <didrocks> I don't think we can release with this, with a very small portion of testing, we have already 2 users with it
[06:20] <RAOF> Yeah, no disc IO for me.
[06:20] <didrocks> so I don't want to imagine at scale :/
[06:20] <didrocks> RAOF: just got one without disc IO?
[06:20] <duflu> Still, it involves me changing and configuring new hardware. I will get to it ASAP
[06:21] <RAOF> didrocks: Mine have *never* involved disc IO, as far as I can tell.
[06:21] <didrocks> RAOF: I didn't look at that really hard, I was used to disc IO issue at unity times, but that was another machinie
[06:21] <didrocks> machine*
[06:22] <RAOF> ```
[06:22] <RAOF> Apr 05 17:21:32 Behemoth gnome-shell[2390]: Couldn’t parse steam.desktop as a desktop file, will treat it as a regular file.
[06:22] <RAOF> Apr 05 17:21:33 Behemoth gnome-shell[2390]: Couldn’t parse examples.desktop as a desktop file, will treat it as a regular file.
[06:22] <RAOF> ```
[06:22] <RAOF> That's rather interesting, though.
[06:22] <RAOF> I get those two lines each time I hit enter in the terminal.
[06:22] <didrocks> terminal, like alt+F2? or gnome-terminal?
[06:23] <RAOF> Or, rather, each time I cause a zsh prompt to be displayed.
[06:23] <didrocks> (nothing here, all my desktop files should be correct)
[06:23] <didrocks> waow
[06:23] <didrocks> don't know why it makes the shell reloading the desktop files
[06:23] <RAOF> So, for some reason, displaying a zsh prompt triggers gnome-shell to try and reparse a bunch of desktop files?
[06:23] <didrocks> I guess you have those 2 in your favorite-apps gsettings key? ^
[06:23] <RAOF> I shouldn't?
[06:24] <didrocks> just to know if it tries to parse the content of favorites-apps or all desktop files
[06:24] <didrocks> (examples.desktop is weird, I don't think we ever supported it in the shell)
[06:24] <didrocks> but I may be wrong
[06:26] <didrocks> RAOF: so, if your steam.desktop is the upstream one, I just added it to favorites-apps and have bash displaying the login prompt multiples times
[06:26] <didrocks> no spam for me in the journal
[06:26] <duflu> In case you guys have different bugs I will focus on RAOF's descriptions for now
[06:27] <RAOF> Yeah, it's only in zsh.
[06:27] <RAOF> Only in zsh.
[06:27] <didrocks> RAOF: do you have the slowness only when you press enter in zsh?
[06:27] <didrocks> like, it never happened when you started an app from the launcher?
[06:28] <didrocks> (that was my main use-case, start an app, everything frozen but a duplicated cursor that I can move for 5 s)
[06:30] <RAOF> I do not see the problem when launching an app from the launcher.
[06:30] <didrocks> argh, so maybe different issues…
[06:31] <RAOF> I *do* recall having the pauses trigger from ways other than having a zsh prompt displayed (not just <enter>, but returning from a nvim session, ctrl-C, starting a terminal) but the pause-on-zsh is just *so* obvious and easy to trigger it rather overwhelms everything else.
[06:31] <oSoMoN> good morning desktoppers
[06:31] <oSoMoN> and happy Friday!
[06:31] <didrocks> RAOF: I have this happening mostly on cold session boot
[06:31] <didrocks> like the first apps I'm launching
[06:31] <didrocks> then, it's at $RANDOM time
[06:31] <didrocks> happy Friday oSoMoN
[06:35] <oSoMoN> salut didrocks
[06:36] <duflu> Morning oSoMoN
[06:37] <duflu> RAOF: I can only think of title bar text that the text shell can affect in the graphical shell
[06:38] <duflu> afk for a bit
[06:38] <RAOF> Removing examples.desktop and steam.desktop (from ~, which for some reason gnome-shell is scanning for desktop files?!) does not eliminate the pauses (but does eliminate the journal entries, funnily enough ☺)
[06:41] <oSoMoN> hey duflu
[07:08] <duflu> RAOF: Is the bug still Nvidia-specific?
[07:08] <duflu> Can you tell?
[07:10] <RAOF> Yes
[07:11] <RAOF> duflu: I guess it might just be specific to my NVIDIA machine.
[07:11] <duflu> Yeah
[07:12] <duflu> RAOF: Also what driver version are you on now?
[07:12] <RAOF> I could try turning on hybrid in the BIOS and seeing if it also happens with Intel if I can get it to use the Intel card.
[07:13] <RAOF> 418. It doesn't help ☹️
[07:13] <duflu> I think mutter likes that... providing the LCD is connected to Intel
[07:13] <RAOF> 418
[07:14] <duflu> Heh. Gitlab is dead. I can definitely ignore upstream issues now
[07:16] <RAOF> The LCD is connected to the Intel in hybrid mode.
[07:16] <RAOF> The trick is getting things to use mesa 😀
[07:21] <duflu> RAOF: Do you have a custom prompt at all?
[07:21] <RAOF> Yes, but I've tried it without and it still triggers.
[07:22]  * RAOF  is still unclear how the zsh prompt can hang gnome-shell
[07:22] <duflu> RAOF: You're sure it happens with gnome-terminal too? Not just qterminal?
[07:24] <RAOF> Yes. I usuallyuse gnome-terminal;I just tested in qterminal to work out if it was a gnome-terminal bug.
[07:26] <duflu> One slight problem with testing video cards now; my desktop is too small to close if one is installed :)
[07:30] <duflu> RAOF: I have one remaining concern before you fade into the night -- the assumption that poor performance is related to the memory usage. Sounds plausible but I also know of other serious Nvidia performance issues that appear over time. I wonder if we can make the bug just about memory to clarify that?
[07:32] <RAOF> Sure, feel free to split of the “gnome-shell hangs for 5s each time I got enter in a terminal” bug 😀
[07:32] <duflu> RAOF: No that's the third problem you reported in the same bug :)
[07:32] <duflu> I was already going to split that
[07:34] <duflu> There being performance problems are a concern, but if we were to fix the memory usage and not fix the performance problems, I don't want that to block the bug, waiting on multiple fixes
[07:34] <RAOF> Oh, I think that is the performance problem.
[07:35] <duflu> Yes, probably. But the first problem you reported was memory usage
[07:35] <RAOF> Right
[07:35] <duflu> I completely agree some part of 10GB RSS would hurt the system but it might not be the only hurt
[07:36] <duflu> I'm working on a few serious Nvidia performance issues upstream
[07:36] <RAOF> To be clear, I think the “general sluggishness” I reported is the “press enter and wait 5s”.
[07:36] <duflu> OK
[07:36] <duflu> So we hope that is related to the memory usage, but if not then the bug needs splitting
[07:37] <duflu> I am now back on Nvidia.
[07:38] <duflu> It's definitely started bigger
[07:38] <duflu> But that's nothing new
[07:39] <RAOF> Yes.
[07:42] <duflu> So far my gnome-shell on Nvidia with zsh has only shrunken and 1% CPU when busy :/
[07:55] <willcooke> morning all, happy Friday!
[07:58] <duflu> Morning willcooke
[08:02] <duflu> RAOF: In case you're still around... it appears the desktop-icons gnome-shell extension actively monitors all desktop files. Can you tell if any are changing?
[08:02] <duflu> Even in metadata?
[08:02] <Laney> hi
[08:03] <duflu> Hi Laney
[08:03] <willcooke> afternoon duflu, morning Laney
[08:06] <RAOF> duflu: I don't know why any would be changing. Nothing I'm doing *should* be modifying desktop files.
[08:06] <duflu> RAOF: Possibly even the metadata of ~ ?
[08:07] <seb128> good morning desktopers
[08:07] <seb128> happy friday!
[08:08] <RAOF> There will be frequent writes to a file in ~
[08:08] <duflu> Morning seb128
[08:09] <Laney> hi duflu willcooke seb128
[08:09] <duflu> RAOF: How about this?; gnome-shell-extension-desktop-icons reacts to all metadata changes. That includes to your home directory. And the home directory's metadata changes every time zsh writes to ~/.zsh_history
[08:09] <seb128> hey RAOF duflu Laney
[08:09] <seb128> ups
[08:10] <duflu> We missed you
[08:10] <seb128> duflu, why is it not monitoring ~/Desktop only? bug?
[08:10] <seb128> :)
[08:10] <RAOF> duflu: that's quite plausible
[08:10] <duflu> seb128, because ~ is visible on the desktop :)
[08:10] <duflu> The icon with your name on it
[08:11] <seb128> well that doesn't require monitor tis content though?
[08:11] <seb128> I guess it would easy enough to disable that extension and see if that makes a performance difference
[08:11] <didrocks> hey seb128, willcooke, Laney
[08:11] <seb128> lut didrocks, bon vendredi à toi! :)
[08:11] <didrocks> merci, toi aussi :p
[08:15] <duflu> seb128, we can't disable or uninstall it :(
[08:15] <duflu> Only turn off some icons
[08:15] <seb128> well you can install gnome-session and log into a GNOME vanilla session to see if it's an issue there
[08:15] <duflu> Also I can't reproduce the bug still, so testing is still hard
[08:15] <seb128> and even enable the ubuntu launcher there
[08:16] <duflu> It appears indeed only zsh commands trigger changes to the ~ metadata
[08:17] <didrocks> so, sounds like my perf issue is unrelated
[08:17] <duflu> didrocks, yeah but please do open a bug. I might know it already
[08:18] <didrocks> duflu: I want to confirm that I don't have it anymore without drm modeset
[08:18] <didrocks> which sounds to be the case so far
[08:18] <duflu> Oh, actually I still have that OFF
[08:18]  * duflu enables it
[08:18] <didrocks> I got it so often (like every 10 minutes) that not having it in ~2h is weird
[08:19] <didrocks> ah ofc, can't open the bug with ubuntu-bug right now as I'm running the scaling factor debug mutter version which isn't the one in the archive…
[08:20] <duflu> didrocks, please open a new bug. Even RAOF is reporting potentially multiple different issues in that one bug
[08:20] <didrocks> yep
[08:21] <oSoMoN> good morning willcooke, seb128
[08:21] <duflu> Weird. My Xorg sessions can't start with nvidia-drm.modeset=1. Only Wayland works
[08:21] <seb128> lut oSoMoN, happy friday! how are you?
[08:21] <seb128> didrocks, when did the issue start for you?
[08:22] <oSoMoN> seb128, I'm good (although a bit tired, but hey, it's Friday!), you?
[08:22] <seb128> same! :)
[08:23] <didrocks> seb128: hard to say, it became more and more important (like it was once a day before)
[08:23] <didrocks> seb128: I bet with the new GNOME stack, but I would need to bisect if we can't find it anymore
[08:23] <didrocks> duflu: yeah, this is another upstream bug
[08:24] <didrocks> duflu: which was investigated but never resolved
[08:24] <didrocks> you have to blacklist their blacklist
[08:24] <duflu> Ugh. And moving the mouse on nvidia requires 45% CPU. It's only 10% on Intel
[08:24] <seb128> is the picker mp going anywhere or still more discussions/arguing?
[08:25] <seb128> we might want to distro patch that next cycle if that doesn't land upstream
[08:25] <duflu> seb128, it's bug free and all discussions resolved. But no current activity
[08:25] <duflu> Interesting Nvidia is so much worse. I might need to profile that for new problems
[08:26] <duflu> Oh. No I don't need to. It's the software cursor. That's the difference. So 45% CPU is about expected
[08:26] <duflu> Not good, but not surprising
[08:27] <didrocks> duflu: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1823301
[08:27] <ubot5`> Ubuntu bug 1823301 in mutter (Ubuntu) "Shell hangs up at random times" [Undecided,New]
[08:27] <duflu> Yay
[08:27] <didrocks> I'll update the bug if I get it again with drm modeset=1
[08:27] <didrocks> oupss
[08:27] <didrocks> modeset=0
[08:27] <didrocks> I meant
[08:28] <duflu> Thanks
[08:32] <seb128> didrocks, did Trevinho email you about sponsoring his recent fixes today btw?
[08:45] <didrocks> seb128: you meant "fix" not "fixes"?
[08:45] <didrocks> seb128: I was wondering if that worth it, it's only rotating the screen, which is less important than the other fixes, correct?
[08:45] <didrocks> like not having a proper scaling on boot, which he's going to work on
[08:45] <didrocks> so I guess aiming an upload on Monday with both?
[08:46] <seb128> https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/365502
[08:46] <seb128> yeah, monday is probably fine
[08:46] <duflu> didrocks, unfortunately rotating the screen is the most popular duplicate reported
[08:46] <duflu> in the xrandr-scaling tagged bugs
[08:46] <didrocks> duflu: 2 duplicates?
[08:47] <duflu> Yeah still true :)
[08:47] <duflu> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=xrandr-scaling
[08:47] <didrocks> sounds less a main use case that not having the correct scaling at boot?
[08:48] <duflu> That's very true. Might not be statistically significant numbers yet
[08:49] <didrocks> let's see…
[08:49] <seb128> I had the impression that Marco said that the fix could resolve some other problems
[08:49] <seb128> also unsure he's able to reproduce/going to fix the on-boot issue by monday
[08:49] <duflu> Yeah the number of fixes required is definitely going to be shorter than the above bug list
[08:50] <seb128> but we can still upload what we have on monday
[08:50] <didrocks> seb128: do we consider releasing disco without fixing that bug?
[08:50] <seb128> I've no idea how many users are impacted
[08:50] <seb128> that some nvidia only right?
[08:50] <didrocks> right
[08:51] <seb128> it would be best to fix but I wouldn't consider it as a blocker
[08:51] <didrocks> ok, so I'll have to reinstall bionic
[08:51] <seb128> it get less reports that the screen rotate one :p
[08:51] <didrocks> I thought the FFe was under the consideration that no obvious regression?
[08:51] <didrocks> for scaling factor
[08:51] <didrocks> sounds crazy to have to argue on that, shrugh
[08:51] <seb128> seems like you are strongly in favor of considering it as a blocker
[08:52] <didrocks> I thought the "high" importance reflected it?
[08:52] <seb128> was anyone able to reproduce
[08:52] <jibel> there are not enough users of disco to get lot of report about the nvidia issue
[08:52] <seb128> or are the only one who saw the issue so far?
[08:52] <jibel> it's critical to me
[08:52] <didrocks> seb128: at least 2 persons
[08:52] <jibel> the system is unusable
[08:52] <didrocks> which is 2 less than rotating the screen, agreed :p
[08:52] <seb128> :)
[08:52] <didrocks> still 50%
[08:53] <seb128> did you try if the screen rotate one helps?
[08:53] <duflu> Aha! I wonder if that explains why I can't log into Xorg sessions now I use Nvidia-DRM
[08:53] <seb128> I think Marco said it could impact on other problems
[08:53] <didrocks> seb128: I didn't, Marco didn't tell this could be related
[08:53] <didrocks> but as I have to reboot, not before EOD
[08:53] <seb128> I'm not sure if it is
[08:53] <seb128> k
[08:53] <seb128> let's wait for him to be online
[08:53] <didrocks> yeah
[08:54] <seb128> but yeah, I think either we consider a blocker or not depends of who is impacted
[08:54] <seb128> if it's all nvidia users it's one for sure
[08:54] <seb128> but I was under the impression that Daniel and Marco couldn't reproduce
[08:54] <seb128> which hints it's not all nvidia
[08:54] <didrocks> nvidia + multiple monitors maybe
[08:54] <seb128> we are missing data at this point
[08:54] <didrocks> one monitor is ok
[08:55] <didrocks> which was another test I spent time on
[08:55] <seb128> k
[08:55] <seb128> and there is an easy workaround iirc?
[08:55] <didrocks> alt-f2 + r
[08:55] <didrocks> or go to g-c-c
[08:55] <didrocks> change the scaling to 200%
[08:55] <seb128> k
[08:55] <didrocks> and revert
[08:56] <didrocks> on each boot
[08:56] <didrocks> which I guess most users won't be able to spot
[08:56] <willcooke> Is this issue only when you enable the gsettings key, or all the time?
[08:56] <didrocks> all the time
[08:56] <didrocks> without the gsettings key enabled
[08:56] <willcooke> got it
[08:56] <seb128> and drm-modeset makes a difference?
[08:56] <didrocks> nope
[08:56] <didrocks> it seems to only benefits on the hang up for me
[08:56] <seb128> k, weird that Marco doesn't reproduce
[08:56] <didrocks> I guess he didn't try with 2 monitors ?
[08:57] <seb128> duflu, did you try nvidia on dual monitor? do you see that scaling issue?
[08:57] <seb128> I've no nvidia hardware so I can't test
[08:57] <didrocks> I guess we can script to alt-f2 +r unconditionnally on user login :p
[08:57] <seb128> I should maybe get some at some point, testing on nvidia keeps being an issue
[08:58] <duflu> seb128, not there yet but I have the hardware in hand to test all today
[08:58] <willcooke> I'll see if I can bring something back from Taipei
[08:58] <seb128> willcooke, thx
[08:58] <seb128> didrocks, but yeah, let's try to get it fixed anyway, would be best
[08:59] <didrocks> I hope so, at least, it's not a LTS but I guess if we confirm that it's for all nvidia users with multiple monitors, it's bad
[08:59] <didrocks> especially as the FFe was acked on the fact that there is no regression spotted
[08:59] <seb128> yes, as said if that's the case then yes I agree it's a rls bug
[08:59] <seb128> but we got few reports so far, we lack data...
[09:00] <didrocks> I don't think comparing 2 vs 4 reporters when the dataset is so small makes one one rls bug and one not
[09:00] <duflu> I would say that's a lot of bug reports, given how few users to early testing, and how few of them are inclined to report problems at all
[09:00] <didrocks> when we go to so few reports
[09:00] <duflu> -to +do
[09:02] <seb128> didrocks, well, you use the dataset to argue the rotation fix is not important enough to warrant an upload :p
[09:02] <didrocks> no warrant an upload today
[09:02] <seb128> (half trolling there, but yeah I agree, that's what I said we need to confirm)
[09:02] <didrocks> without waiting for more fixes
[09:02] <seb128> why*
[09:03] <seb128> we are also due GNOME .1 next week
[09:03] <seb128> which fixes a bunch of launchpad milestoned other problems
[09:03] <didrocks> yeah, so that can be uploaded at the same time
[09:03] <seb128> including the touch coordinate being off on x11
[09:03] <didrocks> when I do an upload, I test it throughfully ;)
[09:03] <seb128> that's the spirit :)
[09:03] <seb128> I hope they do release a tarball on time though
[09:03] <seb128> we need it next week
[09:05] <duflu> seb128, probably not complete but https://bugs.launchpad.net/ubuntu/+bugs?field.tag=fixed-in-3.32.1
[09:05] <willcooke> nice, thanks duflu
[09:09] <seb128> andyrock, looks like you need to follow up on https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/423 ?
[09:10] <gitbot> GNOME issue (Merge request) 423 in gnome-control-center "online-accounts: Don't segfault if get_all_providers_cb is called during init" [1. Crash, 6. Component: Online Accounts, Opened]
[09:10] <duflu> willcooke, your touch bug is now there too (hit refresh)
[09:12] <willcooke> duflu, ha!  I was in the process of adding it, and by the time I'd found it the tag was already there :)
[09:25] <duflu> willcooke, it was there days ago but with a typo
[09:25] <duflu> a day ago?
[09:26] <duflu> The most annoying Nvidia bug right now is with Wayland sessions the monitor goes to sleep forever
[09:26] <duflu> And Xorg sessions never start. I assume something is crashing
[09:34] <seb128> duflu, you should call it a week and go enjoy the w.e, you are not going to debug those issue today now
[09:36] <duflu> Actually I just found my Xorg login failure is one of the xrandr-scaling regressions
[09:36] <duflu> Now updating
[09:36] <seb128> duflu, which one?
[09:37] <duflu> seb128, bug 1822616
[09:37] <ubot5`> bug 1822616 in budgie-desktop (Ubuntu) "[nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size" [Medium,Incomplete] https://launchpad.net/bugs/1822616
[09:37] <seb128> is that fixed with the xorg patch uploaded this week?
[09:37] <duflu> I don't think Marco knows about it yet?
[09:37] <seb128> hum, please ping him about those regressions when you find them, he should know about them
[09:37] <seb128> Trevinho, ^
[09:39] <duflu> And until a minute ago it was not verified
[09:41] <seb128> didrocks, k, so QA has been pinged to know if they can help confirming/verifying if those issues happen on any nvidia config with multimonitor, it should help us to asset priorities hopefully
[09:41] <didrocks> ah, great to know!
[09:43] <seb128> Laney, willcooke, do you have any opinion on skipping the ppc64el/s390x webkit2gtk regression to have the current version migrating to disco proper? I doubt we are going to be able to debug on those archs before release (we could try, but it's not easy to have access and webkit is probably not going to be easy to debug)
[09:43] <seb128> I'm leaning toward declaring we don't support desktop/webkitgtk on those archs anyway
[09:44] <Laney> I don't really have opinions
[09:44] <Laney> is this fixed by xnox's sphinx upload in the queue?
[09:44] <seb128> oh, let me look, I didn't notice he had an upload
[09:44] <seb128> lol
[09:44] <seb128> yes, he basically did what I said
[09:45] <seb128> +  * Skip sphinx-doc test on obscure arches, as there is no js-capable
[09:45] <seb128> +    engine available at the moment to test that js in sphinx generated
[09:45] <seb128> +    html docs is good.
[09:45] <willcooke> :)
[09:45] <Laney> so no I don't think that's a good approach
[09:45] <seb128> that's somewhat a misleading description
[09:45] <Laney> but I don't insist on things, make them unsupported if you think that's best
[09:45] <seb128> that test worked in .91
[09:46] <seb128> Laney, well, I just doubt we are going to be able to sort out webkit on those archs by ourselves (and the upstream bug report from j_bicha didn't get any comment)
[09:46] <seb128> so the options are basically to ship wiht .91 on our main archs
[09:47] <seb128> or to ignore the fact that it's buggy on s390x/ppc64el
[09:48] <Laney> ok, your call
[09:49] <seb128> I vote +1 for skipping the error and shipping the stable version, I think it's the better tradeoff if we can't fix the regression on the weird archs
[09:49] <seb128> (which I think we don't have the engineering resources for, or at least it's not the most important thing to work on for us at this point)
[09:49] <willcooke> seb128, I think you're right about making a decision on not supporting desktop on those archs.  I'd like to hear what xnox thinks about that statement
[09:49] <Laney> I don't have opinions, so fine if you think it's fine
[09:49] <seb128> I've no opinion on the way we skip though
[09:50] <Laney> I'll accept that upload
[09:50] <seb128> I would rather have marked the autopkgtest result to skip
[09:50] <seb128> so we keep a reminder there is an issue
[09:50] <seb128> but I will let you know decide what you prefer between the uploaded workaround and skip
[09:50] <seb128> Laney, thx
[09:51] <Laney> no problem, happy to execute
[09:57] <duflu> seb128, Tidier now: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=xrandr-scaling
[09:58] <seb128> duflu, thx
[09:58] <seb128> Trevinho, ^
[09:58] <duflu> Those are all bugs which can be avoided by downgrading mutter
[09:59] <duflu> Although my bug has a strange overlay with nvidia-drm
[09:59] <duflu> *overlap
[09:59] <seb128> I need to get answers from Trevinho today
[09:59] <seb128> he said that the changeset would be a no-op if the option was not enabled, which it's clearly not
[10:00] <seb128> I'm still unclear if the fact that it's not is a bug which he's going to fix or if it was a wrong statement, and in which case if we should revisit the decision based on that or just push forward fixing the issues found
[10:04] <duflu> Well it pains me to leave you unhappy, but also this has been a productive afternoon
[10:04] <duflu> if only for triage
[10:05] <duflu> For the record, a _plain_ Nvidia install and Xorg login works fine with the new mutter here
[10:06] <seb128> new being current git?
[10:06] <seb128> without the scaling work from marco?
[10:06] <seb128> do you mean they fixed things?
[10:06] <duflu> seb128, no I mean current disco with scaling installed but not configured
[10:09] <duflu> Here's a shorter list :)  https://bugs.launchpad.net/ubuntu/+source/mutter/+bugs?field.tag=xrandr-scaling
[10:09] <seb128> k
[10:12] <duflu> One fix landed. Probably only two more required
[10:43] <didrocks> hum, pushing the mutter "rotate screen" fix to a ppa
[10:43] <didrocks> as I can't build esaily with my nvidia binary blob due to deps
[10:44] <didrocks> and rebooting then multiple times to answer duflu's questions… (could have pinged me rather than treating the bug and set it to incomplete)
[10:45] <seb128> yeah, he tends to do that :/
[10:46] <seb128> didrocks, do you remember what was the outcome about the transparency-mode (or was that a Marco thing also?)
[10:46] <seb128> just saw bug #1823303
[10:46] <ubot5`> bug 1823303 in gnome-shell-extension-ubuntu-dock (Ubuntu) "error in 10_ubuntu-dock.gschema.override" [Undecided,New] https://launchpad.net/bugs/1823303
[10:47] <seb128> that's just cosmetic because it ignores the value, but basically we just need to drop the override?
[10:47] <seb128> or did we need a different value/default change?
[10:55] <didrocks> seb128: we agreed to have no transparency when the dock was fixed and a slight transparency in intellihide
[10:55] <didrocks> but I guess Marco never did it in the end
[10:55] <didrocks> on the key
[10:55] <didrocks> the value doesn't exist anymore indeed, I mentioned it to him
[10:56] <didrocks> (it should have been in the upload dropping those)
[10:56] <didrocks> I think depending on if we want to have this ^ behavior or not, the override can still be needed (but set to something else)
[10:56] <seb128> thx
[10:59] <seb128> (I will check with him when he gets online)
[10:59] <seb128> Marrrrrcoooo :)
[11:00] <didrocks> ok, rebooting with my tools to log CPU/MEM usages
[11:01] <didrocks> let's see if I can spot something for duflu on Wayland or Xorg (as it seems I need to test both…)
[11:06] <didrocks> testing on wayland now, brb
[11:06] <didrocks> quit
[11:12] <didrocks> and finally, rebooting with Marco's rotating patch to see if it fixes the scaling issue on boot for me
[11:16] <didrocks> and the bug is still there.
[11:45] <seb128> didrocks, thx for testing
[11:47] <didrocks> no pb
[11:47] <didrocks> answered on duflu's bug as well
[11:48] <didrocks> as the hanging bug (mine) seems to be drm enabled specific, doesn't seem to be a blocker, but as it was working fine for the past year, maybe better to tackle it early…
[11:50] <seb128> yeah
[11:50] <seb128> let's see if daniel has some ideas about that one
[11:51] <didrocks> yeah, having the Shell eating 100% CPU alone when nothing is happening is weird… especially as it's like 20 times ~ 10 minutes in the first few minutes when you open apps/start your session
[12:05] <willcooke> Odd.  seb128,jibel next time you do a fresh install on real hardware.. can you check the sound panel.  My test laptop had the balance set so only the left speaker was on?!  I'm going to reinstall and see if it happens again.
[12:07] <willcooke> yeah, live session is the same
[12:17] <willcooke> hm. odd.
[12:18] <willcooke> Now I cant make it do it
[12:18] <willcooke> ignore.  I will do more testing
[12:22] <willcooke> jibel, on a different note; have you seen the live session not auto-logging-in often?
[12:24] <willcooke> I can reproduce quite often now on the haunted laptop
[12:24] <xnox> willcooke, seb128, Laney - the sphinx packages does generate correct documentation, and it's js works fine. So imho this is not a regression of sphinx on ppc64el/s390x, hence sphinx shouldn't be blocking things. W.r.t. webkit2gtk -> it seems it doesn't have unittests enabled, nor does it have an autopkgtest itself. Imho - it should have those, cause it's a non-trivial package. Even if we remove webkit2gtk on ppc64le/s390x the sphinx patch will
[12:24] <xnox> still need to go in (cause sphinx needs to stay green across the board). As far as I understand webkit2gtk (in some future update) might come back working on s390x/ppc64el but it's a question of timing and noticing it. And it has 74 reverse dependenices on ppc64el/s390x.
[12:25] <xnox> willcooke, seb128, Laney - my preference is to ship a knowngly broken webkit2gtk on ppc64le/s390x cause it seems to be good enough for most packages, based on autopkgtest results.
[12:25] <xnox> (i guess html core/css, but not js-engine)
[12:27] <jibel> willcooke, yes it's an old bug
[12:27] <willcooke> jibel, live session one?
[12:27] <jibel> willcooke, gnome-shell  fails to start
[12:27] <jibel> yes
[12:27] <willcooke> thx
[12:27] <willcooke> hahaha, I think I know what's causing the left audio only
[12:27] <willcooke> more testing needed
[12:28] <willcooke> xnox, thanks for the info
[12:29] <jibel> willcooke, is there an error in the journal?
[12:29] <jibel> or a timeout more likely
[12:29] <willcooke> next time it breaks I'll look
[13:16] <willcooke> I worked out what's going on with the audio balance :)
[13:16] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823336
[13:16] <ubot5`> Ubuntu bug 1823336 in gnome-shell (Ubuntu) "Scrolling the sound panel with the mouse wheel can result in sliders being moved by mistake" [Undecided,New]
[13:16] <willcooke> not sure if it's really a bug
[13:25] <Laney> xnox: your analysis seems a bit wrong. excuses was saying that webkit2gtk broke sphinx on those arches, which seems like it did do
[13:25] <Laney> might be right to not care about it, but as far as I can tell the machinery did the right thing there
[13:44] <seb128> xnox, Laney, right, my understanding is that the javascript bits are working on s390x/ppc64el with .91 and regressed with .92 so it's a real webkit2gtk bug and the test were right to fail/block it
[13:44] <seb128> willcooke, weird the balance bug, I never saw that one
[13:45] <willcooke> I think screen size has a lot to do with it
[13:47] <seb128> with sound balance?
[13:48] <willcooke> the general layout of the screen meaning that balance slider is under the pointer when you move from the sound panel selector in the list to the main sound panel
[13:49] <seb128> ah
[13:51] <seb128> willcooke, sounds like the bug you opened should have been against g-c-c not gnome-shell? also unsure it's a bug at all, scrolling over a slider has always been moving the slider and is the expected behaviour afaik
[13:56] <willcooke> yeah it's probably not a bug.  I've never seen it happen before and I think it's generally more difficult to trigger on the old layout.  So.... ?  dunno.  I'll log it upsteam and see what they say.
[14:14] <Trevinho> morning
[14:31] <oSoMoN> good morning Trevinho
[14:31] <Trevinho> hi oSoMoN
[14:33] <didrocks> Trevinho: I'm unsure I'll have time to bisect, are every commits buildable in https://gitlab.gnome.org/3v1n0/mutter/commits/xrandr-scaling?
[14:34] <Trevinho> didrocks: should be yes
[14:34] <Trevinho> didrocks: but I'm quite sure it's one of the first ones at this point
[14:34] <Trevinho> but let me try to reproduce this first, then I'll ask you again for help :P
[14:34] <didrocks> yeah
[14:35] <didrocks> Trevinho: FYI I tested your rotating monitor fix, but yeah, it didn't have any effect
[14:35] <Trevinho> yeah I was looking at the backlog, since I just read the highlighths so far, but I wanted to read it full first of commenting
[14:35] <Trevinho> but it was expected, it might have not been true in wayland, but in X11 there's no change.
[15:43] <xnox> Laney, "excuses was saying that webkit2gtk broke sphinx on those arches" no that is not the case, please read the actual autopkgtest in sphinx that failed. The test that failed in sphinx, is a python script which imports webkit2gtk gir, loads a webpage of generated docs, and tries to excersize js search within docs. The sphinx docs themselves generate correctly on those architectures, and sphinx has no build/runtime dependencies on webkit2gtk.
[15:43] <xnox> it's just one autopkgtest uses webkit2gtk as an automated "web-browser window"
[15:43] <xnox> Laney, sphinx is not broken on ppc64el/s390x
[15:43] <xnox> (nor the generated docs)
[15:45] <Laney> thanks, I did read it
[15:45] <Laney> when A triggers B, and B fails, it is an indication that A is broken if all is working well
[15:46] <Laney> that's what is happening here
[17:52] <willcooke> Have a good weekend all.
[17:52] <willcooke> l8r
[19:23] <Eickmeyer> clobrano: I just took a look at Ubiquity running with the patched version of materia-gtk-theme, and I have reason to believe the _xfce.scss file may have needed to be patched as well since Ubuntu Studio uses Xfce.
[19:26] <Eickmeyer> That said, the patch didn't work as expected.
[19:27] <clobrano> Eickmeyer: I thought it used gnome. So I need to install xfce first
[19:27] <Eickmeyer> Okay.
[19:28] <Eickmeyer> Also, you spelled Ubiquity wrong in the original patch / PR, and I didn't catch it until now. :)
[19:41] <clobrano> Oops
[23:06] <flusheddata> Hi, has anyone been able to import gnupg keys into seahorse?
[23:08] <flusheddata> I cannot import my keys nor can I import X.509 certs either.. :-(
[23:08] <sarnold> what error do you get?
[23:08] <flusheddata> The import button is greyed out
[23:08] <flusheddata> when trying to import X.509'x
[23:08] <flusheddata> s
[23:09] <gQuigs> flusheddata: what Ubuntu release?
[23:10] <flusheddata> I can use my X.509 certificate and my gnupg keys with Thunderbird/Enigmail.
[23:10] <flusheddata> 18.10
[23:11] <flusheddata> I got aware of something going wrong when I tried to gpg sign a LibreOffice document. In windows I can sign with pgp/gnupg, but not with ubuntu 18.10.
[23:12] <sarnold> does it work from the command line?
[23:12] <flusheddata> yes, like a charm. Sorry I should habe mentioned that
[23:12] <gQuigs> wow, that was a big bump in version for seahorse 3.20 to 3.30 for 18.04 to 18.10
[23:12] <flusheddata> *have
[23:13] <flusheddata> cli gpg works like a charm. Every option
[23:13] <flusheddata> The thing is that I have noted that to me Seahorse seems a bit buggy.
[23:14] <flusheddata> Also, after a while double clicking on a key in order to see its options, when I double click to enter again the window is blank
[23:14] <flusheddata> Without any control (button, field, etc)
[23:15] <sarnold> is there anything in the ~/.xsession-errors? quite often gui programs will dump warnings and errors to stdout, and usually that winds up in that file
[23:16] <flusheddata> Anyway I can use gpg graphically as the seahorse-nautilus plugin works fine
[23:16] <flusheddata> Going to check...
[23:17] <gQuigs> flusheddata: it also looks like some of the dialogs have been redone in disco..    might be worth trying an upgrade (although still beta..)
[23:18] <gQuigs> you can also use  journalctl -f   while you open it
[23:18] <flusheddata> There is not such a .xsession-erros file in my home
[23:18] <flusheddata> ..folder
[23:19] <flusheddata> gQuigs: I have tried it in virtualbox, but I think I am going to do a fresh install of 19.04 in my new two ssd's
[23:23] <flusheddata> Oh my...
[23:23] <flusheddata> abr 06 01:22:28 TPE550 seahorse[8910]: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed
[23:23] <flusheddata> abr 06 01:22:28 TPE550 seahorse[8910]: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed
[23:23] <flusheddata> abr 06 01:22:28 TPE550 seahorse[8910]: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed
[23:23] <flusheddata> abr 06 01:22:28 TPE550 seahorse[8910]: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed
[23:23] <flusheddata> abr 06 01:22:28 TPE550 seahorse[8910]: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed
[23:23] <flusheddata> Sorry
[23:24] <gQuigs> https://pastebin.ubuntu.com/
[23:24] <flusheddata> Thanx
[23:25] <flusheddata> https://pastebin.ubuntu.com/p/xk7gTV8SKs/
[23:25] <flusheddata> You know, I am a bit newbie and English is not my first language either.
[23:26] <gQuigs> flusheddata: I'm not that good at reading those, but I don't see anything obvious that I would consider related from it...   my last guess would be seahorse expects a certain file extension...
[23:27] <gQuigs> many are not actually useful error message IME
[23:27] <sarnold> they all feel plausibly related
[23:28] <sarnold> a box is grey, why is it grey, maybe because it's not actually a box. or isn't a container. or whatever.
[23:28] <sarnold> but gtk apps just tend to spew this stuff :(
[23:28] <flusheddata> Anyway, I think it could investigate more
[23:29] <flusheddata> Thank you so much you both
[23:29] <hggdh> interesting. Ran seahorse myself, and had it die with an X error (but I am under KDE, and on Disco, so there)
[23:30] <flusheddata> I am affraid Seahorse has some problems
[23:30] <hggdh> flusheddata: it might, indeed. But my experience is probably different from yours -- different versions, and DE
[23:31] <flusheddata> I tried managing my gpg keys with Kleopatra (tough I am gnome) and it works fine.
[23:31] <flusheddata> Sure
[23:33] <flusheddata> hggdh: try to double-click on another person's public key and exit several times. Eventually the opened window would not show controls at all. Well at least in gnome
[23:34] <hggdh> flusheddata: cannot, right now, seahorse dies. Will have to re-login under Gnome to sanely check