u/bionich

I'm running Debian 14 forky as a Proxmox VM for testing purposes only. The latest updates to Gnome broke one of the VPN types: Cisco compatible (vpnc). My OpenVPN and Wireguard VPNs all work fine. Also, vpnc runs fine from the command line, but in Gnome it appears to not even try to activate the Cisco vpnc VPNs. I use Debian for work to manage a lot of remote equipment, so VPN's are huge part of my daily workflow. That's why I'm running testing in a LAB. I want know it works well when it's time to go live sometime next summer.

I reported some weeks back that my Brewzilla 110v was arching at the power plug. I replaced the cable and the A/C input port with properly gauged replacements. It was good for a few brews and then yesterday after a brew day the power cable was fused to the port again. Needless to say I'm done with Kegland products. If you're not familiar with this issue it's pretty common with the US 110v the system. I've read that Kegland believes it's because the system was moved during operation. In both cases, the unit was not moved, at all. I don't want to bash their products, but I also don't want to burn my house down.

Anyway, I've ordered a Clawhammer 10 gallon system. If anyone has any suggestions for a smooth operation, please share! I would rather not use a hop spider. Can anyone share their experience with free range hops in the kettle? I did order a whirlpool arm to help control the hops and keep them out of the pump. I'm a fan of whirlpool additions.

Thanks.

A couple of days ago I blew out one of the usb-c ports on my Framework 13, 13th Gen Intel. The rear right usb-c port is completely dead. This was just the inspiration I needed to order a new Framework Pro main board with 16 gigs of LPCAMM2 memory. I have 32 gigs in my existing Framework laptop 13 but thankfully I no longer need that extra memory.

I think I may have manifested the death of the port, because recently I was thinking about the better battery life of the Panther Lake board. "Someday.", I thought. Too funny!

Debian 14 - Forky is in testing and it's wonderful. I downloaded it the other day and set it up in Proxmox for testing with all of my standard software and feature setups. I have shell scripts to setup my software so it all goes very quickly. Even though it's in testing everything I use works great. That includes multiple VPNs (OpenVPN, WireGuard, and vpnc), VeraCrypt, and Teamviewer. Everything installed, ran, and integrated nicely into Gnome 50 without issues. It's seems to be solid and stable. I realize that the packages haven't been frozen yet and will change in the next year before the release, but for what's there now - wow!

I look forward to seeing how their new plan for "reproducible builds" works out. It seems like a lofty goal, but also a very rewarding one, security wise. As far as I know the only distributions to date to pull that off are NixOS and Tails, but there could be others. At any rate it's going to be tough waiting a year to put Debian 14 on my production machines.

Well done Debian developers!

I just learned that this is a common problem with the Gen 4 35L 110v North American version. You can see some images and read more about it here.

I was able to finish my brew day with no issues, but when I went to clean my BZ the power cord would not free itself from the power supply inlet. It had a total meltdown; the power cord and the AC inlet had fused to each other.

I've already ordered a new power cord and AC power inlet, and It should be a quick 5 minute fix. I just hope it never happens again. Otherwise, I'll be forced to drop some big bucks on a Clawhammer system, which is around $1,500 USD. I really want to keep my Brewzilla. I've only brewed about 20 batches on it.

Because so many folks have had failed BIOS updates, doesn't it make sense for Framework to get on the bandwagon and provide boards with ability to recover from a failed BIOS update? To say someone has to "purchase a new mainboard" due to an update failure seems a little ridiculous to me.

Having a second BIOS chip holding a BIOS factory default so the system can fail over in the event of a main BIOS update failure is getting more common, and it seems like something you want, particularly in the new "Pro" lineup where the computer is likely mission critical.

What are your thoughts?

Today all of the users who access a shared calendar cannot make updates to that calendar. The update shows up for a few seconds and then disappears?

I'm currently trying the uncheck "Turn on shared calendar improvements" feature in Outlook to see if that works.

Anyone else experiencing this issue today?

Today all of the users who access a shared calendar cannot make updates to that calendar. The update shows up for a few seconds and then disappears?

I'm currently trying the uncheck "Turn on shared calendar improvements" feature in Outlook to see if that works.

Anyone else experiencing this issue today?