I don’t disagree exactly, but I’d argue that you’re contributing to the project even if you’re just reporting bugs or helping others with it on e.g. Lemmy.
I could see avoiding all of that pragmatically in order to use some obscure, critical software, but not something you use every day and for which there are reasonable alternatives.
This is what I came here to say. This is a sovereignty issue they could solve with a miniscule portion of their defense budgets.
It’s kind of absurd. When you buy a TV, the bloated adware at least helps lower the price. Imagine paying extra for it.
Fair enough, most of that isn’t something a user should have to worry about.
VT is just Virtual Terminals. You always have one of them active, and in most distros you can switch to others by Ctrl-Alt-F1 through F12. In some distos it’s just Alt-F1.
So if you press Ctrl-Alt-F2 you should be brought to a text login. For crazy historical reasons you may have to either press Ctrl-Alt-F1 or Ctrl-Alt-F7 to get back to your usual graphical session.
Arch docs for example: https://wiki.archlinux.org/title/Linux_console
I use Orgzly, but that’s mostly because I sync it with Emacs on other devices. I tend to organise things in a tree, but it’s quite flexible.
I would try:
I just started using finamp a couple of weeks ago and this inspired me to install the beta.
If I find any problems I’ll try to get involved on the repository. Discord is a bit of a turnoff though.
Have you checked these all on winehq? It would be nice for them to be reported with logs if they haven’t already.
Garmin Express for example is on there with some discussion here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=40213
It might not help in the short term, but even just having logs for more broken programs could be useful for the wine project.
Did you grep that log file for ‘amdgpu’?
I wonder if the error is related to this: https://github.com/NixOS/nixpkgs/issues/229108
I’m still using x11 on my system. Maybe try that and see if it works?
No, I haven’t seen anything like that. That’s odd.
I’ve had those errors on my system for years. I never thought that they were NixOS specific. I just assumed something to do with a buggy firmware:
Enabled 4 GPEs in block 00 to 1F
ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.POT3._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20240322/psparse-529)
[x~20]
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
I don’t notice any ill-effects from them, so it may be a red herring. I have a:
$ < /sys/devices/virtual/dmi/id/board_name
ROG STRIX B450-F GAMING
with a 5900X.
I don’t usually see as many prints as you have there, but it’s quite a few, and the number seems to vary (grow?) over time. I keep meaning to investigate it, but haven’t got around to it.
I think you should keep looking in your logs for other problems. If you can share the full log I’d be happy to take a look.
The original error actually makes it sound like there’s a partition on hda that’s bigger than hda itself.
It probably becomes CPU limited with those other compression algorithms.
You could use something like atop to find the bottleneck.
Have you checked all the ethernet links are actually connected at 1G and not 100M?
I’d probably:
systemctl suspendWhen the screen fails to wake, are you able to get it back by powering it off, or by unplugging it? Is it X or wayland?
Of course not, but you have to either trust your users to some extent or give them a system that’s locked down to the point of hindering them.
What is ‘unallowed software’? A shell script the user wrote? Something they downloaded and compiled?
Limiting that seems fundamentally at odds with FOSS.
If you stop shipping autotools generated artefacts in your tarballs, things will be a lot simpler.
Weirdly enough the malicious code does look eerily similar to the benign code, because both are unnecessarily obfuscated.
This is not a human written or readable file you’re talking about. It’s a generated script.
As the other user suggested, you probably just need to mount the root subvolume somewhere and run it on that.
It’s such a good idea. I can’t believe they didn’t think of it sooner.