I hate how installing or removing (or even updating) a flatpak causes the whole software center to completely refresh, and it doesn’t keep its state so if you were in the middle of a search or scrolled down through a category… say goodbye to it.

Oh wow, I didn’t know about Kandalf and KDE valley, that’s awesome!

Ah I see, that’s unfortunate then. For what its worth, I still think the bot is a great idea for discoverability and bridging the two services together! I hadn’t seen it before since I usually have bot users muted and happened to see this comment chain while logged out.

I’ve given it a follow from my Mastodon account since I do tend to miss quite a few cool Lemmy posts it seems, and I think it’ll help me find some communities in general that I’ll want to subscribe to from over here.

I wonder if perhaps wrapping the majority of the text in a spoiler would work. Though I don’t know if that translates over to Mastodon (if not, it might look a bit funky on that side).

Yep, and it’s opt-in so if you’ve never turned it on explicitly, then it’s off.

Seriously though, KDE’s slider that lets you adjust how much / how little data to send (if any) is probably the best implementation of opt-in telemetry that I’ve seen in a while.

I miss those things so much, along with Etch-A-Sketches…

They’re not hating on Arch, they’re “hating” on the small (but loud) group of people who have a superiority complex for just running Arch and doing it the manual way (and tends to see those who installed with archinstall as a cop-out).

Just like the people who shit on those for using Windows.

And if you really want even more barebones, you can just do git init --bare into a directory on your VPS, and then git clone user@your.ip.here:path/to/the/directory and use git as you would normally!

In that case, couldn’t you just use something like btrfs snapshots + Timeshift to pull this off?

Sure, but at the end of the day, for better or for worse, there are going to be tons of people who simply don’t care about whose fault it is - they’re going to want their system to work.

I was lucky enough that I was finally able to make enough money to swap out my 2080 with a 6700 XT this week (and wow what a significant difference in how the Linux desktop works with AMD cards), but I have plenty of friends who do have Nvidia cards and if they asked me whether they should give Linux a try I’d have to warn them that they’re going to get a subpar experience due to it - and all they’re going to hear despite me saying that it’s Nvidia’s fault is that Linux isn’t good enough.

So when it comes to Wayland + Nvidia, hopefully Nvidia gets with the program, but otherwise we’re (the Linux community) going to be at a crossroads of whether we want to get more adoption on Linux - Nvidia is not a small market by any means.

I don’t go and try to proselytize people into coming over to Linux, but there are absolutely plenty of people who do and the mindset of “It’s not Linux’s fault, its X (ha)” isn’t exactly going to work there.

I get it, you get it, but plenty of people won’t.

Sometimes the only way out is through :)

Hit escape to enter normal mode, :q to quit if you don’t have any pending changes, :wq to save and quit (or Shift ZZ), :q! if you don’t care about your changes (save without exiting)

If you’re interested in learning Vim, I’d recommend running vimtutor, which should be present on most systems. But of course, the best way to learn it is to simply use it as much as you can!

RTX 2080 here, and this is the major blocker for me with Nvidia + Wayland: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317

This issue causes XWayland apps to effectively render previous frames very sporadically, and it’s especially very noticeable in Electron apps. Discord for example, sometimes someone will send a message and the message will appear, then disappear, then reappear, then disappear over and over again until it finally syncs back up. The user isn’t actually deleting and resending their message of course, but the render state of the app is basically “jumping backwards through time”.

Tried out the 544 beta driver, and while we did get Night Light/Color support (and that incessant top-screen flicker bug was fixed, occurred in both Wayland and X11), I started to notice the aforementioned issue heavily occurring in IntelliJ which is a Java based development tool which unfortunately is the final deal breaker for me since I can’t really work when I write a line of code, and it disappears, reappears, disappears, then reappears again.

This only occurs via XWayland, and surprisingly games don’t seem to get hit with it (in my case) so I suppose if you only use Wayland native apps like a web browser then it’s fine - otherwise, it makes things very difficult. It also occurs on both Mutter (GNOME) and KWin (KDE) but I imagine there isn’t a compositor where this doesn’t happen due to what causes the actual problem in the first place.

After trying the 545 beta and the problem getting worse, it’s put the nail in the coffin for me on Nvidia and I’ll be picking up a 6700XT after my next paycheck comes in. It is a beta driver yes, but the root of the issue is due to the architecture of their driver which isn’t going to be magically redone in between the beta and “stable” release.

So, no - I wish it was just a circlejerk, and realistically I can’t see how it’d end up being this popular if it was just user error.

Yep, my desktop PC may or may not have one of its SSDs not mounted…

Oh this looks fantastic! I will be deploying this to all of my systems immediately haha!

If you’re on an EFI based system and have systemd, you can use systemctl reboot --firmware-setup to get into BIOS!

Honestly now I am curious if there is a CLI equivalent. I always end up using tar’s t flag or opening a zip in vim to see if it has a subfolder as my current workaround…

That’s perfectly fair! I always seem to have a 50/50 coin toss of whether there will be a folder inside the archive or not.

I think if things were more consistent for what I end up having, I wouldn’t mind it if archives didn’t have a folder or if they always had a folder, rather than the current state.

I suppose in your case, it would be cool if there were a config option to make this do the reverse, unpack the files within the subdirectory of the archive to your current directory.

It would be nice if it were at least configurable to set as the default extract option. If I had to take a guess, it’d be that it’s not the default option because the amount of single files before needing a subfolder could vary between different people. Some folks may want only one, and others may be fine if it goes up to say 3. However, I suppose that could also just be a configurable option.

That being said, I’ve at the very least developed the muscle memory to always click that option no matter what. I can’t tell by your comment if you weren’t aware of the feature, but if not then hopefully it can be of use to you moving forward as well!

Absolutely, yep! I curse myself every time I just click “extract” forgetting that other file managers don’t do this, and end up with files all over the place

Maybe your bug report didn’t get collected into the other bug report, but it’ll be resolved for Plasma 6 thankfully!