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.
Traversing a motherboard sounds like it would be interesting!
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.
Once I woke up a bit more I had another look at the article, and this phrasing certainly makes it sound like it needs approval at some point:
Due to a licensing dispute between NVIDIA and Activision in 2020, GeForce NOW lost access to all Activision-Blizzard games.
Perhaps though it’s a case of “Better to ask for forgiveness than permission” and they just add games until someone tells them to pull it off, I’m not sure. It’s been 4+ years since I looked into GFN, I tried it out during the beta period but I don’t believe I’ve used it since then.
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.
Correct on all accounts. Just to be more precise, I’m not placing any blame on the players in my prior comments - the blame goes to GFN and Activision since the player expects to be able to play a game that they’ve paid for, on a service that they have paid for.
Right, I didn’t mean to imply that playing on GFN was cheating by any means - I probably should’ve worded that a bit better.
I meant more of “If Call of Duty explicitly allowed GFN to add the game, then players who play via GFN shouldn’t have a chance to be banned just for playing through it”
Doesn’t the publisher of the game have to approve for a game to be put on GeForce Now?
I mean, don’t get me wrong - I know anti cheat detection has never been perfect, but you’d think this would be something they heavily try to make sure they get right.
Yep, I modded my switch, dumped the keys and my games and went “Now what?” and after playing via Yuzu on my PC I realized this was the only way I really wanted to play the few Switch games I enjoy.
Every now and then I’ll boot into the stock firmware to play Mario Kart with some friends when they want to play, and that’s it.
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!
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!
deleted by creator
deleted by creator
Out of curiosity, and I can’t think of why it would affect it - the WaylandEnable=
is generally commented out instead of explicitly set. What happens if you put a #
in front of that line to comment it out again?
I imagine that is the case, however they could refund it given the situation.
I get the feeling they won’t allow refunds.
Was playing it a bit in the morning while it was slow at work, seems fantastic so far!