
The day talon voice users are forced to dump KDE plasma

The day talon voice users are forced to dump KDE plasma

I see. I remember there used to be issues with Intel GPUs on linux back 10-15 years ago, but it should work without issues today.
However, on Linux mint you do have to open the driver manager and select your proprietary graphics driver yourself or you end up with the open source one which is not always as performant (though more backwards compatible). It should have the Intel drivers in there too. In general, only the graphics drivers need to be installed by the user and everything else should be set automatically.
And in the case they were installed, rolling back to an earlier version of the driver might also improve it. It looks like Intel has stopped providing updates to the i7-3770 since a few years back, so a later Intel driver could be causing issues.
It should work without any choppiness in the OS itself, but it might take a bit more configuration than newer ones that generally just immediately work.

Mind if I ask some things? If you don’t want to try again, you can ignore this.
Did this happen while you were trying it out on the USB, or had the installation finished and you had removed the USB and restarted?
Were the nvidia d rivers installed in the driver manager? Was there any difference with the open source drivers?
Was secure boot disabled in your BIOS?
Was it a laptop or desktop? In case of laptop it might have been using battery saver mode. installing https://github.com/linrunner/TLP might have helped setting it up properly if you don’t want to handle it yourself.
What graphics card do you have? I can check if there are any compatibility issues, though there shouldn’t be unless it is decades old, in which case you might want to try out one of the more old hardware compatibility focused Linux distros.

Sounds like something went wrong with the installation. Mint is overall more performant than windows. What slowed down?
Couldn’t add perforce to the list because someone else was checking it out, I see.
Before the ddos they were also spamming a certain n-word. Why are far-right groups targeting codeberg anyway?

About time they retired C. Oh, that’s not what happened?
Fuck elon, but also good riddance.
A laptop running linux mint.
Maybe he would prefer perforce.

Element seems to have voice and video chats in beta right now, and they plan to implement it into the Element application, so it looks like it is on the way at least.

Why not just use Matrix? I thought it was the goto FOSS and decentralized Discord alternative.

Yeah, a name should describe what it is or does, so if you have two turtles, and let’s say turtle1 wants to shit on turtle2’s lawn, you could name them shittingTurtle and victimTurtle. If the name alone tells you what its purpose is, that saves a lot of time for people looking at your code.
Is_Turtle is not a bad variable name because it tells you it is a Boolean with “is” and that the Boolean tells you whether something is a turtle or not.
Also, depending on the language, I suggest either camelCase or snake_case naming of variables. PascalCase is usually for defining classes or in case of C#, methods.
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
The requirements are generally things that were designed away on purpose from Wayland. Even if KDE plasma had a workaround solution, they would need to communicate with all other distros to make sure all distros have similar solutions so accessibility feature devs don’t have to make a version of their application for every distro, and KDE Devs themselves have said that they “don’t want to allow users to shoot themselves in the foot by letting the application bypass security features” as if application A knowing the coordinates of a window in application B has any security implication whatsoever.
Wayland is fundamentally designed without accessibility in mind at all, and will virtually never work with it. The current status is still after 17 years “tough shit” and that infuriates me.