[solved] I'm having audio issues with Linux and while I have a temporary solution, I'd like to have a permanent solution if possible.
gnuhaut @ gnuhaut @lemmy.ml Posts 8Comments 519Joined 2 yr. ago
gnuhaut @ gnuhaut @lemmy.ml
Posts
8
Comments
519
Joined
2 yr. ago
This is so stupid, what's Vietnam supposed to do? What stuff does America produce that they can export to Vietnam to offset this trade imbalance? The US is basically ruining that country, again. Because what, they stole jobs growing coffee, assembling phones and sewing T-shirts from the American workers? I'm sure the American worker would love to do that at competitive wages of like $200 per month.
Also, imagine this perfectly balanced trade scenario: Vietnam sells coffee to the US, gets dollars, uses these dollars to buy oil from the UAE, and the UAE then uses these dollars to buy American weapons or something. As per the braindead Trump administration, this would be a problem, because it involves a third country.
I mean it's definitely weird that wireplumber and pulseaudio are running simultanously, that is probably not great (or maybe it's harmless, idk), but it's normal when using pipewire to have wireplumber on control0.
Anyway you should try running fuser before you apply your fix.
Also I deleted my original post, because I wasn't super happy about it, and made new one, so now there are two versions of this post. Sorry.
I mean something must have changed three days ago, kernel update maybe? You could try running a different kernel and see if this fixes it automagically.
I recently also had an issue where I could only see a dummy device, and that got me wondering. It was caused by fluidsynth hogging the audio device. So maybe could you check something? Look at the log file for pipewire (journalctl --user -u pipewire here) and do fuser -fv /dev/snd/* when it's still in its broken state to see if (maybe) you're misdiagnosing the problem. Because I could possibly sort of imagine that doing the force-reload and start pulseaudio dance might actually have seemingly fixed my fluidsynth issue by inadvertently making it so that pulseaudio got a hold of the audio device.
I had an issue like this recently on Debian testing and it turns out fluidsynth was hogging the sound device and so pipewire couldn't open it. IDK why it was doing that all of a sudden. The symptom was also just having the dummy device.
I think what I did to figure this out was look at the pipewire logs and it said something to the effect that it couldn't open the sound device because it was busy, and according to my bash history I did fuser -fv /dev/snd/* and figured out it was fluidsynth that was using it, which I then disabled or maybe uninstalled because wtf do I need midi for anyway.
Your problem may be different, but I can imagine, theoretically, that all the stuff you're doing makes it so pulseaudio gets first dibs on the (otherwise busy) sound device and so maybe you have misdiagnosed the problem.
It's option caps:escape_shifted_capslock I think.
You can look through /usr/share/X11/xkb/rules/base.lst for all the options.
Edit: Just looked up when this was added, this is a new option from 2024:
IDK if this will work but maybe doing exec sudo -i does the trick.
Otherwise just enable the root account and log in as root. Should be passwd -u root to unlock (passwd -l root to relock), also need to set the root password using passwd root.
We knew about this stuff, but I guess it's really only official once the NYT writes it down.
Apparently the way to write about one nuclear power being heavily involved in strikes on another nuclear power, except for actually pushing the button, which they strongly advise their proxy to do, is to make it kinda cool and daring and not terrifying. This reads like some character drama. Note how the Ukrainian characters seem a lot more flawed.
That they used euphemisms, like "point of interest" instead of "target", to obfuscate what they're doing isn't that surprising, but seriously fuck these guys. Learn this one weird trick on how to avoid WW3: just call it something else. I wonder how insane someone has to be to be a general.
Also makes me wonder what they're leaving out of that story. The Ukrainians did that one on their own, trust us. Sink Russian flagship? No US involved. Invade Kursk? US didn't know about it. Attack Russian oil infra? Yeah not cool Ukraine, not cool. Also no word about who blew up that dam or Nordstream.
Everywhere else though? Yeah basically the US did all that. Total involvement.
We're told it only went south when the Ukrainians stopped following orders. Not doing exactly what the US says is bad apparently. It's either reckless or stupid, and it actually for real doomed their 2023 offensive. For sure that one would have succeeded if the stupid Ukrainians listened.
Great partnership guys, why oh why would anyone be wary if the US actually has their best interests in mind, let alone the best interest of the their soldiers or population? No, you see, you need to charge up that hill now! Don't look at it first! Don't shell it first! We swear it's just a small number of Russians. And no, we don't trust you enough to tell you how we know that. So risk averse these Ukrainians! And btw, I see a lot 18-25 year olds running around in Kiev, what's up with that? Looks like you are not taking this very seriously Mr. Zelensky! Looks like you don't want to win!
Anyone who has never even used a computer before can go to one of these websites, follow the instructions on the screen in front of them, and get it done. Zero experience or skills required.
No they don't. People who have never used a computer before have trouble even using the mouse. They don't know what a file is, they don't know what a filetype is, they don't know that you can convert one type of file to another, they don't know even to look for a file conversion website, they don't know how to upload a file to a website, they don't know how to find a file in the file dialogue, and on and on. Seriously what are you on about?
Overall fair enough I guess. I didn't say it was simple though, i said it was not more complicated. Your experience using GUIs and web interfaces probably spans years. It's not like you're born with GUI skills.
Making a GUI is more work than making a CLI tool. GUIs are not cross-platform, a pure CLI is more portable. You can code a CLI with any programming language you like, while there are many restrictions on what kind of GUI is available on what programming languages and platforms.
The GUI code is tedious and boring to write. That code can become outdated and broken and might need fixing to run on newer platforms. The CLI has essentially no extra dependencies and the interface hasn't changed much since like the 70s.
The sort of person who develops free software usually knows and likely prefers to use the CLI. They're not doing it for users like you, first and foremost. They're doing it themselves, or because they need it for their job. The CLI tool might be exactly what they want, because the file conversion is part of some backend stuff, something that's run from a script, so you can automatically run it on all the files.
Anybody with basic web dev skills can then take these tools, slap together web fronted and try and make some quick bucks. They're basically incentivized to not care about security, privacy or anything like that. Of course that space attracts scammers.
The incentives just aren't there for it to be any other way. You can either learn the CLI commands, written by people who care about their reputations and professional pride and want to share their tools. Or you can trust anonymous internet randos wanting to make a quick buck. And while I sympathize not wanting to have to learn new shit, I swear using a shell isn't actually more complicated than using a web browser, you're just not used to it.
Obviously? They're not able to, and even if they were, the EU economy and population is so much bigger, Russia would become the backwater of its own empire. Why would they want that? The end result would look a lot like the EU admitting Russia.
The file autostart.sh file needs to be executable. This might be why it's not working.
You cannot realistically make it impossible to detect that you're running on wine. Wine just implements the Windows ABIs. The actual code running is totally different. Even just reading any of the binary code of literally any function would reveal it's different from the Windows code. How are you going to stop it from doing memory reads on stuff that it needs to be able to read? You can't. You'd need a full hardware emulator for that.
Anti cheat software tries to find cheats running on the computer, and in order to that, so called kernel-level anticheat hooks into NT (Windows kernel) internals, and runs at the highest possible privilege level. It has to do that so it can monitor everything going on in the system. If it didn't do that, the cheat could just hide from the anticheat software by running with superior privileges.
Wine does not implement undocumented/internal parts of NT, and neither does it run at an elevated privilege level. It also cannot realistically implement any and all possible NT kernel internals, and it cannot possibly hide the fact that it's actually wine, and not real Windows, from any program that really wants to figure this out.
If wine tried to implement a specific workaround for a specific anti-cheat software/version, in order to it trick into thinking it's running on a real Windows system with elevated privileges, the anti-cheat vendor would likely interpret this as a kind of deception, and they could easily update their software to detect this situation.
Theoretically, anti-cheat vendors could do kernel-level anticheat for the Linux kernel specifically if the game runs on Linux, but this has problems: First of all a general backlash and complete lack of cooperation from the Linux community (btw, Microsoft isn't too happy about them doing this on Windows either, and they might at some point do something about this, since it's bad for security and stability). Also, Linux kernel internals aren't at all stable, and so just practically you cannot hook into the Linux kernel nearly as easily as you can into NT.
Some anti-cheat vendors do support Linux though, but only optionally if the game dev allows that. In practice, this just means many checks will just be disabled on Linux, which is presumably why many games do not enable the Linux support.
tl;dr: No. Only the anti-cheat vendor / game dev can realistically fix the situation, and they may not want to because it'll be worse at actually detecting cheats on Linux in practice.
I have had USB thumb drives that just wouldn't boot on some computers. Try a different USB drive maybe.
https://lwn.net/Articles/335415/
The evince PDF reader ran into this issue back in 2005. It is now rare to find a distributor shipping a version of evince which implements copy restrictions. Xpdf implements copy restrictions unconditionally, but Debian patched that code out in 2002, and that patch has spread to other distributors as well. In general, as one would expect, free PDF readers tend not to implement this behavior. Okular is about the only exception that your editor can find; it's interesting to note that the version of Okular shipped with Fedora Rawhide also implements copy restrictions by default. Perhaps this behavior is result of the relative newness of this application; as it accumulates more users, the pressure for more user-friendly behavior is likely to grow.
Another downside of flatpak is that I don't trust upstream devs to have my best interests at heart, but I trust Debian developers far more. I've seen upstream do some annoying or stupid shit and the Debian maintainers not budging.
I think it was poppler or evince that decided they were going to enforce the no-copy-and-paste bit you can set on pdfs. Debian patched it out. I've seen Mozilla decide they were going to enforce their trademarks. They carved out special exceptions for various distros but that still would have meant you would have to rename Firefox if you were to fork Debian. Debian had none of it. There were many dodgy copyright and licensing problems upstream devs gave no shit about. Debian not including these often eventually put pressure on them to fix this shit or for some replacement to get developed.
He's an anti-woke crusader and bigot. A large chunk (probably most) of his "content" is actually about that.
Yeah actually looks like the same issue I had. Just uninstall fluidsynth with
apt remove fluidsynthand (probably) reboot, and see if that fixes it.