The fucking gas lighting in this response
Google provides more assistance to open source software projects than almost any other organization, and these debates are more likely to drive away potential sponsors than to attract them
“We ran AI that may or may not have found a legitimate issue, and you’re not looking into it for us fast enough. That’s going to drive away new volunteers that we need”
It’s also weird, since OpenSUSE Leap uses the exact same binaries as SLES. Specifically to make it easier to start off with the open version and transition to paid SLES without reinstalling
A bigger issue than the APK changes is that Google no longer releases the source for Pixels after the 9.
Graphene claims they are partnering with another OEM, but we’ll see how it goes
https://www.androidauthority.com/graphene-os-major-android-oem-partnership-3606853/
Maybe easier to another suggestion, you’re probably using a systemd based distros -
journalctl -b -1 will show you the logs from the previous boot, so you could check that after resetting to see if anything was logged
For some other ideas to narrow down where the issue is…
If you’re stuck in the frozen state, you can Ctrl+alt+delete 7+ times quickly to tell systemd to try to restart the system. If this works, it means init was still able to process messages
If that doesn’t work, you could enable Magic Sysrq Key (if disabled in your distro), and then use the key sequence REISUB to try to see if the kernel is still responding and can reset the system
Microsoft released Windows Vista, which was absolute dogshit on every PC at the time it was released.
This also just happened to be not long after Ubuntu was released, making it easier than ever to install Linux.
Installed it, quickly found out everything was easier to configure and tinker with in Linux…
Never saw a reason to go back. Used Windows 7 for a little bit, and it was better than Vista, but it still wasn’t anywhere near as easy to use as Linux
I want to see the actual characters … instead of squares
Sounds more like an issue with the font you’re using, rather than the input method.
At least for Chinese, we use ibus on desktop (KDE Wayland) and fctix5 on Android. Both work well in those devices
It’s safer, and uses a systemd mechanism to update with most programs not running.
That said, I’ve never had a problem updating without restarting…
You can change the behavior in System Settings -> Software Update -> Apply System Updates
Pick either immediately or after rebooting
Probably good.
AMD had their own implementation of Vulkan (primarily aimed at their Professional cards) called AMDVLK
The rest of the open source community contributes to radv.
AMD doing their official testing and releases on the Vulkan implementation you’re using should help find bugs and they can submit fixes directly to radv
If you want your updates automatically, you can install unattended-upgrades
The only thing to keep in mind is with Debian, you’ll need to upgrade to the next release for them.
With something like Ubuntu, they can just click the upgrade box when there’s a new major LTS release
Either one can be better depending on how you want to handle maintenance
My take: There was one user that kept making post after post after post as they tried to upgrade, which made it seem like there were more issues than there were
Scrolling through it right now, every support question from the last week appears to be from the same person
You have to at least modify your sources.list.d manually first. For most people, updating sources.list.d and running full-upgrade will probably work fine…
The full instructions are
It takes like an hour? but it’s still not “just press okay.”
Ubuntu’s has broken on some upgrades for friends and they had to do the whole Debian process manually, but it does try to automate the removals, disablements, and updating sources
Edit: instructions taken from Trixie release. I skipped some that aren’t really unique, like make a backup
https://www.debian.org/releases/trixie/release-notes/upgrading.en.html
AMD has been proving that x86_64 can be at least as power efficient as ARM over the last few years (given a floor of performance for like a phone/laptop… I doubt it can get as low power as a little ARM microcontroller)
It seems like x86 was getting so power hungry because of Intel’s laser focus on single core performance
They’re talking about a Debian 12 -> Debian 13 upgrade
On Debian, you get release notes on what commands to run.
Ubuntu has their own software update utility, separate from Software Center or Discover, that runs the commands for you
The devicetrees between Android versions is effectively the same. They define the hardware
We won’t know the impact until they try to bring up the Pixel 10
You can get them off Aurora Store if you don’t want to install Google Services.
Yes, GOS adds the ability to completely disable network access to apps.
For magic eraser, that’s a separate app from Google.
Pixel Camera does night mode, editing tools are in Google Photos
Depending on how you had it installed, Alpaca split support in the Flatpaks.
If you want AMD support, you need to install
com.jeffser.Alpaca.Plugins.AMD
I’m surprised at using ntfs-3g these days, but one major difference is that ntfs-3g uses FUSE in userspace.
Paragon has an in-kernel driver that is much faster, although I would expect your distro already includes it.
You can check with something like cat /boot/config-* | grep NTFS3_FS
I never really looked into what they were doing with KPTI.
Assuming it’s accurate, that first one is a much better technical description, even if it was intended to spell FUCKWIT
On-device routing and the map rendering is way faster in CoMaps.
OsmAnd has way more features.
If you just need basic navigation, I tend to go to CoMaps