The Nvidia driver on Wayland has been decent for a couple of years and stabilized a lot over the past ~6 months. The flickering issue was specific to XWayland. Normal Wayland apps don't have flickering problems (not quite sure why tbh), but XWayland apps would often rapidly flicker between 2 frames since it only supported implicit sync, which confused the Nvidia driver, which only supports explicit sync. Now with a Wayland protocol for explicit sync, XWayland can be updated to support it and resolve the flickering there.
Yeah, the only time I needed to print something in the last 5 years was a passport renewal form. I just spent 10 cents to print it at my local library. I really don't understand why anybody really needs a printer nowadays.
Or they just use a distro that doesn't frequently break dependencies. I used to experience lots of dependency issues on Ubuntu many years ago. Been on Arch for ~10 years and have only had 1 dependency issue, which was fixed within 1 day.
I wonder how much of it is just due to the taboo about sex and private parts. I don't see anything wrong with straight guys watching porn and masturbating together, but it feels wrong because we're taught from a young age that sex is bad and nobody can see our privates and stuff like that.
Context is important though. The reason that the US is now such a huge fuel exporter is because of oil crises in the past. The government realized how dependent the US is on oil and handed out huge subsidies and land grants to produce its own oil and not be dependent on other, not so friendly countries. The side effect of all that production is now huge corporate profit from the excess production.
We are building renewable energy at a really high pace and also quickly increasing the numbers of EVs being sold vs ICEs. But we still need oil in the meantime and it's better to produce our own and be as energy independent as possible.
I used to use this when I still had a hard drive, but this does nothing for performance if you're on an SSD and profile writes are so few with browsers that it doesn't significantly affect drive wear. In the end, all this does is make it more likely that something will break.
Flatpak uses polkit for permissions. System level flatpak updates are typically permitted without password by polkit but only for local users. For SSH, most flatpak operations require a password, so it's a mess if you try to run an update on system level flatpaks without sudo, which solves OP's problem. They could also move everything to a user level install, which IMO makes more sense for flatpaks than the default system level mode.
Because he tried to update a system-wide flatpak install as a non-root user. Flatpak uses polkit for root permissions. Polkit is usually set up to allow non-root local users to update flatpak without a password, but not remote ones, hence having to continually enter the password for polit when using SSH. He could just run the update with sudo like a normal package manager and would only have to enter the password once. But then he wouldn't be able to complain on Lemmy.
It sounds like you're trying to update system-wide flatpak packages as non-root. Most distros use polkit to allow you to update those without a password from the desktop (i.e. a local user), but usually require a password for remote users (like ssh). Just run as root: "sudo flatpak update".
You could also migrate to a user flatpak installation instead a system-wide one. That's what I've done. IMO that's how it should be done, but that's not the default on most distros for some reason.
Cognizant, a professional services company that Alphabet contracted the YouTube Music team through, said in a statement that the workers were let go after their contract ended at its intended date, according to KXAN in Austin.
A spokesperson for Google told Business Insider that Cognizant is responsible for ending the workers' employment, not Google.
"Contracts with our suppliers across the company routinely end on their natural expiry date, which was agreed to with Cognizant," the company said in a statement.
Not sure how much of the fault is from Google's side here since the employees contracted from another company.
The Nvidia driver on Wayland has been decent for a couple of years and stabilized a lot over the past ~6 months. The flickering issue was specific to XWayland. Normal Wayland apps don't have flickering problems (not quite sure why tbh), but XWayland apps would often rapidly flicker between 2 frames since it only supported implicit sync, which confused the Nvidia driver, which only supports explicit sync. Now with a Wayland protocol for explicit sync, XWayland can be updated to support it and resolve the flickering there.