“Why doesn’t this just work I never had this problem on Windows!!” leaves no necessary information to troubleshoot
Vs.
“I have this specific and obscure workflow I use with this one package nobody has heard of, I perform XYZ action and after I ran pacman -Syu I’m seeing that the application is segfaulting and leading to this call trace…”
Five page dump of dmesg
“I mapped this to line 748 of the Linux-Zen kernel source file can somebody help explain how I can work around this?”
No responses for eternity, thread archived
The answer is on a 5+ year old YouTube video in a different language than you need half the time that is presented by a 10 yr. old.
10 yr olds are really talented these days.
Most probably in Hindi too
There’s a third kind that uses some weird magic to be both at the same time.
Please add back spacebar heating bug.
this you?
Feature*
Seriously though. Seen people install Mint, and run non-Linux games through steam with no issues. I had to troubleshoot for about 8 hours so kind of make them run.
Hardware is a big factor in this. Mint in particular is a stable distro based on the ubuntu LTS so it’s slow to get new kernels and you need a ppa to get a fresher mesa install and this is essential for newer amd hardware. Conversely if you’re on a rolling bleeding edge distro and you rely on nvidia and their closed drivers then you’re often one update away from breaking them.
A few days ago there was a video from a relatively known Youtuber on here I think that sparked the idea to try to make the switch again. Mainly because I have experience with Mint and he showed how it “just works”, even with notoriously bad nvidia drivers, which I also need.
What ended up being the issue?
After I switched go the flatpak version of steam and changed the drive from NTFS to ext4 it works. I did both at the same time so I’m not sure which ended up fixing it or if both is necessary
Yeah probably using NTFS was your issue. I had the same problem with ExFAT.
NTFS?! Yuck.
But like what was the issue?
It’s still a dual boot machine. I don’t have the time or nerve to switch over on one go. See it as a prove of concept.
Idk what exactly the issue was. I just know that switching to steam flatpak and ext4 seem to have fixed it.
Since you are not telling me the issue I cant give you what might have went wrong. You might have learned from that.
One advice, nobody will like linux who painstakingly has to play catchup on the terminal on a pre-baked OS.
All the distros I ever cycled through, I always had issues with pre-baked systems. There are always these little things you expect that does not end up happening even if you sweat blood. Then you start looking and you find out that nobody ever had this and there is no documentation whatsoever.
The only antidote aganist that if you are in control and if it is documented. I only ever liked linux in the advanced form.
yeah ntsf doesnt play nice with linux version of steam that was almost definitely the issue.
Wait until later in the spring when the next version of Mint comes out.
Mint is considered the new standard for “it just works”, but I had nothing but problems on my desktop with mint.
I personally had to give up on mint after like a week. Couldn’t for the life of me get multiple displays working.
Works for me. You must just suck
experience helps. after some time, you will suckless :)
Or you might get swayed
Me, installimg a few Flatpak apps, having them work for a while then suddenly break for no apparent reason, spend an enture day trying to fix them, only for an update acouple days later to fix it.
Me when my sound randomly goes poof and starts acting on the fritz
Terminal please run my pulse killer file. Fixed.
Then sometimes my chat/game mixer just breaks. And one only works, then on a random day it is just mysteriously works again without doing anything.
Then my windows laptop is like: File Explorer crashes fairly regularly. Word died sometimes. The battery percentage is now just a percentage with no number!
Now my WiFi toggle states it’s offline… Opens networks, ah lovely it says connected. Same with Bluetooth.
Much rather just have the more reliable Linux.
Lol, that used to happen to me a lot when I used Windows. I resized my Linux partition and rarely return, I only have the basics installed because of some uni projects that might require Windows software and it still manages to bug while updating or opening Teams
me, wondering why my VHDs in 86box kept disappearing until I realised I needed to set the permissions in my distro’s Flatpak settings:
There are 10 kinds of people who understand binary.
Those that do And those that don’t
The two hardest problems in programming are cache invalidation, naming things, and off by one errors.
Don’t worry guys I fixed it
Pretty much Wayland and X11 situation
Or Nvidia vs AMD, but they go quite hand in hand
Theyrethesamepicturememe.png
Cries in Slack screen sharing not working in Wayland
Is this “Wayland changed the way screen sharing works, which broke slack and everything else that does screen share” or “I’ve gotten screensharing working with everything else but it’s still broken in slack”?
I don’t use slack so I’m not sure what the specific issue is, but I remember having to install additional packages on Arch (BTW) to get screen sharing working in Plasma (my three use cases being discord, Google meet, and steam remote play).
It is broken in Slack. Apparently it’s supposed to be an easy fix and there even was a workaround for it.
But then Slack removed that workaround. I’ve heard it’s possible to get it working again, but it’s harder.
Edit: I don’t blame Wayland for it. The entire problem is on Slack, as screen sharing works for other programs.
This was fixed ages ago, but you are using Debian because it is “stable” and thus software from ages ago and don’t have the fix.
There are several dozen Debian Unstable users out there. They seem to be mostly bearded.
The duality of Linux…
Schrödinger’s nerd
Works on my machine.
They’re the same person.
ProtonDB comments… at the very least say if you’re using an nvidia or AMD card ffs
