I just went through F-Droid and counted out all the projects I have on my phone. At £5 each I’m looking at an annual bill of about £70/year… Bargain.
Thanks for the idea!
Canadian software engineer living in Europe.
I just went through F-Droid and counted out all the projects I have on my phone. At £5 each I’m looking at an annual bill of about £70/year… Bargain.
Thanks for the idea!
ExFAT is good for portable devices, but if you’re working with something internally, there’s no reason not to use EXT4 or NTFS.
That’s not been my experience. Lots of drives I’ve bought have been FAT32 out of the box.
In terms of local storage, I usually have everything in ~/projects/project-name
, and I don’t have tiny file size limits because I don’t use FAT32 filesystems — that’s the default filesystem you usually get on USB sticks and external hard drives you buy. You have to format those drives to something like EXT4 (Linux) or NTFS (Windows) or you get stuck with FAT32 which has 2gb file sizes.
Well I just tried it again, and while it won’t let me take a screen shot on the lock screen, it’s definitely still the case for me. It just sits there ringing with the pattern lock on the screen and a little “Return to call” button at the bottom of the screen.
Could be. I do remember trying to get it to work a number of ways at the time. If you’re telling me that this isn’t the case for you though, I might try it out again.
I used this for a while, but every time my phone rang I had to type in my pin to answer it which was a deal breaker for me.
I had no idea! Thanks for the tip.
In one of the other comments, we worked out that it was definitely something to do with ACPI, but yes I do have an external monitor. This is a desktop system.
Disabling the interrupt did the job, but I don’t know why it’s happening. If this is related to the monitor, could this be an Nvidia thing?
There it is! Thank you! It’s a process owned by root called kworker/0:0+kacpid
. Any idea what that is?
[Edit 1] Interestingly, I can’t even kill -9
it.
[Edit 2] With kworker kacpid
to work with, I did a quick search and found this SO page that has some interesting information that I only partially understand, but the following worked like a charm:
# grep -Ev "^[ ]*0" /sys/firmware/acpi/interrupts/gpe?? | sort --field-separator=: --key=2 --numeric --reverse | head -1
/sys/firmware/acpi/interrupts/gpe09:11131050 STS enabled unmasked
# echo disable > /sys/firmware/acpi/interrupts/gpe09
It’s not clear to me what an interrupt is or whether this gpe09
value is meant to be persistent across reboots, or why this only seems to be happening in the last couple months, but if I can make it go away by running the above from time to time, I guess it’s alright?
GitLab. The CI is fantastic.
GIMP is alright. Mostly I stick to it because Krita’s dependency on QT means it looks and works differently from everything else in my GNOME environment.
Oh boy are you going to love-to-hate this then. It’s best viewed on a proper computer, but you’ll get the gist on mobile too.
To be clear, I’m not throwing shade. That’s an impressive piece of software. It’s just, given the number of stories I’ve heard (and experienced) about Bash’s tricky syntax leading to Bad Things, I’m less comfortable with running this than I would be with something in a language with fewer pitfalls.
But if others take the chance and it sticks around a bit, I’ll come around ;-)
Thanks for the contribution! It’s a great idea, and with Google fucking about with blocking things like NewPipe, a project like this is a great answer to that.
That looks really impressive, but at nearly 1000 lines of Bash, I’m afraid I’m not comfortable running it on my machine. My Bash-foo isn’t strong enough to be sure that there isn’t a typo in there that could nuke my home folder.
Yeah that was the big strike against it for me too. I found that you can sort of perch it over a crossed leg and it’s sort of serviceable that way, but yeah… no coding on the train with a Surface.
The Surface Pro keyboard is actually quite good, with the added bonus that it’s also easily detachable.
This too is an excellent take. “Artificial pain points” for capitalism, or “learn some shit” for Linux. Love it.
You make an excellent point. I have a lot more patience for something I can understand, control, and most importantly, modify to my needs. Compared to an iThing (when it’s interacting with other iThings anyway) Linux is typically embarrassingly user hostile.
Of course, if you want your iThing to do something Apple hasn’t decided you shouldn’t want to do, it’s a Total Fucking Nightmare to get working, so you use the OS that supports your priorities.
Still, I really appreciate the Free software that goes out of its way to make things easy, and it’s something I prioritise in my own Free software offerings.
The Framework 16 looks pretty great. Repairable & upgradable, discrete graphics (AMD), and guaranteed Linux support.