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.
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.
Generally it’s just through my distro, it’s always occurred since I’ve used KDE unfortunately (since that was one of my first thoughts). This has been across Fedora (and derivatives), Nix, Arch, and Kubuntu.
Traversing a motherboard sounds like it would be interesting!
Only Human - Memphis May Fire (feat. AJ Channer)
https://piped.video/watch?v=lQenGGMa8fc
(Note, the linked music video has a seizure warning at the start of it)
As far as I know, if you don’t have it on Steam then yes.
The Steam build still gets all of the updates to the game… for now, so if you grabbed it on Steam before it was delisted you can continue to play through that.
I used to justify it with “I’ve had a shit day, I deserve to be able to have something for the convenience” - not to mention, I don’t have a car so realistically it was “Do I want fast food or not”.
Then I started to realize that every day tends to be a bad day for me, due to a multitude of reasons. I live paycheck to paycheck (which is why I don’t have a car in the first place) and the amount I was spending on takeout was way too high.
Now the only time I do so is on Fridays because my workplace lets us spend $25 on their tab just for joining the weekly staff meeting. Aside from that, I might order a takeout once, maybe even twice, during a pay period as a “congrats for making it through last month” but I’d like to even stop doing that ideally.
This doesn’t read as a global Blocklist for all Android phones in the world. It reads more as a local database/API for blocked numbers on your phone.
So blocked numbers would theoretically be applied to your messages apps and other “telephony” based apps that use phone numbers such as WhatsApp (should said apps implement the API).
Google already seems to have a spammer database for numbers, though I’m not sure if that applies to just Fi users, Pixel users, or anyone who uses the Google Phone app. If I have call screen disabled, I’ll see numbers on an incoming call have a red background with a “likely spam” description.
But based on the comments on this post, I feel as if I’ve overlooked something in the article here (I’ve just woken up so it wouldn’t surprise me) - is there a mention of it being a worldwide list?
It would be an alright show… If it didn’t use the Halo name and was written to just be another science fiction/fantasy TV show.
But unfortunately I don’t think the show was ever made for hardcore Halo fans - whether that’s because of the writers or just Paramount going over the writer’s heads I couldn’t say.
They might’ve done so out of necessity. I don’t know if the dev(s) of the Simple Tools apps were working on it full time, but if they were and just not enough contributions were coming in from it… Well everyone has to eat.
As the saying goes, “everyone has their price”. It’s easy to condemn the developers for their choice until you’re in the exact same scenario as they were. Whether that’s because they were starving, or even just offered enough money to make their lives a lot easier - not too many people would turn it down.
deleted by creator
I’m a bit surprised to see that you disagreed with the “NixOS is hard to configure” bit, but then also listed some of the reasons why it can be hard to configure as cons.
By “configure”, they probably didn’t mean just setting up say, user accounts, which is definitely easy to set up in Nix.
The problems start to arise when you want to use something that isn’t in Nixpkgs, or even something that is out of date in Nixpkgs, or using a package from Nixpkgs that then has plugins but said plugin(s) that you want aren’t in Nixpkgs.
From my experience with NixOS, I had two software packages break on me that are in Nixpkgs - one of them being critical for work, and I had no clue where to even begin trying to fix the Nixpkg derivation because of how disorganized Nix’s docs can be.
Speaking of docs inconsistencies you still have the problem of most users saying you should go with Flakes these days, but it’s still technically an experimental feature and so the docs still assume you’re not using Flakes…
I was also working on a very simple Rust script, and couldn’t get it to properly build due to some problem with the OpenSSL library that one of the dependent crates of my project used.
That was my experience with NixOS after a couple of months. The concept of Nix[OS] is fantastic, but it comes with a heavy cost depending on what you’re wanting to do. The community is also great, but even I saw someone who heavily contributes to Nixpkgs mention that a big issue is only a handful of people know how Nixpkgs is properly organized, and that they run behind on PRs / code reviews of Nixpkgs because of it.
I’d still like to try NixOS on say, a server where I could expect it to work better because everything is declarative such as docker containers - but it’s going to be a while before I try it on my PC again.
Realistically, a lot of relationships are “situational” (especially at that age) - but that doesn’t erase the fact that they existed in the first place.
No VPN, it’s strange because I haven’t had a problem with any other services that use IP geolocation (which I assume is what KDE uses) - even Gnome’s auto location tool seems to work fine.
Yeah that’s what I’m unsure about unfortunately. I’d be very surprised if that disabled Wayland. At one point, there was some remote desktop software that disabled Wayland silently, to get around the security restrictions of Wayland… But this project wouldn’t be bound by any Wayland restrictions as far as I can tell.
Hmm, so as long as you have 510 or above on the Nvidia driver you should not be getting blocked by that. I’m unfortunately not sure then.
Perhaps you could try installing sddm
which is KDE’s display manager (the equivalent of GDM) and see if it shows the Wayland option?
Pretty sure it doesn’t require the whole KDE suite, once it’s installed run:
sudo systemctl disable gdm && sudo systemctl enable sddm
and reboot, then you should get SDDM and can try to change the session type at the bottom left.
Note that when using SDDM, you can’t lock your screen in Gnome since that is tied to GDM - you’ll get a notification saying that the screen lock isn’t available.
If SDDM doesn’t show it either, then somehow I think you’d be missing the actual session entry files? Not sure how that would happen though.
Oh wow, I didn’t know about Kandalf and KDE valley, that’s awesome!
Looks fantastic! Although, speaking of the Night Color settings - does anyone know how the location data for the auto night color mode is sourced? It always seems to place me on a different continent…
Hmm, I know at one point GNOME/GDM locked out Wayland for Nvidia cards - but that hasn’t been the case for a while (and possibly was distro specific).
Is there any output from:
cat /etc/udev/rules.d/61-gdm.rules
cat /usr/lib/udev/rules.d/61-gdm.rules
If you haven’t already, it’s worth a shot!
Was playing it a bit in the morning while it was slow at work, seems fantastic so far!