=== arraybolt3_ is now known as arraybolt3
[12:30] <BluesKaj> Hi all
[12:54] <ahoneybun[m]> heyo BluesKaj 
[12:59] <BluesKaj> hey ahoneybun[m]
[13:04] <ahoneybun[m]> heyo
[13:33] <aaronprisk[m]> Meta had a big booth at SCaLE this past weekend where they demonstrated some of their ML/AI tools and they all ran on Kubuntu. Kudos to you folks!
[13:55] <mparillo> And we have used the phabricator wiki.
[14:03] <RikMills> aaronprisk[m]: that is very interesting. thanks!
[15:01] <RikMills> plasma 5.27.3 and fw 5.104 is in backports for kinetic
[15:26] <arraybolt3> mmikowski: Sadly, the Plasma crashes are still happening, but I figured out what's triggering them. When I had my notifications on permanent "Do Not Disturb", they stopped. When I allowed notifications again, they started. Somehow when a notification is triggered, it's causing things to go awry.
[15:27] <arraybolt3> Anyway I'm trying some random things to see if it's a problem purely on my side - there's no way that the things I'm seeing wouldn't be noticed by almost every other user of Kubuntu were this widespread, so I'm assuming it's not widespread.
[17:02] <mmikowski> arraybolt3: from what I have seen, RikMills (please correct me if I'm wrong) has tightened down kubuntu-ppa/experiemental so that it is representative of release intent. Of course, it could still eat your cat, but that's why ppa-purge was invented ;) One weird effect he resolved last week was to add i386 libs that are required by Steam, and that
[17:02] <mmikowski> apparently broke the upgrade. Since then, upgrade have been dreamy-good.
[17:05] <RikMills> yes, I rebuilt it all for all the architectures that the PPAs normally build. means that should we decide to ship it somewhere, it can be copied straight into the official PPAs
[17:05] <RikMills> for inital testing I had only build for amd64 to make things quick and easy
[17:06] <mmikowski> RikMills and arraybolt3: also, not seeing plasma-shell crashes here. Theme switching is still not-so-good, but usually just doesn't full work (85%) or crashes system settings (5%), and then plasma-shell (5%). Those are just estimates based on my experience and that of other testers.
[17:06] <arraybolt3> Very odd. I wonder if maybe it's because Element makes very frequent notification popups?
[17:06] <arraybolt3> (I'm using Element as a Matrix chat client.)
[17:07] <mmikowski> btw, we are running 5.27 on 6 machines currently, and almost all feedback has been "please upgrade this".
[17:07] <mmikowski> RikMills: Thank you, that's great to hear.
[17:09] <mmikowski> arraybolt3: Maybe see if it's Matrix notification related? Stranger things have happened.
[17:09] <mmikowski> One thin we used to see here *all the time* in 5.24.7 is Discover "crashing' after close.
[17:09] <arraybolt3> Might be, though I don't have any other program that generates the number of notifications that Element does. Except for the Element web app, I could switch to that I guess.
[17:10] <mmikowski> Yeah, just for a bit (a day maybe?).
[17:10] <arraybolt3> Will do once I get around to it.
[17:10] <mmikowski> Also, how often does it (plasma-shell?) crash?
[17:10] <mmikowski> haha
[17:11] <arraybolt3> Used to be multiple times a day, now it's down to about once a day.
[17:11] <arraybolt3> It stopped entirely when I turned notifications off.
[17:11] <mmikowski> Well at least it hasn't eaten your cat.
[17:12] <arraybolt3> lol, why does it seem more likely that the cat would try to eat it...
[17:14] <mmikowski> I don't have matrix (I use TheLounge), so testing here is a bit out of range.
[17:15] <mmikowski> If we knew that it is specific to Matrix, we could at least provide advice and move forward.
[17:18] <arraybolt3> K, will try.
[18:27] <mmikowski> thanks arraybolt3. I very much appreciate your help.
[18:29] <arraybolt3[m]> Glad to help! I just switched to the PWA, if this works then I'll file a bug with Element.
[18:38] <mmikowski> thanks mate. bb after lunch.