Maybe there's a service pack?
MyNameIsRichard
Well, that really makes a difference!
I only get a couple of problems.
- A panel that wraps content is sized to one icon when logging in for the first time
- Plasma Shell occasionally crashes and restarts
But then, I'm not running a stock plasma, I have a few add-ons compiled from source and a few widgets downloaded from the get new things. One of those could be causing the crash but I haven't proved that yet. I'm fairly sure the panel is a plasma bug.
Edit: Oh and sorting pinned icons in the icons only taskbar is a real pain in wayland.
Edit 2: It seems the sorting has been fixed since I last did it ~~and I haven't had the crash since the last plasma update~~
You're messing with partitions which means there is the potential for data loss, be it hardware, human error, or a random cat. You should, if the data is important to you, have a backup.
Is it read only?
Why?
Let me put the question back to you. How do think the uniquely identifiable information will help them improve Manjaro?
Do you think they’ve got a Russian satellite and will track down your HDD serial number from space?
No.
There’s lots of benefits to telemetry.
As I basically said, if you bothered to read my comment.
They’ve let TLS certs expire on multiple occasions.
And they told their community to set their clocks back. As a workaround, it will work but all your created and modified data will have the wrong timestamps.
enable telemetry by default ... MAC addresses, disk serial numbers
Another reason to not use Manjaro. Just use Endeavour instead.
Edit: I'm not against telemetry pre se. I have the KDE feedback enabled for example but that was opt in and sends no unique data.
I hesitate to say
You can't fool me, they have another daemon for that
Update /etc/systemd/resolved.conf and add some DNS servers (in this example, 1.1.1.1 is CloudFlare, and 8.8.8.8 and 8.8.4.4 are Google but you can use your preferred DNS servers.)
[Resolve]
DNS=1.1.1.1 8.8.8.8
FallbackDNS=8.8.4.4
Restart system resolved:
service systemd-resolved restart
Run resolvectl status (or systemd-resolve --status in older versions of systemd) to see if the settings took.
If they don't take after a reboot, there's something else going on.
The lunatics are in charge of the asylum