this post was submitted on 04 May 2024
404 points (100.0% liked)
linuxmemes
21440 readers
639 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
It could have helped you by giving you the knowledge of where the issue was. If it was fixed by the update in the VM, you would know that and could then wait for your distro to get the update or even contact the distro community with that knowledge.
I get that it was frustrating but it truly wasn't their job to tell you how risky that move was.
I know perfectly well what upgrading the shell means. You are missing the point entirely. This dev community does not accept bug reports on older versions even if they're in use by a lot of people and then when they're reported on the latest version and they're acknowledged, they tell the reporter to piss off.
it's not that the issue wasn't fixed that got me to give up on Gnome, it's the fact that a known issue was closed with no resolution even after I gave a patch as a workaround. This is why I am done with them.
I'm not missing the point. I understand their policy and it makes sense to me. They cannot really afford to be supporting not only older versions but their implementations in random distros. That's all they'd ever have time for if they did.
I don't think you mentioned the patch before, and that part is shitty, but if you blamed them for borking your system.. that combined with the constant annoyance of people complaining about a free product, I can see them not being willing to help further.
KDE looks like trash to me, like an unstable nightmare. The other desktops don't seem great to me either. So I'm sticking with gnome for the foreseeable future
Yes, this is the attitude right here. This is the one that people complain about. People are not "complaining", people are reporting issues. And it's not free software if it's being gatekept by entitled assholes
You're being defensive about that but I don't know that you did that and didn't say you did. You understand that all support receives irrational and angry requests right? It must be hard to deal with, especially if people are being demanding. This is not to say you were doing that but it is to say I understand the mindset of people enduring that. "Oh this guy told us we broke his system, yeah don't worry about that one."