![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/d3d059e3-fa3d-45af-ac93-ac894beba378.png)
When my pixel 5a decided to stop using the screen, I was able to do a full phone backup using the OTG to plug in a keyboard. Ridiculous but was a fun troubleshooting moment
When my pixel 5a decided to stop using the screen, I was able to do a full phone backup using the OTG to plug in a keyboard. Ridiculous but was a fun troubleshooting moment
Was disables for some reason. Enabling it fixed the issue
Ah that fixed it thanks! Should probably be under look and feel? Is it on by default? I don’t remember turning it off
I can open a bug report, but list view is still not showing the vote scores unfortunately
I have no complaints with the framework keyboard, is there a particular issue you’re concerned about? The track pad is almost apple quality. Certainly better than most laptops I’ve used.
I figured, just wanted to let others know to manage expectations
Also thanks for your work on this, its a great app
Upvote count is still missing when using posts set to list view
Love my 11th gen framework, but there is an issue with the 11th gens where the CMOS battery will die rather quickly. If it does die then the laptop needs to be plugged in to turn on, even if it is fully charged. Framework is aware of the issue and will send a free replacement battery or, if you can solder, a mod that will eliminate the issue for good.
Still love framework and would definitely recommend them - but the 11th gen line (their first product) has a few gotchas
I was looking into this last night, what’s the current Dev status of termux? I saw the last release is from 2022 and there’s a call for more maintaiers.
Friendly reminder that Trader Joes is another Union busting shit company
Not sure your budget, but you might be interested in one of these https://us.starlabs.systems/pages/starlite
I’ll start this by saying I’m not familiar with either model, but as a general rule, always go x86 when you can. The Intel processor is going to be much better supported. You might get the snapdragon version to run, but it likely isn’t supported by mainline Linux.
That being said, touch screen support on Linux is improving rapidly, but still isn’t quite there. Make sure you’re aware of the user experience before buying so you won’t be disappointed.
Also, my unsolicited 2 cents, I would try to avoid buying lenovo. I’ve had the unfortunate responsibility of fixing a few of their products (an all-in-one and a few laptops, including a new thinkpad) and can confidently say their reliability, and repairability have greatly diminished. They use cheap parts and are in general, poorly designed.
Onshape hands down. Browser based so there’s no compatibility issues. It’s super easy to use and pretty powerful. Its free for hobbiests (the caveat being your models will be publically accessible). We use it exclusively at work and it’s been awesome.
I’d love a good Foss CAD package but there are too many issues with the current ones for me to make the jump.
That’s definitely something to be aware of, but the vdev expansion feature was mergered and will be released probably this year.
Additionally, it looks like the authors main gripe is the current way to expand is to add more vdevs. If you plan this out ahead of time then adding more vdevs incrementally isn’t an issue, you just need to buy enough drives for a vdev. In homelab use this might an issue, but if OP is planning on a 40 drive setup then needing to buy drives in groups of 2-3 instead of individually shouldn’t be a huge deal.
You need to research raid 1,6,10 and zfs first. Make an informed decision and go from there. You’re basing the number of drives off of (uninformed) assumptions and that’s going to drive all of your decisions the wrong way. Start with figuring out your target storage amount and how many drive failures you can tolerate.
I’ve been using migadu and its been great so far
Downloaded from the KDE store
The command was rm -rf $pathvariable
Bug in the code caused the path to be root. Wasn’t explicitly malicious
Yeah that’s the one I meant. Damn, that’s too bad
This isn’t a joke. Often times rewriting features like this will allow the code to be more streamlined and use the latest KDE library features. This is brining new features using modern and more maintable code that solves long standing issues. Fixing the old code sometimes isn’t worth the effort for a variety of reasons (based on unmaintained libraries, the original code might have been written a while ago so it’s had many revisions of fixes that necessarily complicated the code, etc.)