I’m sorry for saying this, this may sound rude but I assure you, I have the best interests of Manjaro at heart. But the last two stable updates have caused quite many bugs that users have had to fix themselves. Now, I’d have not said anything if it was Arch or Gentoo, but this is Manjaro ‘stable’. It is supposed to update without users having to hack on config files and settings. Some people may bash me for being a noob (which I am) but these past two updates have not being a pleasant experience that I’ve come to associate with Manjaro.
I disagree. I agree that Manjaro should look for system breakage, and this is the case, we test update in Unstable branch, then Testing branch, then it goes to Stable branch. As most people don’t want to help testing packages, issues are expected because with a very limited number of users testing updates, obviously all the hardware and software combination can’t be tested.
Also you talk about issues many people had in the past two updates, the real question here is what kind of breakage, and why? often users are at fault because they just run Manjaro, expecting there is nothing to do besides clicking update button once in a while, usually without even reading their screen for errors or warnings. But you have things to look for in Manjaro (like the .pacnew files nobody check and merge when needed, or like the EOL kernels user still use, things like that).
I didn’t see what you picture in the last updates.
I was talking about this, this and this. Also, I was careful of not saying system breakage( although some users had that), I said bugs( related to DE and/or applications). These things should be taken care of by the distro maintainers and not by the stable users.
Isn’t this the whole point of marketing Manjaro as a beginner friendly distro? Otherwise why shouldn’t I just use Arch that comes with an installer nowadays?
OK a KDE splashscreen that changed, and people had to change it to the one they preferred, telegram application that had issues for some users on XFCE and quickly fixed afterwards, and yakuake which had a bug easily fixed.
I’d decide for myself, thanks. I love Manjaro, have made my friends come over too and would love for the future releases to be stable(er).
The misconception that rolling releases can’t be expected to be stable is seriously wrong and bad for Manjaro/Arch adoption.
I know, but my point is that these fixes should’ve been applied in testing, not stable. Anyways, thanks for replying.
Great. Switch to Testing or Unstable branch to help out testing the packages and update process.
That’s what’s going to help.
Yes, I’ve read these too. I do love the Manjaro community and this forum is the only one where people actually DO reply with actual help, instead of RTFM.
Would love to but I have only 1 machine( daily driver) that I cannot risk testing on. Sorry if I came across as whiny, I just wanted the betterment of this distro.
You can’t have your cake and eat it.
If everyone is expecting others to do the testing, you see the problem? Some issues can not be spotted before it hits the other 99.9% of Manjaro users on Stable branch (number out of my ass, but probably close to reality).
Another solution is to wait a couple days before updating your system as the few issues with packages will be quickly sorted.
Yeah, I understand, and I really plan to move to testing once I get a new machine. But till then this is the way I guess. Thanks!
The real answer is @Strit 's one and therefore I’ve marked that as an answer, but you can help yourself a lot by:
Keeping at least 2 LTS kernels on your system and boot the latest one unless you run into trouble there and then you boot the previous one…
pamac upgradefrom a command-line to upgrade.
grubis showing while booting:
sudo nano --backup /etc/default/grub
Change (or add?) the following 3 lines:
GRUB_TIMEOUT=3 #GRUB_HIDDEN_TIMEOUT=0 #GRUB_TIMEOUT_STYLE=hidden
(3 or higher is fine, add the # before the lines above if those lines are present)
Ctrl+X Y Enter to save if there is anything to save
If you did save, execute:
Read the #announcements
Read the list of modules/applications/libraries that are going to be updated before you press Y
/var/log/pacman.logafter updating and follow instructions (especially
And for heaven’s sake:
As a user of Manjaro since 2017, I still consider myself to be a “noob”, and I insist upon the fact that I’m not a contributer. I’m sorry to hear that you have encountered problems with the past few updates. As to “Stable” Branch being “press and forget” I would say “Yay” and “Nay” on that one. As I write I’m updating by the way, and I read the release announce and users comments prior to…it helps when you come across something niggly IMO. So, no blind faith, but measured assurance basically. The Wiki is a good idea as well, notwithstanding the Forum and its members - asked nicely you’ll always find some sort of help
of course you free to try. we’ll love to hear how that goes, if you are having issues with you entitlement here.
seriously, there is a reason why there are rolling release distros as opposed to point release distros. you cannot have same expectations from both. if you expect fire and forget “update” button, then you dont belong here, go install ubuntu
I haven’t had any major issues with Manjaro.I started out on the stable branch then switched to testing and now the unstable branch.I have learned to check the forum before doing and major updates to see if there are issues and if there are usually someone has already posted a fix.My main problem is when there’s an update like a new kernel or nvidia driver I have to have it now I can’t wait and yep sometimes I break something.Manjaro is a rolling release so there are times when something isn’t going to go right somewhere.So far and I don’t see it changing anytime soon I’m happy with Manjaro and all the work that goes into trying to please everyone all the time with any and every program driver and app we all expect to just work.
Messages are not in order they were initially.
I’ve been on testing for about 8 months and I’ve not had a single update that has made my machine unbootable/completely unusable. I’m not telling you to switch branches but it is not as perilous as you are making out.
There’s a script in the repos that makes a timeshift backup anytime you update. If you have an update that gives you issues you can easily restore a backup until its fixed.
In manjaros defence there are so many DE’s supported and such a plethora of different hardware its almost impossible for the team to catch every bug
why is that important?
If you know about
grub's Shift magic, it’s not…
If you have no clue what I’m talking about: That’s why!
care to explain?
i don’t know about
grub's Shift magic.
also what’s the difference between
sudo update grub and
sudo grub-mkconfig -o /boot/grub/grub.cfg ? or they’re not related?
This is the content of my /usr/bin/update-grub file:
#! /bin/sh set -e exec grub-mkconfig -o /boot/grub/grub.cfg "$@"