The Linux Thread - The Autist's OS of Choice

[prollyanotherlurker]

I will say that disk management in KDE "Just Works", everything mounted through Dolphin was in a standard place (/run/media/<username>). It is not something I would consider broken

it's probably using udisks2 along with kio then. Since that's where it automatically mounts things. in /run/media/.

which is actually the reason I've moved away from udisk2. Because as far as I can tell, it actually won't let you pick anywhere else to mount things. Also because I don't use gui file managers much anymore. So not having that does really cause me any extra headache. It lets me use other options for rootless device mounting that let me mount drives wherever I would like.

 

[The Saltening]

Lutris is currently unable to install game launchers. The launcher installs then opens to do its install and then fails. For EA App I can get to the login screen before it closes. Battle.net wont even get to the login screen.

edit: idk how i did it but i managed to do it. another W for me on linux. fuck you microsoft

 

[DavidS877]

One of the first things I do on a new Linux Desktop/Laptop is disable media mounting as 95% of the time I put in a stick or sd card is to "dd" something to it so I can move the stick to something else to boot it. The rest of the time I understand the horribly complex "mount" command.

 

[Aidan]

So & makes the process run in bg of the shell? Let's say I use the shell to open most apps, then use it with nVim to program, won't nVim's performance be impacted by the apps because they're shell-bound?

No, the processes don't impact the performance of the shell itself. But if you kill that shell it kills those processes too.

 

[The Saltening]

well fuck me EA-anticheat doesnt work on linux. guess I am not playing battlefield 1

 

[Elysian]

Lutris is currently unable to install game launchers. The launcher installs then opens to do its install and then fails. For EA App I can get to the login screen before it closes. Battle.net wont even get to the login screen.

edit: idk how i did it but i managed to do it. another W for me on linux. fuck you microsoft

Try adding the exe Lutis installed to Steam as a Non-Steam Game and then running it with Proton. Worked for me with Ubisoft Connect.

 

[Enig]

Newest “what the fuck” discovery, running KDE on a laptop with a UHD620 and opening anything in an image viewer makes the framerate of the entire DE cut in half even with triple buffering off. I don’t even know how to diagnose and fix something as absurd and unexplainable as a 64x64 png being more destructive than six, seven Brave windows being open.

 

[Betonhaus]

Newest “what the fuck” discovery, running KDE on a laptop with a UHD620 and opening anything in an image viewer makes the framerate of the entire DE cut in half even with triple buffering off. I don’t even know how to diagnose and fix something as absurd and unexplainable as a 64x64 png being more destructive than six, seven Brave windows being open.

X11 or Wayland?

 

[Enig]

X11 or Wayland?

Forgot to say Wayland, yeah, X11 works correctly since it isn’t in a race to see how many times its dev history can outstretch systemd’s.

 

[Susanna]

Newest “what the fuck” discovery, running KDE on a laptop with a UHD620 and opening anything in an image viewer makes the framerate of the entire DE cut in half even with triple buffering off. I don’t even know how to diagnose and fix something as absurd and unexplainable as a 64x64 png being more destructive than six, seven Brave windows being open.

Which image viewer, and which version of that image viewer? I've never encountered anything like this, and testing Gwenview 25.04.1 on KDE under Wayland just now, it worked fine.

 

[The Saltening]

so for some reason today when I try to launch a game steam takes absolutely FOREVER to process vulkan shaders. It jumps to like 33% instantly and then absolutely crawls up 1% at a time. Like this will easily take an hour to do one game. What gives?

 

[The Count of Monte Cristo]

so for some reason today when I try to launch a game steam takes absolutely FOREVER to process vulkan shaders. It jumps to like 33% instantly and then absolutely crawls up 1% at a time. Like this will easily take an hour to do one game. What gives?

Does steam still enable this shit by default? Just disable it. It was useful on old mesa versions so shaders didnt compile mid gameplay, but nowadays mesa (or the nvidia drivers) should support compiling shaders during loading screens.

 

[Enig]

Which image viewer, and which version of that image viewer? I've never encountered anything like this, and testing Gwenview 25.04.1 on KDE under Wayland just now, it worked fine.

