Hello, first time poster here. I have never had an issue updating to latest on Manjaro, which I’ve been loving for over 4 years. But with the latest update (yesterday), my Brave browser is no worky. Can’t render pages, or nav the web properly it seems. I went according to “downgrading packages manually” instrs according to Majaro wiki, ie. sudo pacman -U from /var/cache/pacman/pkg to prior package (which was working fine), but still no worky. Any ideas?
Thanks,
Tim
Yes. Several times. I did get a notice that Uxplay was available to update, so I did that. But nothing else.
Updating now!
Hello:
Manjaro gnome X11 kernel 5.15 this is my log error:
http://sprunge.us/nQeDlj
It is a new feature. Simply pay your monthly fees and it will go back to normal after that 
Hint: check trouble shoot post #2
2 Likes
Hi,
I had the same issue. Did you try this solution? This fixed the issue for me. I executed:
rm -rf ~/.config/BraveSoftware/Brave-Browser/ShaderCache/GPUCache ~/.config/BraveSoftware/Brave-Browser/Default/GPUCache ~/.config/BraveSoftware/Brave-Browser/GrShaderCache/GPUCache ~/.config/BraveSoftware/Brave-Browser/Guest Profile/GPUCache
1 Like
Very interesting. 
If you want, you could share you script… 
Hello,
After a lot of gnome crashes after this update.
I decided to update with the unstable version with
sudo pacman -U http://manjaro.ucom.am/unstable/extra/x86_64/gnome-shell-1:44.2-1-x86_64.pkg.tar.zst
And it seems the unstable version is more stable than the stable version.
Edit: Or maybe not
See FS#78723 - [gnome-shell] Sporadic coredumps since updating to gnome-shell 44.2
It’s possibly an upstream issue, but I can neither reproduce it on the Manjaro unstable branch nor Arch.
As Toolybird commented…
Only reply to the bug report if you can reproduce it on Arch.
jewimk,
Many Thanks! That did in fact fix my issue. Appreciate your time.
–tim
I donated the first time at this update was time to do that. I also donated to curl because I also contribute there some useful stuff
3 Likes
Yeah, I use btrfs to make a snapshot before upgrading; most people use Timeshift.
Didn’t think to mention it as “it goes without saying”.
I still wait a few days because restoring to the snapshot requires booting from a usb stick and i’m lazy.
FeeBSD has the best method: ZFS snapshots called “boot environments”; the boot loader allows you to choose one, so no need for a usb-stick-boot.
1 Like
IMO - when AUR support is enabled in pamac, then it’s pamac that is supposed to uninstall the colliding package.
If there is python upgrade, 3.10 → 3.11 - would it be such a big deal to just remove python311 automatically before the upgrade?
opensuse does same with btrfs snapshots created at system upgrade time.
1 Like
The upgrade automatically removes 3.10, which is from system repos –
system 3.10 to system 3.11.
Removing a conflicting AUR package
before doing a system upgrade does not exist.
AUR is not supported by Manjaro, and I have not seen an explanation for why ‘pamac’ goes against that policy. I guess it’s like: pamac does that for your convenience, but you still need to know what you’re doing and take responsibilty if it doesn’t work.
This year is unusual for Python in Arch Linux; it took a long time to get 3.11 ready.
Normally the new python appears in Arch/Manjaro soon enough
that few people (if any) bother to install it from AUR.
I’ve never agreed with that statement.
I think that whoever wrote it over-estimates the intellectual capacity of the people who read it. 
It might be true if you do only simple things,
such as only use a web browser and openoffice.
Installing a newer Python from AUR is not a simple thing.
Using Python at all is not simple, unless you only run an app that uses it,
but then you don’t know you’re running Python, and you don’t care what version it is.
1 Like
Yes, @cscs was trying to kindly tell you that people who demonstrate that they are capable of writing are generally also expected to be capable of reading, which just about every major update involving a number of gotchas proves not to be the case.
But then again, the people with an inability for reading do appear to be largely compensating for this with their sense of entitlement and ego manifestation, channeled through their positively acknowledged ability for writing — especially so when it involves a chance for them to be nasty.
When the exact same question is being asked well over a dozen times in the last 48 hours after the solution was posted to an issue people were yet to experience (because they hadn’t had a chance to update their systems yet), then copy/pasting is easier than having to type it all out by hand over and over again.
We are all volunteers here. Perhaps you could take an example after that instead of running your mouth off like you own this place, hmm?
xfs has xfs_copy for that purpose, and btrfs has the btrfs send and btrfs receive commands, so that would work too. I don’t know about F2FS, YAFFS/YAFFS2 et al, though.
4 Likes
And exactly for that reason Manjaro is suitable. Because a new to computers user never does things like that. And thus the system just keeps rolling. The problem lies with intermediate users, that think they know, use sudo liberally, copy paste random commands from internet, installiong random external repos, and wonder why things break.
Protecting against such is really hard without going the windows route of locking everything down.
5 Likes
Every time you think you’ve made something idiot-proof, the universe shows you that it can come up with a better idiot. 
4 Likes
I think it’s even worse. cscs was answering other user, not him. The other user just admitted he didn’t saw the troubleshooting message and thanked cscs. That was all… 
2 Likes
Ah well, the internet wouldn’t be what it is without a good flame war every now and then, I guess. 
1 Like
Updated my KDE/plasma Manjaro machine; did some basic stuff to see if things are still working.
So far so good.
Another boring update, I’m afraid.
4 Likes