[04:13] <guiverc> calamares still says 23.10 (for noble)... you don't need/want a bug report for that do you...  given all the changes in calamares; was that missed?
[04:13] <lubot> [telegram] <tsimonq2> ...huh?
[04:13] <lubot> [telegram] <tsimonq2> Where does it say 23.10? :)
[04:15] <arraybolt3> The welcome image.
[04:15] <arraybolt3> Should be easy enough to fix with a slight tweak to the text in the image.
[04:15] <guiverc> ^  (when first started..)
[04:16] <arraybolt3> I'm currently engrossed in writing a system tray app in Qt Widgets, but I'll try and remember to do that tomorrow (I'm starting my year a bit early it seems :P).
[04:17] <arraybolt3> (by choice, I love working on Lubuntu and this is helping me keep from burning out in other areas)
[14:24] <lubot> [telegram] <Eric> Hello, I'm not Sure if this is the right place, but where would I report a possible Lubuntu bug?
[14:26] <lubot> [telegram] <tsimonq2> Depends on what's going on. :) (re @Eric: Hello, I'm not Sure if this is the right place, but where would I report a possible Lubuntu bug?)
[14:27] <lubot> [telegram] <kc2bez> This is the development channel. Bugs should go on launchpad. Issuing a `ubuntu-bug PACKAGE` Should start things. (re @Eric: Hello, I'm not Sure if this is the right place, but where would I report a possible Lubuntu bug?)
[14:27] <lubot> [telegram] <tsimonq2> This is true, but also, you've piqued my curiosity ;) (re @kc2bez: This is the development channel. Bugs should go on launchpad. Issuing a ubuntu-bug PACKAGE Should start things.)
[14:27] <lubot> [telegram] <Eric> Thank you! Is there a way to see all reported bugs? I wouldn't want to report something that's already been reported
[14:28] <arraybolt3> Generally it's best to just report, just in case your issue is a bit different.
[14:28] <lubot> [telegram] <tsimonq2> We do have a team on Launchpad called the Packages team. Off the top of my head, you're looking for https://bugs.launchpad.net/~lubuntu-packaging (re @Eric: Thank you! Is there a way to see all reported bugs? I wouldn't want to report something that's already been reported)
[14:28] <lubot> [telegram] <tsimonq2> This though, 100% (re @lubuntu_bot: (irc) <arraybolt3> Generally it's best to just report, just in case your issue is a bit different.)
[14:28] <arraybolt3> Many projects hate duplicates, Ubuntu doesn't hate them anywhere near as much.
[14:29] <arraybolt3> In fact if two people independently submit the same bug, that helps us prioritize what to fix via the bug heat system :D
[14:30] <lubot> [telegram] <Eric> Ahh ok. So last night, I was transferring pdf files via bluetooth from my laptop to my phone, and while the files were transferring, I noticed I could no longer refresh my open tabs in Opera. I would get an error message saying that I could not connect, or something along those lines. As soon as the files finished transferring, I was able to refresh the tabs and navigate to new websites though (re @tsimonq2: This is true, but also, y
[14:31] <lubot> [telegram] <Eric> Thanks for the launchpad link, I will go there now (re @tsimonq2: We do have a team on Launchpad called the Packages team. Off the top of my head, you're looking for https://bugs.launchpad.net/~lubuntu-packaging)
[14:33] <lubot> [telegram] <tsimonq2> Off the top of my head, that sounds like an Opera bug. Allow me to explain why.
[14:33] <lubot> [telegram] <tsimonq2> 
[14:33] <lubot> [telegram] <tsimonq2> Opera likely has a mechanism to support Bluetooth in some capacity. If it's listening on the Bluetooth device, and both Opera and the monitor are running in the same thread, Opera is just busy listening, and you won't be able to do much. 
[14:33] <lubot> [telegram] <tsimonq2> 
[14:33] <lubot> [telegram] <tsimonq2> That's just my best guess. The next step would be to see if e.g. Firefox does the same thing. If another web browser does the same thing, we've _isolated that variable_. It's Bluetooth. If other browsers work, but Opera doesn't, I have a good feeling it's what I described.
[14:33] <lubot> [telegram] <tsimonq2> 
[14:34] <lubot> [telegram] <tsimonq2> The reason this is important to determine now is that it helps you figure out which package to file it against. We switched Bluetooth management GUIs between 23.10 and (what will become) 24.04, so you may also consider trying that.
[14:34] <lubot> [telegram] <Eric> Ahh got it! Thank you for all your help, you've all been fantastic and really helpful. I will try other browsers to dee if the issue persists.
[14:35] <lubot> [telegram] <tsimonq2> Please keep us posted! You can't be the only Opera user on Lubuntu; I'd be really interested to hear about what you find :)
[14:35] <lubot> [telegram] <tsimonq2> 
[14:35] <lubot> [telegram] <tsimonq2> Let us know if we can help further, otherwise you're welcome to stick around for as long as you'd like
[14:36] <lubot> [telegram] <Eric> Thank you! I will keep you posted then.
[16:37] <lubot> [telegram] <kc2bez> Firmware updater on noble should produce something other than just a white screen right?
[16:38] <lubot> [telegram] <kc2bez> https://matterbridge.lubuntu.me/f761b7e3/file_10304.jpg
[16:59] <tsimonq2> Can confirm. Syncing a plain Ubuntu desktop ISO now to verify it's not just us.
[17:49] <lubot> [matrix] <kc2bez> Also weird, Picom wasn't started. That didn't fix the all white window though.
[17:51] <lubot> [matrix] <kc2bez> Ah, Picom had a recent sync. Guessing that removed the autostart.
[18:06]  * tsimonq2 hunts down the syncer...
[18:07] <arraybolt3> the autostart was set in Picom? I thought that would have been in one of our packages for some reason.
[18:07] <tsimonq2> Yeah, I'm kinda confused, Dan, what was this about exactly?
[18:10] <lubot> [matrix] <kc2bez> We bumped into the issue where Picom was started automatically as something was set in the packaging. When we set it in our default settings it tried to start again and was throwing an error. I think wxl changed default settings a cycle ago?
[18:13] <lubot> [matrix] <kc2bez> I guess I committed that 👀 https://git.lubuntu.me/Lubuntu/lubuntu-default-settings/commit/dd57ca0858be8aa46bb646360fb06ddba561d12f
[18:13] -ubottu:#lubuntu-devel- Commit dd57ca0 in Lubuntu/lubuntu-default-settings "Remove Picom autostart."
[18:15] <lubot> [matrix] <kc2bez> Anyway, my install today didn't have Picom running, I had to start it.
[18:44] <lubot> [telegram] <lynorian> I really love to contribute I don't have to get past a job interview which I can't do for the life of me (re @lubuntu_bot: (irc) <tsimonq2> https://twitter.com/tsimonquigley2/status/1740110615404806483)
[18:48]  * lubot [matrix] <kc2bez> throws laptop like a Frisbee
[18:49] <lubot> [matrix] <kc2bez> I think firmware-updater is hung up on apparmor
[19:12] <arraybolt3> welp, that would do it, and yikes
[23:21] <arraybolt3> Opinions on seeding breeze-gtk-theme and enabling it by default? That would give a more Lubuntu-y look to some of the GTK apps we ship.
[23:23] <arraybolt3> (in particular it will probably help the bluetooth manager and nm-connection-editor, it's not perfect for either but it's fairly good)
[23:24] <arraybolt3> https://i.imgur.com/h3GRvOB.png vs https://i.imgur.com/HvDbV1M.png
[23:24] <arraybolt3> left is normal GTK theme, right is Breeze
[23:26] <lubot> [telegram] <lynorian> right looks better but glad we are having this conversation before I put screenshots of gtk things in the manual
[23:29] <lubot> [telegram] <kc2bez> Agreed, it does seem better.
[23:33] <lubot> [telegram] <tsimonq2> LGTM shipit JFDI 🚀
[23:33] <lubot> [telegram] <tsimonq2> 😁
[23:35] <arraybolt3> sounds like we have a plan
[23:35] <lubot> [telegram] <tsimonq2> arraybolt3: pls add to hacky janky default settings backports :P
[23:36] <lubot> [telegram] <tsimonq2> (Or I can, if you agree that my approach is messy. :P)
[23:36] <arraybolt3> default settings backports?
[23:36]  * arraybolt3 can't tell if you mean lubuntu-backports-staging or something else
[23:37] <lubot> [telegram] <kc2bez> Was that talk to Texans? :P
[23:37] <lubot> [telegram] <tsimonq2> ~lubuntu-dev/backports
[23:37] <arraybolt3> +1
[23:37] <lubot> [telegram] <tsimonq2> Talk to Texans would have started misspelling by the second word :P (re @kc2bez: Was that talk to Texans? :P)
[23:37] <arraybolt3> though... slight problem with that...
[23:37] <arraybolt3> breeze-gtk-theme isn't installed by default.
[23:37] <arraybolt3> I'd have to make it a Depends or Recommends of something.
[23:37] <lubot> [telegram] <tsimonq2> Yeah, so here's the hacky part :P
[23:37] <arraybolt3> I can do that easily enough though.
[23:37] <arraybolt3> ah, I see your point
[23:38] <arraybolt3> perhaps we shouldn't *seed* it and just make lubuntu-default-settings depend on it since, well, the default settings will now depend on it
[23:38] <arraybolt3> so that's not hacky at all, that's easier even
[23:38] <lubot> [telegram] <tsimonq2> I've split Depends and Recommends randomly between artwork and default settings to get them installed in Backports :P
[23:38] <arraybolt3> fun
[23:38] <lubot> [telegram] <tsimonq2> yes that too :)
[23:39] <lubot> [telegram] <kc2bez> Less seeding more depending :D
[23:39] <arraybolt3> Got very far doing the updater - it can detect when there's updates, how many updates there are, and categorize them and display them in a tree view now.
[23:39] <arraybolt3> I have to fix the label at the top and detect the number of security updates still, and make the install and details buttons do something.
[23:40] <arraybolt3> But after that we have an alpha-quality prototype that we can flesh out and release.
[23:40]  * arraybolt3 's fingers are so cold I'm having a hard time typing :P
[23:40] <arraybolt3> this year's temperatures are not fun
[23:41] <arraybolt3> *turns on hand warmer*
[23:59] <lubot> [matrix] <kc2bez> Ping @kc2bez