Gwenview 25.04.0 on a Thinkpad T480 with the i5-8250U because seemingly every i7 board for the T480 is unstable or in need of reflow by now. If you have the same setup, open a random pic in Gwenview and then open anything on Youtube that is supposed to be playing at 60 FPS while having the FPS counter in KDE enabled, immediate drop to 30 or below for seemingly no reason even with an unlocked BIOS to tweak GPU settings like boosting DVMT to 64MB.

 

[prollyanotherlurker]

Gwenview 25.04.0 on a Thinkpad T480 with the i5-8250U because seemingly every i7 board for the T480 is unstable or in need of reflow by now. If you have the same setup, open a random pic in Gwenview and then open anything on Youtube that is supposed to be playing at 60 FPS while having the FPS counter in KDE enabled, immediate drop to 30 or below for seemingly no reason even with an unlocked BIOS to tweak GPU settings like boosting DVMT to 64MB.

Idk what you need out of your image viewer. If something simple is fine for you. For Wayland. I recommend imv. See if that does any better maybe.

 

[Betonhaus]

Idk what you need out of your image viewer. If something simple is fine for you. For Wayland. I recommend imv. See if that does any better maybe.

I just don't understand how an image viewer can be a problem. Is Wayland just not properly decoding a specific image format?

 

[WielkiWapiesz2137]

The program is run in the background of that shell, you can bring it back to the foreground using fg. If you have multiple backgrounded processes, you can select which one bring back to the "foreground" by listing them with jobs. As I type this I realize I've never backgrounded more than 3 things at once, ever.

You can also use ctrl-z to put process into background.

 

[prollyanotherlurker]

Here you go Linux game niggers. Eat it up.

(I hate how muta always talks in his videos. He talks the same way I type, when I'm trying to make a post on my phone quickly. Because I'm doing something else, and I don't have time to actually think about how I'm saying something. So I can get back to what I'm doing. But he doesn't while talking, in recorded videos)

I just don't understand how an image viewer can be a problem. Is Wayland just not properly decoding a specific image format?

Idk it could the the specific program he was using. Something weird going on with the driver. Something with kde. Or some combination.

Really the only way to know would be looking at exactly what is happening on their machine. But with how Wayland works. It's not going to just be as simple as Wayland alone is the issue. Really anything would just be guessing without seeing what is actually happening.

I know I've never had any issues like this one. but I don't use kde, or the image viewer they were using.

 

[The Saltening]

Here you go Linux game niggers. Eat it up.

(I hate how muta always talks in his videos. He talks the same way I type, when I'm trying to make a post on my phone quickly. Because I'm doing something else, and I don't have time to actually think about how I'm saying something. So I can get back to what I'm doing. But he doesn't while talking, in recorded videos)

Idk it could the the specific program he was using. Something weird going on with the driver. Something with kde. Or some combination.

Really the only way to know would be looking at exactly what is happening on their machine. But with how Wayland works. It's not going to just be as simple as Wayland alone is the issue. Really anything would just be guessing without seeing what is actually happening.

I know I've never had any issues like this one. but I don't use kde, or the image viewer they were using.

1. He is poo in the loo. 2. I watched deorios videos on him and I do not like him.

 

[homeless]

Here you go Linux game niggers. Eat it up.

(I hate how muta always talks in his videos. He talks the same way I type, when I'm trying to make a post on my phone quickly. Because I'm doing something else, and I don't have time to actually think about how I'm saying something. So I can get back to what I'm doing. But he doesn't while talking, in recorded videos)

he's created lots of videos on linux but a ton of them are him going through loads of trouble to put windows inside of linux so that he can play the 5 garbage games that still require that. i don't really understand him, and i don't know why anyone would play games that try to force users onto specific operating systems. sometimes he even has to do some work to make the games not realize they are running inside virtualized windows, because they are so picky they dont even like that. and of course they are all still full of cheaters, retard developers fighting boogeymen.

 

[Frederica Bernkastel]

i don't know why anyone would play games that try to force users onto specific operating systems.

Does he just not know how to use WINE/PROTON every well? If not, normies just have poor taste in vidya. Unfortunately, you need them if you want Linux to be successful in commercial activites. People like him are largely why DXVK, WINE anti-cheat, and SteamOS became a thing. They created demand for it. Sometimes bad people can create good externalities.