[01:19] <valorie> virtually?
[01:19] <valorie> b/c I thought you were over in ID these days?
[01:19] <valorie> Eickmeyer: ^^^
[01:20] <valorie> sorry we were at costco and dinner
[01:20] <Eickmeyer> valorie: Nope, I'm in Renton. Thought I mentioned this last time we chatted.
[01:20] <valorie> oh very cool
[01:20] <valorie> nearly as close as before
[01:23] <Eickmeyer> Yep
=== guiverc2 is now known as guiverc
[10:30] <IrcsomeBot> <myfenris> mine the one not showing in systray is from snap apps (re @IrcsomeBot: <arraybolt3> Eickmeyer: I assume all of those apps are installed as Snaps? Or are some of them installed other ways?)
[10:31] <IrcsomeBot> <myfenris> +1 not happening on ubuntu desktop (re @IrcsomeBot: <Eickmeyer> It's not a problem on Edubuntu or Ubuntu Desktop, so it's gotta be a Plasma thing.)
[12:26] <IrcsomeBot> <myfenris> btw, what are the dependencies this time ? is it -4t64 ?
[12:41] <BluesKaj> Hi all
[17:45] <arraybolt3> So, update on the issue with the app indicators, I noticed something of interest.
[17:46] <arraybolt3> See the blank space between my notification bell and the Barrier icon here? https://i.imgur.com/fMonAwn.png
[17:46] <arraybolt3> That space appeared when I launched the Element Snap.
[17:46] <arraybolt3> So obviously *something* is managing to get through apparmor, but just not fully.
[17:47] <arraybolt3> (also when you're using two computers, Barrier is awesome turns out)
[19:14] <IrcsomeBot> <myfenris> yes, i noticed this too (re @IrcsomeBot: <arraybolt3> See the blank space between my notification bell and the Barrier icon here? https://i.imgur.com/fMonAwn.png)
[19:21] <IrcsomeBot> <myfenris> waiting for the 5.27.11-0ubuntu1~ubuntu24.04~ppa1 to finish build and hoping this fixed the app indicator/systray
[19:21] <IrcsomeBot> <myfenris> waiting for the 5.27.11-0ubuntu1~ubuntu24.04~ppa1 dependencies to finish build and hoping this fixed the app indicator/systray
[19:34] <IrcsomeBot> <sgmoore> Ugh, so sorry my son passed and I need the week to sort stuff out. Maybe @RikMills or Santa can kick them. Hopefully the t_64 mess has settled.
[20:42] <IrcsomeBot> <myfenris> i can confirm element-desktop from .deb works in the systray
[20:42] <IrcsomeBot> <myfenris> i can confirmed element-desktop from .deb works in the systray
[20:43] <IrcsomeBot> <myfenris> i removed the snap :)
[20:44] <IrcsomeBot> <myfenris> so its must be something with apparmor/snap related (re @IrcsomeBot: <arraybolt3> So obviously *something* is managing to get through apparmor, but just not fully.)
[20:45] <IrcsomeBot> <myfenris> https://irc-attachments.kde.org/4de0d79c/file_73512.jpg
[20:46] <IrcsomeBot> <myfenris> the telegram is from snap so it not in the systray
[20:46] <IrcsomeBot> <myfenris> the telegram is from snap so its not in the systray
[21:18] <arraybolt3> armhf appears to still be a disaster, not sure if rebuilds are going to be possible quite yet
[23:35] <arraybolt3> New kubuntu-installer-prompt uploaded to the archive and to Git - this fixes a bug where users could accidentally close modal windows (like the one that shows that a language change is in progress), thus unlocking the rest of the UI mid-change. Also open WiFi networks can now be connected to.
[23:36] <arraybolt3> (Note however that WiFi that is protected by a captive portal does not work. Users who are stuck with that will have to "Try Kubuntu", connect from within a full Plasma session, then launch the installer.)
[23:37] <arraybolt3> s/does not work/will not work/ (because I didn't actually test a captive portal network since I don't have any of those nearby)