=== Mamarok_ is now known as Mamarok === Mamarok is now known as Guest82909 === Guest82909 is now known as Mamarok_ === Mamarok_ is now known as Mamarok [11:08] 'Morning folks [13:39] preparing 5.18.5 bugfix for focal :) [13:45] Very good. :) [13:45] https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-kde/+bug/1876876 [13:45] Launchpad bug 1876876 in xdg-desktop-portal-kde (Ubuntu) "SRU tracking bug for plasma 5.18.5 in Focal" [Undecided,New] [13:49] SRU's are required for all non-backports related point releases? [13:52] @DarinMiller, Yes [13:55] How did you generate the "Affects " list? [13:57] @DarinMiller, This time I basically inspected the upstream changelog and did it manually, choosing the packages with bugfixes. [14:30] Nate says only 2 patches are required to prevent slowness in 5.70. That seems reasonable.... [14:31] @DarinMiller, Where does he say that? [14:32] Only needs one patch as far as I know. [14:37] the kirigami patch was in 5.69, and only defined the 'very long duration', but did not use it [14:44] Nate sent an email a few minutes ago. https://cgit.kde.org/plasma-workspace.git/commit/?id=2958702524348e9e4fcbdf490be731e92b353dad and https://cgit.kde.org/plasma-desktop.git/commit/?id=f3bbc0ba0e34ea1b34b106228c02d85865ed904a [14:48] or you can just revert the culprit change in plasma framewarks for now [14:50] Is that managed via quilt or how is a reverted patch generated? [14:53] from the kde git, checkout the kde git tag for the 5.70.0 release. find the hash for the commit and do 'git revert hash'. then 'git show > patch' give you the patch to use with quilt [14:56] Nates blog gave me the impression several packages were affected by the change. Do you have an easy way to find all of them? (Ask Nate?) [14:57] I did ask, but will check again. I think he just decided on a different way to advise to fix it/ [14:58] The kirigami patch was in 5.69. It enabled a feature but did not use it. [15:03] @DarinMiller Nate says either way works. I'll just need to decide what make most sense for us [19:13] then we'll have to drop patches later, @RikMills? [19:19] yes, either way [19:23] 20.04 is so far wonderful [19:23] I keep wondering if I should just upgrade my travel lappy to Next [19:23] cuz who wouldn't want to be groovy? [19:24] I just filed this bug on behalf of my82 year old father. So even though it's working great for us, there are a few hiccups. https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1878080 [19:24] Launchpad bug 1878080 in hplip (Ubuntu) "HPLIP fails to install working printer and scanner drivers." [Undecided,New] [20:37] So, latest Studio live CD spin can't launch system settings. https://paste.ubuntu.com/p/YDzwPDRfXx/ [20:38] Looks like something wrong with kirigami. [20:39] * Eickmeyer just read the backscroll, looks like you already know. [20:42] Actually, the bug I found might *not* be related. RikMills, any insight? [21:17] Eickmeyer: I'll have to loo in the morning my time. sorry [21:18] RikMills: No worries. Just was wondering if that was happening on Kubuntu as well. Chances are it is. [21:18] it could be some qml parts of frameworks migrating from proposed before kirigami itself has [21:18] Ah, that would explain it. [21:19] our system does not handle qml deps as it does library ones