In my day, the start button hasn’t been invented yet, so Ctrl esc didn’t help much. But by the time windows 8 came around, I was using that specific shortcut. I use alt+space now to invoke my launcher, because in i3wm/swaywn using super for shortcuts meant that using super for the launcher felt a bit conflicting

I have a preference towards keyboard shortcuts, but I dont think I’m in any way anti-mouse, I’m just very pro-keyboard. If there is a quick easy keyboard shortcut, I’ll almost always use it.

Honestly, back in the windows 8 days, I never understood the backlash about the start screen/menu. My workflow was “hit windows key, type name of app. hit enter” and that workflow didnt change with the full screen mobile centric menu, so it never felt problematic to me. Plenty of other problematic things about microsoft and windows, but “But the start menu is full screen!” wasnt one of them for me.

These days there are enough “If we brick your computer, it’s not our fault” caveats that are just basically EULA level nonsense…

He ran: sudo apt-get install steam (after having issues with the GUI)

He got a prompt that said You about to do something potentially harmful. To continue type in the phrase 'Yes, do as I say!'

Steam is a 3rd party app store (🙄)… I get the same kind of fearmongering messaging on my phone when I try to install apps. The warnings say “This could break your computer!”

So he didn’t read the whole message. but asking a computer to install steam and then saying “yes really” when it double checks feels like a reasonable flow.

Should this has prompted him to go “Wait, this still says its removing pop-desktop, that can’t be right?” Probably. But honestly he was doing everything by the book on how to install steam. If he didnt say yes, he was going to be blocked on not being able to install steam, and the video would have highlighted the bug in a different way.

He was using a distro with a MASSIVE bug in it and that was really the problem, not his lack of double checking things.

I’m going to count vim, or any other IDE as a tool. You don’t just will your thoughts into the computer (at least most people don’t, that I know).

Or, y’know, don’t do illegal things and it doesn’t matter. That’s the point of fines being a deterrent

Not detecting case fans sounds like it would be not communicating with the motherboard properly. Unfortunately every specific motherboard is going to have it’s own unique set of constraints. But generally this is all handled through “it87” i believe? But it87 can sometimes take some nonstandard params.

Here’s an example gist of instructions for getting things working on one specific motherboard. https://gist.github.com/bakman2/e801f342aaa7cade62d7bd54fd3eabd8

The wifi7 on my motherboard causes kernel panics pretty regularly, and the RGB isn’t properly exposed so I cant control(/turn off) any of the lights. Usually these things work themselves out with time as drivers for the new/nonstandard chips make their way into the kernel/libraries.

You had a stroke because your mom cancelled your WoW sub?

I think this is just a “person” thing sometimes. It is very commonly recommended in a lot of fields that if you are stuck on a problem, to stop what you’re doing and take a walk and often your subconscious will continue processing the problem, and you will view the problem differently when you get back to the problem.

How that may play out in your emotional/shock examples may be different. But processing things while not “actively” thinking about things is something everyone does.

https://www.commitstrip.com/en/2017/02/28/definitely-not-lazy/

Yeah. In college world, one needs to be prepared for the school to not care at all and declare that it is the student’s responsibility to make sure any required software runs on their machine. And college can be a hectic stressful time, so finding time to be able to get things working on Linux may not be worth it. Having the Windows escape hatch ready is very important to be able to not lose your mind while on a deadline.

It blew my mind when I learned that “venidos” meant “come”… And bienvenidos literally meant “well come”, like it is good that you have came here.

And then I finally realized what welcome meant. 🤯

I’m not raging and I’m not even saying that Debian is bad. I’ve just been told MANY times over the years (including on Lemmy), when I’ve commented about bugs and issues I’ve had on Debian, that stability doesn’t mean “without bugs, always upright” it means “not moving, not changing.”

Debian has a very specific use case. And when people say Debian is stable they mean the base platform isn’t going to change under you and suddenly a config file doesn’t work anymore because Package v2.0 uses a different format.

This is good for people who want a low maintenance system that won’t unexpectedly break due to a random Windows update.

This is good for probably the vast majority of people that fall under “normal” computing habits. If there was a major groundbreaking bug that affected everyone, it probably would have been caught in testing.

This is not good for people who have quirky computing needs or otherwise do things in slightly niche ways, IF a bug shows up. Some bugs are minor annoyances, some require different workflows to get around.

But ultimately, people should know that if they are experiencing an issue with Debian, and it’s not just a configuration issue, they either need to have a solution for themselves (recompiling), or switch distros.

I personally stopped using Debian for my desktop around linux 3.16 days, but I do still use it for my home servers (where I don’t want to be updating things constantly). If Debian works as a desktop platform for you, that’s awesome.

But OP was having issues with Debian. So OP should know that due to Debian’s unchanging nature, it will be quite a while before things start working. And they shouldn’t expect otherwise. And that’s ok, their use case is going to just be a bit more bleeding edge.

Ok? “You only have to wait a few months for this crash to be resolved.” still doesn’t resolve people’s issues.

“Fix playing of custom alarm sounds” doesn’t sound like a severe issue to you, but it was also something that if someone needed, they were forced to wait a few months.

Debian would rather have broken custom alarm sounds for several months, even if it was fixed earlier. Fixing a bug to me lands closer to a security issue than “shipping bleeding edge feature sets”.

It ultimately means if something you need is broken for a non-security reason, it is not being fixed until the next point release. There is a fixed unit of time in which you know your problem will not be resolved.

Packages are individually updated for security fixes. Individual packages are NOT updated for bugfixes.

I’ve been told plenty of times that when I had bugs that weren’t getting fixed that “stability means no unexpected changes, not uptime, compile the package yourself if you need it fixed.”

There are plenty of examples of upstream projects asking debian to not package their stuff because they get bug reports for things that were fixed months ago.

Debian does not ship bugfixes. Debian only ships security fixes.

If something works, it’s not going to break. But if something doesn’t work, it’s not going to unless you fix it yourself by going outside of the official packages.

Also worth noting that Debian’s definition of “stability” doesn’t mean “doesn’t crash” even in the slightest. It means “doesn’t change.” That means not changing broken software to be newer working software.

Any non-security bug that exists will stay because new software only ships for backported security updates. So if you have a crashing issue, Debian has no interest in fixing it until the next release. Unchanging is more important than working.

If you don’t have any crashes or bugs popping up, Debian is great, because it won’t introduce crashes or bugs. Nothing unexpected will happen.

By Debian’s definition, the Titanic is now VERY stable, unmoving at the bottom of the ocean.

Given his history, if he had to sue someone to be able to use a title, it’s probably not a legitimate title.

Sometimes you need to specify in config which clipboard to use on unix systems that might have multiple clipboards too

Well sorry. If it works for glxgears there is probably some other weird interaction happening with Steam + Gamescope + Game launching. (you could try to add glxgears as a non steam game to further push the boundaries of if anything will run from steam).

I don’t have an nvidia GPU so I couldn’t even possibly comment on the state of that situation, but I wish you the best of luck.

Out of curiosity, what happens if you try to run gamescope from the terminal to just run anything (not even having proton in the mix).

For example:

gamescope -f -W 2560 -H 1440 -r 144 --force-grab-cursor --mangoapp – glxgears

If this doesn’t run, you should get some log lines at least to let you know whats on fire with gamescope.

Water, wolves & women.

That’s what www stands for in URLs.