#Random freezing on Manjaro, audio loops
14 messages · Page 1 of 1 (latest)
Reasons to not use Manjaro:
• https://github.com/arindas/manjarno
• https://www.hadet.dev/Manjaro-Bad
• https://rentry.co/manjaro-controversies
• https://manjarno.snorlax.sh
• https://averagelinuxuser.com/manjaro-review
#8745 📣 https://www.youtube.com/watch?v=5KNK3e9ScPo
I've for a long a long time suggested Manjaro Linux if you want to use Arch but don't want to deal with the out of box Arch Linux experience but they've made so many bad decisions I can no longer do so, just use a GUI Arch installer, Endeavour OS, Garuda or another Arch based distro that uses the Arch repos.
==========Support The Channel=======...
They already broke a system by releasing broken kernels
Always try with an LTS kernel as fallback
Well.. manjaro likes to do that so
#10894 📣 https://github.com/arindas/manjarno
https://www.hadet.dev/Manjaro-Bad
https://rentry.co/manjaro-controversies
https://manjarno.snorlax.sh/
https://averagelinuxuser.com/manjaro-review
Reasons for which I don't use Manjaro anymore. Contribute to arindas/manjarno development by creating an account on GitHub.
Manjaro markets itself as a new user friendly distribution. It attempts to cater to the the same demographic of users as Mint(a conversation for another time.) and Ubuntu. The Manjaro maintainers are however very bad at doing this at anything deeper than a surface level. This makes the concept fundamentally fall apart.
Anonymously-posted copy of another
Introduction
Manjaro is a Linux distribution based on the Arch Linux distribution. It focuses on accessibility, friendliness and stability.
However, there has been several major controversies regarding Manjaro over the years. This gist is aimed to address all kn...
Why you shouldn't use Manjaro
... journalctl
#10200 📣 ```js
To actively follow log (like tail -f):
journalctl -f
To display all errors since last boot:
journalctl -b -p err
To filter by time period:
journalctl --since=2012-10-15 --until="2011-10-16 23:59:59"
To show list of systemd units logged in journal:
journalctl -F _SYSTEMD_UNIT
To filter by specific unit:
journalctl -u dbus
To filter by executable name:
journalctl /usr/bin/dbus-daemon
To filter by PID:
journalctl _PID=123
To filter by Command, e.g., sshd:
journalctl _COMM=sshd
To filter by Command and time period:
journalctl _COMM=crond --since '10:00' --until '11:00'
To list all available boots:
journalctl --list-boots
To filter by specific User ID e.g., user id 1000:
journalctl _UID=1000
To filter by specific SYSLOG_INDENTIFIER:
journalctl -t systemd-resolved
tldr:journalctl
journalctl
Query the systemd journal.
More information: https://manned.org/journalctl.
Show all messages with priority level 3 (errors) from this [b]oot:
journalctl -b --priority=3
Show all messages from last [b]oot:
journalctl -b -1
Delete journal logs which are older than 2 days:
journalctl --vacuum-time=2d
[f]ollow new messages (like tail -f for traditional syslog):
journalctl -f
Show all messages by a specific [u]nit:
journalctl -u unit
Filter messages within a time range (either timestamp or placeholders like "yesterday"):
journalctl --since now|today|yesterday|tomorrow --until YYYY-MM-DD HH:MM:SS
Show all messages by a specific process:
journalctl _PID=pid
Show all messages by a specific executable:
journalctl path/to/executable
$```