Hasn’t this been an issue a few days ago? Maybe only with testing.
Hasn’t this been an issue a few days ago? Maybe only with testing.
Foot because it’s sway default. It’s also configurable, has shortcuts and sixel support.
That humanity never existed and will never exist.
They use Apple. And then bitch that its update process is so bad, it can’t restart where it left off when the connection breaks, it can’t use caches/mirrors properly, blabla. Bitch, don’t use it then.
Then let’s call my install 30p87OS, that was made from scratch. Now it’s a distro.
It is. Especially when you need the night to compile FF and it constantly fails. But I learned a lot.
LFS: Not being so complicated actually. Arch: That a fully fletched OS install can be done in less than 10 minutes.
For files of casual users it might be of benefit. They don’t care about capitalization. For system files, I find it pretty weird to name them with random capitalization, and it’s actually pretty annoying. Only lower- (or upper-)case would be ok tho.
And what makes KeePassDX unusable for me is the missing remote support, as my KeePass file is on a Nextcloud webdav share. On PC, as KeePassXC also does not support it, i can just mount my Nextcloud. In KP2A i can connect to the webdav share. But mounting something consistently in Android is hard to impossible.
Well KeePass2Androids keyboard is a lot more ugly and inflexible lol
I can update infinite packages at the same time in pacman tho 😎
Damn, now I’m a normie again apparently. Fml. Gonna switch to KeePass2Androids keyboard then /s
Well you won’t believe what I did then: I’m also trans and am too versatile with my typing to get any use off of any autocorrect (that is what you meant, right?)
Do you have a matrix instance set in the config?
Given that they’ll regularly push updates of Element to the Play Store without tagging releases on their repository, effectively leaving F-Droid users without releases
Just compile it from source with every merge to main, because that’s the fun of it (I also use Arch testing btw).
I had that issue for months. There is no real solution afaik. Apparently, reading the NVM checksum is just not possible on Linux with this chip. It always defaults to 0xFFFFFF I believe. In theory you could write some value, to reset it, but it gave me some permissions error. I resorted to get the source of the kernel, patch out the checking code, compile just the module and then install it. I created a PKGBUILD for it, and I’m currently trying to make it a DKMS package, so you don’t have to reboot first to manually rebuild it.
As you use Debian, you’ll need to create a manual compiling script, but here are my PKGBUILDs for reference: https://git.30p87.de/30p87/e1000e-nocksum-kerne
Note that you need to swap out the kernel source link to the source of your current kernel version.
The current problem is, that you need to reboot to update to a new kernel version, which then means the custom driver will not work anymore, and you need an internet connection to rebuild it, as it will need the most recent kernel version. So never kernel update without wifi in reach.
I will first make it a DKMS package, to ease some of the pain, and then see if I can make it debian compatible.
Hell, I’m 19, using C for 5 years or so now and not even I like the Rust syntax and compiler!
And yay -Pw for arch linux news.